Skip to content

Atlas / NTSB / OPS23FA010

NTSB CAROL · Event

Event OPS23FA010

2023-08-11 San Diego, California, United States Airport · SAN Unknown 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

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 decision to troubleshoot a faulty flight strip printer instead of maintaining direct supervision of the operation.

Factual narrative

Southwest Airlines flight 2493 (SWA2493) and a Textron Aviation, Inc. 560XL (N564HV) were involved in a runway incursion with overflight that resulted in a loss of separation at San Diego International Airport (SAN). SAN was equipped with the Airport Surface Detection Equipment Model-X (ASDE-X) surface radar system. The system was operational and functioned as designed. It produced both aural and visual alerts that indicated that there was an aircraft [N564HV] landing with another aircraft [SWA2493] still in position on the same runway. The local control (LC) controller immediately reacted to the ASDE-X alerts, and issued instructions to resolve the conflict, but not before standard separation had been lost. The SAN Airport Traffic Control Tower (SAN ATCT) facility was equipped with two flight strip printers, one functioned as a primary device, and the second as a backup in case the first unit failed. In post incident interviews, the SAN ATCT personnel stated that they received no training on the use or troubleshooting of these printers. Prior to the incident, the primary printer jammed. During the post-incident interview with the operations supervisor (OS), they stated that they chose to troubleshoot the primary printer rather than switching to the backup, and that this drew their attention away from the operation at the time of the incident. FAA Order JO 7110.65BB, Air Traffic Control, 2-10-3, Tower Team Position Responsibilities, states in part: Tower Team Concept and Intent: There are no absolute divisions of responsibilities regarding position operations. The tasks to be completed remain the same whether one, two, or three people are working positions within a facility/sector. The team, as a whole, has responsibility for the safe and efficient operation of that facility/sector. The LC controller noticed a flight strip at their workstation that indicated an initial altitude for an uninvolved departing aircraft that was not in accordance with facility directives and contacted Southern California Terminal Radar Approach Control (SCT TRACON) to coordinate an appropriate altitude. This diverted their attention from N564HV and SWA2493 momentarily. During the post-incident interview conducted with the LC controller, they stated that they had used poor judgment in prioritizing their duties. This duty prioritization was not consistent with guidance contained in FAA Order JO 7110.65BB, Air Traffic Control, 2-1-1, ATC Service. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • Organizational issues-Support/oversight/monitoring-Oversight-Oversight of operation-ATC
  • Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-ATC personnel
  • Personnel issues-Task performance-Use of equip/info-Use of equip/system-ATC personnel
  • Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-ATC personnel
  • Personnel issues-Task performance-Use of equip/info-Use of equip/system-ATC personnel
  • Organizational issues-Support/oversight/monitoring-Oversight-Oversight of operation-ATC

Verbatim from NTSB's published report. Source file NTSB_2023_OPS23FA010.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway incursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗