# 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. Page 1 of 2 · 59 cases ## Latest cases - [NTSB CEN25LA370](https://openairdocs.org/ntsb/CEN25LA370.md): Boeing E75 · Benton, KS · Accident · No injuries · Class 4 · Limited · Final report · Sep 7, 2025 · N75675 · Substantial damage > The pilot's failure to maintain clearance from a moving vehicle during an evasive maneuver from a perceived conflict with another airplane. Contributing to the accident was the pilot of the other airplane’s non-standard phraseology and inaccurate position… - [NTSB CEN24LA144](https://openairdocs.org/ntsb/CEN24LA144.md): Piper PA28 · Muncie, IN · Accident · 1 fatal · Class 3 · Limited · Final report · Apr 1, 2024 · N8438B · Destroyed > The pilot’s spatial disorientation and subsequent loss of control while maneuvering outside established instrument approach procedures in instrument meteorological conditions, which resulted in an impact with terrain. Contributing to the accident was the… - [NTSB OPS24LA011](https://openairdocs.org/ntsb/OPS24LA011.md): Diamond Aircraft Ind DA20-C1 · North Las Vegas, NV · Incident · No injuries · Class 4 · Limited · Final report · Dec 9, 2023 · N857PA · 2 aircraft · No damage > The local controller’s loss of situational awareness, inadequate provision of traffic advisory or safety alert information, and lack of positive control, that resulted in a near-midair collision. - [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 DCA23LA395](https://openairdocs.org/ntsb/DCA23LA395.md): Airbus A320-214 · Fort Lauderdale, FL · Accident · Serious injuries · Class 4 · Limited · Final report · Jul 23, 2023 · N229NV · No damage > The flight crew’s abrupt change in pitch in response to a traffic collision advisory system resolution advisory that resulted in a serious injury to a flight attendant. - [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 DCA22LA175](https://openairdocs.org/ntsb/DCA22LA175.md): Boeing 777 · Chicago, IL · Accident · No injuries · Class 4 · Limited · Final report · Aug 6, 2022 · A7-BFH · Substantial damage > The ground controller’s inappropriate routing of the B777 through a non-movement area, resulting in the airplane’s right wingtip contacting a light pole. Contributing to the accident was the lack of an appropriate display of taxiway BB2 as a restricted… - [NTSB ERA22FA318](https://openairdocs.org/ntsb/ERA22FA318.md): Piper PA-46-350P · North Las Vegas, NV · Accident · 4 fatal · Class 3 · Field · Final report · Jul 17, 2022 · N97CX · 2 aircraft · Destroyed > The low-wing airplane pilot’s failure to ensure that the airplane was aligned with the correct runway, which resulted in a collision with the high-wing airplane on final approach. Contributing to the accident was the controller’s failure to provide timely and… - [NTSB ERA22LA022](https://openairdocs.org/ntsb/ERA22LA022.md): Cessna 172 · Statesboro, GA · Accident · No injuries · Class 4 · Limited · Final report · Oct 9, 2021 · N8592B · Substantial damage > The student pilot’s failure reduce power and apply sufficient braking after landing, which resulted in a runway excursion and impact with objects and terrain. - [NTSB OPS21LA003](https://openairdocs.org/ntsb/OPS21LA003.md): Boeing 737-8H4 · San Diego, CA · Incident · No injuries · Class 3 · Limited · Final report · Jun 11, 2021 · N8674B · 2 aircraft · No damage > The blocked go-around radio instruction from the air traffic control tower to the arrival aircraft which resulted in the arrival aircraft continuing the landing approach. This led to a loss of separation between the landing aircraft and the aircraft awaiting… - [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 CEN19CA227](https://openairdocs.org/ntsb/CEN19CA227.md): Vans RV-8 · Oshkosh, WI · Accident · No injuries · Data collection · Final report · Jul 20, 2019 · N143MS · Substantial damage > The pilot’s failure to maintain adequate spacing from the lead airplane while landing following revised landing instructions, which necessitated that the pilot conduct an improper landing flare and resulted in a hard landing. - [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 ANC18LA030](https://openairdocs.org/ntsb/ANC18LA030.md): Champion 7GC · Anchorage, AK · Accident · No injuries · Limited investigation · Final report · Mar 26, 2018 · N4844E · Substantial damage > The pilot's failure to maintain directional control during landing with a crosswind, which resulted in a loss of control and failure of the main landing gear. Contributing to the accident was the pilot's self-induced pressure to land. - [NTSB OPS18IA003](https://openairdocs.org/ntsb/OPS18IA003.md): Bombardier CL600 2D24 · Medford, OR · Incident · Class 3 · Incident · Final report · Dec 25, 2017 · N162PQ · No damage > The incident was caused by the air traffic controller assigning an altitude below the published procedure altitude for the approach segment to be flown prior to the aircraft being established on a published portion of the approach. Contributing to the… - [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 OPS16IA009](https://openairdocs.org/ntsb/OPS16IA009.md): Cessna 172S · Honolulu, HI · Incident · Class 3 · Incident · Final report · Feb 26, 2016 · N269ME · 2 aircraft · No damage > The air traffic controller's decision to clear an aircraft to land on a runway occupied by another aircraft that had previously been instructed to line up and wait. Contributing to the runway incursion was the failure of the air traffic controller to visually… - [NTSB CEN16LA067](https://openairdocs.org/ntsb/CEN16LA067.md): Hawker 400 · Telluride, CO · Accident · No injuries · Limited investigation · Final report · Dec 23, 2015 · XA-MEX · Substantial damage > The limitations of the air traffic control equipment that prevented the controller's timely recognition of NOTAM information that was effective immediately and resulted in the issuance of an approach clearance to a closed runway. Also causal was the pilots'… - [NTSB OPS14IA011](https://openairdocs.org/ntsb/OPS14IA011.md): Boeing 777 - 236 · Shemya, AK · Incident · No injuries · Incident investigation · Final report · Aug 16, 2014 · N773AN · No damage > The air traffic controller’s failure to identify a conflict between two aircraft and to issue an adequate clearance, which resulted in a loss of required separation. Contributing to the incident was the Federal Aviation Administration’s failure to provide… - [NTSB OPS14IA007](https://openairdocs.org/ntsb/OPS14IA007.md): Boeing 757 · Powhatan, VA · Incident · Minor injuries · Incident investigation · Final report · Apr 29, 2014 · UNK · Minor damage > The air traffic controller’s failure to provide required advisories about significant radar-observed convective precipitation along both airplanes’ flight routes and the air route traffic control center’s lack of a program to ensure that air traffic… - [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 DCA14IA037](https://openairdocs.org/ntsb/DCA14IA037.md): Boeing 737 7H4 · Branson, MO · Incident · No injuries · Incident investigation · Final report · Jan 13, 2014 · N272WN · No damage > The Flight crew's failure to properly identify the airport and runway of intended landing. Contributing to the incident was the flight crew's failure to comply with procedures for use of navigation information and visual cues to verify the airport and runway… - [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 CEN13LA244](https://openairdocs.org/ntsb/CEN13LA244.md): Dean Leslie N Highlander · Bryan, OH · Accident · 1 fatal · Limited investigation · Final report · Apr 27, 2013 · N58LD · Substantial damage > The pilot's failure to maintain sufficient airspeed during a go-around, which resulted in an aerodynamic stall and subsequent impact with terrain. - [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 OPS12IA535](https://openairdocs.org/ntsb/OPS12IA535.md): Las Vegas, NV · Incident · No injuries · Incident investigation · Final report · Apr 27, 2012 · No damage > Federal Aviation Administration procedures that do not ensure separation in the event of a go-around during simultaneous independent runway operations on runways that do not physically intersect but whose flight paths intersect. - [NTSB DCA12PA049](https://openairdocs.org/ntsb/DCA12PA049.md): Israel Aircraft Industries F21-C2 · Fallon, NV · Accident · 1 fatal · Final report · Mar 6, 2012 · N404AX · Destroyed > fuel exhaustion following missed approaches due to deficient ATC handling under weather conditions which were significantly lower than forecast. The second missed approach may have been initiated due to limited pilot instrument proficiency. Contributing to… - [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 OPS11IA653](https://openairdocs.org/ntsb/OPS11IA653.md): Beech 1900C · Fairbanks, AK · Incident · No injuries · Incident investigation · Final report · Jun 14, 2011 · N121WV · 2 aircraft · No damage > Inadequate air traffic control actions that failed to establish and maintain required separation between the two airplanes. Contributing to the incident was inexperience on the part of the local controller, inadequate oversight by the tower… - [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 OPS11IA499](https://openairdocs.org/ntsb/OPS11IA499.md): Boeing 737 · Camp Springs, MD · Incident · No injuries · Incident investigation · Final report · Apr 18, 2011 · 2 aircraft · No damage > The misapplication of wake turbulence and instrument flight rules (IFR) separation criteria by air traffic controllers. - [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 CEN11CA166](https://openairdocs.org/ntsb/CEN11CA166.md): Mcholland C L Solitare · Wellington, CO · Accident · No injuries · Data collection · Final report · Jan 29, 2011 · N15XP · Substantial damage > The glider pilot’s misjudgment while approaching to land, which resulted in an off-airport landing. - [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 WPR11FA032](https://openairdocs.org/ntsb/WPR11FA032.md): Mooney M20J · Lander, WY · Accident · 4 fatal · Field investigation · Final report · Oct 25, 2010 · N201HF · Substantial damage > The pilot's decision to depart into known adverse weather conditions over mountainous terrain, which required operation near the limits of the airplane's performance capability and which resulted in a loss of airplane control and subsequent ground impact.… - [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 CEN10FA065](https://openairdocs.org/ntsb/CEN10FA065.md): New Piper PA-46-500TP · Mendoza, TX · Accident · 2 fatal · Field investigation · Final report · Dec 7, 2009 · N600YE · Substantial damage > ***This report was modified on May 22, 2014. Please see the docket for this accident to view the original report.*** The pilot's spatial disorientation, which resulted in his loss of airplane control. Contributing to the pilot's spatial disorientation was the… - [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. Next page: https://openairdocs.org/ntsb-events/100/sequence.md?status=final&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."completionStatus" = 'Completed' AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '100' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC ``` This list as a web page: https://openairdocs.org/ntsb-events/100/sequence?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.