FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC03IA037 · Cessna 206

28 Feb 2003 · Homer, AK, United States

Cessna 206 · Incident: airframe, component or system failure during landing

From Homer Airport (PAHO) to BRADLEY LAKE, AK

Report a problem

Event

NTSB case
ANC03IA037
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
Incident
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
Charter & commuter
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 206

Aircraft type
Cessna 206
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
N8337Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Homer Airport (PAHO), Homer, AKTo BRADLEY LAKE, AK
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 135: Air Taxi & Commuter
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
Minor

Cause areas

  • Landing gear, main gear spring › Corroded
  • Landing gear, main gear spring › Fatigue
  • Landing gear, main gear spring › 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 airline transport certificated pilot was landing a nose wheel-equipped airplane at a remote gravel surfaced airstrip during a VFR air taxi flight. The airplane landed hard, and the right main landing gear, a spring steel strut, fractured and separated from the fuselage just outboard of the landing gear fuselage support clamp. The airplane settled onto the belly-mounted cargo pod and sustained minor damage. The airplane had accrued about 17,120 total flight hours. The right main gear was replaced in 1994, at an aircraft total time of 11,848 hours, with a "serviceable unit." Visual examination of the fracture surface revealed beach marks radiating in successive arc patterns from mulitple locations, along the underside of the gear strut. A metallurgical examination revealed that the landing gear spring had two different layers of paint. Multiple fatigue crack initiation sites, coinciding with corrosion pits, were found along the lower surface of the gear. Particles in the pits contained titanium, a component of paint, indicating the corrosion pits were present at the time the gear was painted. Periodic visual inspection of the landing gear is required by 14 CFR Part 43. Neither the manufacturer nor the FAA have established time in service limits (hours or cycles) for the main landing gear strut. Removal of the gear strut for inspection, or the use of nondestructive inspection techniques is not required by the manufacturer or the FAA. On March 16, 2001, the NTSB recommended that the FAA issue an airworthiness directive (AD) to require an initial and recurring inspection of Cessna main landing gear spring steel struts, using nondestructive inspection techniques. On August 31, 2001, the FAA reported to the NTSB that the current inspection criteria outlined in the Cessna Maintenance Manual are adequate to detect cracks in the main landing gear struts, and that additional airworthiness action is not warranted. On March 25, 2002, the NTSB responded by stating, in part: "The Safety Board continues to believe that a visual inspection alone will not detect cracks in the Cessna main landing gear spring struts. However, the Safety Board acknowledges that the statistical evidence does not warrant issuance of ADs at this time as called for in the Board's recommendation." The safety recommendation was then classified as: "Closed-Reconsidered."

Probable cause

The separation of the main landing gear spring strut during landing touchdown due to corrosion and fatigue. Factors contributing to the accident were the manufacturer's and the FAA's insufficient standards/requirements for inspection procedures.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC03IA037
Event ID
20030408X00455
Case number
ANC03IA037
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-03-01.
  • API snapshot SHA-256: 2b4ca994475e598975e69eb805313c2f0e9c39f8e93e2fd5fde6fdd709228cc8; retrieved 2026-09-18T15:54:31.047Z.