Final NTSB investigations
115 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 c.\"completionStatus\" = 'Completed'
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 c."completionStatus" = 'Completed' 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 OPS08IA004Incident · No injuriesIncident investigationFinal reportGulfstream American G5 · Teterboro, NJThe probable cause of this incident was the TEB tower local controller's failure to ensure that the runway was free of all known ground vehicles, equipment, and personnel before permitting a departing aircraft to start takeoff roll.NTSB OPS08IA002Incident · No injuriesIncident investigationFinal reportBombardier CRJ1 · Baltimore, MDThe probable cause of this incident is local controller's failure of maintaining awareness of the situation and failing to provide the appropriate separation between the two aircraft operating on intersecting runways. Providing separation between aircraft is…NTSB OPS08IA001Incident · No injuriesIncident investigationFinal reportCessna C 525 · Memphis, TNThe probable cause of this incident was the pilot's inadvertent departure from a taxiway instead of a runway.NTSB OPS07IA009Incident · No injuriesIncident investigationFinal reportBoeing 737-700 · Los Angeles, CAThe LAX north ground controller's failure to properly coordinate with the tower local controller prior to providing taxi instructions that permitted an aircraft to cross an active runway while another aircraft was departing. **This report was modified on…NTSB OPS07IA008Incident · No injuriesIncident investigationFinal reportLearjet 45 · Teterboro, NJA runway incursion occurred when the local controller did not ensure that N145AP has passed the intersection of runways 1 and 6 prior to authorizing N336FX to depart runway 1.NTSB OPS07IA006Incident · No injuriesIncident investigationFinal reportBoeing 757-232 · Fort Lauderdale, FLThe probable cause of this incident was the United flightcrews' inadvertant entry onto an active runway.NTSB OPS07IA007Incident · No injuriesIncident investigationFinal reportBoeing 737 · New York City, NYATC - The incident occurred because the ground controller instructed COM5196 to cross runway 22, without approval from the local controller, resulting in a loss of separation with DAL1238 that was landing on the same runway.NTSB OPS07IA005Incident · No injuriesIncident investigationFinal reportPiaggio Industrie P180 · Teterboro, NJThe TEB local controller's failure to ensure separation between two aircraft departing intersecting runways.NTSB OPS07IA004Incident · No injuriesIncident investigationFinal reportEmbraer 170 · San Francisco, CAFailure of SFO tower local controller to provide adequate separation between two aircraft departing intersecting runways.NTSB OPS07IA001Incident · No injuriesIncident investigationFinal reportSwearingen SW-4 · Denver, COThe probable cause of the incident was the Key Lime Air flight 4216 pilot's inadvertant entry onto the active runway. A contributing factor to the incident was the failure of the Denver tower ground and local controllers to detect the aircraft on the airport…NTSB OPS06IA008Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILThe failure of the ORD tower south local controller to monitor Atlas Air flight 6972 on arrival to runway 14R and subsequently clearing United Airlines flight 1015 for takeoff on intersecting runway 27L causing a loss of separation between the two aircraft.NTSB OPS06IA007Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Chicago, ILThe probable cause of this incident was the ORD tower local controller's failure to provide sufficient separation between two aircraft departing intersecting runways. Contributing to the incident was the ORD local monitor's failure to monitor the situating…NTSB OPS06IA006Incident · No injuriesIncident investigationFinal reportAirbus Industrie 319 · Chicago, ILThe probable cause of the incident was the local controller's failure to ensure proper separation between Lufthansa flight 437 and Chautauqua (CHQ) flight 7826. Contributing was the failure of the local monitor to monitor the situation and advise the local…NTSB LAX06FA099Accident · 1 fatalField investigationFinal reportBeechcraft F33A · Buckeye, AZThe student pilot's failure to maintain aircraft control for undetermined reasons.NTSB OPS06IA004Incident · No injuriesIncident investigationFinal reportEADS Socata A320 · Las Vegas, NVDeficient FAA procedures for separation of aircraft using converging runways, which failed to ensure that the tower controllers were able to provide adequate separation in the event of a go-around.NTSB OPS06IA001Incident · No injuriesIncident investigationFinal reportBoeing 737-400 · Fort Lauderdale, FLthe local controller's failure to monitor the operation and recognize a developing traffic conflict which resulted in a loss of separation between USA1251 and ComAir 5026. Contributing to the accident was the controller's incorrect prioritization of his…NTSB LAX04IA302Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Los Angeles, CAa loss of separation between Southwest flight 440 and Asiana flight 204 due to the LC2 relief controller's failure to appropriately monitor the operation and recognize a developing traffic conflict. Contributing factors included the FAA's position relief…NTSB DEN02FA105Accident · No injuriesField investigationFinal reportPiper PA-24-260 · Rock Springs, WYthe flight crew of the Beech and the pilot of the Piper's failure to attain proper clearance from the other during their respective landings. Factors contributing to the accident were the crew's and the pilot of the other airplane's inadequate visual lookout…NTSB CHI02FA200Accident · No injuriesField investigationFinal reportPiper PA-20 · Oshkosh, WIInadequate visual lookout by both the accident pilot and the pilot of the other airplane. An additional cause is the arrival procedure used which resulted in a congested traffic pattern and the subsequent inadequate visual separation of the airplanes. Factors…NTSB FTW01IA183Incident · No injuriesIncident investigationFinal reportBoeing 737-347 · DFW Airport, TXThe local controller clearing the taxiing aircraft to cross the runway in front of the aircraft on takeoff roll. Contributing factors were the local controller's failure to follow FAA procedures and directives to visually scan the runway prior to issuing the…NTSB SEA01LA120Accident · No injuriesLimited investigationFinal reportCessna 150L · Port Townsend, WAAn improper decision by the pilot to initiate an evasive maneuver toward the ground at low altitude, resulting in a hard landing. A factor was the aircraft's low altitude.NTSB CHI00IA248Incident · No injuriesIncident investigationFinal reportAerospatiale ATR-42-2000 · Chicago, ILthe improper takeoff clearance issued by the local controller.NTSB ANC00IA088Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas MD-82 · Anchorage, AKAn inoperative traffic alert and collision avoidance system (TCAS).NTSB CHI00IA062Incident · No injuriesIncident investigationFinal reportBritish Aerospace Jetstream 3101 · Milwaukee, WIthe hold-short clearance not being followed by the flightcrew, which resulted in a near collision with the departing Boeing 727-200.NTSB LAX00FA041Accident · No injuriesField investigationFinal reportMcDonnell Douglas DC-10-30F · Honolulu, HIThe pilot-in-command initiated an evasive manuver during a near midair collission. The airplane entered a prestall buffet, which resulted in buckling of the elevator skins.NTSB CHI99IA100Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC-10 · Salina, KSThe ARTCC personnel failed to maintain radio communications with both airplanes and failed to maintain IFR separation standards. Factors relating to the incident were the FAA does not require cargo airplanes to be equipped with TCAS and neither airplane was…NTSB DCA99IA023Incident · No injuriesIncident investigationFinal reportBoeing 757 · Washington, DCUndetermined.NTSB CHI97IA164Incident · No injuriesIncident investigationFinal reportDouglas DC-10-30F · Chicago, ILthe lack of communications to assure safe operations between aircraft on a non-movement area.NTSB CHI97LA162Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Valparaiso, INa delay by the pilot of the other aircraft in turning on his mode C transponder.NTSB LAX97FA164Accident · Serious injuriesField investigationFinal reportBoeing 737-3S3 · Las Vegas, NVinadequate service provided by the TRACON controller, by issuing a radar vector to the Boeing 737 flight, which resulted in inadequate separation from a Beech 99 that the controller had just terminated from radar service; and failure of the controller to…NTSB ANC96IA065Incident · No injuriesIncident investigationFinal reportVeazie Super Acro Zenith CH · Fairbanks, AKthe pilot's improper understanding of his amended clearance, and the local controller's failure to assure that the pilot understood that he was cleared only to land. Factors in the incident were: the airport design that places two airplanes in close proximity…NTSB FTW95IA126Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas MD11 · Dallas-Ft Worth, TXThe local controller's task overload, which led him to forget to issue appropriate traffic advisories and to lose his awareness of the traffic situation, and the failure of the controller's supervisor to recognize that the controller had reached or exceeded…NTSB CHI95IA095Incident · No injuriesIncident investigationFinal reportBoeing 747-136 · Chicago, ILthe North Local Controller's failure to issue a clearance which would ensure separation between the two airplanes and the North Local Control Monitor's failure to adequately back up the controller. Factors were the complexity of the airport operations and…NTSB LAX94IA331Incident · Minor injuriesIncident investigationFinal reportMcdonnell Douglas MD-82 · Reno, NVFailure of the area supervisor/departure controller (supvr/ctlr) to stay at his radar position and ensure that required communications were maintained. Factors related to the incident were: failure of the local tower controller instruct the flightcrew of…NTSB ANC94IA075Incident · No injuriesIncident investigationFinal reportBoeing 737-400 · Juneau, AKThe failure of the local controller to exercise his responsibility to have each aircraft adjust its flightpath to remain clear of the other, and the failure of the pilot of the Cessna 185 to maintain adequate visual separation from the Boeing 737.NTSB CHI93IA167Incident · No injuriesIncident investigationFinal reportCessna 550 · West Chicago, ILInadequate control tower service by the local air traffic controller by providing conflicting clearances to the pilots of two aircraft.NTSB NYC93IA065Incident · No injuriesIncident investigationFinal reportBoeing 727-100 · Newark, NJThe pilot's misunderstanding of landing runway, and the failure of the local controller to adequately monitor the progress of the flight. Factors which contributed to the incident were: the failure of tower personnel to notify TRACON of the ATIS change, the…NTSB ANC93IA007Incident · No injuriesIncident investigationFinal reportBoeing 737-200 · Anchorage, AKImproper ATC clearance instructions by the approach controller, resulting in a failure to insure safe separation between an airplane in visual conditions with an airplane in instrument meteorological conditions on converging courses. A factor which…NTSB CHI92LA259Accident · No injuriesLimited investigationFinal reportMooney 20F · Lacon, ILThe pilot's failure to recognize that the runway he selected for landing was closed. Factors which contributed to the accident were: the pilot's anxiety following the near-collision, and his limited ability to detect the orange-colored marking.NTSB MIA92LA147Accident · Minor injuriesLimited investigationFinal reportMaule MX-7-180 · Okeechobee, FLThe failure of the pilot-in-command of N148DP to obtain NOTAM information concerning military routes along his route of flight, resulting in his encounter with a flight of F16 aircraft who were operating on a military route.NTSB ANC92IA100Incident · No injuriesIncident investigationFinal reportFairchild SA227-AC · Dillingham, AKThe pilot in command's failure to maintain a visual lookout. Factors were the drizzle and fog and the impossibility of updating the recorded weather information by ATC personnel.NTSB FTW92IA158Incident · No injuriesIncident investigationFinal reportPiper PA-31T · Addison, TXThe failure of the pilot-in-command of the PA-38, N2603B, to follow ATC instructions.NTSB CHI92IA061Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-10-30 · Chicago, ILThe local controller's not understanding read back of radio communications. Factors include the pilot-in-command of flight 73 not understanding verbal instructions; local controller not visually identifying the aircraft; and inadequate surveillance (FAA) in…NTSB LAX91IA297Incident · No injuriesIncident investigationFinal reportBoeing 747-200 · Los Angeles, CAThe inadequate runway safety area inherent in the airport design, and, the ATC clearance procedures in use which failed to take into consideration the substandard runway safety area. Factors in the incident were the dark night time conditions and the…NTSB ATL91LA135Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-260 · Springfield, TNThe PA-24 pilot's failure to maintain proper airspeed while executing a go-around, resulting in the stalling of the airplane. A factor in the accident was the PA-24 pilot's failure to visually detect the J-3 in a timely manner.NTSB LAX90FA233Accident · Minor injuriesField investigationFinal reportBellanca 17-30A · Ojai, CAStructural damage sustained by the Bellanca, N39843, as a result of encountering wake turbulence during a near-collision with a navy F-14A.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.