Receiver, Navy, 2008–⁠12

Brandon Turner

Number
No. 86
Height
6′4″
Hometown
Renton, WA

Brandon Turner played receiver at Navy (2008–⁠12).

Career highs

2receiving touchdowns, career highvs. Florida Atlantic, 2012

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2010Navy411328.3163
2011Navy1430021.4359
2012Navy2232114.6449
Career4073418.4863

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009Navy86WR
2010Navy86WR
2011Navy86WR
2012Navy86WR6′4″

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 11 games, 22 catches, 321 yards, 4 TD
DateOpponentResultRecYdsTDLong
Sep 15atPenn StateL 7–⁠34230028
Sep 22vs.VMIW 41–⁠3335018
Sep 29vs.San José StateL 0–⁠12335012
Oct 6atAir ForceW 28–⁠211707
Oct 12atCentral MichiganW 31–⁠13242123
Oct 20vs.IndianaW 31–⁠30218011
Nov 3vs.Florida AtlanticW 24–⁠17245231
Nov 10atTroyL 31–⁠41339014
Nov 17vs.Texas StateW 21–⁠101−300
Dec 8vs.ArmyW 17–⁠13149049
Dec 29 ✦vs.Arizona StateL 28–⁠62224123
2011 Navy 8 games, 14 catches, 300 yards, 3 TD
DateOpponentResultRecYdsTDLong
Sep 3vs.DelawareW 40–⁠17229018
Sep 10atWestern KentuckyW 40–⁠14127127
Oct 1vs.Air ForceL 34–⁠35237026
Oct 8vs.Southern MissL 35–⁠63143143
Oct 15atRutgersL 20–⁠21120020
Oct 22vs.East CarolinaL 35–⁠38272159
Nov 5vs.TroyW 42–⁠14125025
Nov 19atSan José StateL 24–⁠27447029
2010 Navy 4 games, 4 catches, 113 yards, 1 TD
DateOpponentResultRecYdsTDLong
Sep 18atLouisiana TechW 37–⁠23163063
Oct 16vs.SMUW 28–⁠211909
Nov 6atEast CarolinaW 76–⁠351909
Dec 11vs.ArmyW 31–⁠17132132

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Before the draft

Played in the 2013 East–West Shrine Game (East team, lost 13–⁠28).

Rosters and honors: Wikipedia (CC BY-SA).

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.