The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB DCA24FA300 · Preliminary: the investigation is not finished

Boeing 737-9 and Boeing 737-7H4 incident near Nashville, Tennessee, September 12, 2024

On September 12, 2024 at about 2:14 pm local time, 2 aircraft, Boeing 737-9 (N919AK) and Boeing 737-7H4 (N225WN), were involved in the same incident near Nashville, Tennessee (Nashville Intl airport). No one was hurt; 317 people were on board or involved.

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this incident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 12, 2024 · about 2:14 pm local time
Place
Nashville, Tennessee · Nashville Intl · map
Type
Incident
Injuries
No one was hurt; 317 people were on board or involved.
Weather
not recorded
Aircraft 1
Boeing 737-9, built 2021 · all 737-9s on the register
Registration
N919AK · registry record · serial 44087
Damage
Minor damage
Flight
Flight · scheduled airline rules (Part 121)
Aircraft 2
Boeing 737-7H4, built 2005 · all 737-7H4s on the register
Registration
N225WN · registry record · serial 34333
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative for the Boeing 737-9 preliminary · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The NTSB's narrative for the Boeing 737-7H4 preliminary · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record for the Boeing 737-9 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway incursion veh/AC/person during takeoff (rejected takeoff) defining event

The aircraft

  • Maximum gross weight: 187,679 lb
  • Seats: 48
  • Landing gear: fixed
  • Operator: Alaska Airlines INC

The flight

  • Destination: SEA Seattle WA
  • Runway 13/3, 11,030 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 100° at 11 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 19,000 ft; scat at 7,500 ft
  • Temperature: 75°F (24°C), dew point 52°F (11°C)
  • Altimeter: 30.01 inHg
  • Observation at 8:53 am from KBNA, 1 miles away

Weather report (METAR): METAR KBNA 121353Z 10011KT 10SM SCT075 BKN190 OVC250 24/11 A3001 RMK AO2 SLP157 T02390111=

Injuries

FatalSeriousMinorNone
Cabi14
Flig2
Passengers160

The factual record for the Boeing 737-7H4 from the NTSB's investigation tables, in plain English

The aircraft

  • Maximum gross weight: 154,500 lb
  • Seats: 143
  • Landing gear: fixed
  • Operator: Southwest Airlines CO

The flight

  • Destination: JAX Jacksonville FL

Injuries

FatalSeriousMinorNone
Cabi3
Flig2
Passengers136

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number DCA24FA300.