NTSB investigations: Lycoming HIO-360 series
15 cases on aircraft whose registry engine model is Lycoming HIO-360 series, where the first occurrence was “In flight collision with object”. 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
| 1987 | 1 |
|---|---|
| 1989 | 3 |
| 1993 | 4 |
| 1995 | 1 |
| 1997 | 2 |
| 1998 | 1 |
| 2002 | 2 |
| 2006 | 1 |
Where
Latest 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.engine_model_code IN ('41524')
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\" = 220))
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.engine_model_code IN ('41524')
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" = 220))
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 CHI06LA138Accident · 1 fatalLimited investigationFinal reportHughes 269A · Berlin Center, OHThe pilot flew at a low altitude and failed to maintain clearance from the wire. A factor was the wire.NTSB DEN03LA018Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28C · Morrison, COthe pilot not maintaining clearance from the telephone lines during landing. Factors contributing to the accident were the pilot not being able to see the telephone lines, the low altitude, and the dark night.NTSB LAX02LA169Accident · Serious injuriesLimited investigationFinal reportEnstrom F-28C · Stockton, CAThe pilot's failure to maintain an adequate clearance from the water tower during takeoff. Also causal was the pilot's selection of a confined area for the landing and subsequent takeoff.NTSB CHI98LA332Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Decker, INThe pilot's failure to maintain obstacle clearance resulting in a collision with a fence.NTSB ATL98LA021Accident · No injuriesLimited investigationFinal reportHughes TH-55 · Bushnell, FLThe pilot's failure to maintain clearance from the trees during a hover. A factor was the pilot's diverted attention.NTSB CHI98LA021Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Grand Forks, NDthe pilot's inadequate preflight planning which resulted in a low fuel state, and his inability to see the wire which the helicopter contacted. Factors associated to the accident were the precautionary landing, the dark night conditions, and the wire which…NTSB BFO96LA003Accident · No injuriesLimited investigationFinal reportEnstrom F28-280C · Blue Ash, OHthe commercial pilot's failure to maintain clearance from obstacles during hover-taxi operations. Related factors the tailwind, the nearby obstacle, and the misjudged maneuver to avoid obstacles.NTSB NYC93FA115Accident · 1 fatalField investigationFinal reportEnstrom F28C · Gordon, KYThe pilot's failure to see and avoid the wire.NTSB CHI93LA208Accident · No injuriesLimited investigationFinal reportHughes 269 · Valley City, NDthe pilot-in-command's failure to maintain clearance from a tree during an aerial application manuever.NTSB BFO93FA019Accident · 2 fatalField investigationFinal reportHughes 269C · Tonawanda, NYImproper inflight planning/decision by the pilot and his failure to maintain clearance from an obstacle during flight. Factors related to the accident include poor visibility and weather conditions at dusk, and the pilot's excessive airspeed for the…NTSB LAX93LA087Accident · Serious injuriesLimited investigationFinal reportHughes 269C · Folsom, CAThe pilot failing to maintain an adequate visual lookout resulting in the helicopter colliding with electrical transmission wires.NTSB SEA90LA016Accident · 1 fatalLimited investigationFinal reportHughes 269C · Estacada, ORThe pilot misjudged clearance between her external load and the obstruction. Factors related to the accident were: the obstruction, improper maintenance and modification of the external load line/hook by the operator, failure of the pilot to jettison the…NTSB CHI89FA112Accident · Minor injuriesField investigationFinal reportHughes 269C · Lockport, ILImproper flight technique by the PIC during a takeoff from a confined area.NTSB SEA89LA052Accident · Minor injuriesLimited investigationFinal reportSchweizer 269C · Forrest Grove, ORThe pilot's misjudgment of his altitude and clearance while attempting to sling-load a trailer.NTSB CHI87LA072Accident · No injuriesLimited investigationFinal reportEnstrom F-28A · Martinsville, INWhile landing to the east the plt was blinded by the sun and the acft struck telephone wires.