Fatal NTSB investigations: Aerospatiale AS 355F1
6 cases on aircraft the registry lists as Aerospatiale AS 355F1. 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
| 1989 | 1 |
|---|---|
| 1990 | 1 |
| 1994 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2012 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8680810'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8680810'))
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 ERA12FA563Accident · 1 fatalField investigationFinal reportAerospatiale AS 355F1 · West Windsor, NJDisconnection of the upper rod end from the fore/aft servo due to severely worn threads, which resulted in a loss of control and separation of a main rotor blade during cruise flight. Contributing to the accident were incorrect maintenance procedures and…NTSB ATL02FA062Accident · 2 fatalField investigationFinal reportEurocopter France AS355 F1 · Savannah, GAThe pilot's failure to follow operating procedures and, experienced spatial disorientation while attempting a night landing to an offshore platform. A factor was a dark night.NTSB LAX00MA273Accident · 7 fatalMajor investigationFinal reportAerospatiale AS 355F1 · Kahului, Maui, HIThe pilot's inadequate decision by which he continued visual flight rules flight into instrument meteorological conditions. Also causal was his failure to maintain terrain clearance resulting in a collision with mountainous terrain. A contributing factor was…NTSB NYC95LA009Accident · 1 fatalLimited investigationFinal reportAerospatiale AS-355 · Jonesville, VAThe pilot's failure to maintain clearance from the power lines.NTSB FTW90LA060Accident · 1 fatalLimited investigationFinal reportAerospatiale AS355F-1 · High Island Ao6Undetermined due to the lack of physical evidence.NTSB FTW89FA159Accident · 3 fatalField investigationFinal reportCessna 152 · Houma, LAThe failure of both pilots to see-and-avoid each other's aircraft (inadequate visual lookout). A probable factor was: failure of either pilot to issue a traffic advisory.