Defensive back, Air Force, 2015–16
Jesse Washington
- Number
- No. 21
- Height
- 6′0″
- Hometown
- Friendswood, TX
Jesse Washington played defensive back at Air Force (2015–16).
Career highs
8tackles, career highat Utah State, 2016Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2016 | Air Force | 51 | 31 | 2 | 0 | 2 | 11 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2015 | 10 of 14 | 17 | 7 | 24 |
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 12 games, 51 tackles, 2 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | W 37–21 | 5 | 3 | 1 | 0 | 0 | 0 |
| Sep 10 | vs. | W 48–14 | 0 | 0 | 0 | 0 | 0 | 1 |
| Sep 24 | at | W 27–20 | 8 | 2 | 0 | 0 | 0 | 2 |
| Oct 1 | vs. | W 28–14 | 4 | 2 | 0 | 0 | 0 | 0 |
| Oct 8 | at | L 26–35 | 5 | 4 | 1 | 0 | 0 | 0 |
| Oct 15 | vs. | L 40–45 | 7 | 6 | 0 | 0 | 0 | 2 |
| Oct 22 | vs. | L 27–34 | 3 | 2 | 0 | 0 | 1 | 1 |
| Nov 5 | at | W 31–12 | 3 | 3 | 0 | 0 | 0 | 4 |
| Nov 12 | vs. | W 49–46 | 4 | 1 | 0 | 0 | 1 | 0 |
| Nov 19 | at | W 41–38 | 5 | 3 | 0 | 0 | 0 | 0 |
| Nov 25 | vs. | W 27–20 | 4 | 2 | 0 | 0 | 0 | 0 |
| Dec 30 ✦ | vs. | W 45–21 | 3 | 3 | 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.
