NYC99LA003 · Piper PA-38-112
Piper PA-38-112 · Accident: loss of engine power during initial climb
From N57 to an unrecorded destination
Event
- NTSB case
- NYC99LA003
- 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
- 0
- 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-38-112
- Aircraft type
- Piper PA-38
- 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
- N2535A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From N57To not recorded
- 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
- Initial climb
- 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
- Loss of engine power
- 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
- Fluid, fuel › Vapor lock
- Fuel system, strainer › Open
- Pilot in command(cfi) › Aircraft preflight, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After the airplane was preflighted, the SP started the engine, and taxied the airplane for takeoff. After checking both magnetos, the SP executed the takeoff. The airplane accelerated normally, but after, but approximately 60 feet above the ground, the CFI felt a loss of power. He took control of the airplane, extended the flaps, and started to slip the airplane. While slipping the airplane, the CFI confirmed that the primmer was in, the fuel pump was on, and the fuel selector was on the right tank. The airplane touched down passed the departure end of the runway then went over a 30 foot drop-off nose first. No mechanical failures were detected when the engine was examined. The fuel strainer was found locked in the open position, which would allow the engine fuel pump to suck air. The pilot's operating hand states that during the preflight the pilot should drain the fuel strainer.
Probable cause
The pilot's inadequate preflight inspections which failed to detect an open fuel strainer valve, which resulted in a loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99LA003
- Event ID
- 20001211X11328
- Case number
- NYC99LA003
- 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. 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: fdd21dcdf94deb6aee2822453b5b9fb7a839645ccb373c907fbe93d9f38d7761; retrieved 2026-09-22T16:35:14.511Z.