FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI91LA097 · Hughes 269C

20 Feb 1991 · North Mankato, MN, United States

Helicopter Flight Hughes 269C · Accident: airframe, component or system failure while maneuvering

From Mankato Regional Airport (MKT) to an unrecorded destination

Report a problem

Event

NTSB case
CHI91LA097
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
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
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

Hughes 269C

Aircraft type
Hughes 269
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
N8955F
Onboard fatalities
Unknown
Route
From Mankato Regional Airport (MKT), Mankato, MNTo 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 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
Maneuvering
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

  • Maintenance, inspection › Inadequate
  • Miscellaneous rotorcraft › Fatigue

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

NTSB narrative

THE PILOT REPORTED THAT DURING THE AERIAL OBSERVATION FLIGHT HE HEARD A LOUD NOISE FROM THE BACK OF THE HELICOPTER. THE HELICOPTER THEN BEGAN ROTATING CLOCKWISE AND DESCENDED TO IMPACT WITH THE TERRAIN IN A WOODED AREA. POST ACCIDENT IMSPECTION REVEALED A FATIGUE FAILURE OF THE TAIL BOOM SUPPORT STRUT CLUSTER FITTING (LEFT SIDE). AN AIRWORTHINESS DIRECTIVE ISSUED IN 1976 CALLED FOR A DAILY VISUAL INSPECTION AND A 200 HOUR DYE PENETRANT INSPECTION OF THE FITTING. A LOGBOOK ENTRY DATE AUGUST 15, 1990, STATED ALL AD'S HAD BEEN COMPLIED WITH.

Probable cause

THE FATIQUE FAILURE OF THE TAIL BOOM SUPPORT STRUT ATTACHMENT CLUSTER AND THE IMPROPER INSPECTION OF THE CLUSTER ATTACHMENT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI91LA097
Event ID
20001212X16428
Case number
CHI91LA097
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: 5b27f86b1cf8a984857d9e21eb3cef5a54928d406581c2b5ffe2447a49dd9fac; retrieved 2026-09-21T15:31:06.572Z.