CHI82DA149 · Hughes 269C
Hughes 269C · Accident: airframe, component or system failure while standing
From Bishop International Airport (FNT) to Bishop International Airport (FNT)
Event
- NTSB case
- CHI82DA149
- 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
- N8963F
- Operator
- Don D. Goble · private individual
- Onboard fatalities
- Unknown
- Route
- From Bishop International Airport (FNT), Flint, MITo Bishop International Airport (FNT), Flint, MI
- 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
- Standing
- 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
- Substantial
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCREW WERE ON AN INSTRUCTIONAL FLIGHT TO PREPARE THE STUDENT, A RATED PILOT, FOR A FLIGHT INSTRUCTOR RATING. AFTER PRACTICING SEVERAL AUTOROTATION APPROACHES, THE HELICOPTER WAS LANDED. THE INSTRUCTOR PILOT (IP) STATED THAT AFTER TOUCHDOWN, HE AND THE STUDENT WERE IN A DISCUSSION WHEN THEY HEARD A LOUD "POP". THE IP DEPLANED AND INSPECTED THE HELICOPTER, BUT FOUND NO IRREGULARITIES. THEY TOOK OFF AND PERFORMED ANOTHER AUTOROTATION. AFTER TOUCHDOWN, THE COLLECTIVE WAS LOWERED, THE HELICOPTER PITCHED LEFT AND FORWARD, AND THE ROTOR BLADES CONTACTED THE GROUND AND TAIL BOOM. AN INVESTIGATION REVEALED THAT THE LEFT FRONT SHOCK STRUT DAMPER ASSEMBLY, NO: 269A3150-5, HAD FAILED. TOTAL TIME ON THE PART WAS 3614 HRS. ACCORDING TO A METALLURIGICAL REPORT, A SINGLE OVERLOAD FRACTURE WAS FOUND AT THE CLEVIS ON THE PISTON END OF THE DAMPER. THE CFI DID NOT REPORT ANY HARD LANDINGS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI82DA149
- Event ID
- 20020917X02902
- Case number
- CHI82DA149
- 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: 5c064101d0f2fbf1521f6c7651e5c886b02f8bd652d5461c35b62512f250c3e1; retrieved 2026-09-24T03:18:28.474Z.