NTSB investigations, CT
7 cases where the first occurrence was “Fire”.
Cases per year
| 1983 | 1 |
|---|---|
| 1984 | 1 |
| 1993 | 1 |
| 2000 | 1 |
| 2002 | 2 |
| 2003 | 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.\"eventStateOrRegion\" = 'CT' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 171)
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."eventStateOrRegion" = 'CT' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 171) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run 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 NYC04IA037Incident · No injuriesIncident investigationFinal reportDassault-Breguet Falcon 50 · Windsor Locks, CTAn in-flight fire, originating from electrical arcing, which subsequently created a hole in an oxygen line.NTSB IAD03FA024Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Woodbury, CTAn engine fire for undetermined reasons, which resulted in the pilot's loss of control, and the airplane's subsequent impact with terrain.NTSB IAD02FA086Accident · 2 fatalField investigationFinal reportCessna 172S · Plainville, CTAn in-flight engine compartment fire of unknown origin, and a loss of engine power for undetermined reasons. Also causal, was the pilot's failure to maintain airspeed during a turn back to the airfield, which resulted in an inadvertent stall and subsequent…NTSB NYC00IA131Incident · No injuriesIncident investigationFinal reportBeech BE-58 · Windsor Locks, CTInadequate screw length information provided by the manufacturer, which allowed an inadvertent installation of a holding screw that was too long, and the subsequent fracture of the switch/circuit breaker. Factors included a short circuit of the beacon motor,…NTSB NYC93LA060Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Danbury, CTThe pilot's improper emergency procedures for an engine fire during starting which resulted in the substantial damage. Factors related to the accident were the pilot's improper starting procedure and his lack of total experience.NTSB NYC84FNE05Accident · Serious injuriesFinal reportMooney M20C · Danbury, CTAn eng compartment fire occurred shortly after takeoff & smoke entered the cockpit. The plt then made a forced landing in a sand pit aprx 1 mi fm the arpt. He & the pax exited the acft with serious burns. An inv revealed an exhaust pipe had failed at a…NTSB NYC84LA021Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · New Milford, CTThe pilot reported that as he was starting the engine, fire broke out. He attempted to put out the fire with on-board extinguishers, but failed. The acft was destroyed by fire.