BRUNSWICK — Hamilton’s Jeffrey Hopsicker threw a 41-yard touchdown pass to classmate Joe Jensen with 5:16 remaining in the fourth quarter to give the host 1-3 Continentals a 14-13 comeback win over 1-3 Bowdoin on Saturday.
Bowdoin was led by 84 yards from tailback Zach Donnarumma, who carried the ball 27 times. Quarterback Thomas Romero went 18- 35 for 206 yards and a touchdown while David Black led the Polar Bear receivers with five catches for 71 yards. Defensively, Tom Wells had nine tackles, including two for a loss, and a forced fumble for Bowdoin. Jon Fraser had nine tackles and an interception.
After a mostly scoreless opening period, Bowdoin used an impressive drive late in the first half to get on the scoreboard. Taking over at their own 18 with 5:15 to go, the Polar Bears converted on four third-downs, the last of which saw Romero toss a 33-yard touchdown strike to Ken Skon to give the visitors a 7-0 lead at halftime. The catch was the first of Skon’s collegiate career.
Hamilton answered with a five-play, 72-yard drive to open the third quarter, capped by a 26- yard strike from Jordan Eck to Simon Jia.
Bowdoin regained the lead early in the fourth quarter when Jimmy Garvey nailed a 31-yard field goal.
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