CHI95LA317 · Piper PA-28-181
Piper PA-28-181 · Accident: overrun during landing
From Dupage Airport (DPA) to RLA · WI
Event
- NTSB case
- CHI95LA317
- 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
Piper PA-28-181
- Aircraft type
- Piper PA-28
- 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
- N3071H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dupage Airport (DPA), West Chicago, ILTo RLA · WI
- 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
- Landing · aborted
- 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
- Overrun
- 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 › Aborted landing, delayed
- Pilot in command › Lack of total experience in type operation
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT SAID HE PERFORMED A GO-AROUND DURING HIS FIRST LANDING APPROACH DUE TO BEING A '...LITTLE HIGH AND FAST... .' DURING THE SECOND LANDING APPROACH HE SAID THE AIRPLANE'S AIRSPEED WAS 79 KIAS AND THE AIRPLANE WAS DESCENDING AT 500 FPM WITH 40 DEGREES OF FLAPS EXTENDED. ACCORDING TO THE AIRPLANE'S PILOT OPERATING HANDBOOK, THE FINAL APPRACH SPEED SHOULD HAVE BEEN 66 KNOTS INDICATED AIRSPEED. THE PILOT SAID THE AIRPLANE FLOATED DOWN THE RUNWAY AND BOUNCED TWO TIMES AFTER TOUCHING DOWN. THE PILOT SAID HE DECIDED TO GO-AROUND BUT WAS TOO LATE IN HIS DECISION MAKING PROCESS. HE SAID HE ADDED FULL POWER BUT NEGLECTED TO RETRACT THE FLAPS. THE AIRPLANE RAN OFF THE END OF THE RUNWAY, COLLIDING WITH TREES AND A BERM BEFORE COMING TO A STOP. THE PILOT SAID HE NORMALLY DOES NOT FLY INTO SMALL AIRPORTS. HE SAID HE ALWAYS TRIES TO FLY INTO CONTROLLED AIRPORTS THAT ARE SERVED BY INSTRUMENT APPROACHES. THE RUNWAY THE PILOT WAS ATTEMPTING TO LAND ON WAS 2,100 FEET LONG AND 50 FEET WIDE.
Probable cause
The pilot's lack of experience in the type of operation being conducted, the pilot not maintaining the proper airspeed while on final approach to landing, and a delayed decision to abort the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA317
- Event ID
- 20001207X04456
- Case number
- CHI95LA317
- 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: 03609786b13ed5516076440b9a1255d1cc0eeefc3fdfe00847abe1bb25ed0d80; retrieved 2026-09-22T23:16:42.731Z.