CEN22LA120 · Cessna 172N
Southern Illinois Airport Authority Cessna 172N · Accident: collision with terrain/object (non-CFIT) on approach
From Southern Illinois Airport (MDH) to Southern Illinois Airport (MDH)
Event
- NTSB case
- CEN22LA120
- 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
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- 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
Cessna 172N
- 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
- N737SY
- Onboard fatalities
- Unknown
- Route
- From Southern Illinois Airport (MDH), Murphysboro, ILTo Southern Illinois Airport (MDH), Murphysboro, IL
- Aircraft age
- About 45 years (built 1977)
- 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
- Defining eventThe 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
- Collision with terrain/object (non-CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was practicing takeoffs and landings during a solo instructional flight at the time of the accident. She completed 7 landings without incident, and the accident approach was to be the final landing. The pilot reported that the runway was in sight, but she did not see the power lines. The airplane hit the lines and subsequently impacted the ground below the lines. The airframe sustained damage to the fuselage and left wing. According to the pilot, there were no failures or malfunctions associated with the airplane before the accident. The accident occurred about 24 minutes after sunset and about 3 minutes before the end of civil twilight. The runway was equipped with Precision Approach Path Indicator (PAPI) system. An inspection of the system after the accident revealed that it was operating normally at that time.
Probable cause
The pilot’s failure to maintain clearance from power lines during approach for landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA120
- Event ID
- 20220214104637
- Case number
- CEN22LA120
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: e4d2a91bbbb2d9469f7aed6de91f45fed3915c2972e10f8d4eeaf26e1b988218; retrieved 2026-09-16T14:57:25.397Z.