Defensive back, Boston College, 2010–13
James McCaffrey
- Number
- No. 29
- Height
- 5′10″
- Hometown
- Winchester, MA
James McCaffrey played defensive back at Boston College (2010–13).
Returns
| Season | Team | KR | Yds | TD |
|---|---|---|---|---|
| 2012 | Boston College | 4 | 55 | 0 |
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2012 | Boston College | 4 | 8 | 2.0 | 0 | 7 |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2012 | Boston College | 1 | 7 | 7.0 | 0 | 7 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2011 | 6 | 4 | 5 | 9 |
| 2012 | 9 | 6 | 4 | 10 |
| 2013N | 11 | 2 | 1 | 3 |
| On file | 12 | 10 | 22 | |
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
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2010 | Boston College | 29 | DB | |
| 2011 | Boston College | 29 | DB | |
| 2012 | Boston College | 29 | DB | |
| 2013 | Boston College | 29 | DB | 5′10″ |
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
2012 Boston College 3 games, 4 returns, 55 yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Sep 15 | at Northwestern | L 13–22 | 2 | 36 | 0 |
| Oct 6 | at Army | L 31–34 | 2 | 19 | 0 |
| Oct 13 | at Florida State | L 7–51 | – | – | – |
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.