# Final NTSB investigations: Air traffic event 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. ## Latest cases - [NTSB OPS24LA004](https://openairdocs.org/ntsb/OPS24LA004.md): Airbus A321-271N · Long Beach, CA · Incident · Class 4 · Limited · Final report · Oct 27, 2023 · N216HA · 2 aircraft · No damage > The local controller’s poor judgment in prioritization of their ground traffic ahead of their airborne traffic, that became a distraction and led to a loss of situational awareness resulting in a near midair collision. Contributing to the incident was the… - [NTSB OPS23FA010](https://openairdocs.org/ntsb/OPS23FA010.md): Boeing 737-7BD · San Diego, CA · Incident · Class 4 · Field · Final report · Aug 11, 2023 · N7734H · 2 aircraft · No damage > The local control controller’s poor judgment in duty prioritization which distracted them from monitoring arriving and departing traffic and resulted in a runway incursion and loss of same runway separation. Contributing was the operations supervisor’s… - [NTSB DCA23LA179](https://openairdocs.org/ntsb/DCA23LA179.md): Boeing 737-823 · Sarasota, FL · Incident · No injuries · Class 3 · Limited · Final report · Feb 17, 2023 · N976NN · 2 aircraft · No damage > The local controller’s failure to prioritize and properly monitor the runway and airport environment along with his erroneous assumption that ROU 1633 would depart from runway 14 before AAL2172 arrived to land on the same runway, which resulted in a loss of… - [NTSB OPS21LA002](https://openairdocs.org/ntsb/OPS21LA002.md): Airbus A319-112 · St Petersburg-Clearwater, FL · Incident · No injuries · Class 3 · Limited · Final report · Apr 29, 2021 · N306NV · 2 aircraft · No damage > The air traffic controller’s failure to properly scan the runway and local area, and their general loss of situational awareness, resulting in a near midair collision. Contributing to the incident was the Cessna 337 pilot's poor decision making when he failed… - [NTSB OPS18IA014](https://openairdocs.org/ntsb/OPS18IA014.md): Embraer EMB145 · Springfield, MO · Incident · Class 3 · Incident · Final report · Jun 27, 2018 · N655AE · No damage > The local controller failing to follow established facility directives and issuing a clearance for takeoff from a runway not under his control. - [NTSB DCA18LA024](https://openairdocs.org/ntsb/DCA18LA024.md): Boeing 777 · Jamaica, NY · Accident · Class 3 · Limited · Final report · Nov 28, 2017 · SU-GDL · 2 aircraft · Substantial damage > The air traffic controller's improper instruction to the Egypt Air airplane flight crew to pass in an area where passing is prohibited, which led to a ground collision. - [NTSB OPS17IA021](https://openairdocs.org/ntsb/OPS17IA021.md): Cessna 172S · New Orleans, LA · Incident · Class 3 · Incident · Final report · May 9, 2017 · N520ER · 2 aircraft · No damage > The air traffic controller not following Federal Aviation Administration directives to establish sequencing and spacing between aircraft operating to the same runway. - [NTSB OPS17IA014](https://openairdocs.org/ntsb/OPS17IA014.md): Embraer S A ERJ 170-200 LR · San Francisco, CA · Incident · Class 3 · Incident · Final report · Feb 16, 2017 · N214NN · 2 aircraft · No damage > The local controller's issuance of a landing clearance for runway 28L to the ERJ170, and the subsequent issuance of line up and wait instructions to the A320 for runway 28L, resulting in a runway incursion. - [NTSB OPS17IA010](https://openairdocs.org/ntsb/OPS17IA010.md): Boeing 777 · Mt. Wilson, CA · Incident · No injuries · Incident investigation · Final report · Dec 16, 2016 · B-16726 · No damage > The incident was caused by the air traffic controller assigning the pilots a left turn instead of the required right turn after departure which placed the aircraft in an unsafe proximity with terrain and obstructions. Contributing to the incident was the air… - [NTSB OPS16IA010](https://openairdocs.org/ntsb/OPS16IA010.md): Mooney M20R · Jacksonville, FL · Incident · Class 3 · Incident · Final report · Apr 3, 2016 · N57GX · 2 aircraft · No damage > The air traffic controller's decision to issue climb instruction to one aircraft without ensuring the required separation with another could be maintained. Contributing to the incident was the air traffic controller's failure to issue a safety alert in a… - [NTSB OPS14IA005](https://openairdocs.org/ntsb/OPS14IA005.md): Embraer EMB 145XR · Newark, NJ · Incident · No injuries · Incident investigation · Final report · Apr 24, 2014 · N11176 · 2 aircraft · No damage > The local controller’s failure to comply with Federal Aviation Administration separation requirements for aircraft operating on intersecting runways. - [NTSB OPS13IA071](https://openairdocs.org/ntsb/OPS13IA071.md): Gulfstream GIV - Undesignat · Las Vegas, NV · Incident · No injuries · Incident investigation · Final report · Jul 5, 2013 · N0 · No damage > The Federal Aviation Administration's (FAA) inadequate procedures, which did not require specific separation between aircraft operating on nonintersecting runways where flightpaths may intersect and led to an airborne conflict between two aircraft.… - [NTSB ERA13LA042](https://openairdocs.org/ntsb/ERA13LA042.md): Piper PA-32R-300 · Sevierville, TN · Accident · Minor injuries · Limited investigation · Final report · Oct 28, 2012 · N4478F · Substantial damage > The air traffic controller’s failure to comply with the required vectoring and safety alert procedures, which resulted in the airplane’s flight into rising terrain. Contributing to the accident was the Federal Aviation Administration’s continued practice of… - [NTSB OPS12IA849](https://openairdocs.org/ntsb/OPS12IA849.md): Arlington, VA · Incident · No injuries · Incident investigation · Final report · Jul 31, 2012 · No damage > A hearback/readback error on the part of the tower traffic management coordinator, who did not understand the request being made by the approach control area supervisor and then communicated that misunderstanding to the local controllers. Contributing to the… - [NTSB OPS11IA819](https://openairdocs.org/ntsb/OPS11IA819.md): Embraer EMB-135KL · Chicago, IL · Incident · No injuries · Incident investigation · Final report · Aug 8, 2011 · N377SK · 2 aircraft · No damage > The improper air traffic control takeoff clearance issued by the local controller because of his lack of monitoring and lack of awareness of the conflicting arrival airplane. - [NTSB OPS11IA673](https://openairdocs.org/ntsb/OPS11IA673.md): Embraer EMB-145EP · Gulfport, MS · Incident · No injuries · Incident investigation · Final report · Jun 19, 2011 · N13929 · 2 aircraft · No damage > the Gulfport control tower local controller cleared two aircraft for takeoff from runways with intersecting departure flight paths without ensuring the first aircraft had passed the flight path intersection prior to clearing the second aircraft for takeoff. - [NTSB OPS11IA552](https://openairdocs.org/ntsb/OPS11IA552.md): Embraer EMB-145LR · Chicago, IL · Incident · No injuries · Incident investigation · Final report · May 16, 2011 · N15574 · 2 aircraft · No damage > The air traffic controller’s failure to adhere to runway separation requirements and his issuance of an improper takeoff clearance. Contributing to the incident was the controller's failure to recall that there was an arrival inbound to a crossing runway. - [NTSB OPS11IA401](https://openairdocs.org/ntsb/OPS11IA401.md): Arlington, VA · Incident · No injuries · Incident investigation · Final report · Mar 23, 2011 · No damage > The tower controller's loss of consciousness induced by lack of sleep, fatigue resulting from working successive midnight shifts, and air traffic control scheduling practices. - [NTSB OPS11IA410](https://openairdocs.org/ntsb/OPS11IA410.md): Boeing 757-232 · Atlanta, GA · Incident · No injuries · Incident investigation · Final report · Mar 11, 2011 · N693DL · No damage > The air traffic controllers’ failure to adhere to required radar identification procedures, which resulted in loss of separation between the departing Boeing 757 and three other airplanes. Contributing to the incident was the pilots’ inadequate preflight… - [NTSB OPS11IA173](https://openairdocs.org/ntsb/OPS11IA173.md): Boeing 737-832 · Covington, KY · Incident · No injuries · Incident investigation · Final report · Dec 9, 2010 · N3731T · 2 aircraft · No damage > The local controller's distraction with a helicopter south of the field. - [NTSB OPS11IA054](https://openairdocs.org/ntsb/OPS11IA054.md): Dassault FALCON900EX · Teterboro, NJ · Incident · No injuries · Incident investigation · Final report · Oct 20, 2010 · PHILC · 3 aircraft · No damage > The pilot of the F900 overshooting of the final approach course, which conflicted with traffic in the pattern. Contributing to the accident was the lack of appropriate coordination between the tower controller and the approach controller. - [NTSB OPS10IA538](https://openairdocs.org/ntsb/OPS10IA538.md): Boeing 737-7H4 · Los Angeles, CA · Incident · No injuries · Incident investigation · Final report · Sep 4, 2010 · N907WN · 2 aircraft · No damage > Failure of the air traffic controller to exercise positive control of the situation by issuing clear and timely control instructions to the helicopter pilot. Contributing to the incident was delay by the helicopter pilot in responding to instructions issued… - [NTSB OPS10IA196](https://openairdocs.org/ntsb/OPS10IA196.md): Airbus Industrie A319-132 · Anchorage, AK · Incident · No injuries · Incident investigation · Final report · May 21, 2010 · N810AW · 2 aircraft · No damage > The approach controller's delayed transfer of communications on the A319 to the tower controller and failure to account for the aircraft's speed when he directed the crew to turn north. Contributing to the incident was the 747 crew's transfer of radio… - [NTSB OPS10IA132](https://openairdocs.org/ntsb/OPS10IA132.md): Boeing 737-7H4 · Houston, TX · Incident · No injuries · Incident investigation · Final report · Apr 28, 2010 · N242WN · 2 aircraft · No damage > The failure of the local controller to issue control instructions necessary to ensure positive control/standard separation of traffic operating within the Class B airspace. - [NTSB OPS10IA090](https://openairdocs.org/ntsb/OPS10IA090.md): Boeing 737-7H4 · Burbank, CA · Incident · No injuries · Incident investigation · Final report · Apr 19, 2010 · N473WN · 2 aircraft · No damage > The improper separation procedures by air traffic control. - [NTSB OPS10IA002](https://openairdocs.org/ntsb/OPS10IA002.md): Airbus A320 · Cortez, CO · Incident · No injuries · Incident investigation · Final report · Nov 6, 2009 · C-FKOJ · No damage > The failure of the ACA795 flight crew to monitor and/or switch to the appropriate air traffic control frequency. - [NTSB DCA10IA001](https://openairdocs.org/ntsb/DCA10IA001.md): Airbus A320 · Minneapolis, MN · Incident · No injuries · Incident investigation · Final report · Oct 21, 2009 · N374NW · No damage > The flight crew's failure to monitor the airplane’s radio and instruments and the progress of the flight after becoming distracted by conversations and activities unrelated to the operation of the flight. - [NTSB OPS09IA002](https://openairdocs.org/ntsb/OPS09IA002.md): Tampa, FL · Incident · No injuries · Incident investigation · Final report · Feb 19, 2009 · No damage > The controller's issuance of an improper climb clearance to the pilot of Berry Aviation flight 510. Contributing to the incident was the controller's distraction while he searched for a misplaced flight progress strip. - [NTSB OPS08IA008](https://openairdocs.org/ntsb/OPS08IA008.md): Boeing 737-300 · New York, NY · Incident · No injuries · Incident investigation · Final report · Jul 6, 2008 · VP-CKW · 2 aircraft · No damage > The probable cause of this incident was JFK air traffic control tower non-compliance with FAA separation requirements for operations on non-intersecting runways where flight paths intersect, and poor judgment by the LC2 controller in clearing LAN533 for… ## 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."completionStatus" = 'Completed' AND c."mKey" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e."isDefiningEvent" AND e."tier2Number" = '100') ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC ``` This list as a web page: https://openairdocs.org/ntsb-events/100/cases?status=final --- 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.