Fly Denali de Havilland DHC-2 accident
de Havilland DHC-2 · Accident: airframe, component or system failure en route
From Talkeetna Airport (TKA) to an unrecorded destination
Event
- NTSB case
- ANC05LA046
- 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
de Havilland DHC-2
- Aircraft type
- de Havilland DHC-2
- 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
- N3307S
- Operator
- Fly Denali
- Onboard fatalities
- Unknown
- Route
- From Talkeetna Airport (TKA), Talkeetna, AKTo not recorded
- 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
- En route · cruise
- 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
- Flight control, aileron › Flutter
- Other maintenance personnel › Maintenance, balancing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was conducting a mountain sightseeing flight with three passengers under Title 14, CFR Part 135. The pilot said the flight was at 11,000 feet msl and encountering some turbulence, when the airplane started to shake violently. He said he could not control the airplane, and stopped the engine in case it was creating the problem. The shaking continued until he slowed the airplane to 80 mph. He restarted the engine, and landed safely. An examination of the airplane revealed that both wings were structurally damaged. Prior to the event, the pilot had been taking a digital video with audio through the window of the airplane. The recording shows the airplane in a wings level attitude in VFR conditions. When dropped to the floor after the initiation of the event, the camera continued to record. The audio recording revealed a vibration for about 3 to 7 seconds in the 8.2 to 8.4 Hz range, which is in the appropriate range for the wing bending/torsional first mode of vibration. Nothing on the visual or audio recording indicated the airplane was being flown outside its normal operating envelope. The airplane was examined by aerospace engineers from the Anchorage FAA Aircraft Certification Office. Damage signatures indicated that the rear spars of both wings oscillated up and down with significant amplitude at span station 92.5. The bushing holes in the rear spar attachment fittings were elongated, and the right aileron and rudder were severely under-balanced. The engineers were not able to ascertain if the aileron cable tension was adjusted properly prior to the event. In 1980, prompted by flutter events, the manufacturer produced Service Bulletin 2/29, relating aileron/wing flutter to more than one of the following four conditions: ailerons not balanced; aileron cables in the wing slack; deterioration in the stiffness of the aileron mounting structure in the fuselage; and/or the airplane being flown outside the limits of the flight manual. On February 20, 1980, in response to the manufacturer's service bulletin, the FAA issued Airworthiness Directive AD 80-24-02, which required inspections of the airplane's wings, spars, and aileron cable tension and balance, based on service time and part numbers.
Probable cause
Aerodynamic flutter of the ailerons during normal cruise flight due to their improper maintenance/balancing, which resulted in structural damage to the airplane's wings.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC05LA046
- Event ID
- 20050314X00308
- Case number
- ANC05LA046
- 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, 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: f993a1b446129ef408bf8cbe3ec7496a873205c4aabe54d776880e327c8aa1e4; retrieved 2026-09-18T15:04:54.497Z.