FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04LA194 · Cessna 205

17 Apr 2004 · Page, AZ, United States

Cessna 205 · Accident: airframe, component or system failure during landing

From 3V5 · Fort Collins, CO to Page Municipal Airport (PGA)

Report a problem

Event

NTSB case
LAX04LA194
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 205

Aircraft type
Cessna 205
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
N1815Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From 3V5 · Fort Collins, COTo Page Municipal Airport (PGA), Page, 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
Landing · flare/touchdown
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
Airframe, component or system 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

  • Flt control syst, yoke/control stick › Fatigue
  • Flt control syst, yoke/control stick › Separation

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane landed hard after the pilot's control wheel fractured and separated in the landing flare. The pilot said that as he was adding back pressure to flare the airplane his control wheel fractured and separated at the upper left corner. The airplane's nose dropped rapidly and impacted the runway surface first, resulting in the airplane bouncing back into the air. The pilot repositioned his hand behind the broken wheel to the control column and manipulated the broken control yoke forward in an effort to maneuver the airplane back down to the runway surface; the nose landing gear bent and the propeller impacted the runway. The airplane was manufactured in 1962 and equipped with a polymeric control wheel. A metallurgical examination of the fracture surface on the control wheel revealed smooth crack arrest markings along with bands of slightly different colors, indicative of fatigue cracking. The location of the fracture indicated that the fatigue crack propagated as a result of tensile stress from the continual force of the pilot manipulating the control wheel forward and aft. The discoloration and crazing gave evidence of aging effects. The fatigue cracks likely initiated from age related crazed cracks in an area of maximum tensile stresses. The dirt and discoloration of the fracture (and the adjacent cracks and/or crazes), along with the depth of the fatigue crack would suggest that the crack has been in existence for a relatively long time (years, perhaps). Although the fatigue crack would not have been visible from the pilot's viewpoint, it occurred in an area where cracking would be most likely to occur based on the geometry of the yoke. The airplane underwent its last annual inspection 17.76 hours prior to the accident. The airplane manufacturer issued a Service Letter in1964 requiring a one time inspection and proof testing of applicable control wheels. The Service Letter further stated that once control wheels were checked, no further control wheel inspection was required. To show compliance with the Service Letter, a red dot was to be placed on the forward rivet butt on the bottom of the yoke. Both control wheels installed on the accident airplane showed evidence of a red material within the forward rivet butt, indicating that the inspections dictated by the Service Letter were previously preformed. The Federal Aviation Administration issued a Special Airworthiness Information Bulletin (SAIB) in 2001 recommending that during periodic (100-hour or annual) inspections "special emphasis" should be placed on the original plastic control wheels installed in applicable airplanes. If crack indications were "unclear," it recommended that a test be performed in accordance with the manufacturer's Service Letter. The SAIB does not provide a specific location or guidance as to the visual indicators where the cracks are likely to propagate. A review of the Service Difficulty Report (SDR) database revealed a history of 18 control wheel failures in the applicable airplanes, of which a majority reported failures that occurred during a critical phase of flight, including: takeoff, initial climb, spin recovery, and landing flare. Five of the reported failures occurred after the issuance of the SAIB.

Probable cause

the fatigue fracture and separation of the pilot's control wheel, which resulted in a momentary loss of control and a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04LA194
Event ID
20040506X00571
Case number
LAX04LA194
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, coordinates. 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: 63d976b26fafe05d57c75664d59e6e10726cee31cd8c9da0dc0b1ea7c1347130; retrieved 2026-09-22T07:43:35.346Z.