Safety, Navy, 2015–18
Juan Hailey
- Number
- No. 13
- Height
- 6′1″
- Weight
- 199 lb
- Class (2018)
- Senior
- Hometown
- Louisville, KY
Juan Hailey played safety at Navy (2015–18).
At a glance
Career highs
13tackles, career highvs. Army, 2018Defense
Season lines from CollegeFootballData, regular season and bowls.
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
2018 Navy 11 games, 66 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | at Hawai’i | L 41–59 | 5 | 4 | 0 | 0 | 0 |
| Sep 8 | vs. Memphis | W 22–21 | 4 | 3 | 0 | 0 | 0 |
| Sep 15 | vs. Lehigh | W 51–21 | 1 | 1 | 0 | 0 | 1 |
| Sep 22 | at SMU | L 30–31 | 6 | 3 | 0 | 0 | 0 |
| Oct 20 | vs. Houston | L 36–49 | 5 | 3 | 0 | 0 | 0 |
| Oct 27 | vs. Notre Dame | L 22–44 | 3 | 2 | 0 | 0 | 0 |
| Nov 3 | at Cincinnati | L 0–42 | 8 | 5 | 0 | 0 | 0 |
| Nov 10 | at UCF | L 24–35 | 10 | 7 | 0 | 0 | 0 |
| Nov 17 | vs. Tulsa | W 37–29 | 7 | 5 | 0.5 | 0 | 1 |
| Nov 24 | at Tulane | L 28–29 | 4 | 3 | 0 | 0 | 0 |
| Dec 8 | vs. Army | L 10–17 | 13 | 7 | 0.5 | 0 | 0 |
2017 Navy 8 games, 25 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 23 | vs.Cincinnati | W 42–32 | 2 | 2 | 0 | 0 | 0 |
| Sep 30 | atTulsa | W 31–21 | 3 | 1 | 0 | 0 | 0 |
| Oct 7 | vs. Air Force | W 48–45 | 4 | 3 | 0 | 0 | 0 |
| Oct 14 | atMemphis | L 27–30 | 3 | 3 | 0 | 0 | 1 |
| Nov 2 | at Temple | L 26–34 | 2 | 2 | 0 | 0 | 0 |
| Nov 11 | vs.SMU | W 43–40 | 4 | 3 | 0 | 0 | 0 |
| Nov 18 | atNotre Dame | L 17–24 | 6 | 4 | 0 | 0 | 0 |
| Dec 28 ✦ | vs. Virginia | W 49–7 | 1 | 1 | 0 | 0 | 0 |
2016 Navy 2 games, 3 tackles
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.