FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX93FA141 · Piper PA-32RT-300 PA-32RT-30

7 Mar 1993 · Big Bear City, CA, United States

Piper PA-32RT-300 PA-32RT-30 · Accident: partial loss of engine power (mechanical failure) during takeoff

From L35 to Montgomery-Gibbs Executive Airport (MYF)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
LAX93FA141
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
2 · 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-32RT-300 PA-32RT-30

Aircraft type
Piper PA-32
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
N2221G
Onboard fatalities
Unknown
Route
From L35To Montgomery-Gibbs Executive Airport (MYF), San Diego, 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
Takeoff · roll/run
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
Partial loss of engine power (mechanical failure)
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

  • Company maintenance personnel › Maintenance, 100-hour inspection, inadequate
  • Ignition system, ignition points › Incorrect
  • Ignition system, magneto › Incorrect
  • Ignition system, spark plug › Incorrect
  • Ignition system, spark plug › Worn
  • Pilot in command › Aborted takeoff, not performed

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

NTSB narrative

DURING TAKEOFF, THE AIRPLANE WAS HEARD TO REDUCE POWER AT MID-FIELD, THEN FULL POWER WAS APPLIED. IT CLIMBED TO ABOUT 6 FT, SETTLED BACK ONTO THE RWY, CLIMBED AGAIN TO 6 FT, SETTLED AGAIN, THEN CONTINUED ITS TAKEOFF ROLL USING MOST OF THE 5,850-FT RWY UNTIL REACHING THE ARPT PERIMETER FENCE. IT CLIMBED TO ABOUT 20 FT AGL, THEN SETTLED INTO A HOUSE. THE DENSITY ALTITUDE WAS 7,800 FT. ENGINE EXAMINATION REVEALED THAT THE MAGNETO-TO-ENGINE TIMING WAS OFF, THE MAGNETO INTERNAL TIMING WAS OFF ON BOTH SETS OF POINTS, AND BOTH POINT GAPS WERE OFF. IN ADDITION, 5 OF THE 12 SPARK PLUGS WERE FOUND TO HAVE WORN ELECTRODES. ONE SPARK PLUG WAS NOT APPROVED FOR THE ENGINE. A 100-HR INSPECTION HAD BEEN COMPLETED ON 2/2/93, ABOUT 17 FLIGHT-HOURS BEFORE THE ACCIDENT.

Probable cause

A PARTIAL LOSS OF TAKEOFF POWER DUE TO INADEQUATE MAINTENANCE AND INSPECTION WHICH FAILED TO DETECT MAGNETO AND SPARK PLUG DEFICIENCIES. IN ADDITION, THE PILOT FAILED TO ABORT THE TAKEOFF AFTER TWO UNSUCCESSFUL ATTEMPTS TO GET AIRBORNE. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE: THE HIGH DENSITY ALTITUDE AND THE PILOT'S LACK OF PILOTING EXPERIENCE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX93FA141
Event ID
20001211X11994
Case number
LAX93FA141
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: 9e5aad58970cc205120c5a973ec466485d8560a5722f271c4fb24eed72b554a4; retrieved 2026-09-21T00:40:02.891Z.