K Bay Air Cessna U206 F accident
Cessna U206 F · Accident: part(s) separation from aircraft during landing
From Homer Airport (PAHO) to Pedro Bay, AK
Event
- NTSB case
- ANC18LA067
- 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
- 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 U206 F
- 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
- N441GR
- Operator
- K Bay Air
- Onboard fatalities
- Unknown
- Route
- From Homer Airport (PAHO), Homer, AKTo Pedro Bay, AK
- Aircraft age
- About 46 years (built 1972)
- 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 · landing roll
- 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
- Part(s) separation from aircraft
- 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 systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, before landing on the tidal beach, he conducted two passes over the landing area to check for debris and determine wind direction. He stated that, after touchdown on the beach, the airplane felt like it had a flat tire and subsequently veered to the right. The airplane came to rest in a left-wing-low attitude on a tidal mudflat and sustained substantial damage to the left wing, left horizontal stabilizer, and left elevator.
The pilot examined the airplane and noted that both main landing gear legs had separated just above the main axle attach point. A laboratory examination revealed that both main landing gear legs failed due to fatigue cracking.
Probable cause
The fatigue fracture of both main landing gear legs during the landing roll, which resulted in the collapse and separation of both main landing gear legs.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC18LA067
- Event ID
- 20180828X64220
- Case number
- ANC18LA067
- 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, 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: 9483896ff0052086f6e262f37b7633791fbcc2c7d75b9c7d7c5d2c3477a6bd6a; retrieved 2026-09-16T08:10:21.733Z.