Fatal NTSB investigations: Beech B200
7 cases on aircraft the registry lists as Beech B200. 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
| 1987 | 2 |
|---|---|
| 1996 | 1 |
| 2000 | 1 |
| 2003 | 1 |
| 2020 | 1 |
| 2023 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1152922'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1152922'))
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 CEN23FA113Accident · 5 fatalClass 3 · FieldFinal reportBeech B200 · Little Rock, ARThe loss of control during initial climb for undetermined reasons. Contributing to the accident were the sudden wind shifts during the initial climb.NTSB CEN20FA093Accident · 3 fatalClass 3 · FieldFinal reportBeech 200 · Coleman, TXThe pilot’s loss of airplane control due to spatial disorientation. Contributing to the accident was the pilot’s distraction with a “popped” circuit breaker and communications with air traffic control.NTSB ATL04FA045Accident · 2 fatalField investigationFinal reportBeech B200 · Morlan, GAThe pilot's inadequate in-flight planning/decision when he continued the flight below the decision height and collided with trees. A related factor was the low ceiling.NTSB NYC01FA058Accident · 2 fatalField investigationFinal reportBeech B200 · Rangeley, METhe pilot-in-command's failure to maintain sufficient altitude while maneuvering to land, which resulted in a collision with terrain. Factors in the accident were the dark night, mountainous terrain, snow showers, clouds, and the pilot's decision to cancel…NTSB MIA96WA140Accident · 2 fatalForeign investigationBeech 200 · Treasure Cay, BahamasNTSB CHI88MA026Accident · 8 fatalMajor investigationFinal reportBeech 200 · Jefferson, WIWhile cruising abv frzg lvl at 12,000', the flt was clrd to dscnd & maint 9000'. Abt 1-1/2 min ltr, the flt declared a mayday (emergency). Radio & radar ctc were lost & the acft crashed in a nr vertical dscnt. Radar data showed that after starting a dscnt,…NTSB SEA87FA141Accident · 4 fatalField investigationFinal reportBeech B200 · Crystal Bay, NVWhile on an instrument flight plan in IMC, the flight was cleared for an instrument approach to the south lake tahoe airport, the intended destination. The aircraft departed the initial approach fix on the published transition to the final approach course.…