NTSB investigations: Consolidated Vultee BT-13A
8 cases on aircraft the registry lists as Consolidated Vultee BT-13A. 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
| 1972 | 1 |
|---|---|
| 1981 | 1 |
| 1984 | 1 |
| 1989 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 2016 | 1 |
| 2021 | 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 ('2420224'))
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 ('2420224'))
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 WPR21FA170Accident · 1 fatalClass 3 · FieldFinal reportConsolidated Vultee BT-13A · Camas, WAThe pilot’s exceedance of the airplane’s critical angle of attack during an aborted landing, resulting in an aerodynamic stall and impact with terrain.NTSB GAA16CA429Accident · No injuriesData collectionFinal reportConsolidated Vultee BT13 · Joseph, ORThe pilot's failure to maintain directional control during the landing roll, which resulted in a runway excursion and damage to the left aileron and elevator.NTSB NYC98LA044Accident · Minor injuriesLimited investigationFinal reportConsolidated-Vultee BT-13A · Oxford, CTThe loss of power for undetermined reasons.NTSB SEA96LA098Accident · No injuriesLimited investigationFinal reportConsolidated-Vultee BT-13A · Brookings, ORthe pilot's misjudgment of distance/speed during the approach to landing, his failure to attain a proper touchdown point for landing, and his failure to perform a go-around, while there was sufficient runway and airspeed remaining. The tailwind was a related…NTSB MKC89LA189Accident · No injuriesLimited investigationFinal reportConsolidated-Vultee BT-13A · Kansas City, MOInadequate control tower service provided by tower personnel, and inadequate remedial action by the vehicle driver. The pilot's lack of visual lookout was considered to be a contributing factor.NTSB CHI84LA307Accident · No injuriesLimited investigationFinal reportBoeing A75N1 · Huntley, ILThe plts of a Boeing A75, N55070, & a vultee BT-13, N176VR, where in formation as they apchd their destination. When the saw the arpt, they separated for separate landings & lost sight of each other. Before landing, both plts flew over the arpt & noted the…NTSB FTW81FRA53Accident · No injuriesClosedVultee BT-13A · Friendswood, TXNTSB LAX73FUQ07Accident · Minor injuriesClosedVultee BT-13A · Lancaster, CA