FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Alaska Airlines Flight 369

12 Sept 2024 · Nashville, TN, United States

Boeing 737-9 and Southwest Airlines Boeing 737-7H4 · Incident: runway incursion (vehicle, aircraft or person) during takeoff

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
DCA24FA300
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
Ongoing
Event fatalities
Unknown
Ground fatalities
Unknown
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
Not recorded

Aircraft 1 · Boeing 737-9

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
N919AK
Onboard fatalities
Unknown
Route
From not recordedTo Seattle–Tacoma International Airport (SEA), Seattle, WA
Aircraft age
About 3 years (built 2021)
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
Takeoff · rejected takeoff
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
Runway incursion (vehicle, aircraft or person)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Aircraft 2 · Boeing 737-7H4

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
N225WN
Onboard fatalities
Unknown
Route
From not recordedTo Jacksonville International Airport (JAX), Jacksonville, FL
Aircraft age
About 19 years (built 2005)
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
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On September 12, 2024, about 0914 central daylight time (CDT), Alaska Airlines flight 369 (ASA369), a Boeing 737-900, N919AK, rejected their take-off on runway 13 at Nashville International Airport (BNA), Nashville, Tennessee, when Southwest Airlines flight 2029 (SWA2029), a Boeing 737-700, N225WN, crossed the runway at taxiway T5 . There was no damage to the airplanes nor injuries to crew or passengers onboard either airplane. ASA369 was operating under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from BNA to Seattle-Tacoma International Airport (SEA), Seattle, Washington. SWA2029 was operating under Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from BNA to Jacksonville International Airport (JAX), Jacksonville, Florida. The NTSB was notified of the incident and operations, air traffic control (ATC), human factors, aircraft performance, flight data recorder (FDR), and cockpit voice recorder (CVR) specialists were assigned. The ATC group convened at the BNA air traffic control tower the week of September 16th to conduct interviews, review documentation and data. Parties to the investigation are the Federal Aviation Administration (FAA), National Air Traffic Controller Association (NATCA), Alaska Airlines, Southwest Airlines, Air Line Pilots Association (ALPA), Southwest Airlines Pilots Association (APA), and Boeing Commercial Airplanes . History of Flight The following timeline (Table 1) was constructed from certified ATC audio re-recordings and automatic dependent surveillance- broadcast (ADS-B) data provided by the FAA. All times are in CDT. A graphical depiction of the event location with the path of the involved aircraft is shown on an overlay of a Google Earth image in figure 1.

Time Event 0912:11 Local Controller instructed the flight crew of ASA369 to line up and wait on runway 13 with good read back. 0913:01 SWA2029 flight crew contacted Ground Controller. 0913:05 Ground Controller instructed flight crew of SWA2029 to proceed to runway 20C, and to cross runway 13 at taxiway T5. 0913:13 Flight Crew of SWA2029 correctly read back the taxi instructions to Ground Controller. 0913:28 Local Controller cleared ASA369 for take off on runway 13 with good read back. 0914:30 The flight crew of ASA369 reported to Local Controller that they were aborting, followed by the Local Controller canceling takeoff clearance. 0915:10 Local Controller asked the flight crew of ASA369 if they were able to exit on Taxiway 4 and they responded yes. Table 1. Timeline of events.

Figure 1. A graphic depicting the event with ground track of involved aircraft. ASA369 exited runway 13 on taxiway T4 and proceeded to the gate area. While ASA369 was waiting for an open gate, fuse plugs deflated all four main landing gear tires. Passengers were deplaned via air stairs on the ramp. SWA2029 taxied to runway 20C, received takeoff clearance and departed BNA for JAX. The FDR and CVR were retrieved from the Alaska Airlines airplane, and the FDR was retrieved from the Southwest Airlines airplane. The CVR from the Southwest Airlines airplane had been overwritten. All the recorders were sent to the NTSB Vehicle Recorder Laboratory, and data has been retrieved from all the recorders. The Operations Group will be performing interviews of both flight crews involved in the incursion. The investigation continues.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record DCA24FA300
Event ID
20240912195112
Case number
DCA24FA300
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, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 66ddd29ea1373ea2c4fa9afab0d366652ac52a60dd6ebc4abfb7e70d0dac4a8a; retrieved 2026-09-13T18:46:30.699Z.