Quarterback, Holy Cross (from Pittsburgh), 2023–26
David Lynch
- Number
- No. 16
- Height
- 6′3″
- Weight
- 215 lb
- Class (2026)
- Junior
- Hometown
- East Greenwich, RI
David Lynch plays quarterback for Holy Cross, after Pittsburgh (2023–25). Last time out, at Harvard: 11 of 22, 120 yards, 2 INT. Lynch leads Holy Cross in passing touchdowns and passing yards this season.
2026 so far
1,398 passing yards, 10 TD
Last game: 11 of 22, 120 yards, 2 INT at Harvard, L 7–30
Next game: vs. Bucknell, Oct 24
Filled bars: wins; outlined: losses.
Career highs
313passing yards, career highvs. Lehigh, 20264touchdown passes, career highat Lafayette, 2026Passing
* The season in progress, so far.
| Season | Team | Cmp | Att | Pct | Yds | Y/A | TD | Int |
|---|---|---|---|---|---|---|---|---|
| 2024 | Pittsburgh | 16 | 27 | 59.3 | 111 | 4.1 | 0 | 3 |
| 2026 | Holy Cross | 122 | 223 | 54.7 | 1,398 | 6.3 | 10 | 9 |
| Career | 138 | 250 | 55.2 | 1,509 | 6.0 | 10 | 12 | |
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024 | Pittsburgh | 4 | −14 | −3.5 | 0 | 2 |
| 2026 | Holy Cross | 25 | −5 | −0.2 | 1 | 13 |
| Career | 29 | −19 | −0.7 | 1 | 13 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2023 | Pittsburgh | 16 | QB | RS | ||
| 2024 | Pittsburgh | 16 | QB | Fr. | ||
| 2025 | Pittsburgh | 16 | QB | So. | ||
| 2026 | Holy Cross | 16 | QB | Jr. | 6′3″ | 215 |
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 |
|---|---|---|---|---|---|---|---|
| 2024 | Pittsburgh | 30 | -0.44 | – | – | -13.3 | 13% |
| 2026 | Holy Cross (FCS) | 243 | 0.12 | 28th (n=273) | 0.21 | 28.5 | 53% |
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
2026 Holy Cross 7 games, 1,398 passing yards, 10 TD
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | vs. Lehigh | L 10–35 | 25 | 40 | 313 | 1 | 2 | 28 |
| Sep 5 | at Colgate | L 10–35 | 19 | 35 | 264 | 0 | 3 | −2 |
| Sep 12 | at Miami (OH) | L 7–45 | 13 | 25 | 141 | 1 | 0 | −4 |
| Sep 19 | vs. Yale | L 28–38 | 16 | 38 | 144 | 2 | 1 | −4 |
| Sep 26 | at Lafayette | W 38–30 | 22 | 37 | 230 | 4 | 0 | 2 |
| Oct 3 | at William & Mary | W 41–14 | 16 | 26 | 186 | 2 | 1 | −15 |
| Oct 17 | at Harvard | L 7–30 | 11 | 22 | 120 | 0 | 2 | −10 |
2024 Pittsburgh 3 games, 111 passing yards
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Nov 23 | at Louisville | L 9–37 | 5 | 7 | 43 | 0 | 1 | −1 |
| Nov 30 | at Boston College | L 23–34 | 1 | 2 | 3 | 0 | 0 | – |
| Dec 26 ✦ | vs. Toledo | L 46–48 | 10 | 18 | 65 | 0 | 2 | −13 |
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.