NTSB investigations, 1989
12 cases where the first occurrence was “Near collision between aircraft”.
Cases per year
| 1982 | 4 |
|---|---|
| 1984 | 8 |
| 1985 | 3 |
| 1986 | 10 |
| 1987 | 18 |
| 1988 | 14 |
| 1989 | 12 |
| 1990 | 1 |
| 1991 | 3 |
| 1992 | 5 |
| 1993 | 2 |
| 1994 | 2 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 3 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 3 |
| 2001 | 2 |
| 2002 | 2 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 5 |
| 2007 | 10 |
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\") = 1989
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\" = 280)
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") = 1989 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" = 280) 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 MIA90IA039Incident · No injuriesIncident investigationFinal reportBoeing 727 · Ormond Beach, FLFailure of the pilot in command in the Beech 300 to comply with an ATC clearance in a timely manner, while diverting his attention, and failure of the ATC controller to assure that IFR separation was maintained.NTSB CHI89IA179Incident · Minor injuriesIncident investigationFinal reportBoeing 767-231 · Knox, INThe radar controlller's failure to maintain radar separation. Factors contributing to the incident were: misunderstanding of an ATC instruction by the pilot of the incident airplane, and unclear phraseology used in the instructions issued by the radar…NTSB CHI89IA144Incident · No injuriesIncident investigationFinal reportDornier DO-228 · Chicago, ILPoor lookout by the crew of the Dornier and the baron.NTSB CHI89IA143Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-32 · Chicago, ILPoor lookout by the crew of the DC-9 and the Cessna pilot.NTSB BFO89IA036Incident · No injuriesIncident investigationFinal reportNorthrop T-38A · Washington, DCFailure of the T-38 pilot (in the other aircraft) to follow the ATC clearance and to maintain the proper altitude. Factors related to the incident were: failure of air traffic control (ATC) personnel to recognize the T-38'S improper altitude in a timely…NTSB LAX89IA184Incident · Minor injuriesIncident investigationFinal reportBoeing 747 · Los Angeles, CAInadequate visual look-out by the pilot of the other (small twin engine) aircraft. A factor related to the incident was: a delay of the 747 crew to see-and-avoid the other aircraft.NTSB NYC89IA222Incident · No injuriesIncident investigationFinal reportCessna 421C · New York, NYFailure of the liberty sector controller to advise pan am flight 542 of the presence of the Cessna 421 and/or restrict the climb of flight 542 until it had passed the Cessna, and failure of the pan am aircrew to see the Cessna in adequate time to avoid a near…NTSB NYC89IA123Incident · No injuriesIncident investigationFinal reportFairchild Swearingen SA-227AC · New York, NYThe failure of the swearingen flight crew to properly identify the airplane they were to follow, prior to accepting the visual approach to runway 31R.NTSB DEN89IA089Incident · No injuriesIncident investigationFinal reportBoeing 727-200A · San Antonio, TXFailure of the ARTCC controller to assure that the aircraft maintained IFR separation standards. The controller's heavy workload was a related factor.NTSB CHI89IA054Incident · No injuriesIncident investigationFinal reportShort Brothers SD360 · Chicago, ILThe PIC followed a clearance intended for another airplane.NTSB FTW89IA064Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-82 · Houston, TXFailure of the TRACON final approach controller to assure radar separation between the aircraft. Factors related to the accident were: inadequate supervision by the ATC supervisor, excessive workload for the controller, unclear instructions by the controller,…NTSB LAX89IA112Incident · No injuriesIncident investigationFinal reportBritish Aerospace BAE 146-200A · Los Alamitos, CAInadequate coordination among the ATC controllers which resulted in their failure to maintain adequate radar separation of the two aircraft.