FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Henson Airlines de Havilland DHC-8-102 incident

16 Jul 1991 · Savannah, GA, United States

de Havilland DHC-8-102 · Incident: airframe, component or system failure en route

From 49J · Hilton Head Island, SC to Jacksonville International Airport (JAX)

Report a problem

Event

NTSB case
ATL91IA134
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
Airline
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-8-102

Aircraft type
de Havilland DHC-8
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
N922HA
Onboard fatalities
Unknown
Route
From 49J · Hilton Head Island, SCTo Jacksonville International Airport (JAX), Jacksonville, FL
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 121: Air Carrier
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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Landing gear, normal retraction/extension assembly › Fatigue
  • Landing gear, normal retraction/extension assembly › Loose
  • Maintenance, inspection › Inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

AFTER FLT 4317 TOOK OFF, THE MAIN LNDG GEAR DID NOT RETRACT. THE FLT CREW ACCOMPLISHED THE EMERG CHECKLIST, EXTDD THE LNDG GEAR & MADE AN UNEVENTFUL LNDG. AN EXAM OF THE ACFT DISCLOSED THAT THE RGT LNDG GEAR RETRACTION FITTING HAD FAILED & A HYDRAULIC LINE WAS SEVERED. ALSO, THE QUANTITY LIMITING VALVE(S) WERE CORRODED & THE RESPECTIVE PISTON MOVEMENT WAS RESTRICTED. SUBSEQUENTLY, BOTH HYDRAULIC SYSTEMS WERE DRAIN OF FLUID. AN EXAM OF THE FITTING ATTACHMENT BOLTS REVEALED THE TOP BOLT LOST TORQUE & THE BOLT FAILED IN FATIGUE; THE BOTTOM BOLTS FAILED IN OVERLOAD. ADNLY, THE FITTING SPIGOT FAILED DUE TO HYDROGEN EMBRITTLEMENT; AN IMPROVED FITTING HAS BEEN PRODUCED TO CORRECT HYDROGEN EMBRITTLEMENT PROBLEMS. THE OPER CONDUCTED A FLEET CAMPAIGN & FND 13 LOOSE BOLTS IN OTHER 100 SERIES ACFT. SVRL AIRWORTHINESS DIRECTIVES WERE ISSUED TO CORRECT THE LOSS OF TORQUE ON ATTACHMENT BOLTS, WHICH INCLUDED CHECKING THE TORQUE AT THE 300 HR LNDG GEAR INSPN.

Probable cause

THE INADEQUATE INSPECTION PROCEDURES WHICH ALLOWED THE LOSS OF TORQUE ON THE TOP RETRACTION FITTING ATTACHMENT BOLT WHICH SUBSEQUENTLY FAILED IN FATIGUE. FACTORS WERE THE LOSS OF HYDRAULIC FLUID THROUGH A SEVERED LINE, AND THE CORROSION OF A HYDRAULIC QUANTITY LIMITING VALVE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL91IA134
Event ID
20001212X17430
Case number
ATL91IA134
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1991-07-17.
  • API snapshot SHA-256: 0c34cd87cf1a97dc31eaa786d463d668879dd4e4968910982d1f0f54ec1db00c; retrieved 2026-09-18T18:53:40.068Z.