Warbelow'S Air Ventures Flight 911
Cessna 206 · Accident: airframe, component or system failure during initial climb
From 5S8 · St. Michael, AK to Stebbins Airport (WBB)
Event
- NTSB case
- ANC01LA057
- 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 206
- 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
- N756DJ
- Operator
- Warbelow'S Air Ventures
- Onboard fatalities
- Unknown
- Route
- From 5S8 · St. Michael, AKTo Stebbins Airport (WBB), Stebbins, 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
- Initial climb
- 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
- Airframe, component or system failure
- 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
- Company maintenance personnel › Maintenance, inadequate
- Electrical system, electric wiring › Entangled
- Flt control syst, yoke/control stick › Jammed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The solo certificated commercial pilot was departing for another airport about 5 miles away. During the takeoff roll, as the airplane's airspeed approached 60 knots, the pilot applied aft control yoke pressure to rotate the nose of the airplane. When the desired pitch angle for takeoff was attained, she released the back pressure, but the yoke failed to move forward. The airplane then pitched-up uncontrollably, and she disengaged the electric trim, as she was concerned about a runaway trim condition. She regained control of the airplane, noted that she had very limited aileron and elevator range of motion available, and elected to continue straight ahead to her next scheduled stop. She added that she tried to transmit a "mayday" to other airplane’s in the area, but the radio transmit button, located on the pilot's control yoke, was now inoperative. During the short flight, she was able to adjust the altitude and airspeed by adjusting engine power. During approach to the accident airport, while using a combination of engine power, rudder, and the remaining amount of aileron control, she was able to maneuver the airplane for landing on runway 05. As the airplane passed over the approach end of the runway, she attempted to flare just before touchdown. The nose of the airplane failed to rise, and the nose wheel struck the gravel-covered runway. The nose landing gear collapsed, and the airplane bounced off the right side of the runway. A postaccident examination of the control yoke mechanism, behind the instrument panel, revealed that a wiring harness had become entangled in a series of roller bearings associated with the control yoke mechanism. A subsequent inspection revealed that the accident airplane's control column did not have a required STA-Strap, part number S-2209-2, installed. The proper installation of the required STA-Strap would provide proper clearance between the wiring harness, and the control yoke roller bearings. The roller bearing assembly was disassembled, and the entangled wiring harness was removed. The correct length for the factory installed wiring harness is 49 inches. The wiring harness that was removed from the roller bearing assembly measured at 34 inches. A review of the airplane's maintenance history disclosed no maintenance activity concerning the control yoke assembly. A review of the FAA's aircraft registry database disclosed that the operator owned the airplane for about 11 years. The airplane had been added to the operator's Approved Aircraft Inspection Program (AAIP), on February 11, 2001. In order for an airplane to be initially placed on the AAIP, it must be inspected in accordance with AAIP Events1, 2, 3, and 4. According to the operator's AAIP inspection schedule, an inspection of the control wheels, columns, pulleys, and cables, for condition is required during the Event 4 inspection.
Probable cause
A jammed control yoke during landing, an entangled wiring harness, and inadequate maintenance by company personnel. A factor associated with the accident was the pilot's inability to flare the airplane during landing, due to the mechanical malfunction.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC01LA057
- Event ID
- 20010605X01079
- Case number
- ANC01LA057
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 365336892b783ef0146f809e01cc0608825ac5a1463afbbc1d70eec7ff7753b6; retrieved 2026-09-18T16:13:38.840Z.
- The NTSB's operator name is blank for N756DJ; the operator shown is the name the NTSB's other records give its FAA operator code, WVBA.