NTSB investigations, 2001
17 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\") = 2001
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") = 2001 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 IAD02LA020Accident · No injuriesLimited investigationFinal reportCessna 401A · Martinsburg, WVthe owner/mechanic's failure to comply with an Airworthiness Directive, which resulted in a cracked fuel supply line and subsequent in-flight fire.NTSB NYC02LA038Accident · No injuriesLimited investigationFinal reportAero Vodochody Aero. Works L-39C · Wilmington, DEA ruptured oil line, which resulted in oil spraying onto the APU exhaust and a subsequent fire.NTSB CHI01LA284Accident · Minor injuriesLimited investigationFinal reportCameron Balloons Shuttle 90 · Centralia, ILThe balloon envelope fire. A contributing factor was the flammability of the envelope.NTSB LAX01LA250Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200 · Chandler, AZThe failure of maintenance personnel to properly tighten a fuel line fitting during an engine installation resulting in a fuel leak and fire during the maintenance checkflight. A factor in the accident was inadequate inspection of the installation prior to…NTSB MIA01LA171Accident · No injuriesLimited investigationFinal reportLockheed P-38L-5LD · Greenwood, MSthe failure and uncontained separation of supercharger impeller blades for undetermined reasons during normal descent, resulting in a punctured fuel line and the subsequent in-flight engine fire and emergency descent and forced landing to a farm field.NTSB LAX01LA214Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Sedona, AZthe induction manifold fire resulting from an engine backfire during engine start. The reason for the engine backfire was not determined.NTSB SEA01LA112Accident · No injuriesLimited investigationFinal reportCessna 150F · Arlington, WAA fire that originated in the aircraft's carburetor.NTSB DEN01LA109Accident · Serious injuriesLimited investigationFinal report2001 Mcgirl Questair Venture · Ogden, UTan in-flight fire, which originated from a fuel leak of unknown origin.NTSB SEA01IA093Incident · No injuriesIncident investigationFinal reportBeech C-99 · Salem, ORA short to electrical wiring while in cruise flight.NTSB SEA01FA085Accident · No injuriesField investigationFinal reportMBB BO-105C · Medford, ORA leaking engine oil outlet line fitting in the #1 engine compartment, resulting in an oil fire in the engine compartment.NTSB FTW01LA113Accident · Minor injuriesLimited investigationFinal reportCessna 172RG · Washington, OKthe in-flight fire for an undetermined reason, which resulted in a forced landing. A contributory factor was the lack of suitable terrain for the forced landing.NTSB FTW01LA102Accident · No injuriesLimited investigationFinal reportCap 232 · Laporte, TXFailure of the brake system during taxi. A contributing factor was the pilot's decision to continue taxiing after discovering the brakes were not functioning normally.NTSB NYC01IA126Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Newark, OHThe company maintenance personnel's failure to comply with the service bulletin, which resulted in a fuel boost pump leakage and subsequent fire during taxi. A factor was the manufacturer's confusing service bulletin.NTSB DEN01LA077Accident · No injuriesLimited investigationFinal reportBell UH-1H · Zuni, NMa hard landing due to the pilot's failure to maintain aircraft control during autorotation/flare. A factor was the total loss of engine power due to mechanical failure.NTSB MIA01LA097Accident · No injuriesLimited investigationFinal reportEnstrom F-28C · Orlando, FLa fire due to a broken and separated turbocharger exhaust which allowed hot exhaust to ignite the engine shroud.NTSB MIA01LA079Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Lakeland, FLThe pilot's failure to disengage the parking brake prior to taxi and his failure to stop and investigate the brakes when they malfunctioned during taxi for takeoff resulting in the wheel brakes heating and starting the tires on fire.NTSB ATL01LA026Accident · Serious injuriesLimited investigationFinal reportCessna 172 F · Greenwood, MSAn in-flight fire for undetermined reasons. Finding: A factor is the maintenance modification was performed by company personnel prior to the flight.