RICHMOND
A low clearance train trestle on Route 24 in Richmond was hit again Thursday afternoon.
This time a small Hyundai excavator being hauled on a trailer, struck the bridge and was pushed over backwards. In the process, the boom was pushed into the machine’s cab. The town of Richmond used a front end bucket loader to right the excavator and drag it up Route 24 (River Road) to Old Ferry Road, down Route 197 and back to the Route 24 and 197 junction where it awaited removal.
The crash happened at around 3 p.m., closing the portion of Route 24 until about 5 p.m.
The truck hauling the excavator was driven by Richmond contractor Joshua Watson, 38. He was traveling north to a job when the crash occurred, said Richmond Police Sgt. Doug Bellevue.
No one was injured and no charges were issued. Bellevue said Watson had only bought the excavator two months ago.
Bridge engineers responded from the Maine Department of Transportation and a front end bucket loader was used to pushed the bridge back in place. Some repairs will need to be made to the bridge and tracks, which public safety officials on scene said aren’t used.
The low-clearance train trestle is often hit by several trucks towing trailers, materials or equipment over the years.
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