After failing to stop at an intersection, the firefighter collided with two poles; no pedestrians were injured.
In a statement released by Toronto Police, they say that the fire truck was travelling north on Mount Pleasant Road on Sunday April 4th at 2:06PM, en route to an emergency situation. The driver of the fire truck then appeared not to notice that traffic was stopped at the Lawrence Avenue East intersection up ahead.
According to The Toronto Star, investigators say the fire truck, which had its lights and sirens on, allegedly "did not stop before turning right to go east in the westbound lanes of Lawrence Avenue" causing it to collide with two poles.
No pedestrians were hurt, however the firefighter was taken to the hospital with minor injuries. He has since been charged with 'careless driving' and 'making an unsafe turn' under Ontario's Highway Traffic Act, reports The Star.
0423 13:00 Chgs Laid Agnst To. Firefighter In Pi Colisn, Lawrence Av...unt Pleasant Rd https://t.co/xdXHwAFyWi
— Toronto Police (@TorontoPolice) April 23, 2021
The firefighter's name has not been disclosed as Toronto Police only publicly identifies people charged under the Criminal Code of Canada, not the provincial Highway Traffic Act.
In their statement on Friday, Toronto Police announced that Traffic Services has completed their investigation, and that the firefighter is set to appear at “C Court” in Old City Hall" at 1:30pm on June 3rd.
Join and support independent free thinkers!
We’re independent and can’t be cancelled. The establishment media is increasingly dedicated to divisive cancel culture, corporate wokeism, and political correctness, all while covering up corruption from the corridors of power. The need for fact-based journalism and thoughtful analysis has never been greater. When you support The Post Millennial, you support freedom of the press at a time when it's under direct attack. Join the ranks of independent, free thinkers by supporting us today for as little as $1.
Remind me next month
To find out what personal data we collect and how we use it, please visit our Privacy Policy
