1966 South Dakota Coyotes football team
The 1966 South Dakota Coyotes football team was an American football team that represented the University of South Dakota in the North Central Conference (NCC) during the 1966 NCAA College Division football season. In its first season under head coach Joe Salem, the team compiled a 5–5 record (2–4 against NCC opponents), finished in a three-way tie for fourth place out of seven teams in the NCC, and outscored opponents by a total of 225 to 160.[1] The team played its home games at Inman Field in Vermillion, South Dakota.
| 1966 South Dakota Coyotes football | |
|---|---|
| Conference | North Central Conference |
| 1966 record | 5–5 (2–4 NCC) |
| Head coach | Joe Salem (1st season) |
| Home stadium | Inman Field |
| 1966 North Central Conference football standings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Conf | Overall | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Team | W | L | T | W | L | T | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| North Dakota + | 5 | – | 1 | – | 0 | 8 | – | 2 | – | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| North Dakota State + | 5 | – | 1 | – | 0 | 8 | – | 2 | – | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| State College of Iowa | 4 | – | 2 | – | 0 | 4 | – | 5 | – | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Augustana (SD) | 2 | – | 4 | – | 0 | 5 | – | 4 | – | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| South Dakota | 2 | – | 4 | – | 0 | 5 | – | 5 | – | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| South Dakota State | 2 | – | 4 | – | 0 | 3 | – | 7 | – | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Morningside | 1 | – | 5 | – | 0 | 3 | – | 6 | – | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Schedule
| Date | Opponent | Site | Result |
|---|---|---|---|
| September 10 | vs. Colorado State-Greeley | Rapid City, SD | W 27–12 |
| September 17 | Wayne State (NE) | W 40–6 | |
| September 24 | Montana | W 21–7 | |
| October 1 | at Augustana | L 20–24 | |
| October 8 | at North Dakota | L 17–31 | |
| October 15 | at Morningside | W 38–0 | |
| October 22 | South Dakota State | L 18–22 | |
| October 29 | North Dakota State | L 0–13 | |
| November 5 | State College of Iowa | W 30–14 | |
| November 12 | at Drake | L 14–31 |
gollark: I mean, if my laptop gets hacked or something, people can at least not irreversibly overwrite my brain, only... delete my notes and stuff.
gollark: I'm pretty scared of brain implants because they would probably involve computer systems of some kind with read/write access to my brain. And computers/software seem to have more !!FUN!! security problems every day.
gollark: Personally, I blame websites and the increasingly convoluted web standards for browser performance issues. Websites with a few tens of kilobytes of contents to a page often pull in megabytes of giant CSS and JS libraries for no good reason, and browsers are regularly expected to do a lot of extremely complex things. With Unicode even text rendering is very hard.
gollark: Memory safety issues are especially problematic in things like browsers, so avoiding them is definitely worth something.
gollark: > google blames c/c++ and its lack of warnings to devs about memory issues for most of the critical bugs in chrome<@528315825803755559> I mean, it's a fair criticism. You can avoid them if you have a language (like Rust) which makes them actual compile errors.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.