NTSB investigations: Bell 407
6 cases on aircraft the registry lists as Bell 407, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1997 | 1 |
|---|---|
| 2001 | 1 |
| 2003 | 3 |
| 2007 | 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 ('1182206')
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\" = 130))
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 ('1182206')
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" = 130))
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 DFW08IA045Incident · No injuriesIncident investigationFinal reportBell 407 · Hig Island A595The loss of tail rotor effectiveness for undetermined reasons.NTSB FTW04IA023Incident · No injuriesIncident investigationFinal reportBell 407 · Eugene Is. 27The loss of engine power due to the failure of the 3rd stage turbine wheel and subsequent catastrophic failure of the turbine assembly.NTSB FTW03FA148Accident · No injuriesField investigationFinal reportBell 407 · Gulf Of MexicoThe short circuit of the C321capacitor in the Electronic Control Unit (ECU) that resulted in a single-point failure of the ECU's -15V power supply which disengaged/reverted the Hydro-mechanical Unit (HMU) from automatic to manual fuel control. Factors…NTSB FTW03FA117Accident · No injuriesField investigationFinal reportBell 407 · Houma, LAThe loss of tail rotor drive and anti-torque control resulting from the fracture and separation of the #5 tail rotor drive segment due to the overtemperature and subsequent failure of the #5 hangar bearing.NTSB FTW01FA115Accident · No injuriesField investigationFinal reportBell 407 · Vermillion 44Failure of the engine-to-transmission driveshaft coupling due to fatigue.NTSB FTW97FA352Accident · Minor injuriesField investigationFinal reportBell 407 · Grand Isle S108The tail rotor blade strike(s) that severed the aft portion of the tailboom, subsequently rendering the pilot with no tail rotor control while in cruise flight. A factor was the lack of suitable terrain for the forced autorotative landing.