NTSB CAROL · Event
Event CHI04LA104
Aircraft involved
Probable cause & findings
Visual lookout not maintained by the pilots of both airplanes.
Factual narrative
On April 9, 2004, about 1918 central daylight time, a Cessna 172M, N73213, co-owned by the pilot, sustained substantial damage during a midair collision with a Cessna 182S, N355BD, operated by Waukegan Wings as a rental airplane, near New Munster, Wisconsin. N355BD sustained substantial damage. Visual meteorological conditions prevailed at the time of the accident. The 14 CFR Part 91 personal flights were operating without flight plans and were not receiving air traffic control services. The private pilot of N73213 and the private rated rental pilot of N355BD were uninjured. N73213 originated from Palwaukee Municipal Airport, Wheeling, Illinois, at 1905, and N355BD originated from Waukegan Regional Airport (UGN), Waukegan, Illinois, at 1800. Both airplanes were en route to Burlington Municipal Airport (BUU), Burlington, Wisconsin. Following the midair collision, N73213 landed at BUU and N355BD landed at UGN. Both airplanes landed without further incident. The pilot of N73213 stated that he was en route to BUU on a heading of 340 degrees. The airplane's beacon, navigation, and taxi lights were on throughout the flight. He flew over Fox Lake and initiated a climb to about 3,000 feet mean sea level (MSL). About 15 miles from BUU, he descended to 2,500 feet MSL in order to intercept the BUU VOR and "perhaps" fly a visual BUU VOR 29 practice approach. About 9.4 miles south of BUU, while in straight and level flight, the pilot felt and heard a loud thump from the rear of his airplane. He did not see another airplane prior to the midair collision. Approximately 3 or 4 seconds after the collision, the pilot noticed another high-wing aircraft above, to the left, and in front of him. The other airplane was beginning to turn to a southbound heading. The pilot of N355BD stated that he departed on a local proficiency flight and upon leaving UGN's airspace, he tuned to BUU's common traffic advisory frequency. About 1850, he departed from the BUU VOR at 2,500 feet MSL to an area south of Bong Air Force Base in order to avoid traffic at Westosha, Burlington, or Galt airports. About 1900, he made a clearing turn from 180 degrees to 90 degrees and the another clearing turn back to 180 degrees. The pilot stated that he did not see any air traffic during or after either clearing turn. He then performed a 45-degree steep turn to the right from 180 degrees and 2,500 feet MSL. After completing the turn, he retrimmed the airplane, and checked for traffic. He then made another 45-degree steep turn to the left at 2,440 feet MSL. He did not see any traffic while performing either turn. He began his rollout to straight and level on a heading of about 200 degrees at 2,440 feet MSL. As he rolled out, he saw a Cessna Skyhawk at his 2 o'clock position, slightly low, on a heading of about 310 degrees, and very close. A moment later, his landing gear struck the Skyhawk's vertical stabilizer. According to a Federal Aviation Administration inspector, the pilot of N355BD stated that the purpose of his flight was flight proficiency with the intent to fly to BUU to practice holding, procedure turns, and instrument approaches. The pilot of N73213 did not hold an instrument rating and was receiving instruction prior to the accident flight toward an airplane instrument rating. The pilot of N355BD held an airplane instrument rating at the time of the accident. Neither pilot had a safety pilot aboard the accident flights. A Cessna 172M and a Cessna 182S both received substantial damage during a midair collision. Both airplanes landed without further incident. Visual meteorological conditions prevailed at the time of the accident. The pilot of the Cessna 172M stated that he was in level flight at 2,500 feet mean sea level when he felt and heard a thump from the rear of the airplane. After the collision, the pilot saw the Cessna 182S above, to the left, and in front of him. The pilot of the Cessna 182S stated that as he rolled out from a steep turn, he saw the Cessna 172M at his 2 o'clock position, slightly low and very close. A moment later, his landing gear struck the Cessna 172M's vertical stabilizer. Neither airplane was receiving air traffic control services. The pilot of the Cessna 182S stated that the purpose of his flight was flight proficiency with the intent to practice holding, procedure turns, and instrument approaches. The pilot of the Cessna 172M did not hold an airplane instrument rating and was receiving instruction prior to the accident flight toward an instrument ratting. The pilot of the Cessna 182S held an airplane instrument rating at the time of the accident. Neither pilot had a safety pilot aboard the accident flights. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_CHI04LA104.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (midair collision). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Airspace Saturation and Midair Collision Risk: A Case Study at a Class D Airport
Near midair collisions are precursor events to actual collisions and may be an indicator of risk. While previous studies have used reports of near midair collisions to relate factors such as airspace …
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for Urban Air Mobility (UAM)
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for UAM
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2019 · Other - Patent
Apparatus for aiding a pilot in avoiding a midair collision between aircraft
An apparatus for aiding a pilot in avoiding a midair collision between aircraft is described. A protected aircraft carries a transmitter, a transponder, a receiver, and a data processor; and an intrud…
- Embry-Riddle Scholarly Commons 2018 · Journal article (IJAAA)
Evaluating Small UAS Near Midair Collision Risk Using AeroScope and ADS-B
As small unmanned aircraft systems (sUAS) continue to proliferate in the National Airspace System (NAS), near midair collisions are becoming more common.
- NASA NTRS 2011 · Reprint (Version printed in journal)
Midair collisions - The accidents, the systems, and the Realpolitik
Two midair collisions occurring in 1978 are described, and the air traffic control system and procedures in use at the time, human factors implications and political consequences of the accidents are …
Browse the full corpus — academia portal ↗