Running back, Air Force, 2013–⁠14

Paco Solano

Hometown
Houston, TX

Paco Solano played running back at Air Force (2013–⁠14).

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2013Air Force12443.708
2014Air Force13584.5124
Career251024.1124

Season lines from CollegeFootballData, regular season and bowls.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2013Air Force12-0.12––-1.4–
2014Air Force9-0.06––-0.6–

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

2014 Air Force 5 games, 58 rushing yards, 1 TD
DateOpponentResultCarYdsTDLong
Aug 30vs.NichollsW 44–⁠16420111
Oct 11atUtah StateL 16–⁠34124024
Nov 8atUNLVW 48–⁠212403
Nov 28vs.Colorado StateW 27–⁠241606
Dec 20 ✦vs.Western MichiganW 38–⁠245403
2013 Air Force 3 games, 44 rushing yards
DateOpponentResultCarYdsTDLong
Sep 7vs.Utah StateL 20–⁠522806
Sep 21vs.WyomingL 23–⁠5651405
Oct 26vs.Notre DameL 10–⁠4552208

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.