Defensive back, Baylor, 2013–⁠16

Travon Blanchard

Lettered 2014–⁠16 (school media guide)

Number
No. 48
Height
6′2″
Hometown
Orange, TX

Travon Blanchard played defensive back at Baylor (2013–⁠16).

Career highs

15tackles, career highat West Virginia, 2016

Team titles: Big 12 champions, 2013 and 2014

Defense

SeasonTeamTklSoloTFLSacksIntPDHur
2014Baylor––––1––
2015Baylor––––2––
2016Baylor734891.5151
Career734891.5451

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.

On the roster

SeasonTeamNo.PosHt
2013Baylor48DB
2014Baylor48DB
2015Baylor48DB
2016Baylor48DB6′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.

Game by game

2016 Baylor 11 games, 73 tackles, 1.5 sacks, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 16atRiceW 38–⁠10973101
Sep 24vs.Oklahoma StateW 35–⁠241184.5001
Oct 1atIowa StateW 45–⁠42830000
Oct 15vs.KansasW 49–⁠7100001
Oct 29atTexasL 34–⁠35550001
Nov 5vs.TCUL 22–⁠62750001
Nov 12atOklahomaL 24–⁠45420.50.500
Nov 19vs.Kansas StateL 21–⁠42740000
Nov 25vs.Texas TechL 35–⁠54331000
Dec 3atWest VirginiaL 21–⁠241580000
Dec 27 ✦vs.Boise StateW 31–⁠12330010
2015 Baylor 2 games, 2 INT
DateOpponentResultTklSoloTFLSacksIntPD
Oct 3vs.Texas TechW 63–⁠35––––1–
Nov 14vs.OklahomaL 34–⁠44––––1–
2014 Baylor 1 game, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Nov 29vs.Texas TechW 48–⁠46––––1–

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Before the draft

DrillPro day 2018
Height6′1⅞″
Weight208 lb
Arm length33⅜″
Hand size9″
40-yard dash4.65 s
Vertical jump33″
Broad jump9′8″
Bench press15 reps
3-cone drill7.34 s
20-yard shuttle4.77 s

Combine and pro day results compiled by array-carpenter (nfl-draft-data).

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.