Safety, Oklahoma State, 2015–16
Derrick Moncrief
- Number
- No. 36
- Height
- 6′2″
- Hometown
- Prattville, AL
Derrick Moncrief played safety at Oklahoma State (2015–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2016 | Oklahoma State | 16 | 10 | 1 | 0 | 1 | 1 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2015 | Oklahoma State | 36 | S | |
| 2016 | Oklahoma State | 36 | S | 6′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 Oklahoma State 10 games, 16 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. SE Louisiana | W 61–7 | 4 | 1 | 0 | 0 | 0 | 0 |
| Sep 17 | vs. Pittsburgh | W 45–38 | 0 | 0 | 0 | 0 | 0 | 1 |
| Sep 24 | at Baylor | L 24–35 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 1 | vs. Texas | W 49–31 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 8 | vs. Iowa State | W 38–31 | 1 | 1 | 0 | 0 | 1 | 0 |
| Oct 29 | vs. West Virginia | W 37–20 | 2 | 2 | 0 | 0 | 0 | 0 |
| Nov 5 | at Kansas State | W 43–37 | 3 | 3 | 1 | 0 | 0 | 0 |
| Nov 12 | vs. Texas Tech | W 45–44 | 1 | 1 | 0 | 0 | 0 | 0 |
| Nov 19 | at TCU | W 31–6 | 1 | 0 | 0 | 0 | 0 | 0 |
| Dec 29 ✦ | vs. Colorado | W 38–8 | 2 | 0 | 0 | 0 | 0 | 0 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Before the draft
| Drill | Pro day 2017 |
|---|---|
| Height | 6′2″ |
| Weight | 215 lb |
| Arm length | 31⅜″ |
| Hand size | 8⅞″ |
| 40-yard dash | 4.55 s |
| Vertical jump | 36½″ |
| Broad jump | 10′6″ |
| Bench press | 16 reps |
| 3-cone drill | 7.25 s |
| 20-yard shuttle | 4.52 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.