advertisement

Glenbard South runs by Fenton

With a conference championship hanging in the balance on senior night, Glenbard South took a giant step toward that goal Friday night in Glen Ellyn as the Raiders ran all over Fenton in a 40-8 Metro Suburban Conference victory.

Leading the charge as usual for Glenbard South (4-3, 3-0) was senior running back Wes Sanders, as the electric back went for 2 rushing and 1 receiving touchdown. Sanders had 127 all-purpose yards and 2 of his touchdowns came early, giving the Raiders a 20-0 lead.

"We started off in a no-huddle that we started to work on this week (in practice) and that was fun," Sanders said. "This was my last regular-season home game, and it was a great win and we want homefield for the playoffs. We plan on winning the conference championship next week. We just need to keep bringing the intensity."

Defensively, the Raiders bent without breaking, as five Fenton drives ended with interceptions. Every time the Bison appeared to have something going offensively, the Raiders defense came up with big plays. Aaron Kelly led the way in that department with 2 interceptions.

"We studied them all week in practice and we got in the zone and it was a great feeling," Kelly said. "The seniors have led so much throughout the season and we wanted to make tonight special for them and I'm sure they're all very proud to come out with a W."

Fenton (5-2, 0-2) had opportunities to claw back in the game, but untimely penalties and turnovers sealed the Bison's fate.

Fenton must right the ship quickly for a playoff push.

"We have two opportunities to clinch a playoff berth and to work on our seeding," Fenton coach Mark Kos said. "Please don't write any obituaries for Fenton because we are willing to fight until the end."

Article Comments
Guidelines: Keep it civil and on topic; no profanity, vulgarity, slurs or personal attacks. People who harass others or joke about tragedies will be blocked. If a comment violates these standards or our terms of service, click the "flag" link in the lower-right corner of the comment box. To find our more, read our FAQ.