FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX97FA217 · Piper PA 31-310

20 Jun 1997 · San Diego, CA, United States

Piper PA 31-310 · Accident: loss of engine power during initial climb

From Brown Field Municipal Airport (SDM) to Montgomery-Gibbs Executive Airport (MYF)

Report a problem

Event

NTSB case
LAX97FA217
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
3 · 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 31-310

Aircraft type
Piper PA-31
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
N266MM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Brown Field Municipal Airport (SDM)To Montgomery-Gibbs Executive Airport (MYF), CA
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
Destroyed

Cause areas

  • Pilot in command › Airspeed(vmc), not maintained
  • Reason for occurrence undetermined

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

NTSB narrative

The aircraft concluded an aerial survey and landed at Brown Field to clear U.S. Customs. On restart, as the left engine began running, a witness noticed two short, yellow flame bursts exit the exhaust. During taxi, the witness heard a popping sound coming from the aircraft. As power was applied to cross runway 26L, the sound went away. The aircraft stopped for a few seconds prior to pulling onto the runway; the witness did not observe or hear a run-up. Witnesses reported hearing a series of popping sounds similar to automatic gunfire and observed the aircraft between 600 and 1,000 feet above the ground with wings level and the landing gear up. The aircraft was observed to make an abrupt, 45-degree banked, left turn as the nose dipped down. Witnesses reported the nose of the aircraft then raised up toward the horizon. This was followed by the aircraft turning to the left and becoming inverted in an estimated 30-degree nose low attitude. With the nose still low, the aircraft continued around to an upright position and appeared to be in a shallow right bank. Witnesses then lost sight of the aircraft due to buildings and terrain. A May 20, 1997, work order indicated the left manifold pressure fluctuated in flight. Both wastegates were lubricated and a test flight revealed the left engine manifold pressure lagged behind the right engine manifold pressure. On June 18, 1997, the left engine differential pressure controller was noted to have been removed and replaced. This was the corrective action for a discrepancy write up that the left engine manifold pressure fluctuated up and down 2 inHg and the rpm varied by 100 in cruise. A test flight that afternoon by the accident pilot indicated the discrepancy still occurred at cruise power settings, but the engine operated normally at high and low power settings. Postaccident functional checks were performed on various components. No discrepancies were noted for the left governor. The left engine differential pressure controller was damaged and results varied on each test. The left density controller was too damaged to test. The right engine density and differential pressure controllers tested satisfactory. The left and right fuel pumps operated within specifications. Both fuel servos were damaged. One injection nozzle on the left engine was partially plugged; all others flow tested within specifications.

Probable cause

The loss of power in the left engine for undetermined reasons and the pilot's subsequent failure to maintain minimum single-engine control airspeed. A contributing factor was the pilot's decision to fly with known deficiencies in the equipment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX97FA217
Event ID
20001208X08160
Case number
LAX97FA217
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: badcf920d59873c9ee650042b27cf444b1e98721085440a2d77dc013cac6aab7; retrieved 2026-09-20T22:55:19.920Z.