NTSB investigations, FL
7 cases where the first occurrence was “Fire/explosion”.
Cases per year
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1993 | 2 |
| 2001 | 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\" = 'FL' 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\" = 170)
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" = 'FL' 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" = 170) 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 MIA01LA236Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Venice, FLan on ground fire that started in the engine due to an excessive fuel flow causing the engine to flood. A factor in this accident was the pilot-in-command did not follow all the emergency procedures for an engine fire during start.NTSB MIA94LA019Accident · No injuriesLimited investigationFinal reportCessna 421 · Miami, FLFailure of the pilot-in-command to obtain the proper assistance after being notified of a fuel leak from the left wing fuel tanks after refueling.NTSB MIA93FA155Accident · 1 fatalField investigationFinal reportBeech 95-A55 · Jacksonville, FLAn explosion and fire from undetermined fuel and ignition sources in the left wing.NTSB MIA88LA033Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Miami, FLPlt stated that shortly after starting the left engine he heard an explosion and saw flame spreading from the accessory area of the left engine toward the left wing tip and the cabin. He shut down the engine by turning off the magnetos and he and his…NTSB MIA86LA176Accident · No injuriesLimited investigationFinal reportCessna 411 · Tallahassee, FLThe plt observed a fuel spill on the ground as a result of refueling overflow. He attempted to start the engines & an explosion & fire resulted.NTSB MIA83IA165Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-51 · Tampa, FLSmoke was observed coming from under the right rear lavatory door during the taxi from landing. The fire was not contained within the waste receptacle. Source of the fire could not be determined.NTSB MIA82DA154Accident · No injuriesFinal reportBellanca 17-31 · Lake Wales, FLThe aircraft was on a maintenance flight to check a recently installed engine oil temperature gauge. After determining that the gauge was operating satisfactorily, the pilot began a descent toward the airport. While descending through 3000 ft, the pilot…