Yute Air Alaska Cessna 207A accident
Cessna 207A · Accident: loss of control on ground/water during takeoff
From Bethel Airport (BET) to Kongiganak Airport (DUY)
Event
- NTSB case
- ANC01LA017
- 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
- 0
- 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 207A
- Aircraft type
- Cessna 207
- 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
- N7336U
- Operator
- Yute Air Alaska
- Onboard fatalities
- Unknown
- Route
- From Bethel Airport (BET)To Kongiganak Airport (DUY), KONGIGANAK, 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
- Takeoff · roll/run
- 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
- Loss of control on ground/water
- 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
- Pilot in command › All available runway, not used
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The certificated commercial pilot was departing runway 29, from intersection Echo. He noted that the gravel runway had a light accumulation of heavy, wet snow/slush, and estimated about 1,500 feet of runway remained from intersection Echo. During the departure roll, the airplane veered to the left, and he applied full right rudder to correct the veer. He was unable to correct the veer, so he closed the throttle, aborted the takeoff, and applied maximum braking. The airplane ran off the end of the runway, down an embankment, and struck a chain link fence. The airplane sustained substantial damage to both wings. Airport personnel reported that when departing runway 29 from intersection Echo, the published usable runway remaining is 1,350 feet. The published usable full-length of runway 29, is 1,850 feet. At the time of the accident winds were reported to be from 093 degrees (magnetic) at 9 knots.
Probable cause
The pilot's failure to use all available runway. Factors associated with the accident were the pilot's inadequate preflight planning/preparation, a short runway, a tailwind, and a slush-covered runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC01LA017
- Event ID
- 20001226X45474
- Case number
- ANC01LA017
- 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: 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: 8bce6642a05ee2f995d67f06fa8df3bc9eaee3bd0d8a8639c0a133d0e133d1db; retrieved 2026-09-18T16:21:15.548Z.