CEN12FA654 · Piper PA-28R-180
Piper PA-28R-180 · Accident: fuel contamination during takeoff
From Aero Valley Airport (52F) to Aero Valley Airport (52F)
Event
- NTSB case
- CEN12FA654
- 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
- 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-28R-180
- 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
- N4567J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aero Valley Airport (52F), Roanoke, TXTo Aero Valley Airport (52F), Roanoke, TX
- 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
- Takeoff
- Defining eventThe 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
- Fuel contamination
- 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
- Aircraft › Fluids/miscellaneous hardware
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot, who had purchased the airplane about 2 months earlier, and the flight instructor departed on an instructional flight. Two witnesses reported that the airplane's engine did not sound right during the takeoff and the ground roll was longer than normal. Just beyond the runway, the airplane turned slightly left and then impacted the top of several trees. Both wings separated and remained lodged in the treetops; first responders noted fuel running from the wings. The emergency locater transmitter (ELT) was in found in the off position. Examination of the engine revealed water and contaminants in the fuel system, especially in the injection servo and fuel pump, which would have resulted in the rough-running engine and loss of engine power.
A review of the airplane's maintenance records did not reveal any entries since the pilot had purchased the airplane. The airplane's last maintenance entry was at the annual inspection, which was about the time the airplane was purchased. The entry stated "found water in tanks - sumped tanks, cleaned flow divider, fuel screens and lines." The log also had the entry that stated "c/w FAR 91.207 ELT insp by installing new batteries, due March 2017." The airport manager had witnessed the same pilot depart in the accident airplane about a month earlier; however, the airplane's engine did not sound right, and the pilot returned to the airport. A review of the pilot's logbook revealed an entry "aborted X-country, lost engine power, so landed" on that date. About 2 weeks later, an e-mail from the pilot to family members stated that a clogged fuel injection system was found after the aborted flight. Two days after that, the pilot's logbook reflected 1.1 flight hours with a note that stated "test flight, perfect." On that same date, the pilot wrote a check to a maintenance company at the airport on which the airplane's registration number and "Maint" were written in the memo field. It is likely that either at the annual inspection and/or 2 weeks before the accident, maintenance personnel did not appropriately address the fuel contamination issues that persisted at the time of the accident.
The airplane was not equipped with shoulder belts. During the impact sequence, the pilot likely rotated about his lap belt, braced himself with his arms and fractured his shoulders, but his head struck the instrument panel, resulting in his fatal skull injury. The flight instructor similarly rotated forward about his lap belt; his chest and abdomen struck the instrument panel resulting in his fatal injuries. Had the airplane been equipped with single or double shoulder restraints, the pilots' injuries likely would have been less severe and they might have survived.
Probable cause
The loss of engine power during takeoff due to fuel contamination. Contributing to the accident was maintenance personnel's failure to adequately correct the water contamination effects. Contributing to the severity of the occupants' injuries was the lack of shoulder restraints.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12FA654
- Event ID
- 20120922X92533
- Case number
- CEN12FA654
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 09d2e944a33e218139bd4aef957569f674793010108ab559e4d41dd9ea43f068; retrieved 2026-09-14T15:45:03.321Z.