CHI97FA218 · Cessna 172P
Cessna 172P and Beech A-36 · Accident: midair collision en route
Event
- NTSB case
- CHI97FA218
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 7 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Cessna 172P
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5323K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 3HA · Lansing, ILTo Chunga Airstrip (CGX)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Beech A-36
- Aircraft type
- Beechcraft A-36
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2071L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Michigan City Municipal Airport (MGC), Michigan City, INTo Chunga Airstrip (CGX)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Visual separation, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of a Cessna was cleared to pass southbound through Class D Airspace by the ATC controller. At 1802:09 CDT the controller advised the pilot to '...report abeam... .' At 1802:13 CDT The pilot acknowledged the controller, but did not report abeam the airport. The record shows that the controller did not ask the Cessna pilot if she was abeam the airport. The controller stated she was monitoring an airplane that was about 5-miles southeast of the airport during this period. The pilot of that airplane reported having difficulty with its landing gear. At 1803:35 CDT the pilot of a Beech A-36 Bonanza called the tower advising the controller the airplane was '...9-miles south ... inbound...' for landing. At 1803:41 CDT the controller told the pilot to '...report 4 south of the field plan on runway 36.' The pilot of the A-36 asked the controller about an airplane that reported 10-miles south of the airport at 1803:47 CDT. The controller said that the airplane was '...well clear of the Class Delta surface area sorry about that.' The A-36 pilot responded, 'No problem.' At 1804:06 the controller advised the pilot of the A-36 about the airplane she had been monitoring. The A-36's pilot acknowledged the controller s information. The A-36 pilot reported 4 miles south at 1805:53 CDT. The controller cleared the A-36's pilot to land on runway 36 at 1803:56 CDT. The A-36 pilot acknowledged the clearance. The record shows that the controller did not advise the Cessna and A-36 Bonanza pilot s of each others proximity to the other. The two airplanes collided with each other about 3-miles south of the airport.
Probable cause
the pilots not maintaining visual separation between their airplanes. A factor in this accident was the pilot of the southbound airplane not reporting her position abeam the airport as directed by the ATC controller.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97FA218
- Event ID
- 20001208X08309
- Case number
- CHI97FA218
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 3253ab8b9f6c76a9dd06a579d636e46be2cde0e264b04e68960f27feaf8452b1; retrieved 2026-09-20T22:53:49.166Z.