CHI06FA026 · Piper PA-31-350
Piper PA-31-350 · Accident en route
From Ankeny Regional Airport (IKV) to Emmetsburg Municipal Airport (EGQ)
Event
- NTSB case
- CHI06FA026
- 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
- 2 · 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
- Charter & commuter
- 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-31-350
- Aircraft type
- Piper PA-31
- 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
- N27177
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ankeny Regional Airport (IKV), Ankeny, IATo Emmetsburg Municipal Airport (EGQ), Emmetsburg, IA
- 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 135: Air Taxi & Commuter
- 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
- En route · cruise
- 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
- Miscellaneous/other
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft preflight, not performed
- Pilot in command › Airspeed, low
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The twin-engine airplane was destroyed by impact with terrain about 2.5 miles northeast of the airport while returning to the airport with an engine problem. A witness reported that the FAR Part 135 on-demand passenger flight had been scheduled for a 0900 departure, but because the flight had not been confirmed, a pilot was not scheduled to fly the flight. The accident pilot arrived at the airport about 1005. A witness reported that the pilot was not in the office for more than two minutes when he "grabbed the status book," walked straight to the airplane, and boarded. A lineman serviced both engines at 0930 with oil, but failed to put the dipstick back in the right engine oil filler tube. Witnesses reported that they did not see the pilot perform a preflight. The pilot was unaware that the dipstick was left on the right wing of the airplane. The pilot taxied the airplane forward about 5 feet and abruptly stopped and shut down both engines. The pilot got out of the airplane. The lineman reported that he approached the pilot and asked what was wrong. The lineman reported that the pilot closed the oil flap door on the right engine, and said that the oil flap door had been left open. The pilot restarted the engines and departed about 1008. About three minutes after takeoff, the pilot informed departure control that he needed to return to the airport due to an oil leak. The pilot reported over the Unicom radio frequency that he was returning because he was having trouble with the right engine. Radar track data indicated that about 1013, the airplane's position was about 1.5 miles directly north of the airport about 1,800 feet msl, heading south at 126 knots calibrated airspeed (CAS). The airplane continued to fly south directly to the airport. The radar track data indicated that instead of landing on runway 18, the airplane flew over the airport, paralleling runway 18. About 1014, the airplane's position was over the airport at an altitude of about 1,460 feet msl (550 feet above ground level), heading south at about 97 knots CAS. The airplane continued to fly south past the airport, entered a left turn, and turned back to the north. The last radar return was recorded about 1016. The airplane's position was approximately 1.5 miles east of the approach end of runway 18 at an altitude of about 1,116 feet msl (344 feet agl), heading north at about 99 knots CAS. The impact site was located about 2.5 miles north of the last radar return. A witness, located about 1/4 mile from the accident site, observed the airplane flying "really low." He reported, "The motor on the plane wasn't cutting out or sputtering." Another witness reported, "The plane lifted up over power lines then went across a field about 50 to 80 ft off ground." The airplane impacted a harvested cornfield in a steep nose-down attitude, and traveled 45 feet before stopping. The inspection of the airplane revealed that the landing gear was down, flaps were found in a 20-degree down position, and neither propeller was feathered. The post accident inspection of the airplane's engines and airframe revealed no preexisting anomalies that could be associated with a pre-impact condition.
Probable cause
The pilot's failure to preflight the airplane, the pilot's improper in-flight decision not to land the airplane on the runway when he had the opportunity, and the inadvertent stall when the pilot allowed the airspeed to get too low. Factors that contributed to the accident were the lineman's improper servicing of the airplane when he left the oil dipstick out and the subsequent oil leak.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06FA026
- Event ID
- 20051116X01847
- Case number
- CHI06FA026
- 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: 1bf448e29eb14855e22af8618ebdddce6ebc56fe9852738cb290910deb67baa9; retrieved 2026-09-18T12:57:58.739Z.