Defensive line, Arizona, 2010–16
Aiulua Fanene
Lettered 2011, 2015–16 (school media guide)
- Number
- No. 62
- Height
- 6′5″
- Hometown
- Nu’uuli, American Samoa
Aiulua Fanene played defensive line at Arizona (2010–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Arizona | 15 | 12 | 2 | 0 | 1 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl | TFL | FF |
|---|---|---|---|---|---|---|
| 2011 | 4 | 7 | 1 | 8 | 1.5 | 1 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2010 | Arizona | 62 | DL | |
| 2011 | Arizona | 62 | DL | |
| 2012 | Arizona | 62 | DL | |
| 2013 | Arizona | 62 | DL | |
| 2014 | Arizona | 62 | DL | |
| 2015 | Arizona | 62 | DL | |
| 2016 | Arizona | 62 | DL | 6′5″ |
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 Arizona 8 games, 15 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 24 | vs. Washington | L 28–35 | 1 | 1 | 0 | 0 | 0 |
| Oct 1 | at UCLA | L 24–45 | 2 | 2 | 1 | 0 | 0 |
| Oct 8 | at Utah | L 23–36 | 3 | 1 | 0 | 0 | 0 |
| Oct 15 | vs. USC | L 14–48 | 1 | 1 | 0 | 0 | 0 |
| Oct 29 | vs. Stanford | L 10–34 | 3 | 3 | 1 | 0 | 1 |
| Nov 12 | vs. Colorado | L 24–49 | 3 | 3 | 0 | 0 | 0 |
| Nov 19 | at Oregon State | L 17–42 | 1 | 0 | 0 | 0 | 0 |
| Nov 25 | vs. Arizona State | W 56–35 | 1 | 1 | 0 | 0 | 0 |
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.