Defensive back, Memphis, 2012–⁠16

Chris Morley

Number
No. 17
Height
5′11″
Hometown
Plantation, FL

Chris Morley played defensive back at Memphis (2012–⁠16).

Career highs

11tackles, career highat Navy, 2016

Team titles: American champions, 2014

Defense

SeasonTeamTklSoloTFLSacksIntPDHur
2013Memphis––––1––
2015Memphis––––1––
2016Memphis755321251
Career755321451

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

Defense before 2016

SeasonGSoloAstTklTFLIntPBU
2013128210214

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2012Memphis17DB
2013Memphis17DB
2014Memphis17DB
2015Memphis17DB
2016Memphis17DB5′11″

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

2016 Memphis 13 games, 75 tackles, 1 sack, 2 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3vs.Southeast Missouri StateW 35–⁠17210000
Sep 17vs.KansasW 43–⁠7870000
Sep 24vs.Bowling GreenW 77–⁠3520010
Oct 1atOle MissL 28–⁠48770001
Oct 6vs.TempleW 34–⁠27330002
Oct 14atTulaneW 24–⁠14410000
Oct 22atNavyL 28–⁠421160000
Oct 29vs.TulsaL 30–⁠59640001
Nov 5atSMUW 51–⁠7440000
Nov 12vs.South FloridaL 42–⁠49981000
Nov 18atCincinnatiW 34–⁠7841110
Nov 25vs.HoustonW 48–⁠44550001
Dec 20 ✦vs.Western KentuckyL 31–⁠51310000
2015 Memphis 1 game, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Oct 23atTulsaW 66–⁠42––––1–
2013 Memphis 1 game, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Nov 30vs.TempleL 21–⁠41––––1–

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.