FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX96LA167 · Maule M-5-235C

13 Apr 1996 · LAKE HAVASU CTY, AZ, United States

Maule M-5-235C · Accident: partial loss of engine power (mechanical failure) en route

From Laughlin Bullhead International Airport (IFP) to Lake Havasu City Airport (HII)

Report a problem

Event

NTSB case
LAX96LA167
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

Maule M-5-235C

Aircraft type
Maule M-5
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
N9177E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Laughlin Bullhead International Airport (IFP), BULLHEAD, AZTo Lake Havasu City Airport (HII)
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
En route · cruise
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
Substantial

Cause areas

  • Engine assembly, valve, intake › Open
  • Ignition system, distributor › Failure
  • Ignition system, ignition points › Fouled
  • Ignition system, magneto › Failure, partial
  • Owner/pilot mechanic › Maintenance, inadequate

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

NTSB narrative

The pilot owned and operated the seaplane and had flown it for 803 hours. During the dark nighttime cruise flight, the engine began surging and then gradually lost power. The pilot planned to make a forced landing at the shoreline of the Colorado River; however, during landing the airplane slid on the grass bank and impacted a 3-foot-high tree trunk. The airplane was subsequently examined, and the following discrepancies were found: (1) Sediment was observed in the fuel filter and carburetor; (2) The number 3 cylinder intake valve was found open and stretched in excess of 0.200 inches; (3) No compression was obtained from the number 3 cylinder; (4) The engine oil was black in color; (5) The magneto's drive end seal bearing was found leaking oil; (6) The left set of points were oil fouled, and the right set of points had oil on the contacts and were coked up; and (7) The left distributor gear was missing a gear tooth.

Probable cause

the pilot-owner's inadequate engine maintenance which resulted in a progressive ignition failure. Factors which contributed to the accident were the dark nighttime light condition and the presence of hidden obstructions in the forced landing area.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX96LA167
Event ID
20001208X05612
Case number
LAX96LA167
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 1996-04-14.
  • API snapshot SHA-256: 966bee4d87acb3a28e723f44c08404243722becfc3b06bce40f908a6f44e39ee; retrieved 2026-09-22T22:38:21.096Z.