NTSB investigations, 1990, CT
180,610 investigations by the National Transportation Safety Board since 1962: 174,589 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 | 32 |
| 1965 | 45 |
| 1966 | 50 |
| 1967 | 48 |
| 1968 | 34 |
| 1969 | 31 |
| 1970 | 34 |
| 1971 | 40 |
| 1972 | 31 |
| 1973 | 34 |
| 1974 | 24 |
| 1975 | 22 |
| 1976 | 18 |
| 1977 | 27 |
| 1978 | 26 |
| 1979 | 26 |
| 1980 | 21 |
| 1981 | 14 |
| 1982 | 22 |
| 1983 | 21 |
| 1984 | 33 |
| 1985 | 17 |
| 1986 | 23 |
| 1987 | 24 |
| 1988 | 17 |
| 1989 | 18 |
| 1990 | 17 |
| 1991 | 15 |
| 1992 | 21 |
| 1993 | 15 |
| 1994 | 13 |
| 1995 | 10 |
| 1996 | 14 |
| 1997 | 8 |
| 1998 | 16 |
| 1999 | 10 |
| 2000 | 9 |
| 2001 | 15 |
| 2002 | 12 |
| 2003 | 8 |
| 2004 | 13 |
| 2005 | 9 |
| 2006 | 7 |
| 2007 | 7 |
| 2008 | 9 |
| 2009 | 2 |
| 2010 | 4 |
| 2011 | 11 |
| 2012 | 6 |
| 2013 | 7 |
| 2014 | 5 |
| 2015 | 9 |
| 2016 | 8 |
| 2017 | 13 |
| 2018 | 8 |
| 2019 | 8 |
| 2020 | 5 |
| 2021 | 5 |
| 2022 | 5 |
| 2023 | 6 |
| 2024 | 6 |
| 2025 | 9 |
| 2026 | 3 |
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\") = 1990
AND c.\"eventStateOrRegion\" = 'CT' 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") = 1990 AND c."eventStateOrRegion" = 'CT' 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 NYC91LA043Accident · Minor injuriesLimited investigationFinal reportCessna 210L · New Haven, CTThe failure of the vehicle driver to adequately monitor the radio/traffic pattern. Factors related to the accident were: darkness, the aircraft's loss of electrical power after activating the runway lights and entering the pattern, and the lack of visual…NTSB NYC91DNE01Accident · No injuriesFinal reportCraig A. Gordon Teenie TWO · Oxford, CTThe failure of the pilot to maintain airspeed which resulted in an inadvertent stall and hard landing. Factors related to the accident were: the power loss and improper maintenance on the engine.NTSB NYC91LA017Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Bridgeport, CTThe pilot used excessive airspeed on the approach and landed long. The airplane went off the runway and struck a fence.NTSB NYC91FA006Accident · 2 fatalField investigationFinal reportCessna 152 · Griswold, CTA broken ehaust valve spring that resulted in a partial loss of power. Factors related to the accident were: darkness, lack of suitable terrain, and failure of the occupants to use their shoulder harnesses.NTSB NYC90LA207Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainville, CTThe pilot lost control of the airplane during a cross wind landing, subsequently running off the side of the runway and collided with the terrain.NTSB NYC90LA190Accident · No injuriesLimited investigationFinal reportBeech BE-23 · Burlington, CTThe CFI failed to maintain a safe sink rate resulting in an undershoot of the runway.NTSB NYC90LA146Accident · No injuriesLimited investigationFinal reportde Havilland DH-82-A · Burlington, CTThe pilot's inadequate compensation for the wind condition.NTSB NYC90LA145Accident · No injuriesLimited investigationFinal reportCessna 177B · Danielson, CTThe failure of the pilot to maintain proper runway alignment, and his failure to obtain or maintain adequate airspeed during a go-around, which resulted in an inadvertent stall and collision with the shrubs and trees.NTSB NYC90LA143Accident · 1 fatalLimited investigationFinal reportBoeing A75L3 · Groton, CTAn impact with the ground following an improperly executed roll with insufficient altitude for recovery. Factors related to the accident were improper use of the flight controls by the pilot.NTSB NYC90LA136Accident · Minor injuriesLimited investigationFinal reportClassic Waco · Plymouth, CTThe failure of the pilot to correctly recover from a bounced landing. Factors related to the accident were: improper use of the brakes by the pilot.NTSB NYC90FA130Accident · 1 fatalField investigationFinal reportConsolidated Aeronautics LA-4-200 · Danbury, CTThe inadvertent stall. A factor was the pilot's misjudgement of the landing flare.NTSB NYC90LA109Accident · No injuriesLimited investigationFinal reportStinson 108-3 · Warehouse Point, CTThe pilot failed to maintain directional control during a landing with a gusty crosswind.NTSB NYC90LA095Accident · No injuriesLimited investigationFinal reportBeech Baron 58 · Danbury, CTPilot factor in that the pilot elected to abort the takeoff with insufficient r/w remaining to stop the aircraft on the runway and collided with a fence, car & van.NTSB NYC90LA089Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Bridgeport, CTThe pilot failed to maintain directional control during a crosswind landing.NTSB NYC90LA065Accident · No injuriesLimited investigationFinal reportPiper PA-34-200 · E. Haddam, CTThe pilot failed to adequately compensate for wind conditions.NTSB NYC90FA063Accident · 1 fatalField investigationFinal reportPiper PA-28-181 · Fairfield, CTThe intoxicated pilot's failure to attain/maintain a safe altitude to provide clearance from the tree.NTSB NYC90LA056Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Danbury, CTImproper maintenance, inadequate surveillance by the company/operator, and inadequate preflight by the pilot, which resulted in a fire during an attempted engine start. A factor related to the accident was: the unsecured fuel line.