# NTSB investigations: Near collision between aircraft NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports. Page 1 of 3 · 115 cases ## Latest cases - [NTSB OPS08IA004](https://openairdocs.org/ntsb/OPS08IA004.md): Gulfstream American G5 · Teterboro, NJ · Incident · No injuries · Incident investigation · Final report · Dec 27, 2007 · N90AM · 2 aircraft · No damage > The 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 OPS08IA002](https://openairdocs.org/ntsb/OPS08IA002.md): Bombardier CRJ1 · Baltimore, MD · Incident · No injuries · Incident investigation · Final report · Dec 3, 2007 · N781CA · 2 aircraft · No damage > The 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 OPS08IA001](https://openairdocs.org/ntsb/OPS08IA001.md): Cessna C 525 · Memphis, TN · Incident · No injuries · Incident investigation · Final report · Oct 12, 2007 · N241EP · No damage > The probable cause of this incident was the pilot's inadvertent departure from a taxiway instead of a runway. - [NTSB OPS07IA009](https://openairdocs.org/ntsb/OPS07IA009.md): Boeing 737-700 · Los Angeles, CA · Incident · No injuries · Incident investigation · Final report · Aug 16, 2007 · C-FUWS · 2 aircraft · No damage > The 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 OPS07IA008](https://openairdocs.org/ntsb/OPS07IA008.md): Learjet 45 · Teterboro, NJ · Incident · No injuries · Incident investigation · Final report · Aug 13, 2007 · N145AP · 2 aircraft · No damage > A 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 OPS07IA006](https://openairdocs.org/ntsb/OPS07IA006.md): Boeing 757-232 · Fort Lauderdale, FL · Incident · No injuries · Incident investigation · Final report · Jul 11, 2007 · N6714Q · 2 aircraft · No damage > The probable cause of this incident was the United flightcrews' inadvertant entry onto an active runway. - [NTSB OPS07IA007](https://openairdocs.org/ntsb/OPS07IA007.md): Boeing 737 · New York City, NY · Incident · No injuries · Incident investigation · Final report · Jul 5, 2007 · N737DA · 2 aircraft · No damage > ATC - 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 OPS07IA005](https://openairdocs.org/ntsb/OPS07IA005.md): Piaggio Industrie P180 · Teterboro, NJ · Incident · No injuries · Incident investigation · Final report · Jun 17, 2007 · N152SL · 2 aircraft · Minor damage > The TEB local controller's failure to ensure separation between two aircraft departing intersecting runways. - [NTSB OPS07IA004](https://openairdocs.org/ntsb/OPS07IA004.md): Embraer 170 · San Francisco, CA · Incident · No injuries · Incident investigation · Final report · May 26, 2007 · N872RW · 2 aircraft · No damage > Failure of SFO tower local controller to provide adequate separation between two aircraft departing intersecting runways. - [NTSB OPS07IA001](https://openairdocs.org/ntsb/OPS07IA001.md): Swearingen SW-4 · Denver, CO · Incident · No injuries · Incident investigation · Final report · Jan 5, 2007 · N425MA · 2 aircraft · No damage > The 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 OPS06IA008](https://openairdocs.org/ntsb/OPS06IA008.md): Boeing 737-322 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Jul 24, 2006 · N315UA · 2 aircraft · No damage > The 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 OPS06IA007](https://openairdocs.org/ntsb/OPS06IA007.md): Boeing 737-300 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Mar 23, 2006 · N309UA · 2 aircraft · No damage > The 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 OPS06IA006](https://openairdocs.org/ntsb/OPS06IA006.md): Airbus Industrie 319 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Mar 21, 2006 · D-APAC · 2 aircraft · No damage > The 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 LAX06FA099](https://openairdocs.org/ntsb/LAX06FA099.md): Beechcraft F33A · Buckeye, AZ · Accident · 1 fatal · Field investigation · Final report · Feb 1, 2006 · N1563A · Destroyed > The student pilot's failure to maintain aircraft control for undetermined reasons. - [NTSB OPS06IA004](https://openairdocs.org/ntsb/OPS06IA004.md): EADS Socata A320 · Las Vegas, NV · Incident · No injuries · Incident investigation · Final report · Jan 28, 2006 · UNK · 2 aircraft · No damage > Deficient 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 OPS06IA001](https://openairdocs.org/ntsb/OPS06IA001.md): Boeing 737-400 · Fort Lauderdale, FL · Incident · No injuries · Incident investigation · Final report · Nov 9, 2005 · UNKNO WN · No damage > the 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 LAX04IA302](https://openairdocs.org/ntsb/LAX04IA302.md): Boeing 737-7H4 · Los Angeles, CA · Incident · No injuries · Incident investigation · Final report · Aug 19, 2004 · N461WN · No damage > a 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 DEN02FA105](https://openairdocs.org/ntsb/DEN02FA105.md): Piper PA-24-260 · Rock Springs, WY · Accident · No injuries · Field investigation · Final report · Sep 15, 2002 · N8822P · 2 aircraft · Substantial damage > the 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 CHI02FA200](https://openairdocs.org/ntsb/CHI02FA200.md): Piper PA-20 · Oshkosh, WI · Accident · No injuries · Field investigation · Final report · Jul 21, 2002 · N1592A · Substantial damage > Inadequate 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 FTW01IA183](https://openairdocs.org/ntsb/FTW01IA183.md): Boeing 737-347 · DFW Airport, TX · Incident · No injuries · Incident investigation · Final report · Aug 16, 2001 · N308WA · 2 aircraft · Minor damage > The 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 SEA01LA120](https://openairdocs.org/ntsb/SEA01LA120.md): Cessna 150L · Port Townsend, WA · Accident · No injuries · Limited investigation · Final report · Jun 20, 2001 · N19218 · Substantial damage > An 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 CHI00IA248](https://openairdocs.org/ntsb/CHI00IA248.md): Aerospatiale ATR-42-2000 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Aug 6, 2000 · N269AE · 2 aircraft · No damage > the improper takeoff clearance issued by the local controller. - [NTSB ANC00IA088](https://openairdocs.org/ntsb/ANC00IA088.md): McDonnell Douglas MD-82 · Anchorage, AK · Incident · No injuries · Incident investigation · Final report · Jul 11, 2000 · N935AS · No damage > An inoperative traffic alert and collision avoidance system (TCAS). - [NTSB CHI00IA062](https://openairdocs.org/ntsb/CHI00IA062.md): British Aerospace Jetstream 3101 · Milwaukee, WI · Incident · No injuries · Incident investigation · Final report · Jan 21, 2000 · N842JS · No damage > the hold-short clearance not being followed by the flightcrew, which resulted in a near collision with the departing Boeing 727-200. - [NTSB LAX00FA041](https://openairdocs.org/ntsb/LAX00FA041.md): McDonnell Douglas DC-10-30F · Honolulu, HI · Accident · No injuries · Field investigation · Final report · Nov 8, 1999 · N602GC · Substantial damage > The 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 CHI99IA100](https://openairdocs.org/ntsb/CHI99IA100.md): McDonnell Douglas DC-10 · Salina, KS · Incident · No injuries · Incident investigation · Final report · Mar 2, 1999 · N40061 · 2 aircraft · No damage > The 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 DCA99IA023](https://openairdocs.org/ntsb/DCA99IA023.md): Boeing 757 · Washington, DC · Incident · No injuries · Incident investigation · Final report · Nov 29, 1998 · UNK · No damage > Undetermined. - [NTSB CHI97IA164](https://openairdocs.org/ntsb/CHI97IA164.md): Douglas DC-10-30F · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Jun 10, 1997 · N302FE · No damage > the lack of communications to assure safe operations between aircraft on a non-movement area. - [NTSB CHI97LA162](https://openairdocs.org/ntsb/CHI97LA162.md): Boeing 737-300 · Valparaiso, IN · Accident · Serious injuries · Limited investigation · Final report · Jun 8, 1997 · N321UA · No damage > a delay by the pilot of the other aircraft in turning on his mode C transponder. - [NTSB LAX97FA164](https://openairdocs.org/ntsb/LAX97FA164.md): Boeing 737-3S3 · Las Vegas, NV · Accident · Serious injuries · Field investigation · Final report · Apr 19, 1997 · N313AW · No damage > inadequate 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 ANC96IA065](https://openairdocs.org/ntsb/ANC96IA065.md): Veazie Super Acro Zenith CH · Fairbanks, AK · Incident · No injuries · Incident investigation · Final report · May 2, 1996 · N200BV · No damage > the 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 FTW95IA126](https://openairdocs.org/ntsb/FTW95IA126.md): Mcdonnell Douglas MD11 · Dallas-Ft Worth, TX · Incident · No injuries · Incident investigation · Final report · Feb 28, 1995 · N1763 · 2 aircraft · No damage > The 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 CHI95IA095](https://openairdocs.org/ntsb/CHI95IA095.md): Boeing 747-136 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Feb 26, 1995 · GAWNM · No damage > the 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 LAX94IA331](https://openairdocs.org/ntsb/LAX94IA331.md): Mcdonnell Douglas MD-82 · Reno, NV · Incident · Minor injuries · Incident investigation · Final report · Aug 19, 1994 · N954AS · No damage > Failure 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 ANC94IA075](https://openairdocs.org/ntsb/ANC94IA075.md): Boeing 737-400 · Juneau, AK · Incident · No injuries · Incident investigation · Final report · Jul 2, 1994 · N769AS · 2 aircraft · No damage > The 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 CHI93IA167](https://openairdocs.org/ntsb/CHI93IA167.md): Cessna 550 · West Chicago, IL · Incident · No injuries · Incident investigation · Final report · May 10, 1993 · N41SM · No damage > Inadequate control tower service by the local air traffic controller by providing conflicting clearances to the pilots of two aircraft. - [NTSB NYC93IA065](https://openairdocs.org/ntsb/NYC93IA065.md): Boeing 727-100 · Newark, NJ · Incident · No injuries · Incident investigation · Final report · Mar 23, 1993 · N107FE · No damage > The 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 ANC93IA007](https://openairdocs.org/ntsb/ANC93IA007.md): Boeing 737-200 · Anchorage, AK · Incident · No injuries · Incident investigation · Final report · Oct 8, 1992 · N673MA · 2 aircraft · No damage > Improper 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 CHI92LA259](https://openairdocs.org/ntsb/CHI92LA259.md): Mooney 20F · Lacon, IL · Accident · No injuries · Limited investigation · Final report · Aug 29, 1992 · N3486N · Substantial damage > The 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 MIA92LA147](https://openairdocs.org/ntsb/MIA92LA147.md): Maule MX-7-180 · Okeechobee, FL · Accident · Minor injuries · Limited investigation · Final report · Jul 7, 1992 · N148DP · Substantial damage > The 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 ANC92IA100](https://openairdocs.org/ntsb/ANC92IA100.md): Fairchild SA227-AC · Dillingham, AK · Incident · No injuries · Incident investigation · Final report · Jun 26, 1992 · N620PA · 2 aircraft · No damage > The 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 FTW92IA158](https://openairdocs.org/ntsb/FTW92IA158.md): Piper PA-31T · Addison, TX · Incident · No injuries · Incident investigation · Final report · Jun 10, 1992 · N182TC · 2 aircraft · No damage > The failure of the pilot-in-command of the PA-38, N2603B, to follow ATC instructions. - [NTSB CHI92IA061](https://openairdocs.org/ntsb/CHI92IA061.md): Mcdonnell Douglas DC-10-30 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Dec 23, 1991 · N142AA · 2 aircraft · No damage > The 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 LAX91IA297](https://openairdocs.org/ntsb/LAX91IA297.md): Boeing 747-200 · Los Angeles, CA · Incident · No injuries · Incident investigation · Final report · Aug 13, 1991 · ZKNZW · No damage > The 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 ATL91LA135](https://openairdocs.org/ntsb/ATL91LA135.md): Piper PA-24-260 · Springfield, TN · Accident · Minor injuries · Limited investigation · Final report · Jul 16, 1991 · N8739P · Substantial damage > The 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 LAX90FA233](https://openairdocs.org/ntsb/LAX90FA233.md): Bellanca 17-30A · Ojai, CA · Accident · Minor injuries · Field investigation · Final report · Jun 28, 1990 · N39843 · 2 aircraft · Substantial damage > Structural damage sustained by the Bellanca, N39843, as a result of encountering wake turbulence during a near-collision with a navy F-14A. - [NTSB MIA90IA039](https://openairdocs.org/ntsb/MIA90IA039.md): Boeing 727 · Ormond Beach, FL · Incident · No injuries · Incident investigation · Final report · Dec 15, 1989 · N64339 · 2 aircraft · No damage > Failure 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 CHI89IA179](https://openairdocs.org/ntsb/CHI89IA179.md): Boeing 767-231 · Knox, IN · Incident · Minor injuries · Incident investigation · Final report · Sep 5, 1989 · N608TW · No damage > The 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 CHI89IA144](https://openairdocs.org/ntsb/CHI89IA144.md): Dornier DO-228 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Jul 9, 1989 · N263MC · No damage > Poor lookout by the crew of the Dornier and the baron. - [NTSB CHI89IA143](https://openairdocs.org/ntsb/CHI89IA143.md): Mcdonnell Douglas DC-9-32 · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Jul 9, 1989 · N939ML · No damage > Poor lookout by the crew of the DC-9 and the Cessna pilot. Next page: https://openairdocs.org/ntsb.md?occurrence=280&page=2 ## The whole list in SQL Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS: ```sql 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."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 ``` This list as a web page: https://openairdocs.org/ntsb?occurrence=280 --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.