Mechanical & Engine Failure · NTSB WPR21FA048

CESSNA 182 — Los Angeles, CA

1 fatal
DateNovember 12, 2020
LocationLos Angeles, CA
AircraftCESSNA 182
Purpose of flightPositioning
ConditionsDay · Visual Meteorological Cond
Phase / occurrenceApproach Loss of engine power (total)
Pilot age59
Pilot total timeUnknown
Time in typeUnknown
Fatalities1

Probable cause

Maintenance personnel’s failure to properly secure the throttle control hardware during recent maintenance, which resulted in its disconnection and a subsequent loss of engine power on approach for landing.

NTSB findings

  • Aircraft-Aircraft power plant-Engine controls-Power lever-Failure
  • Personnel issues-Task performance-Inspection-Scheduled/routine inspection-Maintenance personnel
  • Environmental issues-Physical environment-Object/animal/substance-Wire-Effect on equipment

What happened

While on final approach to the runway, the pilot reported to the tower controller a loss of engine power, and that he was attempting to make the runway. Shortly thereafter, the airplane collided with power lines in a residential area about 175 ft short of the runway threshold. A postaccident fire consumed the wreckage.

Postaccident examination of the wreckage revealed that the engine’s throttle control rod was separated from the throttle body control arm. None of the attachment hardware, which comprised of a bolt, washer, castellated nut, and cotter pin, was found. Additionally, no evidence of impact damage was noted in the throttle lever linkage control rod end or the control arm where it attached. The airplane’s most recent annual inspection was 78 flight hours and about 2 months before the accident. During the inspection, a new engine was installed. Based on the available information, it is likely that the throttle control connecting hardware was improperly installed or secured during the most recent maintenance, which resulted in its disconnection and a loss of engine power and throttle control while on final approach.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →