Receiver, Penn State, 2009–11
Curtis Drake
- Number
- No. 7
- Height
- 5′11″
- Hometown
- Philadelphia, PA
Curtis Drake played receiver at Penn State (2009–11).
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2009 | Penn State | 8 | 98 | 12.3 | 0 | 28 |
| 2011* | Penn State | 5 | 102 | 20.4 | 1 | 44 |
| Career | 13 | 200 | 15.4 | 1 | 44 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2009 | Penn State | 7 | WR | |
| 2010 | Penn State | 7 | WR | |
| 2011 | Penn State | 7 | WR | 5′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
2011 Penn State 5 games, 5 catches, 102 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 24 | vs. Eastern Michigan | W 34–6 | 1 | 17 | 0 | 17 | −2 |
| Oct 22 | at Northwestern | W 34–24 | 1 | 11 | 0 | 11 | – |
| Nov 12 | vs. Nebraska | L 14–17 | 1 | 31 | 0 | 31 | – |
| Nov 19 | at Ohio State | W 20–14 | – | – | – | – | 50 |
| Nov 26 | at Wisconsin | L 7–45 | 2 | 43 | 1 | 44 | 4 |
2009 Penn State 6 games, 8 catches, 98 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 5 | vs. Akron | W 31–7 | 1 | 7 | 0 | 7 | – |
| Sep 19 | vs. Temple | W 31–6 | 1 | 10 | 0 | 10 | −17 |
| Oct 31 | atNorthwestern | W 34–13 | 1 | 13 | 0 | 13 | – |
| Nov 14 | vs. Indiana | W 31–20 | 2 | 34 | 0 | 28 | 26 |
| Nov 21 | at Michigan State | W 42–14 | 2 | 22 | 0 | 11 | 18 |
| Jan 1 ✦ | vs. LSU | W 19–17 | 1 | 12 | 0 | 12 | −3 |
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.