NTSB investigations: Bell 206B, SD
4 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
| 1988 | 1 |
|---|---|
| 1990 | 1 |
| 1999 | 1 |
| 2005 | 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\" = 'SD' 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" = 'SD' 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 CHI05CA271Accident · No injuriesData collectionFinal reportBell 206B · Elk Point, SDThe loss of directional control for undetermined reasons which led to the pilot not being able to maintain clearance from the embankment during the forced landing. The rising embankment was a factor.NTSB CHI99FA285Accident · 2 fatalField investigationFinal reportBell 206B · Custer, SDThe pilot's failure to maintain adequate altitude/clearance from the trees. Contributing to the accident was the pilot's inadvertent settling with power.NTSB CHI90TL#03Accident · Serious injuriesClass 3Final reportBell 206B · Fort Thompson, SDNTSB DEN88LA180Accident · No injuriesLimited investigationFinal reportBell 206B · Sturgis, SDThe plt was on a flt with 2 pax to take pictures. He stated that 'while in level flight at 120 mph and 300 feet above the ground, a pitch over was initiated for picture taking. At that moment, it appeared that the fuel flow cavitated. The forward fuel pump…