Fullback, Arizona State, 2019–22
Case Hatch
- Number
- No. 44
- Height
- 6′1″
- Weight
- 235 lb
- Class (2022)
- Senior
- Hometown
- Gilbert, AZ
Case Hatch played fullback at Arizona State (2019–22).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2019 | Arizona State | 12 | 10 | 0 | 0 | 0 | 0 |
| 2020 | Arizona State | 3 | 3 | 0 | 0 | 0 | 0 |
| 2021 | Arizona State | 3 | 2 | 0 | 0 | 0 | 0 |
| 2022 | Arizona State | 1 | 1 | 0 | 0 | 0 | 0 |
| Career | 19 | 16 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | Arizona State | 44 | FB | Fr. | ||
| 2020 | Arizona State | 44 | FB | So. | ||
| 2021 | Arizona State | 44 | FB | Jr. | ||
| 2022 | Arizona State | 44 | FB | Sr. | 6′1″ | 235 |
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.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2019 | Arizona State | 1 | 1.96 | – | – | 2.0 | – |
| 2020 | Arizona State | 2 | 1.54 | – | – | 3.1 | – |
| 2021 | Arizona State | 2 | 0.68 | – | – | 1.4 | – |
| 2022 | Arizona State | 1 | -1.19 | – | – | -1.2 | – |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2022 Arizona State 2 games, 0 rushing yards
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Oct 1 | at USC | L 25–42 | – | – | – | – | – |
| Nov 19 | vs. Oregon State | L 7–31 | 1 | 1 | 0 | 0 | 0 |
2021 Arizona State 4 games, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 25 | vs. Colorado | W 35–13 | 1 | 1 | 0 | 0 | 0 |
| Oct 30 | vs. Washington State | L 21–34 | 1 | 1 | 0 | 0 | 0 |
| Nov 20 | atOregon State | L 10–24 | – | – | – | – | – |
| Nov 27 | vs. Arizona | W 38–15 | 1 | 0 | 0 | 0 | 0 |
2020 Arizona State 3 games, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Nov 7 | atUSC | L 27–28 | 2 | 2 | 0 | 0 | 0 |
| Dec 11 | atArizona | W 70–7 | – | – | – | – | – |
| Dec 19 | atOregon State | W 46–33 | 1 | 1 | 0 | 0 | 0 |
2019 Arizona State 8 games, 12 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 29 | vs. Kent State | W 30–7 | 3 | 3 | 0 | 0 | 0 |
| Sep 6 | vs. Sacramento State | W 19–7 | 2 | 1 | 0 | 0 | 0 |
| Sep 21 | vs.Colorado | L 31–34 | 1 | 1 | 0 | 0 | 0 |
| Oct 12 | vs.Washington State | W 38–34 | 1 | 1 | 0 | 0 | 0 |
| Oct 19 | at Utah | L 3–21 | 1 | 0 | 0 | 0 | 0 |
| Oct 26 | at UCLA | L 32–42 | 2 | 2 | 0 | 0 | 0 |
| Nov 16 | atOregon State | L 34–35 | 1 | 1 | 0 | 0 | 0 |
| Dec 31 ✦ | vs. Florida State | W 20–14 | 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.