Skip to content

Atlas / NTSB / CHI04CA195

NTSB CAROL · Event

Event CHI04CA195

2004-07-25 Omaha, Nebraska, United States Airport · 3NO None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

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.

Factual narrative

On July 25, 2004, at 1710 central daylight time, a Piper PA-28-235, N9290W, piloted by a commercial pilot, was substantially damaged when it overran runway 17 (2,480 feet by 40 feet, concrete) during landing at the North Omaha Airport (3NO), Omaha, Nebraska. The personal flight was operating under 14 CFR Part 91 without a flight plan. Visual meteorological conditions prevailed at the time of the accident. The pilot and three passengers reported no injuries. The flight departed Clinton Municipal Airport (CWI), Clinton, Iowa. In his written statement, the pilot noted that the winds were reported as calm by the automated weather observing system at nearby Millard Airport (MLE), located 11 miles south of 3NO. He reported that he entered left traffic for runway 17 at 3NO, at which time the wind sock indicated no-wind. The pilot noted that construction vehicles in the area required a steeper-than-normal approach angle. He stated that 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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2004_CHI04CA195.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗