Navy, 2009–⁠12

John Howell

Number
No. 33
Height
5′8″
Hometown
Hatfield, PA

John Howell played at Navy (2009–⁠12).

Career highs

113rushing yards, career highat Western Kentucky, 20112rushing touchdowns, career highat Western Kentucky, 2011

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2010Navy151026.8215
2011Navy353409.7557
2012Navy66010.0019
Career565029.0757

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009Navy33
2010Navy33
2011Navy33
2012Navy335′8″

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

2012 Navy 3 games, 60 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1vs.Notre DameL 10–⁠50140419
Sep 15atPenn StateL 7–⁠34437017––
Sep 29vs.San José StateL 0–⁠12119019––
2011 Navy 12 games, 340 rushing yards, 5 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3vs.DelawareW 40–⁠1721309––
Sep 10atWestern KentuckyW 40–⁠143113257––
Sep 17atSouth CarolinaL 21–⁠24432127––
Oct 1vs.Air ForceL 34–⁠35150515
Oct 8vs.Southern MissL 35–⁠6376612519
Oct 15atRutgersL 20–⁠21––––140
Oct 22vs.East CarolinaL 35–⁠38749011––
Oct 29atNotre DameL 14–⁠56222015––
Nov 5vs.TroyW 42–⁠1431507142
Nov 12atSMUW 24–⁠17315111––
Nov 19atSan José StateL 24–⁠272604––
Dec 10vs.ArmyW 27–⁠211404––
2010 Navy 10 games, 102 rushing yards, 2 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 6vs.MarylandL 14–⁠17113013––
Sep 18atLouisiana TechW 37–⁠231808125
Oct 16vs.SMUW 28–⁠211606––
Oct 23vs.Notre DameW 35–⁠171606––
Oct 30vs.DukeL 31–⁠341−100––
Nov 6atEast CarolinaW 76–⁠35226015––
Nov 13vs.Central MichiganW 38–⁠3721519––
Nov 20vs.Arkansas StateW 35–⁠1924112––
Dec 11vs.ArmyW 31–⁠17––––177
Dec 23 ✦vs.San Diego StateL 14–⁠3542509––

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.