CHI04CA195 · Piper PA-28-235
Piper PA-28-235 · Accident: overrun during landing
From Clinton Municipal Airport (CWI) to North Omaha Airport (3NO)
Event
- NTSB case
- CHI04CA195
- 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
- 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
Piper PA-28-235
- 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
- N9290W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clinton Municipal Airport (CWI), Clinton, IATo North Omaha Airport (3NO), Omaha, NE
- 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
- 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 › Distance/speed, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was substantially damaged when it overran the end of the runway during landing. The pilot reported that there was little or no wind as he approached to land. He noted that construction vehicles in the area required a steeper-than-normal approach angle. The aircraft was configured with full flaps, however, "final [approach] was flown too fast, [approximately] 90 [miles per hour]." The airplane touched down over halfway down the runway. The pilot reportedly applied full brakes but was unable to stop on the pavement. The aircraft subsequently skidded off the end of the runway, encountering a ditch and a roadway. In his statement, the pilot added that "a go around was not deemed safe after the middle of the runway even though touch down had not occurred because of rising terrain and tall trees off the south end of the [runway]." He also noted that before landing, a non-negotiable go-around point should have been selected.
Probable cause
The pilot's failure to attain a proper touchdown point on the runway during landing. Contributing factors were the pilot's failure to perform a go-around, the ditch and the roadway encountered during the overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA195
- Event ID
- 20040818X01246
- Case number
- CHI04CA195
- 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, coordinates. 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: 68c2a671dfbf9569a94a7ab1c79b4bae41704c845d3094943836ccfdbfe3cdec; retrieved 2026-09-22T06:58:38.927Z.