Fatal NTSB investigations: Socata TB 10
6 cases on aircraft the registry lists as Socata TB 10. 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 | 1 |
|---|---|
| 1989 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 2012 | 1 |
| 2020 | 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 ('8680696'))
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 ('8680696'))
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 ERA21LA080Accident · 1 fatalClass 3 · LimitedFinal reportSocata TB10 · Pembroke Pines, FLThe pilot’s failure to use carburetor heat in environmental conditions favorable for serious carburetor ice during a prolonged wait with the engine at a low power setting before takeoff, which resulted in a partial loss of engine power due to carburetor ice.…NTSB ERA12FA514Accident · 2 fatalField investigationFinal reportSocata TB 10 · Shirley, NYThe pilot/owner's operation of the airplane with known deficiencies, and the mechanic's failure to reattach the mixture control cable to the mixture control arm following maintenance of the carburetor.NTSB MIA93FA198Accident · 3 fatalField investigationFinal reportSocata TB 10 · Aguadilla, PRIn flight encounter with a level ii thunderstorm and flight into known advese weather by the pilot in command. Contributing to the accident was failure of the pilot in command to obtain a preflight weather briefing.NTSB FTW90FA160Accident · 4 fatalField investigationFinal reportAerospatiale/Socata TB-10 · Ada, OKImproper planning/decision by the pilot, which resulted in his failure to attain sufficient airspeed for a climb profile. Factors related to the accident were: the pilot allowed the weight and balance of the aircraft to exceed the certified limits, his use of…NTSB NYC89FA105Accident · 4 fatalField investigationFinal reportAerospatiale TB-10 · Pittsfield, MAFailure of the pilot to maintain proper altitude. Factors related to the accident were: inadequate briefing provided by the flight service station (fss) specialist, dark night, low clouds, and terrain conditions.NTSB SEA87FA102Accident · 3 fatalField investigationFinal reportSocata TB10 · Battle Mountain, NVAfter receiving a weather briefing calling for mountains occasionally obscured, occasional moderate icing from 18000 ft & below, and ceilings across north & central Nevada, the noninstrument rated pilot filed a VFR flight plan and departed salt lake city for…