NTSB investigations, 1987, DE
180,641 investigations by the National Transportation Safety Board since 1962: 174,620 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 per year
| 1962 | 1 |
|---|---|
| 1964 | 12 |
| 1965 | 18 |
| 1966 | 8 |
| 1967 | 21 |
| 1968 | 6 |
| 1969 | 14 |
| 1970 | 15 |
| 1971 | 9 |
| 1972 | 6 |
| 1973 | 9 |
| 1974 | 10 |
| 1975 | 12 |
| 1976 | 6 |
| 1977 | 2 |
| 1978 | 7 |
| 1979 | 3 |
| 1980 | 4 |
| 1981 | 5 |
| 1982 | 3 |
| 1983 | 4 |
| 1984 | 8 |
| 1985 | 4 |
| 1986 | 3 |
| 1987 | 5 |
| 1988 | 5 |
| 1989 | 4 |
| 1990 | 1 |
| 1991 | 4 |
| 1992 | 5 |
| 1993 | 1 |
| 1994 | 6 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 3 |
| 1998 | 3 |
| 1999 | 4 |
| 2000 | 2 |
| 2001 | 2 |
| 2002 | 1 |
| 2003 | 3 |
| 2005 | 5 |
| 2006 | 2 |
| 2007 | 4 |
| 2008 | 2 |
| 2009 | 3 |
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 2 |
| 2017 | 4 |
| 2018 | 1 |
| 2019 | 1 |
| 2020 | 4 |
| 2022 | 1 |
| 2024 | 2 |
| 2025 | 2 |
| 2026 | 1 |
Where
Latest 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\") = 1987
AND c.\"eventStateOrRegion\" = 'DE' AND c.\"eventCountry\" = 'USA'
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") = 1987 AND c."eventStateOrRegion" = 'DE' AND c."eventCountry" = 'USA' 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 BFO88DHD02Accident · No injuriesFinal reportBoeing A75N1 · Milton, DEThe pilot's improper brake application during a 'wheel' landing, which resulted in the aircraft nosing over. The slight downslope of the airstrip, a quartering tailwind, inadequate supervision on the part of the check pilot, and the pilot's lack of…NTSB BFO87DHD08Accident · Minor injuriesFinal reportBede BD5B · Wilmington, DEThe pilot's failure to attain sufficient altitude to clear obstacles located off the departure end of the runway. His overconfidence in the homebuilt aircraft's performance was a contributing factor.NTSB BFO87LA038Accident · Minor injuriesLimited investigationFinal reportCessna 150K · Selbyville, DEDuring takeoff the pilot stated that at about 150 to 200 feet he experienced a slow sinking of the aircraft. The engine was at full throttle, the flaps set at 10 degrees and the airspeed at 70 knots. The aircraft continued to sink and collided with trees.…NTSB BFO87LA028Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Dover, DEThe rockwell was in level flight at 2800 ft and the Piper was climbing when midair collision occurred. Neither acft was operating under ATC. Neither plt saw the otr acft before the collision occurred. The bottom of the rockwell cabin and the left tiptank of…NTSB ATL87FA100Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Georgetown, DEThe plt was cleared for approach with instructions to close flt plan upon landing. Aprx thirty min later approach control called the fss and asked if the plt had been in contact. The reply was negative. No further action was taken by approach control.…