From Surf Wiki (app.surf) — the open knowledge base
1969 Duke Blue Devils football team
| 1969 Duke Blue Devils football |
|---|
| Atlantic Coast Conference |
| 3–6–1 (3–3–1 ACC) |
| Tom Harp (4th season) |
| Jacque Hetrick (4th season) |
| George Hill (4th season) |
| Leo Hart |
| Jim Dearth |
| Wallace Wade Stadium |
The 1969 Duke Blue Devils football team was an American football team that represented Duke University as a member of the Atlantic Coast Conference (ACC) during the 1969 NCAA University Division football season. In their fourth year under head coach Tom Harp, the Blue Devils compiled an overall record of 3–6–1, with a conference record of 3–3–1, and finished fifth in the ACC.
| Date | Opponent | Site | Result | Attendance | Source |
|---|---|---|---|---|---|
| September 20 | at South Carolina | Carolina StadiumColumbia, SC | L 20–27 | 42,791 | |
| September 27 | at Virginia | Scott StadiumCharlottesville, VA | L 0–10 | 25,000 | |
| October 4 | Pittsburgh* | Wallace Wade StadiumDurham, NC | L 12–14 | 18,000 | |
| October 11 | at Wake Forest | Groves StadiumWinston-Salem, NC (rivalry) | W 27–20 | 21,000 | |
| October 18 | at Maryland | Byrd StadiumCollege Park, MD | L 7–20 | 26,700 | |
| October 25 | at NC State | Carter StadiumRaleigh, NC (rivalry) | T 25–25 | 32,700 | |
| November 1 | at Georgia Tech* | Grant FieldAtlanta, GA | L 7–20 | 41,113 | |
| November 8 | Clemson | Wallace Wade StadiumDurham, NC | W 34–27 | 22,000 | |
| November 15 | vs. Virginia Tech* | Foreman FieldNorfolk, VA (Oyster Bowl) | L 12–48 | 23,000 | |
| November 22 | North Carolina | Wallace Wade StadiumDurham, NC (Victory Bell) | W 17–13 | 44,000 | |
| *Non-conference gameHomecoming |
Ask Mako anything about 1969 Duke Blue Devils football team — get instant answers, deeper analysis, and related topics.
Research with MakoFree with your Surf account
Create a free account to save articles, ask Mako questions, and organize your research.
Sign up freeThis content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.
Report