ANC03LA021 · de Havilland DHC-3
de Havilland DHC-3 · Accident: airframe, component or system failure en route
From 5NI · Nikolai, AK to 5NI · Nikolai, AK
Event
- NTSB case
- ANC03LA021
- 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
- General aviation
- 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-3
- Aircraft type
- de Havilland DHC-3
- 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
- N3904
- Operator
- Glenn, David Hamilton · private individual
- Onboard fatalities
- Unknown
- Route
- From 5NI · Nikolai, AKTo 5NI · Nikolai, 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 91: General Aviation
- 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 · climb to 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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, elevator attachment › Asymmetrical
- Flight control, elevator › Disconnected
- Unknown › Maintenance, major repair, 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 commercial certificated pilot reported that just after takeoff in a wheel/ski equipped airplane, he heard a very loud bang, followed by a loud rattling noise. As he turned towards the departure airstrip, he had difficulty using the airplane's rudder pedals. Using a combination of aileron input and the remaining amount of rudder control, he was able to maneuver the airplane for a landing on the airstrip. He said that as the airplane passed over the approach end of the airstrip, it drifted to the right, and he initiated a go-around. The airplane subsequently collided with a stand of trees bordering the airstrip, and sustained structural damage to the wings, fuselage, and empennage. In a written statement to the NTSB, the pilot stated that he suspected that the right elevator's outboard and center hinges or hinge pins failed, allowing the right elevator to swing rearward and jam the airplane's rudder. An FAA airworthiness inspector traveled to the accident scene to examine the airplane. He reported that the right elevator was discovered about 150 feet behind the airplane, within the wreckage debris path through a stand of trees. He said that the right elevator sustained a significant amount of damage along the leading edge, which would normally be protected by the horizontal stabilizer. The FAA inspector examined the airplane's horizontal stabilizer in the area where the right and left elevators connect, and noted signs of new paint on the rivets that held the torque tube support assembly, indicating recent reinstallation or replacement of the torque tube support assembly. He indicated that the torque tube support assembly was installed at a slight angle to the right, which allowed the right elevator to eventually slip off of the center and outboard hinge pins. The inspector said that witness marks on the center and outboard hinge pins showed signs of excessive wear towards the outboard portion of each pin. The inspector noted that a review of the airplane's maintenance records failed to disclose any entries of repair/replacement of the elevator torque tube support assembly.
Probable cause
An improper and undocumented major repair of the elevator torque tube support assembly by an unknown person, which resulted in an in-flight disconnection of the airplane's right elevator, and a jammed rudder. A factor associated with the accident is the inadequate inspection of the airplane by company maintenance personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC03LA021
- Event ID
- 20030103X00005
- Case number
- ANC03LA021
- 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: a338e940f92cf8da1cf2eab0488d4055c45fb3648616c4ede736567b674a3070; retrieved 2026-09-22T09:45:55.523Z.