NTSB investigations: Bell 206B, 1998
13 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
| 1967 | 1 |
|---|---|
| 1968 | 1 |
| 1969 | 1 |
| 1970 | 1 |
| 1971 | 1 |
| 1972 | 7 |
| 1973 | 12 |
| 1974 | 6 |
| 1975 | 20 |
| 1976 | 16 |
| 1977 | 18 |
| 1978 | 16 |
| 1979 | 18 |
| 1980 | 22 |
| 1981 | 25 |
| 1982 | 14 |
| 1983 | 18 |
| 1984 | 19 |
| 1985 | 18 |
| 1986 | 17 |
| 1987 | 11 |
| 1988 | 12 |
| 1989 | 23 |
| 1990 | 20 |
| 1991 | 13 |
| 1992 | 9 |
| 1993 | 16 |
| 1994 | 22 |
| 1995 | 13 |
| 1996 | 23 |
| 1997 | 15 |
| 1998 | 13 |
| 1999 | 14 |
| 2000 | 15 |
| 2001 | 10 |
| 2002 | 10 |
| 2003 | 17 |
| 2004 | 17 |
| 2005 | 14 |
| 2006 | 8 |
| 2007 | 17 |
| 2008 | 5 |
| 2009 | 4 |
| 2010 | 11 |
| 2011 | 9 |
| 2012 | 11 |
| 2013 | 12 |
| 2014 | 11 |
| 2015 | 8 |
| 2016 | 8 |
| 2017 | 11 |
| 2018 | 8 |
| 2019 | 10 |
| 2020 | 5 |
| 2021 | 7 |
| 2022 | 11 |
| 2023 | 8 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 2 |
Where
Latest 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 year(c.\"eventDate\") = 1998
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 year(c."eventDate") = 1998
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 FTW99LA026Accident · No injuriesLimited investigationFinal reportBell 206B · Matagorda 713The pilot's loss of control due to his failure to untie ground straps. A factor was his inadequate preflight inspection.NTSB IAD99LA015Accident · Minor injuriesLimited investigationFinal reportBell 206-B · Louisville, KYA loose 'B' nut on the aircraft's PC Air line which resulted in fuel starvation, and the pilot's abrupt application of aft cyclic to prevent a nose over. Contributing factors were soft terrain and dark night conditions.NTSB CHI98TA354Accident · No injuriesFinal reportBell 206B-3 · Hinkley, MNLoss of engine power due to failure of the engine governor.NTSB ANC98TA125Accident · No injuriesFinal reportBell 206B II · Chickaloon, AKA fracture of the main rotor drag pin assembly.NTSB FTW98LA260Accident · No injuriesLimited investigationFinal reportBell 206B · Corpus Christi, TXThe failure of the tail rotor drive shaft due to the separation of a bolt at one of the drive shaft disc couplings for an undetermined reason, which resulted in the pilot's inability to maintain directional control during landing.NTSB FTW98LA235Accident · No injuriesLimited investigationFinal reportBell 206BIII · Hurst, TXThe pilot's delayed recovery from a simulated autorotative landing.NTSB LAX98LA159Accident · No injuriesLimited investigationFinal reportBell 206B · Temecula, CAA loss of engine power due to a deteriorated compressor air seal which resulted in the fracture and separation of several stator vanes. Deterioration was not detected as a result of an inadequate maintenance inspection frequency.NTSB LAX98LA139Accident · No injuriesLimited investigationFinal reportBell 206B · Grand Canyon, AZThe malfunction and erratic speed control of the engine's governor, and the flight instructor's delayed remedial action.NTSB FTW98LA187Accident · No injuriesLimited investigationFinal reportBell 206B · Cameron, LAThe loss of engine power for undetermined reasons and the pilot's improper flare which resulted in a hard landing.NTSB FTW98FA167Accident · 1 fatalField investigationFinal reportBell 206B · Round Top, TXThe pilot's attempted VFR flight into instrument meteorological conditions. Contributing factors were fog, low ceilings, and trees.NTSB LAX98TA123Accident · No injuriesFinal reportBell 206B · Santa Clarita, CAThe failure of the pilot to maintain adequate clearance with the wires. Additional factors in this accident are the position of the sun at that time of the day, which made it difficult to see the wires, and the lack of markings or poles for that series of…NTSB MIA98LA070Accident · No injuriesLimited investigationFinal reportBell 206B · Miami, FLThe pilot's improper use of flight controls (cyclic) while attempting a takeoff to a hover, which led to an on-ground loss of control (dynamic rollover).NTSB MIA98LA053Accident · Minor injuriesLimited investigationFinal reportBell 206B · Pooler, GAThe pilot's failure to maintain a safe altitude and a visual lookout while operating under a special visual flight rules clearance in instrument flight rule conditions, which resulted in the helicopter colliding with trees. Contributing to the accident was…