NYC97LA100 · Piper PA-28-140
Piper PA-28-140 · Accident: total loss of engine power (non-mechanical) during initial climb
From Martin State Airport (MTN) to Bay Bridge Airport (W29)
Event
- NTSB case
- NYC97LA100
- 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-28-140
- 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
- N6927W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Martin State Airport (MTN)To Bay Bridge Airport (W29), Stevensville, MD
- 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
- Total loss of engine power (non-mechanical)
- 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
- 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
- Fluid, fuel › Contamination, water
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After takeoff, at an altitude of about 300 feet AGL, the engine lost power. The pilot turned the airplane 30 degrees left and landed on the grass near the runway. During the ground roll, the airplane went through a ditch and struck a chain link fence. The airplane was secured by emergency personnel who drained the fuel tanks. The next morning the pilot checked the airplane and found the fuel tanks empty. He drained the main sump and only water was found. The pilot reported that the day prior to the accident it had rained hard all day, and the airplane was tied down outside. He also reported that he did not drain the tanks before the flight.
Probable cause
the pilot's inadequate preflight of the airplane which failed to detect water in the fuel, and resulted in a power loss after departure due to fuel contamination.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA100
- Event ID
- 20001208X08006
- Case number
- NYC97LA100
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1997-05-27.
- API snapshot SHA-256: aca93ea399a38a47152522be54ee8511c2ba621787f865084fff802e1b75de9b; retrieved 2026-09-22T19:34:02.574Z.