Final NTSB investigations: Sikorsky S-64E

8 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

19692026
Final NTSB investigations: Sikorsky S-64E per year, 1969–2026: 8 cases
19691
19701
19761
19781
19911
19991
20031
20231

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.\"completionStatus\" = 'Completed'
    AND 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.

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…Aug 7, 2023 · N555AS · 2 aircraft · Substantial damageNTSB 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.Jul 8, 2003 · N6979R · Substantial damageNTSB 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).Mar 2, 1999 · N194AC · No damageNTSB 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…Jun 27, 1991 · N6959R · DestroyedNTSB MKC78DA061Accident · No injuriesClosedSikorsky S-64 · Buffalo, MNAug 8, 1978 · N4036S · No damageNTSB DEN77FA019Accident · Serious injuriesClosedSikorsky S-64E · Cowdrey, CODec 13, 1976 · N6965R · Substantial damageNTSB MIA71FKD01Accident · No injuriesClosedSikorsky S-64E · Union City, TNJul 3, 1970 · N6962R · Substantial damageNTSB ANC70A0020Accident · 3 fatalClosedSikorsky S-64E · Prudhoe Bay, AKSep 2, 1969 · N6964R · Destroyed