Tundra Copters McDonnell Douglas 369D accident
McDonnell Douglas 369D · Accident: airframe, component or system failure on approach
Event
- NTSB case
- ANC92FA164
- 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
- 3 · 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
McDonnell Douglas 369D
- Aircraft type
- McDonnell Douglas 369
- Category
- Helicopter
- 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
- N1096X
- Operator
- Tundra Copters
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Approach
- 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
- Destroyed
Cause areas
- Company maintenance personnel › Maintenance, compliance with ad, not performed
- Manufacturer › Inadequate quality control
- Rotor system, main rotor blade › Fatigue
- Rotor system, main rotor blade › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
SHORTLY AFTER TAKEOFF THE PILOT RADIOED HE WAS RETURNING DUE TO POOR VISUAL FLIGHT CONDITIONS, AND WAS LAST SEEN CIRCLING THE EAGLE RUNWAY. THE WRECKAGE WAS FOUND APRX 7 HRS LATER 150 YDS NORTH OF THE RUNWAY. THE BLUE M/R BLADE WAS FOUND SEPARATED; THE TRAILING ATTACHMENT LUGS OF BOTH THE UPPER AND LOWER BLADE ROOT FITTINGS WERE FRACTURED THROUGH THE HOLES, AND THE LEAD LAG DAMPENER LUG WAS ALSO FRACTURED. METALLURGICAL EXAMINATION REVEALED FATIGUE PROGRESSION ON ALL FOUR ROOT FRACTURES. OPERATOR MAINTENANCE PERSONNEL STATED THAT THEY WERE NOT AWARE OF AD91-17-04 REQUIREMENT TO REMOVE & INSPECT THE M/R BLADES AT 100-HR INTERVALS.
Probable cause
AN INFLIGHT FATIGUE FAILURE AND SEPARATION OF A MAIN ROTOR BLADE, INADEQUATE OPERATOR MAINTENANCE AND INSPECTION, AND MATERIAL DEFECT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC92FA164
- Event ID
- 20001211X15555
- Case number
- ANC92FA164
- 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: 385bf5e2e16ff04a5aafba22be84391eaf03f5a71b694cc6eb7221eacceff6a6; retrieved 2026-09-18T13:57:03.279Z.