TOPSHAM — Topsham police and rescue workers responded to a crash on Middlesex Road early Sunday night.
The crash was reported at 5:09 p.m. According to responding officer Sgt. Mark Gilliam’s report, a 1999 Kia driven by 20-year-old Tylor J. Weaver of 357 Middlesex Road, while traveling west on Middlesex Road, pulled to the right and started to turn left into the driveway at 357 Middlesex Road.
A 2002 Honda driven by Cody A. White was traveling west at the same time. White reportedly thought Weaver was pulling to the right side of the road. White attempted to pass Weaver and struck his car.
The impact damaged the left rear quarter panel of the Kia and front passenger quarter panel of the Honda. The Honda was towed from the scene.
According to Gilliam, the drivers offered conflicting reports as to whether Weaver had activated his turn signal, which he could not determine because the bulb shattered and filament was gone.
White complained of neck pain. Weaver complained of pain to his head and a passenger, 19-year-old Sarah J. Ruby, complained of back pain. Topsham Rescue transported two patients to Mid Coast Hospital in Brunswick.
A hospital spokesman said Monday that Weaver and Ruby were discharged Sunday from the emergency department in stable condition.
dmoore@timesrecord.com
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