LAX04FA042 · Cessna 177RG
Cessna 177RG · Accident: total loss of engine power (mechanical failure) en route
From Flagstaff Pulliam Airport (FLG) to Phoenix Deer Valley Airport (DVT)
Event
- NTSB case
- LAX04FA042
- 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
- 1 · 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 177RG
- Aircraft type
- Cessna 177
- 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
- N431DL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo Phoenix Deer Valley Airport (DVT), Phoenix, AZ
- 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
- Total 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
- Destroyed
Cause areas
- Ignition system, ignition points › Not operating
- Ignition system, magneto › Improperly serviced
- Other maintenance personnel › Maintenance, inspection, improper
- Other maintenance personnel › Maintenance, lubrication, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During cruise flight over mountainous terrain, a loss of engine power occurred and the airplane impacted trees during the subsequent forced landing attempt. The pilot radioed air traffic control personnel that the engine was losing power and would not sustain flight. He was attempting to make it to an airport when the airplane impacted trees in mountainous terrain. An airframe inspection was conducted with no discrepancies noted that would have precluded normal operation. The engine was equipped with a single-drive dual magneto that remained secure at its mounting pad. During manual rotation of the crankshaft, investigators could hear the "snapping" of the coupling, but no spark was observed at any of the leads. Magneto-to-engine timing could not be established because the contacts were not breaking electrical continuity. A functional check by the magneto manufacturer revealed that both magneto primary circuits had short-circuited to ground in all magnet positions, which was consistent with the breaker points not opening. Disassembly revealed that the plastic cam followers were melted and smeared in the direction of normal cam rotation. The breaker cams, made of sintered iron material, are supposed to be impregnated with oil per the service manual or production instructions for lubrication purposes at each overhaul. The oil lubricates the surface of the breaker cams over the cams service life. Four months prior to the accident the single-drive dual magneto had been removed, and the mechanic at a local fixed based operator had internally timed the magneto, then had completed a ground run and full operational check. The accident flight occurred 38.2 hours after this maintenance operation. According to the manufacturer, to internally time the magneto, maintenance personnel have to partially disassemble the magneto and physically touch the cam and breaker points. In accordance with the Service Support Manual instructions for the magneto, during this process the breaker cams and contact points should be inspected for lubrication, wear, burning, or melting. The on-scene examination revealed that the pilot was not wearing his shoulder harness, which remained stowed in the stowage sheath above the pilot's cabin door. The airframe manufacturer indicated that the airplane had been delivered new in 1975 with shoulder harnesses as standard equipment for the pilot and co-pilot. The coroner listed the cause of death as blunt force craniocerebral trauma due to an airplane crash.
Probable cause
a loss of engine power due to the failure of the single-drive dual magneto that resulted from inadequate lubrication of the breaker cam. Also causal was the improper maintenance by other maintenance personnel during a recent inspection, which should have detected the lubrication deficiency. A contributing factor in the accident that likely exacerbated the pilot's injuries was his decision not to wear the installed shoulder harness.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04FA042
- Event ID
- 20031126X01957
- Case number
- LAX04FA042
- 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: be2bbf190a431d0e82f5b587812b6dea4efbe8103bf5b377b2c439a4ee83a4bb; retrieved 2026-09-20T18:48:10.761Z.