NTSB investigations, UT
9 cases where the first occurrence was “Fire”.
Cases per year
| 1985 | 1 |
|---|---|
| 1986 | 1 |
| 1995 | 1 |
| 1996 | 2 |
| 2000 | 1 |
| 2001 | 1 |
| 2007 | 2 |
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\" = 'UT' 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" = 'UT' 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 SEA08CA004Accident · No injuriesData collectionFinal reportPiper PA 28-151 · Salt Lake City, UTThe leak at the fuel line fitting, which resulted in a fire during engine start.NTSB SEA07FA124Accident · 1 fatalField investigationFinal reportCessna P210N · Spanish Fork, UTAn engine oil line leak and subsequent engine compartment fire while in cruise flight.NTSB DEN01LA109Accident · Serious injuriesLimited investigationFinal report2001 Mcgirl Questair Venture · Ogden, UTan in-flight fire, which originated from a fuel leak of unknown origin.NTSB DEN00LA103Accident · No injuriesLimited investigationFinal reportCessna 185B · Moab, UTThe fire in the engine compartment for unknown reason.NTSB SEA96FA094Accident · 2 fatalField investigationFinal reportCessna 320A · Provo, UTA fuel leak most probably ignited by hot exhaust gases from the leaking right engine manifold exhaust system, the decision by the pilots to operate the aircraft with knowledge of the fuel leak, and the pilot-in-command's failure to maintain adequate clearance…NTSB SEA96LA063Accident · Minor injuriesLimited investigationFinal reportCessna 172 · West Jordan, UTimproper installation of the airplane's carburetor fuel lines by maintenance personnel.NTSB SEA96LA048Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Salt Lake City, UTa carburetor fire.NTSB DEN86LA132Accident · No injuriesLimited investigationFinal reportCessna 152 · Salt Lake City, UTAcft carburetor had been removed for maintenance and sign posted in acft to this effect. Student plt called to schedule acft and was put in another acft. Scheduler said plt was told acft was out of service but plt claimed he did not hear this. Plt met flt…NTSB DEN85LA142Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Bluff, UTThe acft was destroyed by fire which began during an engine start. The plt stated that he used porper hot engine start procedures. He said the throttle was not pumped. The plt observed that the fuel pressure went to zero during the second start attempt. Smoke…