NTSB investigations, 2004
12 cases where the first occurrence was “Fire”.
Cases per year
| 1982 | 27 |
|---|---|
| 1983 | 25 |
| 1984 | 21 |
| 1985 | 30 |
| 1986 | 28 |
| 1987 | 28 |
| 1988 | 15 |
| 1989 | 20 |
| 1990 | 14 |
| 1991 | 16 |
| 1992 | 17 |
| 1993 | 14 |
| 1994 | 22 |
| 1995 | 20 |
| 1996 | 11 |
| 1997 | 15 |
| 1998 | 13 |
| 1999 | 9 |
| 2000 | 12 |
| 2001 | 17 |
| 2002 | 15 |
| 2003 | 7 |
| 2004 | 12 |
| 2005 | 12 |
| 2006 | 13 |
| 2007 | 17 |
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 year(c.\"eventDate\") = 2004
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 year(c."eventDate") = 2004 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 ANC05IA020Incident · No injuriesIncident investigationFinal reportBoeing 747-123 · Anchorage, AKThe failure of a high-pressure fuel line fitting, which resulted in an engine fire during takeoff/initial climb.NTSB ATL05IA025Incident · No injuriesIncident investigationFinal reportCirrus Design SR22 · Peachtree City, GAThe failure of maintenance personnel to properly torque a fuel line fitting, which resulted in a fuel leak and in-flight engine fire.NTSB IAD05LA005Accident · No injuriesLimited investigationFinal reportBeech C24R · Hyannis, MAThe mechanic's failure to secure the fuel pressure line to the fuel pressure gauge fitting, which resulted in an engine compartment fire and a subsequent loss of engine power.NTSB ANC05LA003Accident · No injuriesLimited investigationFinal reportScan 30 · Anchorage, AKAn in-flight fire during cruise flight for an undetermined reason.NTSB LAX04LA334Accident · No injuriesLimited investigationFinal reportBritish Aerospace BAE 125-1000A · San Francisco, CAAn electrical arc from an undetermined source initiated a hydraulic line rupture, which resulted in an equipment bay fire.NTSB ANC04LA104Accident · Minor injuriesLimited investigationFinal reportPiper PA-18-150 · Cantwell, AKAn in-flight fire for an undetermined reason, which resulted in an off-airport forced landing and subsequent destruction of the airplane by fire.NTSB CHI04LA295Accident · Serious injuriesLimited investigationFinal reportAero Commander Callair A-9B · Norton, KSThe fire in the area of the fuel line and the unsuitable terrain encountered during an emergency landing by the pilot. Contributing factors were the pole.NTSB ATL04LA153Accident · 1 fatalLimited investigationFinal reportConvair Div. of Gen. Dynamics 440 · Beef IslandThe in-flight fire on the number two engine, for undetermined reasons.NTSB FTW04LA142Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Cleveland, TXThe in-flight fire that resulted from an electrical arc in the main battery cable near the main power bus. The cause of the arcing event could not be determined.NTSB FTW04IA104Incident · No injuriesIncident investigationFinal reportCessna 414 · Midland, TXThe in-flight wing fire for undetermined reasons.NTSB CHI04LA078Accident · No injuriesLimited investigationFinal reportCessna R182 · Elberfeld, INThe in-flight and on-ground fires in the cabin and engine compartment for undetermined reasons during the flight's cruise and emergency landing.NTSB NYC04LA060Accident · No injuriesLimited investigationFinal reportStinson 108-3 · Sanford, MEAn engine fire for undetermined reasons during start-up.