Corporate Air Cessna 208B accident
Cessna 208B · Accident: loss of control on ground while taxiing
From Southwest Wyoming Regional Airport (KRKS) to KCRP · Casper, WY
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR09CA067
- 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 208B
- Aircraft type
- Cessna 208
- 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
- N890FE
- Operator
- Corporate Air
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Southwest Wyoming Regional Airport (KRKS), Rock Springs, WYTo KCRP · Casper, WY
- 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
- Taxi · to runway
- 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 reported that the pilot taxied the high-wing airplane from the ramp along the parallel taxiway to the active runway (27) with a quartering tailwind. He reported that when the pilot initiated a turn to the right at the taxiway intersection, the airplane did not respond to the control inputs and continued straight ahead. The pilot applied full right brake and rudder; however, the airplane continued to track forward and exited the hard surface taxiway. The airplane continued off the taxiway and traveled an additional 80 feet through rough terrain before it came to rest in a nose-down attitude. The airplane sustained substantial damage to the right wing. Winds at the time of the accident were from 260 degrees at 27 knots, gusting to 38 knots. No preaccident mechanical malfunctions or failures were reported with the control system or brakes.
Probable cause
The pilot's failure to maintain control of the airplane while taxiing. Contributing to the accident were the gusty winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA067
- Event ID
- 20081228X24007
- Case number
- WPR09CA067
- 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: 52ba12df0517fc15cae0ff55f97601e4ca7c99c9354533a742c8acf91d7f88ef; retrieved 2026-09-15T10:38:17.107Z.