NTSB investigations, 2000
180,624 investigations by the National Transportation Safety Board since 1962: 174,602 accidents, the rest incidents and other occurrences. Each has NTSB’s narrative and, once the investigation is done, its probable cause; since 2008, its findings and sequence of events.
Cases, newest first
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\") = 2000 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") = 2000 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 FTW00LA059Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Sweeney, TXThe pilot's excessive flare resulting in a hard landing. Factors were the loss of engine power for undetermined reasons, the power lines on final approach and the dark night conditions.NTSB DCA00RA019Accident · 10 fatalForeign investigationSaab-Scania 340 · Zurich, SwitzerlandNTSB NYC00LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Harpswell, MEwas the improper decision of the pilot to depart at night, from an unlighted runway with no visual references to obstructions on the sides of the runway. Factors were the dark night conditions, and the lack of runway side lights.NTSB MIA00LA067Accident · No injuriesLimited investigationFinal reportSwearingen SX300 · Jekyll Island, GAfailure of the left main landing gear attachment during the landing/flare touchdown for undetermined reasons, resulting in the loss of directional control and the airplane exiting the runway and colliding with a runway light.NTSB MIA00LA065Accident · 1 fatalLimited investigationFinal reportSlater P-51 · Hampstead, NCThe pilots failure to maintain airspeed (VSO) while maneuve ring on a turn to crosswind resulting in an inadvertent stall/spin, and subsequent in-flight collision with trees and terrain.NTSB IAD00LA016Accident · No injuriesLimited investigationFinal reportBellanca 7ECA · Waynesburg, PAthe pilot's failure to maintain aircraft control during the landing roll-out.NTSB DEN00LA040Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201 · Pueblo, COCollision with a deer during landing roll. Factors were a dark night and lack of wildlife control devices on the airport.NTSB DEN00LA039Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Albuquerque, NMThe pilot's failure to comply with proper procedures for engine startup by failing to disengage the magneto prior to hand-turning the propeller.NTSB LAX00LA070Accident · Serious injuriesLimited investigationFinal reportHawker Siddeley Hunter F MK 4 · Chino, CAA loss of engine power for undetermined reasons. A factor was the particulate contamination in the fuel.NTSB LAX00LA069Accident · No injuriesLimited investigationFinal reportCessna 177B · Rialto, CAThe failure of the maintenance personnel to follow the manufacturer's procedures and directives regarding the proper torquing of the screws securing the oil pressure screen housing, which resulted in the loss of lubricating oil, and the subsequent seizure of…NTSB LAX00LA068Accident · 1 fatalLimited investigationFinal reportClark Pitts S1X · Upland, CAThe pilot's failure to recover from an intentional aerobatic maneuver.NTSB DEN00LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · Huntsville, UTThe snow shower, and the lack of suitable terrain for the precautionary landing.NTSB DEN00LA038Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Rock Springs, WYA forced landing on rough, unsuitable terrain. Factors were: Inadequate preflight planning, flight into known adverse weather conditions containing snow, high gusting winds, low temperatures, and a total loss of power for non mechanical reasons due to…NTSB ATL00FA023Accident · 2 fatalField investigationFinal reportBeech 23 · Macon, GAThe loss of engine power for undetermined reasons. A factor was conditions favorable for the formation of carburetor ice.NTSB SEA00FA037Accident · 1 fatalField investigationFinal reportCessna 150G · Marysville, WAFuel exhaustion due to the non-certificated 'pilot's' failure to determine the fuel quantity prior to takeoff. Factors include a dark night, and a non-iluminated electrical transmission wire strung across the highway upon which the pilot was attempting to…NTSB NYC00FA063Accident · 2 fatalField investigationFinal reportCessna 310N · Old Forge, PABoth pilots' failure to adequately manage the fuel supply, which resulted in fuel starvation.NTSB MIA00FA064Accident · 1 fatalField investigationFinal reportCessna 172R · Atlantic Ocean (Atlantic Ocean)The pilot's lack of total experience in instrument flight, simulated instrument flight, and night flight resulting in the pilot becoming spatially disoriented, and subsequent in-flight collision with water. Contributing to the accident was the dark night with…NTSB CHI00FA057Accident · 1 fatalField investigationFinal reportBeech D-95A Travelair · Dunbar, WIthe pilot failed to maintain a proper glidepath and obstacle clearance during an instrument approach. Additional factors to the accident included the dark night, icing conditions, flight into known adverse weather, and conditions conducive to pilot fatigue.NTSB IAD00LA015Accident · No injuriesLimited investigationFinal reportBell 206A · Brutus, NYWas the pilot's failure to maintain directional control after encountering a loss of tail rotor effectiveness.NTSB DEN00LA036Accident · No injuriesLimited investigationFinal reportBeech B200 · Jackson, WYThe pilot misreading the visual approach lighting system, resulting in his failure to maintain proper alignment with the runway and his selection of an improper touchdown point. Factors were the low ceiling weather conditions and the snow covered runway.NTSB MIA00LA061Accident · No injuriesLimited investigationFinal reportEaa Chapter 229 Zenair 601 · Kissimmee, FLThe pilot's failure to maintain directional control on landing resulting in the airplane going off the side of the runway and colliding with a barricade.NTSB LAX00LA071Accident · No injuriesLimited investigationFinal reportRotorway Exec 90 · Chandler, AZthe fatigue fracture and separation of the secondary drive shaft, which resulted from the manufacturer's inadequate quality control process.NTSB ATL00FA021Accident · 2 fatalField investigationFinal reportPiper PA-24-180 · Cordesville, SCThe pilot's inadequate inflight planning that resulted in fuel exhaustion and the subsequent loss of engine power.NTSB MIA00FA060Accident · No injuriesField investigationFinal reportRobinson R44 · Cayey, PRThe pilot's failure to use carburetor heat as required by the Pilot's Operating Handbook resulting in a loss of engine and rotor rpm, forced landing to none suitable terrain (residence), and subsequent roll over.NTSB LAX00LA063Accident · No injuriesLimited investigationFinal reportCessna 172G · Victorville, CAThe failure of the pilot to maintain positional awareness, which resulted in his becoming lost and disoriented. Contributing factors were the pilot's delay requesting assistance from air traffic control and the failure of the airplane's electrical generator.NTSB FTW00LA067Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Corning, ARThe loss of engine power for an undetermined reason. A factor was the dark night light condition.NTSB FTW00LA058Accident · No injuriesLimited investigationFinal reportCessna A185F · Houston, TXthe loss of engine power during climb as a result of fatigue cracking of the #4 cylinder head and its subsequent separation from its barrel.NTSB LAX00LA062Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Dos Palos, CAA partial loss of engine power due to the failure of maintenance personnel to properly install and safety the throttle arm to the carburetor throttle shaft.NTSB FTW00LA057Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Odessa, TXThe separation of the #1 piston pin due to fatigue, which resulted in a total loss of engine power. A factor was the lack of suitable terrain for the forced landing.NTSB DEN00FA037Accident · 1 fatalField investigationFinal reportCessna 421B · Telluride, COThe non-instrument rated pilot's intentional flight into IMC, and his subsequent spatial disorientation that resulted in an inadvertent stall. A factor was the snow showers weather condition.NTSB DCA00WA018Incident · No injuriesForeign investigationBoeing 737-3K2 · Amsterdam, NetherlandsNTSB MIA00LA063Accident · No injuriesLimited investigationFinal reportCessna 550 · Homestead, FLAn inadvertent in-flight collision with a bird in cruise flight resulting in substantial damage to the airplane.NTSB ATL00FA019Accident · 2 fatalField investigationFinal reportBellanca BL-17-30A · Monteagle, TNThe pilot's failure to adequately evaluate weather conditions that resulted in the continuation of visual flight into instrument weather conditions and the subsequent collision with trees.