A car sank into Sebago Lake on Saturday morning after a Portland man drove off an unoccupied ferry dock and into the water, officials said.
Cumberland County sheriff’s deputies and first responders from Raymond were called to the mainland side of the Frye Island Ferry Landing around 8:45 a.m. Saturday, according to a news release from Capt. Kerry Joyce of the Cumberland County Sheriff’s Office.
The driver, identified as a 73-year-old Portland man, reportedly drove off the vacant pier — no ferry was docked at the time — and into Sebago Lake, where the car sank into the 8-foot-deep water, Joyce said.
The man was able to escape the car, and good Samaritans helped him out of the water, Joyce said. No injuries were reported, but the man was taken to Maine Medical Center in Portland “as a precautionary measure,” Joyce added.
The cause of the crash is under investigation, Joyce said.
Ferry service to and from Frye Island was briefly interrupted by the incident but has since resumed as normal. Joyce said removal of the submerged car may cause further delays over the weekend.
Officials notified the Maine Environmental Protection Agency of the incident because of the potential that the water could be contaminated.
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