Running back, Air Force, 2023–⁠25

Dylan Carson

Number
No. 5
Height
6′0″
Weight
215 lb
Class (2025)
Senior
Hometown
Marysville, WA

Dylan Carson played running back at Air Force (2023–⁠25).

Career highs

132rushing yards, career highat Boise State, 20232rushing touchdowns, career hightwice; last at UConn, 2025

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2023Air Force684937.3268
2024Air Force1386004.3550
2025Air Force914194.6464
Career2971,5125.11168

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Air Force5RBSo.
2024Air Force5RBJr.
2025Air Force5RBSr.6′0″215

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/playPctileMedianTotalUsageAdj. rush
2023Air Force680.2677th (n=450)0.1717.912%0.17
2024Air Force1360.0928th (n=434)0.1611.920%0.13
2025Air Force900.1050th (n=576)0.109.311%0.12

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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2025Air Force43%3.200.601.0010%

Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.

Game by game

2025 Air Force 12 games, 419 rushing yards, 4 TD
DateOpponentResultCarYdsTDLong
Aug 30vs.BucknellW 49–⁠131152117
Sep 13atUtah StateL 30–⁠49853017
Sep 20vs.Boise StateL 37–⁠4916109164
Sep 27vs.Hawai’iL 35–⁠4451106
Oct 4atNavyL 31–⁠3492406
Oct 11atUNLVL 48–⁠513904
Oct 18vs.WyomingW 24–⁠21431023
Nov 1vs.ArmyL 17–⁠201404
Nov 8atSan José StateW 26–⁠16113108
Nov 15atUConnL 16–⁠261158214
Nov 22vs.New MexicoL 3–⁠2061907
Nov 28atColorado StateW 42–⁠2161804
2024 Air Force 10 games, 600 rushing yards, 5 TD
DateOpponentResultCarYdsTDLong
Aug 31vs.MerrimackW 21–⁠671404
Sep 28atWyomingL 19–⁠31733015
Oct 5vs.NavyL 7–⁠3461306
Oct 12atNew MexicoL 37–⁠5252107
Oct 19vs.Colorado StateL 13–⁠211260021
Nov 2atArmyL 3–⁠2041205
Nov 9vs.Fresno StateW 36–⁠2833120112
Nov 16vs.Oregon StateW 28–⁠0269718
Nov 23atNevadaW 22–⁠1914105150
Nov 30atSan Diego StateW 31–⁠2024125217
2023 Air Force 10 games, 493 rushing yards, 2 TD
DateOpponentResultCarYdsTDLong
Sep 2vs.Robert MorrisW 42–⁠7550029
Sep 9vs.Sam HoustonW 13–⁠331507
Sep 15vs.Utah StateW 39–⁠211101
Sep 22atSan José StateW 45–⁠201163014
Sep 30vs.San Diego StateW 49–⁠10527010
Oct 21atNavyW 17–⁠6––––
Nov 11atHawai’iL 13–⁠271387135
Nov 18vs.UNLVL 27–⁠3116104023
Nov 24atBoise StateL 19–⁠2712132168
Dec 23 ✦vs.James MadisonW 31–⁠2121409

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.