Final NTSB investigations
33 cases where the sequence of events included Near midair/TCAS alert/loss of separation.
Cases per year
| 2008 | 3 |
|---|---|
| 2009 | 1 |
| 2010 | 8 |
| 2011 | 7 |
| 2012 | 1 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 1 |
| 2018 | 1 |
| 2021 | 2 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 1 |
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 s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '260' 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"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 s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '260' 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
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 DCA25LA306Accident · Serious injuriesClass 4 · LimitedFinal reportAirbus Industrie A320-212 · Chase City, VAThe abrupt maneuver required to comply with a traffic alert and collision avoidance system resolution advisory during descent.NTSB DCA24LA316Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 757-224 · Dunnigan, CAThe abrupt pitch control input by the flight crew in response to a TCAS resolution advisory resulted in two serious passenger injuries.NTSB OPS24LA011Incident · No injuriesClass 4 · LimitedFinal reportDiamond Aircraft Ind DA20-C1 · North Las Vegas, NVThe 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 DCA23LA395Accident · Serious injuriesClass 4 · LimitedFinal reportAirbus A320-214 · Fort Lauderdale, FLThe 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 DCA23FA149Incident · No injuriesClass 1 · FieldFinal reportBoeing 737-79P · Austin, TXthe local controller’s incorrect assumption that the Southwest Airlines (SWA) airplane would depart from the runway before the Federal Express airplane arrived on the same runway, which resulted in a loss of separation between both airplanes. Contributing to…NTSB WPR22FA067Accident · 2 fatalClass 3 · FieldFinal reportVans RV6 · Show Low, AZThe pilot’s exceedance of the airplane’s critical angle of attack following an aborted landing approach, which resulted in an aerodynamic stall and loss of control at an altitude too low for recovery.NTSB OPS21LA002Incident · No injuriesClass 3 · LimitedFinal reportAirbus A319-112 · St Petersburg-Clearwater, FLThe 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 DCA18IA265Incident · No injuriesClass 3 · IncidentFinal reportGulfstream G IV · Philadelphia, PAThe flight crew’s misalignment of the airplane with a taxiway instead of the assigned runway, resulting in a low-altitude go-around late in the final approach and reduced separation with the airplanes on the taxiway.NTSB DCA18IA026Incident · No injuriesClass 3 · IncidentFinal reportBoeing 737-932ER · Atlanta, GAThe flight crewmembers’ failure to properly monitor the airplane’s flightpath, which caused the approach to become unstabilized and resulted in the airplane’s descent below the decision altitude while misaligned with the localizer course. Contributing to the…NTSB OPS16IA010IncidentClass 3 · IncidentFinal reportMooney M20R · Jacksonville, FLThe 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 OPS15IA017Incident · No injuriesIncident investigationFinal reportBoeing 767 34AF · Miami, FLThe controller's issuance of a landing clearance to an arriving aircraft while another aircraft was in position on the same runway. Contributing to the incident was the controller's non-compliance with traffic advisory procedures, and insufficient…NTSB OPS14IA011Incident · No injuriesIncident investigationFinal reportBoeing 777 - 236 · Shemya, AKThe 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 OPS14IA005Incident · No injuriesIncident investigationFinal reportEmbraer EMB 145XR · Newark, NJThe local controller’s failure to comply with Federal Aviation Administration separation requirements for aircraft operating on intersecting runways.NTSB OPS12IA535Incident · No injuriesIncident investigationFinal reportLas Vegas, NVFederal 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 OPS12IA122Incident · No injuriesIncident investigationFinal reportKahului, HIFailure of the Honolulu Control Facility controller to issue control instructions necessary to establish and maintain required separation between all three aircraft. Contributing to the losses of separation was inadequate training provided to controllers…NTSB OPS12IA041Incident · No injuriesIncident investigationFinal reportCessna 172S · Daytona Beach, FLThe departing pilot's incorrect runway selection and non-compliance with an air traffic control clearance. Contributing to the incident was the air traffic controller's inadequate monitoring of the departing aircraft to ensure that the pilot complied with the…NTSB OPS11IA686Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-83(MD-83) · Apache Junction, AZThe failure of the pilots of both airplanes to see and avoid each other and to maneuver as advised by the air traffic controller in time to prevent the conflict that resulted in the reported near midair collision.NTSB OPS11IA653Incident · No injuriesIncident investigationFinal reportBeech 1900C · Fairbanks, AKInadequate 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 OPS11IA499Incident · No injuriesIncident investigationFinal reportBoeing 737 · Camp Springs, MDThe misapplication of wake turbulence and instrument flight rules (IFR) separation criteria by air traffic controllers.NTSB OPS11IA476Incident · No injuriesIncident investigationFinal reportBeech 400 · Midland, TXInadequate planning and control instructions issued to the pilots involved by the trainee controller operating the local control position and inadequate supervision by the instructor responsible for the position.NTSB OPS11IA428Incident · No injuriesIncident investigationFinal reportCirrus Design SR22 · Orlando, FLThe air traffic controllers’ application of inappropriate separation between the B737 and the Cirrus and their inappropriate use of airborne civilian aircraft for observation of other airborne aircraft. Contributing to the incident was the crew of the B737's…NTSB OPS11IA101Incident · No injuriesIncident investigationFinal reportBoeing 737-832 · 66 NM East of Hobe Sound, FLAir traffic controllers did not maintain required awareness of available flight data and aircraft positions, resulting in issuance of an incorrect altitude clearance that caused a loss of standard instrument flight rules separation between the two aircraft.NTSB OPS10IA574Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-214 · Minneapolis, MNThe Local North Controller's issuance of a left-turn heading to the Airbus without establishing the position and heading of the Beech. Contributing to the incident was the Local South Controller's distraction with a ground movement operation and lack of…NTSB DCA10LA083Accident · Serious injuriesLimited investigationFinal reportEmbraer ERJ 170 100 SE · Summit, MSthe abrupt maneuver that was appropriately initiated to comply with the TCAS resolution advisory caused by the momentary projected loss of separation from converging traffic. Contributing to the accident was a passenger's decision to disregard the seatbelt…NTSB OPS10IA163Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2B19 · Burbank, CAThe local controller’s failure to issue control instructions necessary to ensure positive control/standard separation of traffic operating within the Class C airspace.NTSB OPS10IA155Incident · No injuriesIncident investigationFinal reportEmbraer EMB-135KL · Chicago, ILThe air traffic controller's issuance of an improper takeoff clearance to the pilot of the Embraer. Contributing to the incident was the instructor’s inadequate monitoring of the trainee local controller.NTSB OPS10IA020Incident · No injuriesIncident investigationFinal reportBoeing 777-222 · San Francisco, CAThe local controller's issuance of a takeoff clearance to the Boeing 777 without ensuring that approved separation would exist with the Cessna 182. Contributing to the incident were tower procedures that permitted transitioning aircraft to cross the runway 28…NTSB OPS10IA014Incident · No injuriesIncident investigationFinal reportBoeing 737 · Worton, MDThe R10/12 controller issued an improper vector and descent clearance to the GII that put the airplane on a coverging flight path with the B737. Contributing to the incident was the failure of the FAA's training program to correct ongoing controller…NTSB OPS10IA015Incident · No injuriesIncident investigationFinal reportCessna 208B · Phoenix, AZThe Cessna 208 pilot’s failure to identify the correct landing runway.NTSB OPS09IA006Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas MD80 · Chicago, ILThe Chicago TRACON West Arrival controller's omission of a required clearance, resulting in AAL 879 overshooting the final for runway 28 and losing separation with AAL 93.NTSB OPS09IA001Incident · No injuriesIncident investigationFinal reportPeoria, ILThe tower local controller's failure to provide adequate separation between EGF4075 and SKW5961 that landed on intersecting runways.NTSB OPS08IA014Incident · No injuriesIncident investigationFinal reportBoeing B744 · Atlantic OceanThe San Juan CERAP controllers failure to ensure the two aircraft were properly separated using non-radar separation standards.NTSB OPS08IA011Incident · No injuriesIncident investigationFinal reportLearjet 60 · Chicago, ILThe LC-10 controller's failure to ensure the appropriate separation between two airplanes operating on runways where flight paths intersect.