Receiver, Air Force, 2019–23
Dane Kinamon
- Number
- No. 23
- Height
- 6′0″
- Weight
- 205 lb
- Class (2023)
- Senior
- Hometown
- Peachtree City, GA
Dane Kinamon played receiver at Air Force (2019–23).
Career highs
94receiving yards, career highat Navy, 2023Receiving
Rushing
Returns
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | Air Force | 23 | WR | Yr 1 | ||
| 2021 | Air Force | 23 | WR | Yr 3 | ||
| 2022 | Air Force | 23 | WR | Yr 4 | ||
| 2023 | Air Force | 23 | WR | Sr. (Yr 5) | 6′0″ | 205 |
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 | Adj. rush |
|---|---|---|---|---|---|---|---|---|
| 2019 | Air Force | 1 | -1.14 | – | – | -1.1 | – | – |
| 2021 | Air Force | 45 | 0.69 | 54th (n=410) | 0.67 | 31.0 | 6% | 0.36 |
| 2022 | Air Force | 6 | 2.68 | – | – | 16.1 | – | – |
| 2023 | Air Force | 14 | 0.82 | – | – | 11.5 | – | – |
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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.
Game by game
2023 Air Force 7 games, 6 returns, 41 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 9 | vs. | W 13–3 | – | – | – | – | – |
| Sep 15 | vs. | W 39–21 | 1 | 7 | 0 | 7 | 4 |
| Sep 22 | at | W 45–20 | 1 | 6 | 0 | 6 | – |
| Oct 21 | at | W 17–6 | 1 | 94 | 1 | 94 | – |
| Oct 28 | at | W 30–13 | 1 | 9 | 1 | 9 | 8 |
| Nov 4 | vs. | L 3–23 | 1 | 10 | 0 | 10 | – |
| Dec 23 ✦ | vs. | W 31–21 | – | – | – | – | 9 |
2022 Air Force 2 games, 2 catches, 88 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | W 48–17 | 1 | 80 | 1 | 80 | 77 |
| Sep 10 | vs. | W 41–10 | 1 | 8 | 0 | 8 | 21 |
2021 Air Force 11 games, 10 catches, 141 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 11 | at | W 23–3 | – | – | – | – | 1 |
| Sep 18 | vs. | L 45–49 | – | – | – | – | 10 |
| Sep 25 | vs. | W 31–7 | – | – | – | – | 29 |
| Oct 2 | at | W 38–10 | – | – | – | – | 21 |
| Oct 9 | vs. | W 24–14 | – | – | – | – | −3 |
| Oct 16 | at | W 24–17 | – | – | – | – | −1 |
| Oct 23 | vs. | L 14–20 | 1 | 14 | 0 | 14 | 13 |
| Nov 6 | vs. | L 14–21 | 4 | 66 | 1 | 23 | 3 |
| Nov 13 | at | W 35–21 | 2 | 21 | 1 | 20 | 65 |
| Nov 19 | at | W 41–39 | – | – | – | – | 22 |
| Dec 28 ✦ | vs. | W 31–28 | 3 | 40 | 0 | 15 | 5 |
2019 Air Force 2 games, 1 tackle
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Aug 31 | vs. | W 48–7 | – | – | – | – | 0 |
| Dec 27 ✦ | vs. | W 31–21 | – | – | – | – | – |
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.
