Kentucky beats No. 10 LSU in overtime on Minchey conversion
Summarised from 2 outlets · Updated 11 Oct, 04:49 · Archive
Kentucky defeated tenth-ranked LSU 35-34 in overtime when quarterback Kenneth Minchey ran for a two-point conversion.
Kentucky defeated tenth-ranked LSU 35-34 in overtime on Saturday night in Lexington. Minchey ran untouched for the winning two-point conversion after running back C.J. Baxter scored on a one-yard run. LSU had scored first in overtime when quarterback Sam Leavitt ran 15 yards for a touchdown, but Kentucky forced the extra period when kicker Adam Zouagui made a 33-yard field goal with 12 seconds left in regulation after missing two earlier attempts.
Minchey completed 23 of 36 passes for 246 yards, including 206 in the second half. Baxter rushed for 123 yards and two touchdowns, 77 of those yards coming on Kentucky's opening play. Freshman receiver Kenneth Darby, who had originally committed to LSU, caught four passes for 79 yards including a crucial 22-yard reception in overtime that set up the winning play.
Leavitt was 25 of 34 passing for 275 yards and two touchdowns but also threw an interception and fumbled. LSU's defence, which had been allowing 220.6 yards per game and ranked third nationally, gave up 401 yards against Kentucky.
How it is being reported
- Kentucky QB Minchey scores 2-point conversion in overtime to beat No. 10 LSU 35-34Kentucky quarterback Kenneth Minchey ran untouched for a 2-point conversion, lifting his team to a 35-34 overtime victory over No. 10 LSU.Clickorlando · 11 Oct, 04:29
- Kentucky QB Minchey scores 2-point conversion in overtime to beat No. 10 LSU 35-34Kentucky quarterback Kenneth Minchey ran untouched for a 2-point conversion, lifting his team to a 35-34 overtime victory over No. 10 LSU.News4Jax · 11 Oct, 04:29
In this story: Kentucky · LSU · Kenneth Minchey · C.J. Baxter · Sam Leavitt · Kenneth Darby · Lexington
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem
Comments (0)