NTSB investigations: Brantly B-2B
5 cases on aircraft the registry lists as Brantly B-2B, 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
| 1982 | 1 |
|---|---|
| 1988 | 1 |
| 1995 | 1 |
| 2003 | 1 |
| 2004 | 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 ('1440506')
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 ('1440506')
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 FTW04LA111Accident · Minor injuriesLimited investigationFinal reportBrantly Helicopter B-2B · Holliday, TXThe failure of the upper tail rotor shaft due to excessive misalignment after two hard landings. Also causal was the manufacturer's failure to provide specific maintenance procedures for checking the alignment of the upper tail rotor shaft.NTSB NYC03LA063Accident · No injuriesLimited investigationFinal reportBrantly Helicopter B-2B · Zelienople, PAThe failure of the tail rotor assembly due to improper maintenance by the owner/pilot.NTSB CHI95LA130Accident · No injuriesLimited investigationFinal reportBrantly Helicopter B-2B · Winfield, KSThe total failure of the rotor drive system clutch assembly due to excessive wear of the clutch assembly. A factor in this accident was the soft ground in the emergency landing area.NTSB FTW88LA152Accident · No injuriesLimited investigationFinal reportBrantly Helicopter B-2B · Sallisaw, OKAcft experienced a hard landing and rolled over following a loss of control in a hover. Plt delayed cutting the throttle in order to clear a ditch. Investigation revealed that the tail rotor driveshaft coupling retaining screw had separated. The separation…NTSB MIA82DA138Accident · No injuriesFinal reportBrantly B-2B · Ruskin, FLThe plt experienced heavy vibration followed by loss of control of the acft. Witnesses described the acft in abrupt changes in attitude. Exam of the pitch link assemblies revealed failure under static overload conditions. A third pitch link assembly was not…