EDITOR'S NOTE: We received this press release late last night. We didn't publish it because of the error in the report. We responded to their email asking for a correction and so far have not received one. Here is the press release just as it was sent. See if you can find the error.
No fatality was listed despite the heading that says it was a fatal accident.
ReplyDeleteIt was not a fatality.
ReplyDeleteIt says fatal collision but they were treated and released. Hmmmmm
ReplyDeleteWTH, a fatal MVC yet all victims were treated & released. That sure says something about the investigative process of this collision!!!!
ReplyDeleteI hope people where LAUGHING and making fun of the Troopers like they did to that poor young man with the boat who then HUNG HIMSELF ?????????..POS
ReplyDeleteI agree 💯
DeleteOnly thing I see is that Main doesn't intersect with 50 it becomes Quantico Rd.
ReplyDeleteYears ago I worked at the West OC food lion. I was outside on break and happened to see a truck trying to make a u-turn at 611 and 50 to head back toward OC. It was late at night and dark out. A cop car with no flashers on came up eastbound doing every bit of 90mph in this 40 or 45 zone and plowed right into the side of the truck. They arrested the truck driver for DUI. I'm sure the report said "speed was not a factor"
It says fatal but all occupants were treated and released
ReplyDeleteFatal??
ReplyDeleteNot a fatal...
ReplyDeleteIono, the hospital could've treated and released a dead person. After all, it is PRMC!
ReplyDeleteLt. Davala...this is not the first press release that your barrack has sent out with glaring errors. Spelling, grammatical and factual errors are found in almost everything published by the barrack. Are duty officers failing to proof read press releases? It is an embarrassment and reflects poorly on MSP. Please ensure press releases are proof read before sending them out for public consumption.
ReplyDeleteSomeone doesn't know what fatal means.
DeleteWho thinks PRMC is so good they can bring the dead back to life?
ReplyDeleteI seen it was 2 cops and made a U Turn.
ReplyDeleteSo maybe someone at the sheriff's office doesn't know what there posting ? Just like how first Alert said ???.. just asking.
ReplyDeleteFatal
ReplyDeleteThey are just copying and pasting previous releases
Troopers excessive speed and failure to control is the cause here.
ReplyDeleteWhen they unlawfully approach intersections at 85 to 90 miles per hour in camouflage vehicles as they all do daily in violation of established traffic ordinances, they overcome the crossing exponentially giving the other vehicle less time to accelerate across when they think they have plenty of time. Unmarked or unlighted emergency Vehicles careening down the road carrying that excessive speed get to the intersection much quicker than law abiding vehicles operated at normal lawful marked speeds of 55 to 65 miles per hour. The unlawful speeding troopers create a false visual anomaly of safe crossing and causes collisions as they close on the crossing vehicle at exorbitant speeds.
Troopers think they can do no wrong and can handle their vehicles but prove regularly they can’t. They break the law multiple times daily every time they get behind the wheel.. This is just another example of damage done and blame placed on an innocent civilian when the Government, pompous machismo attitudes and its training are at fault.
2 State Troopers and excessive speed wasn't a factor? They were driving 55?
ReplyDeleteI seen a Asian state trooper 5'2
ReplyDelete1:28 is probably spot on. I've never seen a MSP trooper driving less than 15-20 MPHs over the speed limit.
ReplyDeleteI once witnessed, and was first on the scene, a very similar accident near Wachapreague, same age of driver who crossed into the path of a trooper who had to be going 80+. She was charged with failure to yield the right of way, completely ignoring my eyewitness statement.
Cops are NEVER at fault, are they? Plus, they drive without daytime running lights on 90 and 50 when the rest of us have to have them on. WTF?