NTSB investigations: Beech B24R
4 cases on aircraft the registry lists as Beech B24R, where the first occurrence was “In flight collision with object”. 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
| 1984 | 2 |
|---|---|
| 1989 | 1 |
| 1992 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151253')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151253')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 ATL92LA157Accident · No injuriesLimited investigationFinal reportBeech 23-B24R · Walterboro, SCThe inadequate preflight planning by the pilot in command. Factors were the soft runway, and the high density altitude which existed at the time of the attempted departure.NTSB ATL89LA115Accident · No injuriesLimited investigationFinal reportBeech B24R · New Carlisle, OHThe pilot's failure to clear the trees after the in-flight collision with an undetermined object. He allowed the altitude to decrease to the point of colliding with trees before initiating remedial action to maintain flight and land the airplane.NTSB CHI84LA360Accident · No injuriesLimited investigationFinal reportBeech B-24-R · Independence, WIThe acft collided with trees near the departure end of the field during an attempted go-around. A passenger reported that the go-around was initiated at about 100 ft AGL, 1/2 way down the fld. The plt said the fld was in a valley, it wasa hot (reported temp…NTSB NYC84LA153Accident · Minor injuriesLimited investigationFinal reportBeech B24R · Clinton, MDThe main rwy at the arpt was closed due to resurfacing. The plt was attempting a landing on rwy 31 knowing it would be a deliberate downwind landing. According to the operator of the arpt, plts were discouraged from using rwy 13 because the traffic directly…