Linebacker, Air Force, 2014–16
Patrick Healy
- Number
- No. 41
- Height
- 6′1″
- Hometown
- Castle Rock, CO
Patrick Healy played linebacker at Air Force (2014–16).
Career highs
8tackles, career hightwice; last at Fresno State, 2016Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2016 | Air Force | 33 | 18 | 4 | 0.5 | 1 | 3 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2014 | 12 of 13 | 1 | 4 | 5 |
| 2015 | 10 of 14 | 12 | 15 | 27 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.
On the roster
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
2016 Air Force 9 games, 33 tackles, 0.5 sacks, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Oct 8 | at Wyoming | L 26–35 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 15 | vs. New Mexico | L 40–45 | 3 | 3 | 1 | 0 | 0 | 0 |
| Oct 22 | vs. Hawai’i | L 27–34 | 8 | 3 | 1.5 | 0 | 0 | 1 |
| Oct 28 | at Fresno State | W 31–21 | 8 | 5 | 1 | 0 | 1 | 1 |
| Nov 5 | at Army | W 31–12 | 1 | 0 | 0 | 0 | 0 | 0 |
| Nov 12 | vs. Colorado State | W 49–46 | 3 | 1 | 0 | 0 | 0 | 0 |
| Nov 19 | at San José State | W 41–38 | 4 | 3 | 0.5 | 0.5 | 0 | 0 |
| Nov 25 | vs. Boise State | W 27–20 | 3 | 1 | 0 | 0 | 0 | 0 |
| Dec 30 ✦ | vs. South Alabama | W 45–21 | 2 | 1 | 0 | 0 | 0 | 1 |
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.