TOPSHAM
Topsham police have released the names of the drivers involved in a four-vehicle crash on Route 196 Wednesday afternoon.
The crash was reported at 2:58 p.m. on Route 196 at the intersection of the Interstate 295 on ramp.
A black 2012 Toyota driven by Shaun Fraser, 21, of 17 Wadsworth Road, Brunswick, was traveling west on Route 196 at a high rate of speed, according to police, and drove over the island into the eastbound lane and turned to head back over the island. At this point he struck a white 2007 Lexus on the driver’s side door driven by 74-yearold Richard Sullivan of Savannah, Ga.; and then struck a silver 2007 Honda driven by Sean Corbett, 32, of Portland, in the rear. After striking the Honda, the car operated by Fraser flipped into the air, spun around and struck the Honda again on the side — causing the Honda to strike the rear of a blue 2006 Subaru driven by 57- year-old Audrey Findlen of Pownal. The Toyota then flipped in the air and landed on the roof.
Fraser was transported to Parkview Adventist Medical Center in Brunswick, according to Topsham Police Chief Christopher Lewis. A female passenger in the car with Fraser, 20-year-old Nichole Hachey, was not transported.
Fraser was arrested and charged with operating after suspension and driving to endanger.
Comments are not available on this story. Read more about why we allow commenting on some stories and not on others.
We believe it's important to offer commenting on certain stories as a benefit to our readers. At its best, our comments sections can be a productive platform for readers to engage with our journalism, offer thoughts on coverage and issues, and drive conversation in a respectful, solutions-based way. It's a form of open discourse that can be useful to our community, public officials, journalists and others.
We do not enable comments on everything — exceptions include most crime stories, and coverage involving personal tragedy or sensitive issues that invite personal attacks instead of thoughtful discussion.
You can read more here about our commenting policy and terms of use. More information is also found on our FAQs.
Show less