FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC20FA024 · Cessna 305 A

22 Feb 2020 · Mokuleia, HI, United States

Cessna 305 A · Accident: loss of control in flight during initial climb

From Kawaihapai Airfield (HDH) to Kawaihapai Airfield (HDH)

Report a problem

Event

NTSB case
ANC20FA024
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
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 305 A

Aircraft type
Cessna 305
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
N65070
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kawaihapai Airfield (HDH), Mokuleia, HITo Kawaihapai Airfield (HDH), Mokuleia, HI
Aircraft age
About 41 years (built 1979)
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
Initial climb
Defining eventThe 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
Loss of control in flight
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

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

NTSB narrative

The flight instructor was providing familiarization training to the airline transport pilot in the tailwheel-equipped airplane. Witnesses saw the airplane land hard; the pilots shut down the engine on the runway, the instructor got out and inspected the airplane, then boarded the airplane again and the pilots subsequently departed. The witnesses stated that, upon becoming airborne, the airplane entered a significant right yaw over the runway. The airplane continued to the right and subsequently impacted terrain about 1,000 ft from the runway.

Examination of the engine revealed no anomalies that would have precluded normal operation. Examination of the airframe revealed that the left rudder cable was separated at the rudder pulley area behind the rear seat floor and displayed a combination of severely frayed and fractured strands with tension overload signatures. There was evidence of cable abrasions and rubbing in the area of the pulley bracket. A detailed examination of the cable fractures revealed that only 16 of the 133 total wires that comprised the cable were intact before they failed in overload, resulting in cable separation. The remainder of the cable strand wires were either degraded, shortened, or bent, indicative of abnormal cable contact and abrasion. Although the aileron and elevator control cables were continuous or displayed indications of overload separation due to impact, all of the cables exhibited areas of fraying and extensive wear.

The most recent documented maintenance was a 100-hour inspection completed 5 months before the accident. The mechanic who had been responsible for maintaining the airplane for the previous 2 years stated that he cleaned, inspected, and lubricated the flight control cables during the inspection; however, the debris in the under-floor compartment, excessive black grease deposits, significant wear and fractured wires of each control cable were indicative of wear that had occurred over a period of time that should have been observed and rectified during previous inspections.

Based on witness statements and examination of the wreckage, the pilots experienced a loss of yaw control after takeoff due to an overload separation of the left rudder cable and were unable to regain adequate control to land safely. Although when the separation occurred could not be determined, it is possible that the hard landing just before the accident takeoff may have caused the already degraded rudder cable to be displaced and encounter excessive stress loads in the pulley area.

Probable cause

A separation of the left rudder cable due to inadequate maintenance, which resulted in an in-flight loss of control and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC20FA024
Event ID
20200223X34938
Case number
ANC20FA024
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 59a02fdc4c5c2e2c024b5f94c505fe60720587fd736a9339bc64dcf738346421; retrieved 2026-09-15T07:12:09.647Z.