NTSB investigations: Lycoming HI0-360 series
5 cases on aircraft whose registry engine model is Lycoming HI0-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
| 1984 | 1 |
|---|---|
| 1987 | 1 |
| 1992 | 1 |
| 1995 | 1 |
| 2001 | 1 |
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.engine_model_code IN ('41553')
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 ('41553')
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 MIA02FA026Accident · 2 fatalField investigationFinal reportEnstrom 280FX · Tallassee, ALThe failure of the pilot to maintain a safe altitude above terrain and maintain a visual lookout resulting in the helicopter colliding with power transmission lines and crashing into a river. A factor in the accident was the power transmission lines not being…NTSB FTW95LA356Accident · No injuriesLimited investigationFinal reportEnstrom 280C · Houston, TXThe flight instructor's poor judgement, and his disregard of the owner's objection to air taxi into the hangar.NTSB SEA92LA112Accident · No injuriesLimited investigationFinal reportEnstrom 280FX · Wenatchee, WAThe pilot in command's inadequate visual lookout. Factors contributing to the accident were: object (fence post) and windshield dirty (foggy)NTSB DEN87LA245Accident · Serious injuriesLimited investigationFinal reportEnstrom 280C · Bountiful, UTWhile on a local low level pleasure flt the plt failed to see power lines and an in flight collision with the lines occurred severing the right skid and 90 degree gear box from the acft. A semi-autorotative crash occurred on the bank of a irrigation reservoir.NTSB NYC85FA015Accident · 2 fatalField investigationFinal reportEnstrom 280C · Butler, PAThe helicopter struck the static line of a high voltage transmission line while on a flt to photograph an apartment complex. The owner of the complex accompanied the plt on the flt, there after the acft was to be used for passenger sightseeing flts as part of…