Kicker, Navy, 2008–⁠11

Jon Teague

Number
No. 45
Height
6′3″
Hometown
Hickory, NC

Jon Teague played kicker at Navy (2008–⁠11).

Kicking

Field goals made, season by season, with his team’s record
SeasonTeamFGMFGAPctLongXPPts
2009Navy1250.03158
2010Navy22100.0381622
2011Navy101376.9544272
Career131776.55463102

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
2008N13325
200914415
201112101
On file8311

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2009Navy45PK
2010Navy45PK
2011Navy45PK6′3″

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

2011 Navy 12 games, 10 of 13 field goals
DateOpponentResultFGMFGALongXPPts
Sep 3vs.DelawareW 40–⁠172254410
Sep 10atWestern KentuckyW 40–⁠1400044
Sep 17atSouth CarolinaL 21–⁠2400033
Oct 1vs.Air ForceL 34–⁠35233728
Oct 8vs.Southern MissL 35–⁠6300055
Oct 15atRutgersL 20–⁠21234128
Oct 22vs.East CarolinaL 35–⁠3800055
Oct 29atNotre DameL 14–⁠5601022
Nov 5vs.TroyW 42–⁠1400066
Nov 12atSMUW 24–⁠17113936
Nov 19atSan José StateL 24–⁠27112436
Dec 10vs.ArmyW 27–⁠21224439
2010 Navy 3 games, 2 of 2 field goals
DateOpponentResultFGMFGALongXPPts
Oct 23vs.Notre DameW 35–⁠1700055
Oct 30vs.DukeL 31–⁠3400011
Nov 6atEast CarolinaW 76–⁠3522381016
2009 Navy 1 game, 1 of 2 field goals
DateOpponentResultFGMFGALongXPPts
Sep 26vs.Western KentuckyW 38–⁠22123158

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.