Piper PA-28-180 accident near Sibley, Iowa, September 21, 2009
On September 21, 2009 at about 6:50 pm local time, a Piper PA-28-180, registered N57354, was substantially damaged in an accident during takeoff near Sibley, Iowa (Sibley Municipal Airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's long and fast landing and her delayed decision to execute a go-around.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 21, 2009 · about 6:50 pm local time
- Place
- Sibley, Iowa · Sibley Municipal Airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-180 · all PA-28-180s on the register
- Registration
- N57354 · no longer on the register · serial 28-7405044
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that she attempted a landing with a 10-degree flap setting. Calm winds were reported by the pilot. The airplane, which has tricycle-type landing gear, touched down in a "perfect" three-point landing at about 75 knots. The pilot told the Federal Aviation Administration inspector that the touchdown point was about halfway down the runway, at about 105 knots. The pilot realized that the airplane speed was too fast and then performed an aborted landing by retracting flaps to 0 degrees and adding full power. The airplane impacted a traffic sign and terrain when it overran the runway without becoming airborne, which resulted in substantial damage to the firewall. The pilot sustained minor injuries.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Abnormal runway contact during landing
- Runway excursion during takeoff defining event
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- Aircraft › Aircraft systems › Flight control system › TE flap control system › Incorrect use/operation
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 572 hours in all; 524 in this make and model; 524 as pilot in command
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 2,223 hours
- Last inspection: annual inspection, April 28, 2009
- Maximum gross weight: 2,450 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-360-A4A (piston); 0 hours total
The flight
- Departed from: SPW Spencer IA at 6:20 pm
- Destination: ISB Sibley IA
- Flight plan: none
- Runway 35
Weather at the time
- Light: daylight
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.