NTSB investigations: Hughes 269A
12 cases on aircraft the registry lists as Hughes 269A, where the first occurrence was “Airframe/component/system failure/malfunction”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1984 | 2 |
|---|---|
| 1986 | 1 |
| 1988 | 1 |
| 1990 | 3 |
| 1993 | 1 |
| 1996 | 1 |
| 2001 | 1 |
| 2002 | 2 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('4470402')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('4470402')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB FTW03FA028Accident · 1 fatalField investigationFinal reportHughes 269A · Fort Gibson, OKThe in-flight separation of the tail boom resulting from the failure of the fuselage to tail boom attachment fitting lugs, due to fatigue.NTSB CHI02LA293Accident · No injuriesLimited investigationFinal reportHughes 269A · Council Bluffs, IAThe premature fracture of the cyclic/mixture bracket resulting in the inability to conduct a landing flare.NTSB NYC01LA167Accident · Minor injuriesLimited investigationFinal reportHughes 269A · Clay, NYFailure of the left aft cluster fitting due to a fatigue crack. Factors in the accident were the mechanic's failure to identify the crack at the last annual inspection, and the pilot's failure to identify the crack during the last daily inspectionNTSB MIA96LA209Accident · Serious injuriesLimited investigationFinal reportHughes 269A · Cottondale, FLimproper assembly of the main rotor blade dampners by a mechanic which resulted in the helicopter being damaged by ground resonance.NTSB CHI94LA013Accident · No injuriesLimited investigationFinal reportHughes 269A · Coldwater, MIthe fatigue failure of the tailboom support strut attachment lug.NTSB FTW90FA183Accident · 1 fatalField investigationFinal reportHughes 269A · Kingsville, TXThe fatigue failure of the left flange on the tail boom saddle fitting.NTSB NYC90LA134Accident · Minor injuriesLimited investigationFinal reportHughes 269A · Pittstown, NJGround resonance due to inadequate servicing and maintenance of the landing gear dampers.NTSB SEA90LA084Accident · No injuriesLimited investigationFinal reportHughes 269A · Bremerton, WAFailure of the tail rotor control for an undetermined reason.NTSB MIA89IA030Incident · No injuriesIncident investigationFinal reportHughes 269A · Daytona Beach, FLDuring normal cruise flt, the main rotor drive system failed for undetermined reason(s). Grass was ignited by exhaust gasses after touchdown, resulting in fire, destroying the helicopter. Examination of eng compartment revealed no evidence of catastrophic…NTSB CHI86LA127Accident · Minor injuriesLimited investigationFinal reportHughes 269A · Ft. Wayne, INApprox 10-15 minutes after takeoff the student pilot lost control of the helicopter and crash landed into trees. Following the accident, the only unusual thing FAA personnel could locate was a failed horizontal stabilizer spar. Post-crash examination of the…NTSB FTW85LA030Accident · Minor injuriesLimited investigationFinal reportHughes 269A · Terrell, TXAcft was substantially damaged during an autorotative landing after the plt heard a 'loud pop' from the rear of the helicopter. Investigation revealed the spines on the lower pulley shaft coupling were severly stripped.NTSB NYC84LA134Accident · No injuriesLimited investigationFinal reportHughes 269A · Danbury, CTWhile in flt, the helicopter yawed & the eng RPM increased. The plt retarded the throttle to idle, lowered the collective & initiate an autorotation. While attempting to reach a suitable landing area, the plt kept his speed up to avoid buildings. However,…