NTSB investigations: Sikorsky S-64E
9 cases on aircraft the registry lists as Sikorsky S-64E. 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
| 1969 | 1 |
|---|---|
| 1970 | 1 |
| 1976 | 1 |
| 1978 | 1 |
| 1991 | 1 |
| 1999 | 1 |
| 2003 | 1 |
| 2019 | 1 |
| 2023 | 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 ('8142604'))
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 ('8142604'))
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 WPR23FA302Accident · 3 fatalClass 3 · FieldFinal reportBell 407 · Cabazon, CAThe Skycrane flight crew’s decision to enter the Fire Traffic Area’s 7-nm NOCOM ring at an altitude significantly above their maximum cleared altitude, which resulted in their need for an aggressive descent into congested airspace and subsequent failure to…NTSB WPR19WA147Accident · Minor injuriesForeign investigationSikorsky S64 · Mount Eliza, AustraliaOn January 28, 2019, at 1956 local time, a Sikorsky S-64E, N173AC, sustained substantial damage after colliding into a pond near Mount Eliza, Australia. The pilot and two crewmembers were not injured. The investigation is under the jurisdiction of the…NTSB LAX03TA229Accident · No injuriesFinal reportSikorsky S-64E · Tucson, AZthe pilot's failure to maintain tail rotor clearance while hovering resulting in a tail rotor blade strike.NTSB SEA99LA038Accident · 1 fatalLimited investigationFinal reportSikorsky S-64E · Shelton, WAThe failure of the victim to follow the procedure that required him to make sure that all choker lines had separated from the helicopter's release mechanism prior to entering the landing (collection area).NTSB SEA91FA143Accident · Serious injuriesField investigationFinal reportSikorsky S-64E · Index, WAThe control interference by the mechanic when he inadvertently raised the collective pitch and the copilot's failure to attend the flight controls. Factors relating to the accident were the motion sickness of the mechanic, inadequate collective pitch control…NTSB MKC78DA061Accident · No injuriesClosedSikorsky S-64 · Buffalo, MNNTSB DEN77FA019Accident · Serious injuriesClosedSikorsky S-64E · Cowdrey, CONTSB MIA71FKD01Accident · No injuriesClosedSikorsky S-64E · Union City, TNNTSB ANC70A0020Accident · 3 fatalClosedSikorsky S-64E · Prudhoe Bay, AK