Cornerback, Oregon State, 2006–⁠10

James Dockery

Number
No. 4
Height
6′1″
Hometown
La Quinta, CA

James Dockery played cornerback at Oregon State (2006–⁠10).

Defense

SeasonTeamInt
2009Oregon State2
2010Oregon State4
On file (2009–⁠10)6

Season lines from CollegeFootballData, regular season and bowls. Before 2016 our source records only interceptions for most defenders (no tackles, tackles for loss or sacks), so these lines count interceptions only. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.

Defense before 2016

SeasonGSoloAstTklTFLIntPBU
2007N13111120––
2009132414382.528
2010124115560.545
On file76301063––

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, 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
2009Oregon State4CB
2010Oregon State4CB6′1″

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

2010 Oregon State 3 games with an interception on file, 4 INT
DateOpponentResultInt
Sep 18vs.LouisvilleW 35–⁠281
Oct 2vs.Arizona StateW 31–⁠282
Nov 6atUCLAL 14–⁠171
2009 Oregon State 2 games with an interception on file, 2 INT
DateOpponentResultInt
Oct 24atUSCL 36–⁠421
Dec 3atOregonL 33–⁠371

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file. Before 2016 our source’s box scores record only interceptions for defenders (no tackles, tackles for loss or sacks), so only those games are listed. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.

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.