LAX02LA172 · Cessna 172K
Cessna 172K · Accident: partial loss of engine power (mechanical failure) en route
From Reedley Municipal Airport (O32) to Milford Municipal-Ben and Judy Briscoe Field (MLF)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX02LA172
- 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
- Unknown
- 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
Cessna 172K
- Aircraft type
- Cessna 172
- 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
- N79944
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reedley Municipal Airport (O32), Reedley, CATo Milford Municipal-Ben and Judy Briscoe Field (MLF), Milford, UT
- 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 · climb to 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)
- 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
- Tree(s)
- 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
- Ignition system, ignition harness › Leak
- Ignition system, magneto › Failure, partial
- Other maintenance personnel › Maintenance, inspection, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane experienced a partial loss of engine power and collided with a tree stump during a precautionary landing on a beach. While climbing through 9,000 feet mean sea level (msl) the pilot leaned the airplane by relying solely on the exhaust gas temperature gauge. When reaching about 9,500 feet msl, about 1,500 feet above ground level over mountainous terrain, the pilot reported that the engine lost partial power. The propeller continued to turn, and the tachometer showed about 2,450 to 2,500 rpm, but the engine failed to produce enough power to sustain level flight. The pilot adjusted the mixture control, while also turning the carburetor heat to the on position, and applying full throttle. The engine failed to respond and the pilot made an approach to a sandy beach. The pilot flared the airplane about 2 feet above ground level, and the left wing collided with a tree stump, veering the airplane to the right. The elevation at the crash site was about 7,600 feet msl. A post accident investigation revealed that the left magneto exhibited excessive play at the cam end (points) of the main shaft. The subject magneto was later functionally tested, which revealed an intermittent spark on ignition lead T1. According to Textron Lycoming Mandatory Service Bulletin 515 the magnetos must be inspected every 500 hours. At the time of the accident, the magneto had accumulated a total time in service of 1,540.23 hours, and there was no maintenance entry indicating that the Service Bulletin had been complied with. While post accident tests showed that the left magneto was working only on an intermittent basis, information provided by Lycoming suggests that in and of itself the complete loss of one magneto would only result in a 3 to 5 percent loss of power. It is likely that the combined effects of the magneto malfunction, the high density altitude, and the pilot's manipulation of the mixture and carburetor heat all played roles in the engine's decreased performance capability.
Probable cause
a partial loss of engine power due to the partial malfunction of the left magneto and leakage of the ignition leads for that magneto, due to inadequate maintenance inspections. Factors in the accident include the high density altitude, the maintenance personnel's failure to accomplish a service bulletin, and the effects of the pilot's manipulation of the mixture and carburetor heat controls.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA172
- Event ID
- 20020530X00781
- Case number
- LAX02LA172
- 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: 2d8f6f8d45e6f3b488ab8fff6e149b0d5a324096e4607acc8c079f34cc2f01d6; retrieved 2026-09-21T09:39:11.122Z.