FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX93LA373 · Piper PA-28-140

30 Sept 1993 · Lompoc, CA, United States

Piper PA-28-140 · Accident: total loss of engine power (non-mechanical) during initial climb

Report a problem

Event

NTSB case
LAX93LA373
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
N430FL
Operator
Patrick A. Marshall · private individual
Onboard fatalities
Unknown
Route
From not recordedTo 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
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 starvation
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 › Starvation

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, during initial climb on the maintenance test flight the airplane gained between 250 and 300 feet altitude when the engine backfired two times and quit. The pilot stated that he turned the airplane to avoid colliding with obstacles and crashed into a plowed wet field. Exam of the airframe and engine did not reveal any mechanical failures. Fuel was found in both fuel tanks and the fuel pumps were found functional. No fuel was found in the carburetor. Prior to the accident flight, the pilot, who was also an A & P mechanic, had performed maintenance on the airplane. The last annual inspection had been completed over seven years earlier, and the airplane had not been flown since that time.

Probable cause

was fuel starvation. A factor in the accident was the mechanic's inadequate inspection of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX93LA373
Event ID
20001211X13446
Case number
LAX93LA373
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: aa9281267ff2b66cbc478634f5fe95568dd57eb9e814c73e908169b6aeb9dd2b; retrieved 2026-09-21T22:47:42.055Z.