WPR09CA084 · Cessna U206E
Rugby Aviation Cessna U206E · Accident: loss of control on ground during landing
From Friday Harbor Airport (FHR) to Crane Island, WA (no airport)
Narrative check · The NTSB narrative appears to contradict this record's flight rules. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR09CA084
- 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 U206E
- 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
- N9428G
- Operator
- Rugby Aviation
- Onboard fatalities
- Unknown
- Route
- From Friday Harbor Airport (FHR), Friday Harbor, WATo Crane Island, WA (no airport)
- 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 Possible conflict
- 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
- Loss of control on ground
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The operator's Director of Operations reported that the flight was dispatched from their home base to pickup a waiting passenger for a flight under their 14 Code of Federal Regulations Part 135 operating certificate. Upon arriving over the airstrip, the pilot made a traffic pattern approach and observed that the wind was calm. The pilot stated that his airspeed and approach path were approximately normal and that he was familiar with the airstrip, having landed there in a southerly direction on previous days. The airplane touched down near the beginning of the short, 1,350-foot-long grass runway. The pilot further reported that he used light to firm brake pressure and that the airplane began sliding. He stated that the south portion of the runway (near its departure end) was soggy. He attempted a rapid left turn to avoid encountering the drop-off adjacent to the runway's end. As the airplane turned left, the right wing dipped down, impacted the ground, and broke. The Cessna Aircraft Company's "Landing Distance Table" in the U206 operating handbook provides guidelines for ascertaining the approximate landing distance needed under various conditions. The performance data in the handbook indicated that on a dry grass runway, a distance of at least 897 feet is needed to stop the airplane. The table data does not provide distance information for a "soggy" wet grass runway.
Probable cause
The pilot's failure to maintain directional control during landing. Contributing to the accident was the pilot's improper application of brakes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA084
- Event ID
- 20090115X12631
- Case number
- WPR09CA084
- 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. 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: f67aab51f16c2f2d98644b56d8167aa31bec32042fae59649d6af7947633edcd; retrieved 2026-09-15T10:41:35.001Z.