NTSB investigations, 1992
12 cases where the first occurrence was “Midair collision”.
Cases per year
| 1982 | 30 |
|---|---|
| 1983 | 14 |
| 1984 | 26 |
| 1985 | 25 |
| 1986 | 29 |
| 1987 | 25 |
| 1988 | 18 |
| 1989 | 19 |
| 1990 | 23 |
| 1991 | 23 |
| 1992 | 12 |
| 1993 | 13 |
| 1994 | 12 |
| 1995 | 15 |
| 1996 | 17 |
| 1997 | 15 |
| 1998 | 15 |
| 1999 | 17 |
| 2000 | 19 |
| 2001 | 7 |
| 2002 | 10 |
| 2003 | 11 |
| 2004 | 12 |
| 2005 | 11 |
| 2006 | 8 |
| 2007 | 9 |
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\") = 1992
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\" = 270)
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") = 1992 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" = 270) 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 LAX93FA055Accident · 5 fatalField investigationFinal reportCessna T210M · Thornton, CAThe failure of the pilots of both airplanes to see and avoid each other. Contributing to the accident was the failure of the sacramento controller to advise the stockton controller of the impending unsafe situation, and the failure of the stockton controller…NTSB BFO93LA006Accident · No injuriesLimited investigationFinal reportCessna 182 · Suffolk, VAFailure of the pilots in the Cessna 182 to visually identify and avoid the Cessna 150 (inadequate visual lookout). A factor related to the accident was: use of a nonstandard entry into the traffic pattern by the Cessna 182 flight crew.NTSB FTW93LA010Accident · Serious injuriesLimited investigationFinal reportRaven S-60A · Albuquerque, NMThe pilot's failure to maintain visual lookout.NTSB DCA92MA049Accident · 6 fatalClass 1 · MajorFinal reportMitsubishi MU-2B-60 · Greenwood, INThe inherent limitations of the see-and-avoid concept of separation of aircraft operating under visual flight rules that precluded the pilots of the MU-2 and the PA-32 from recognizing a collision hazard and taking actions to avoid the midair collision.…NTSB SEA92FA195Accident · 3 fatalField investigationFinal reportSnodgrass Starduster TOO · Lacey, WAThe failure of both pilots to see and avoid each other.NTSB LAX92FA367Accident · 1 fatalField investigationFinal reportCessna 182Q · Santa Paula, CAThe failure of both pilots to see and avoid each other. Contributing to the accident was the azimuth of the setting sun and the Cessna 182 pilots non standard flight pattern.NTSB CHI92FA201Accident · 4 fatalField investigationFinal reportCessna 172N · St Paul, MNInadequate visual lookout by the pilots of both airplanes, which resulted in their failure to see-and-avoid conflicting traffic, and failure of the relieving controllers to use the radar display to identify and sequence an airplane entering the pattern.…NTSB NYC92FA093Accident · 3 fatalField investigationFinal reportCessna 172N · Brookeville, MDImproper inflight planning/decision by the flight instructor (pic/cfi) in the Cessna 172, his misjudgement of distance between the two airplanes, and inadequate visual lookout by both pilots in the Cessna 172.NTSB ANC92FA069Accident · No injuriesField investigationFinal reportCessna 172 · Ruth Glacier, AKThe failure of the pilots of both airplanes to maintain an adequate visual lookout. Factors which contributed to the accident was the failure of the pilot of the CE-172 to become aware of and to use the listed frequency for inter aircraft communications, and…NTSB CHI92LA131Accident · Serious injuriesLimited investigationFinal reportCessna 152 · Branson, MOInadequate inflight planning/decision by the pilot in command in failing to maintain distance separation from the other aircraft.NTSB LAX92LA157Accident · No injuriesLimited investigationFinal reportCessna 172 · Prescott, AZThe other airplane's flight instructor's poor supervision of the flight; the other airplane's flight instructor's and dual student's misidentification of the airplane the student pilot was following and the other airplane's flight instructor's and dual…NTSB MIA92LA086Accident · No injuriesLimited investigationFinal reportCessna 172N · Orlando, FLThe pilots in command of both aircraft failure to maintain vigilance and see and avoid each other resulting in a midair collision. Contributing to the accident was the local controllers failure to issue traffic advisories.