NTSB investigations: Bell 206B, MO
7 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
| 1989 | 1 |
|---|---|
| 1990 | 1 |
| 1992 | 1 |
| 2007 | 1 |
| 2010 | 1 |
| 2013 | 1 |
| 2025 | 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\" = 'MO' 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" = 'MO' 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 CEN25LA232Accident · No injuriesClass 3 · LimitedPreliminary reportBell 206B · Edgerton, MOOn July 1, 2025, at 0845 central daylight time, a Bell 206B, N17626, was substantially damaged when it was involved in an accident near Edgerton, Missouri. The commercial pilot was uninjured. The helicopter was operated under Title 14 Code of Federal…NTSB CEN13LA378Accident · No injuriesLimited investigationFinal reportBell 206B · St Louis, MOThe loss of engine power due to the separation of compressor blades, which resulted from fatigue cracking.NTSB CEN11GA020Accident · 1 fatalFinal reportBell 206B · Clarkson Valley, MOThe total loss of engine power due to fuel exhaustion, which resulted from the pilot's inadequate preflight planning and decision-making, and his improper control inputs following the loss of engine power, which resulted in mast bumping and separation of the…NTSB CHI07CA244Accident · Minor injuriesData collectionFinal reportBell 206B · Columbia, MOThe pilot's failure to maintain control of the helicopter, which resulted in impact with terrain during takeoff. A factor in the accident was the tall grass.NTSB CHI92FA232Accident · 2 fatalField investigationFinal reportBell 206B · St. Charles, MOThe pilot-in-command's failure to see and avoid the wires, and his physical impairment due to alcohol consumption. A factor which contributed to the effect of the alcohol impairment was the medicine.NTSB CHI90IA181Incident · No injuriesIncident investigationFinal reportBell 206A · Lake Ozark, MOCompression assembly blade and emergency floatation gear failure.NTSB MKC89LA178Accident · No injuriesLimited investigationFinal reportBell 206B · Marys Home, MOThe failure of the pilot to maintain control of the helicopter.