Cazenovia beats Oneida for Class B football championship

Early in the second quarter, the Indians struck back. It moved to the Lakers' 35, then on third-down-and-five Barlow barreled through a hole on the left side of the line and went untouched to the end zone. Oneida then faked the PAT as Matt Mosack, the holder, ran and fumbled near the goal line - only to have lineman Travis Morrison recover it for two points.

Now trailing 8-7, Cazenovia went back to a huddle - and moved right back down the field. A key completion to Tanner Whiteman and effective runs from Greacen and Hopsicker moved the Lakers inside the 20, but on third down Hopsicker threw into traffic - and Kyle Armstrong picked it off at the Indians' 12-yard line, the Lakers' first turnover.

This changed the field position, for though the sides exchanged punts, Hopsicker pinned a quick kick on Oneida's one-yard line late in the half. But (unlike Marcellus the week before) Barlow used a 10-yard run to escape danger, and the Indians carried that slim 8-7 lead into the break.

So Cazenovia was behind, just as in the first meeting (it was 8-3 back then), and now it had to make a second comeback, even if it was of the modest variety. Of course, the circumstances were anything but modest - and the way the Lakers answered the challenge was far from subtle.

Taking the second-half kickoff, Hopsicker quickly moved his team 65 yards, with key completions to Judge and Ben Romagnoli, plus some timely running from Greacen, during the march. From the two-yard-line on third-down-and-goal, the 5-5, 135-pound Wells leaped over the Indian defenders into the end zone, and the Lakers were back in front 14-8.

Jimmy Moyer promptly returned the ensuing kickoff 42 yards into Laker territory, giving Oneida a short field, and it quickly moved toward the Cazenovia goal line. But once again, Mimms made a big defensive play, sacking Mosack on third down back at the 35 and forcing a turnover on downs.

Vote on this Story by clicking on the Icon


Use the comment form below to begin a discussion about this content.

Sign in to comment