Gamecocks lose to Kentucky 16-10 in defensive showdown

Watch WIS News 10 at 11 p.m. every Saturday.
Published: Sep. 25, 2021 at 8:31 PM EDT
Email This Link
Share on Pinterest
Share on LinkedIn

COLUMBIA, S.C. (WIS) - The Gamecocks took on the Kentucky Wildcats at home on a beautiful September evening at Williams Brice Stadium.

The Gamecocks, fresh off their first loss of the season to a rolling Georgia Bulldogs team, looked to bounce back.

The Wildcats opened the game with an impressive 12-play, 75-yard drive -- that drive ended in a Kavosiey Smoke 15-yard touchdown run. The Wildcats went up early 7-0.

Since Kentucky’s first touchdown, both defenses stepped up.

Most notably, in the second quarter, Gamecock defensive back Jaylan Foster intercepted a deep ball by Will Levis on the 1-yard line.

Kentucky booted a field goal at the end of the half, putting them up 10-0.

Much like Wildcats started the game, the Gamecocks mimicked that drive to open the half. On a 10-play, 75-yard drive -- the Gamecocks punched in their first score of the game on a Luke Doty pass to Jalen Brooks for a 5-yard touchdown. The Gamecocks finally began to close the gap at 7-10.

Kentucky marched down the field on their next drive, but the Gamecock defense would hold strong near the goal line, forcing the Wildcats to settle for a field goal.

The name of the game... defense.

In the fourth quarter, the Gamecocks forced yet another turnover near the 50-yard line. However, they could not capitalize, failing on a fourth down, putting them at 0-3 on fourth down for the game.

The Wildcats drove down the field and converted on yet another field goal, putting them up 16-7 with about 5 minutes remaining.

Gamecock kicker Parker White nailed a 54-yard field goal to keep life for the Gamecocks with about 2 minutes in the game. 16-10, Wildcats.

Kentucky gave the Gamecocks no life after the score, milking the clock all the way down to triple zeros. Kentucky would win with a final of 16-10.

Copyright 2021 WIS. All rights reserved.

Notice a spelling or grammar error in this article? Click or tap here to report it. Please include the article’s headline.