NTSB investigations: Sikorsky S-76
6 cases on aircraft the registry lists as Sikorsky S-76. 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
| 1983 | 1 |
|---|---|
| 1985 | 1 |
| 1988 | 1 |
| 1992 | 1 |
| 1994 | 1 |
| 2005 | 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.aircraft_model_code IN ('8143010'))
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 ('8143010'))
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 DFW05MA230Accident · Serious injuriesMajor investigationFinal reportSikorsky S76 · Gulf of Mexico, TXThe pilots' delayed response to the No. 1 engine fire warning and the loss of power to both engines, which occurred for undetermined reasons. The pilots' delayed response was most likely due to stress and fatigue. Contributing to the delay of the initiation…NTSB CHI95FA035Accident · 1 fatalField investigationFinal reportSikorsky S-76A · Cameron, LAthe copilot's failure to maintain altitude and the pilot-in-command's inadequate supervision of the operation. Factors include the dark night and low ceiling, and the flightcrew's failure to set the proper altimeter setting.NTSB FTW92LA155Accident · No injuriesLimited investigationFinal reportSikorsky S-76A · Morgan City, LAThe second pilot's failure to maintain aircraft control.NTSB NYC88LA204Accident · No injuriesLimited investigationFinal reportSikorsky S-76A · Teterboro, NJThe S-76 helicopter was taxiing on its company ramp when the copilot taxied onto a grass area. During a left turn the right main wheel stuck in a soft spot and the helicopter rolled over on its right side receiving substantial damage. The ground maneuver that…NTSB FTW85LA268Accident · Minor injuriesLimited investigationFinal reportSikorsky S-76 · Eugene IslandThe plt had landed on the offshore heliport in the gulf of Mexico. The S76 helicopter rolled backward on the platform with the helicopter tilting to its right. The coplt exited the acft and found the right main gear wheel off the platform and into the deck…NTSB FTW84IA094Incident · No injuriesIncident investigationFinal reportSikorsky S76A · Cameron, LAThe helicopter was on initial climb when the #1 engine failed explosivly. A post explosion fire ensued and both fire bottles were utilized to no avail. During landing the gear collapsed and the acft settled on its belly. The cause of the engine failure is…