FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Airlines Flight 2493

11 Aug 2023 · San Diego, CA, United States

Boeing 737-7BD and Textron Aviation Inc 560XL · Incident: air traffic event while taxiing

Report a problem

Event

NTSB case
OPS23FA010
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Boeing 737-7BD

Aircraft type
Boeing 737
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7734H
Onboard fatalities
Unknown
Route
From not recordedTo Mineta San Jose International Airport (KSJC), San Jose, CA
Aircraft age
About 17 years (built 2006)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Taxi · into takeoff position
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Air traffic event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Aircraft 2 · Textron Aviation Inc 560XL

Aircraft type
Cessna 560
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N564HV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Des Moines International Airport (KDSM), Des Moines, IATo not recorded
Aircraft age
About 7 years (built 2016)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Not recorded
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Organizational issues › Support/oversight/monitoring
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB 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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS23FA010
Event ID
20230812192847
Case number
OPS23FA010
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas, damage. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: a539d2344e5f0a2c0bfbfaad67b808e9f331162857d88528b02ec7be7abd4156; retrieved 2026-09-13T18:41:49.975Z.