NTSB investigations: Bell 206B, TN
6 cases on aircraft the registry lists as Bell 206B. 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
| 1983 | 1 |
|---|---|
| 1996 | 1 |
| 2007 | 1 |
| 2010 | 1 |
| 2019 | 1 |
| 2022 | 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.\"eventStateOrRegion\" = 'TN' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1181511'))
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."eventStateOrRegion" = 'TN' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1181511'))
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 ERA22FA383Accident · 2 fatalClass 3 · FieldFinal reportBell 206B · Whiteside, TNThe pilot’s failure to maintain clearance from the powerlines.NTSB GAA19CA457Accident · Minor injuriesData collectionFinal reportBell 206 · Dukedom, TNThe pilot's failure to maintain clearance from wires during an agricultural application flight.NTSB ERA10TA292Accident · No injuriesFinal reportBell 206B · Memphis, TNThe pilot’s failure to maintain adequate rotor rpm and the certificated flight instructor’s delayed remedial action, which resulted in a hard landing.NTSB ATL07CA076Accident · No injuriesData collectionFinal reportBell 206-B · Sevierville, TNThe pilot's improper use of the flight controls while at a hover that resulted in the tail colliding with the ground, a subsequent hard landing, and collapse of the skids.NTSB MIA96LA180Accident · Serious injuriesLimited investigationFinal reportBell 206B · Pigeon Forge, TNfatigue failure of the engine PC line, induced by damage from improper installation, which resulted in a loss of engine power and an autorotative landing to unsuitable terrain.NTSB ATL83LA294Accident · Minor injuriesLimited investigationFinal reportBell 206B · Nr Gatlinburg, TNThe plt reported that he was beginning his apch to a landing site at an elevation of 5200 ft when he felt a bump in the tail rotor pedals. The helicopter begun to spin to the right & the plt found he has no tail rotor control. An autorotative landing was made…