CHI96LA156 · Cessna 172N
Cessna 172N · Accident: in flight collision with object on approach
From Lake Lawn Airport (C59) to 3CK
Event
- NTSB case
- CHI96LA156
- 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
- 0 · 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
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
- N738CS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake Lawn Airport (C59), LAKE LAWN, WITo 3CK
- 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
- In flight collision with object
- 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
- Pilot in command › Proper glidepath, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he 'intended to bleed off speed and touchdown on the numbers,' of the runway. The passenger on board noticed the large semi-truck and notified the pilot. The pilot said that he had no time to react. He only had enough time to identify what he had struck. A witness at the hold line for the active runway observed the airplane as it approached from the east. 'I noted that he was low on his approach and assumed that he would take corrective action. As he approached the road, a semi crossed in front of the airplane. The airplane appeared to impact the side of the truck with its landing gear. The airplane flipped over the truck and impacted the ground upside-down.'
Probable cause
the pilot not flying a proper glidepath for the displaced runway threshold.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA156
- Event ID
- 20001208X05719
- Case number
- CHI96LA156
- 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: 2cf83f56e48ac38040a4073c213495f5ac40d572570c6fd8b5beb18b77872642; retrieved 2026-09-21T21:50:37.817Z.