Quarterback, McNeese (from Kansas State), 2011–⁠14

Daniel Sams

Lettered 2012–⁠13 at Kansas State (school media guide)

Number
No. 4
Height
6′2″
Hometown
Slidell, LA

Daniel Sams played quarterback at Kansas State (2011–⁠13) and McNeese (2014).

At a glance

Best season
452
Passing yards, 2013 (Kansas State, 8–⁠5)
Best game
199 yards
Vs. Baylor, week 7, 2013: No. 2 rushing game in FBS that week

Career highs

181passing yards, career highat Oklahoma State, 2013199rushing yards, career highvs. Baylor, 20133rushing touchdowns, career highvs. Baylor, 2013

Team titles: Big 12 champions, 2012

Passing

Passing yards, season by season, with his team’s record
SeasonTeamCmpAttPctYdsY/ATDInt
2012Kansas State6875.0556.900
2013Kansas State385371.74528.544
2014McNeese3933.3596.600
Career477067.15668.144

Rushing

SeasonTeamCarYdsAvgTDLong
2012Kansas State322357.3346
2013Kansas State1528075.31137
2014McNeese10747.4026
Career1941,1165.81446

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2011Kansas State4QB
2012Kansas State4QB
2013Kansas State4QB
2014McNeese4QB6′2″

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
2013Kansas State1870.2250th (n=144)0.2240.525%0.12
2014McNeese (FCS)190.34––6.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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Game by game

2014 McNeese 1 game, 59 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Sep 6atNebraskaL 24–⁠3139590074

No box score in the source for Sep 13 vs. Prairie View A&M; Sep 27 vs. Arkansas Tech; Oct 4 vs. Nicholls; Oct 11 at Sam Houston; Oct 18 vs. Abilene Christian; Oct 25 at Incarnate Word; Nov 1 at Northwestern State; Nov 9 vs. Stephen F. Austin; Nov 15 at SE Louisiana; Nov 22 vs. Lamar, so those games are not listed.

2013 Kansas State 13 games, 452 passing yards, 4 TD; 807 rushing yards, 11 TD
DateOpponentResultCmpAttYdsTDIntRush
Aug 30vs.North Dakota StateL 21–⁠24–––––17
Sep 7vs.LouisianaW 48–⁠2712270063
Sep 14vs.MassachusettsW 37–⁠722120077
Sep 21atTexasL 21–⁠31–––––48
Oct 5atOklahoma StateL 29–⁠33152118123118
Oct 12vs.BaylorL 25–⁠35474101199
Oct 26vs.West VirginiaW 35–⁠1288931016
Nov 2vs.Iowa StateW 41–⁠745641056
Nov 9atTexas TechW 49–⁠2612110081
Nov 16vs.TCUW 33–⁠31352300109
Nov 23vs.OklahomaL 31–⁠41–––––7
Nov 30atKansasW 31–⁠10–––––−7
Dec 28 ✦vs.MichiganW 31–⁠140100023
2012 Kansas State 7 games, 235 rushing yards, 3 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 1vs.Missouri StateW 51–⁠9–––––61
Sep 8vs.MiamiW 52–⁠13–––––47
Sep 15vs.North TexasW 35–⁠21–––––19
Oct 6vs.KansasW 56–⁠16–––––67
Oct 20atWest VirginiaW 55–⁠141210004
Oct 27vs.Texas TechW 55–⁠24–––––17
Nov 3vs.Oklahoma StateW 44–⁠3056450020

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.