Running back, Florida A&M (from Purdue), 2009–⁠13

Al-Terek McBurse

Number
No. 5
Height
6′0″
Hometown
Winter Springs, FL

Al-Terek McBurse played running back at Purdue (2009–⁠10) and Florida A&M (2011–⁠13).

Career highs

81rushing yards, career highvs. Western Illinois, 2010

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2009Purdue400.006
2010Purdue221898.6157
2011*Florida A&M5−1−0.203
2013Florida A&M4184.5010
Career352065.9157

Returns

SeasonTeamKRYdsTD
2009Purdue194681
2010Purdue214460
2011*Florida A&M3650
2013Florida A&M2390
Career451,0181

Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.

On the roster

SeasonTeamNo.PosHt
2009Purdue5RB
2010Purdue5RB
2011Florida A&M5RB
2012Florida A&M5RB
2013Florida A&M5RB6′0″

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.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2013Florida A&M (FCS)7-0.03––-0.2–

Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.

Game by game

2013 Florida A&M 1 game, 18 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 21atOhio StateL 0–⁠764180239

No box score in the source for Sep 1 vs. Mississippi Valley State; Sep 7 vs. Tennessee State; Sep 14 vs. Samford; Oct 5 at Morgan State; Oct 12 at Savannah State; Oct 19 vs. Howard; Oct 26 vs. North Carolina A&T; Nov 2 at Norfolk State; Nov 9 at South Carolina State; Nov 16 vs. Delaware State; Nov 23 at Bethune-Cookman, so those games are not listed.

2011 Florida A&M 1 game, −1 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 17atSouth FloridaL 17–⁠705−10365

No box score in the source for Sep 3 vs. Fort Valley State; Sep 8 at Hampton; Sep 24 vs. Southern; Oct 1 vs. Delaware State; Oct 8 vs. Howard; Oct 15 at Savannah State; Oct 22 at South Carolina State; Nov 5 vs. North Carolina A&T; Nov 12 at North Carolina Central; Nov 19 at Bethune-Cookman, so those games are not listed.

2010 Purdue 10 games, 189 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 4atNotre DameL 12–⁠234−20338
Sep 11vs.Western IllinoisW 31–⁠215811228
Oct 9atNorthwesternW 20–⁠17130––
Oct 16vs.MinnesotaW 28–⁠174110249
Oct 23atOhio StateL 0–⁠49–––357
Oct 30atIllinoisL 10–⁠442630128
Nov 6vs.WisconsinL 13–⁠3422405133
Nov 13vs.MichiganL 16–⁠27370254
Nov 20atMichigan StateL 31–⁠35120239
Nov 27vs.IndianaL 31–⁠34–––120
2009 Purdue 6 games, 19 returns, 468 yards
DateOpponentResultCarRush ydsRush TDKRYds
Oct 17vs.Ohio StateW 26–⁠18–––361
Oct 24vs.IllinoisW 24–⁠14160126
Oct 31atWisconsinL 0–⁠373−606141
Nov 7atMichiganW 38–⁠36–––483
Nov 14vs.Michigan StateL 37–⁠40–––238
Nov 21atIndianaW 38–⁠21–––3119

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.