Defensive line, Louisville, 2016–19
Gary McCrae
- Number
- No. 93
- Height
- 6′4″
- Weight
- 238 lb
- Class (2019)
- Senior
- Hometown
- Cuthbert, GA
Gary McCrae played defensive line at Louisville (2016–19).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2017 | Louisville | 4 | 3 | 0 | 0 | 0 | 0 |
| 2019 | Louisville | 10 | 7 | 0 | 0 | 0 | 0 |
| Career | 14 | 10 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2016 | Louisville | 93 | DL | Fr. | ||
| 2017 | Louisville | 93 | DL | So. | ||
| 2018 | Louisville | 93 | DL | Jr. | ||
| 2019 | Louisville | 93 | DL | Sr. | 6′4″ | 238 |
As each season’s roster listed the player (CollegeFootballData). Classes before the latest listing are counted back from it; “Yr 1” is the year on file where that count can’t place a season he played (a redshirt, transfer or 2020 year); height and weight as last listed.
Game by game
2019 Louisville 8 games, 10 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 7 | vs. Eastern Kentucky | W 42–0 | 1 | 1 | 0 | 0 | 0 |
| Sep 14 | vs. Western Kentucky | W 38–21 | 1 | 0 | 0 | 0 | 0 |
| Oct 5 | vs. Boston College | W 41–39 | 2 | 2 | 0 | 0 | 0 |
| Oct 19 | vs. Clemson | L 10–45 | 1 | 0 | 0 | 0 | 0 |
| Nov 9 | at Miami | L 27–52 | 1 | 1 | 0 | 0 | 0 |
| Nov 16 | at NC State | W 34–20 | 2 | 2 | 0 | 0 | 0 |
| Nov 23 | vs. Syracuse | W 56–34 | 1 | 0 | 0 | 0 | 0 |
| Dec 30 ✦ | vs. Mississippi State | W 38–28 | 1 | 1 | 0 | 0 | 0 |
2017 Louisville 3 games, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Nov 18 | vs.Syracuse | W 56–10 | 1 | 0 | 0 | 0 | 0 |
| Nov 25 | at Kentucky | W 44–17 | 2 | 2 | 0 | 0 | 0 |
| Dec 30 ✦ | vs.Mississippi State | L 27–31 | 1 | 1 | 0 | 0 | 0 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Is this you, or do you know of something wrong or missing here? Suggest a correction. We check each one against a source before changing the page.