FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Rustair Cessna U206G 200 accident

23 May 2016 · Chinita Bay, AK, United States

Cessna U206G 200 · Accident: dragged wing/rotor/float/other while taxiing

From Lake Hood Seaplane Base (PALH) to Chinita Bay, AK

Report a problem

Event

NTSB case
GAA16CA272
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 U206G 200

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
N4596U
Operator
Rustair
Onboard fatalities
Unknown
Route
From Lake Hood Seaplane Base (PALH), Anchorage, AKTo Chinita Bay, AK
Aircraft age
About 37 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 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
Taxi
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
Dragged wing/rotor/float/other
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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, after landing he taxied the tri-cycle landing gear-equipped airplane on a rocky, soft sand beach and the nose wheel bounced off of a sand berm. He reported that when the nose wheel bounced, the tail section contacted the ground. He recalled that he parked the airplane, inspected the empennage and determined the damage to be minor, and departed on a subsequent flight. However, a subsequent inspection of the empennage by the company's mechanic revealed that the aft fuselage bulkhead had sustained substantial damage.

The pilot reported that prior to the taxi there were no mechanical malfunctions or anomalies with the airplane or any of its systems that would have prevented normal flight operations.

Probable cause

The pilot's selection of unsuitable terrain for taxi, resulting in a tail strike and aft fuselage substantial damage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA272
Event ID
20160602X32125
Case number
GAA16CA272
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: 1502c86d610ebc709b7e7ad68a70edf79a8951fc19fe2a857cd9719727e46bf0; retrieved 2026-09-16T03:27:22.546Z.