Cape Smythe Air Service de Havilland DHC-6-100 incident
de Havilland DHC-6-100 · Incident: airframe, component or system failure during initial climb
From an unrecorded airport to Atqasuk Edward Burnell Sr Memorial Airport (ATK)
Event
- NTSB case
- ANC89IA059
- 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
- Incident
- 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
de Havilland DHC-6-100
- Aircraft type
- de Havilland DHC-6
- 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
- N100AP
- Operator
- Cape Smythe Air Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Atqasuk Edward Burnell Sr Memorial Airport (ATK), ATQASUK, 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
- None
Cause areas
- Flt control syst, elevator control › Failure, total
- Flt control syst, elevator control › Fatigue
- Manufacturer › Inadequate quality control
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE HAD JUST DEPARTED BARROW, AK, ON A SCHEDULED COMMUTER FLIGHT WITH FIVE PASSENGERS AND TWO CREW MEMBERS ON BOARD. UPON REACHING AN ALTITUDE OF 150 AGL, THE CONTROL YOKE WAS PULLED FORWARD OUT OF THE CAPTAIN'S HANDS AND PINNED AGAINST THE CONTROL PANEL. SIMULTANEOUSLY, THE NOSE OF THE AIRPLANE SUDDENLY PITCHED UP 60 DEGREES ABOVE THE HORIZON. THE CAPTAIN REDUCED POWER AND THE NOSE PITCHED 30 DEGREES BELOW THE HORIZON. THE FLIGHT CREW WAS EVENTUALLY ABLE TO MAINTAIN A LEVEL ATTITUDE BY POWER ADJUSTMENTS ALONE, AND RETURNED FOR A SAFE LANDING. INSPECTION REVEALED A FATIGUE FRACTURED ELEVATOR BELLCRANK MOUNTING QUADRANT, P/N C6CFM1142-1, RESULTING IN A COMPLETE LOSS OF ELEVATOR CONTROL. THE ELEVATOR BELLCRANK MOUNTING QUADRANT HAD BEEN IN SERVICE SINCE 1966 AND HAD BEEN OPERATING 17,826 HRS. THE FRACTURE OCCURRED BETWEEN THE VERTICAL STABILIZER STUB FIN ATTACHMENT BULKHEAD AND THE BELLCRANK. METALLURGICAL EXAM REVEALED MULTIPLE FATIGUE ORIGINS IN THE VICINITY OF SUPERFICIAL MACHINING ABRASIONS.
Probable cause
THE PROPAGATION OF A FATIGUE CRACK FROM MULTIPLE ORIGINS DUE TO MANUFACTURING DEFECTS IN THE ELEVATOR BELLCRANK MOUNTING QUADRANT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC89IA059
- Event ID
- 20001213X28013
- Case number
- ANC89IA059
- 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: local date, investigation status, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-04-14.
- API snapshot SHA-256: 5e3b33c7e85aa4c7c111ce73f2c54ac31ffb2f277aa7d26be7a60e166323c3c5; retrieved 2026-09-18T19:12:35.365Z.
- The NTSB's operator name is blank for N100AP; the operator shown is the name the NTSB's other records give its FAA operator code, CSAA.