WPR14LA099 · Piper PA 24-250
Piper PA 24-250 and Nice Air Cessna 172N · Accident: fuel contamination during takeoff
Event
- NTSB case
- WPR14LA099
- 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
Aircraft 1 · Piper PA 24-250
- Aircraft type
- Piper PA-24
- 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
- N6570P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reid-Hillview Airport of Santa Clara County (RHV), San Jose, CATo Sonoma Skypark Airport (0Q9), Sonoma, CA
- Aircraft age
- About 54 years (built 1960)
- 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
Aircraft 2 · Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N737CL
- Operator
- Nice Air
- Onboard fatalities
- Unknown
- Route
- From Reid-Hillview Airport of Santa Clara County (RHV), San Jose, CATo Reid-Hillview Airport of Santa Clara County (RHV), San Jose, CA
- Aircraft age
- About 37 years (built 1977)
- 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
- Not recorded
- 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
- Not recorded
- 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
- Not determined › Not determined
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
This was the first flight for the Piper airplane in the last 3 months, during which time, it was parked on a ramp outside in the winter. The pilot reported that he performed a preflight inspection but that he did not sump the fuel system. The airplane's main fuel tanks were full with fuel, and the fuel selector valves were set to the main fuel tanks. Shortly after takeoff at an altitude of about 300 to 400 feet above ground level, the engine began to "sputter" with a corresponding partial loss of power. The pilot cycled the throttle control with no change in engine power and then turned back toward the airport. The airplane did not have sufficient altitude to reach a runway, so the pilot performed a gear-up landing onto a taxiway. After landing, the airplane slid across the taxiway surface and struck a taxiing Cessna airplane; both airplanes sustained substantial damage.
Postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation, and it started and ran smoothly during a subsequent test run. Given the pilot's failure to sump the fuel system and the fact that the engine did not experience a total loss of engine power, it is likely that the fuel system became contaminated with water while the airplane sat on the ramp for the preceding 3 months.
Probable cause
The pilot’s failure to sump the fuel tanks, which resulted in water contamination, a partial loss of engine power during takeoff, and collision with a taxiing airplane during the subsequent forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14LA099
- Event ID
- 20140118X22741
- Case number
- WPR14LA099
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-01-18.
- API snapshot SHA-256: 4c10631b3be38e211d40112b9618204523c701abb9c17ca345ae44e209b21fbf; retrieved 2026-09-13T18:22:58.856Z.