Southwest B738 at Orlando on Mar 20th 2025, attempted to takeoff from taxiway
Last Update: December 11, 2025 / 17:47:11 GMT/Zulu time
Incident Facts
Date of incident
Mar 20, 2025
Classification
Incident
Airline
Southwest Airlines
Flight number
WN-3278
Departure
Orlando, United States
Destination
Albany, United States
Aircraft Registration
N8315C
Aircraft Type
Boeing 737-800
ICAO Type Designator
B738
Airport ICAO Code
KMCO
A replacement Boeing 737-8 MAX registration N8802Q reached Albany with a delay of about 3:20 hours.
The FAA reported: "An air traffic controller at Orlando International Airport canceled the takeoff clearance for Southwest Airlines Flight 3278 around 9:30 a.m. local time on Thursday, March 20, after the aircraft began its takeoff roll on a taxiway. The taxiway runs parallel to the runway. The flight was headed to Albany International Airport in New York. No other aircraft were involved. The FAA is investigating."
The occurrence aircraft returned to service about 4 hours after the rejected takeoff.
On Oct 15th 2025 the NTSB reported they have opened a class 4 investigation into the occurrence, a preliminary report is not to be published, but a final report will be released at the conclusion of the investigation.
On Dec 11th 2025 the NTSB released their final report and investigation docket concluding the probable causes of the incident were:
The captain’s failure to recognize that the airplane’s location did not agree with the assigned departure runway as required per the Southwest Airlines Airplane Operating Manual, and the captain’s plan continuation error when he missed several cues that would have informed him that he was not on the assigned departure runway when he initiated takeoff.
The NTSB analysed:
On March 20, 2025, about 0930 eastern daylight time (EDT), Southwest Airlines (SWA) flight 3278, a Boeing 737-8H4, N8315C, taxied onto and initiated a takeoff roll from taxiway “H” at Orlando International Airport (MCO), Orlando, Florida. SWA flight 3278 discontinued its takeoff roll and subsequently returned to the gate area. The flight was operated under Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight to Albany International Airport (ALB), Albany, New York. All 158 occupants (2 flight crew members, 4 cabin crew members, and 152 passengers) deplaned at the gate without any injuries.
According to an Aircraft Communication Addressing and Reporting System (ACARS) message, at 0917 the L1 door was closed and at 0922 an “out gate message” was sent, and the flight began pushback from gate 103. According to the first officer, they had started both engines during the pushback. About 0925, the first officer contacted the Airport Traffic Control Tower (ATCT) ground control to request taxi clearance and was told to taxi to runway 17R via the ramp and taxiway H2. Subsequently, the flight began to taxi on the airside 2 ramp.
About 0927, the airplane stopped taxiing abeam the taxiway H1 entrance from the ramp.
According to crew statements the flight stopped in this area due to a company aircraft that had pushed back from a gate, and there was not room to taxi around the airplane. The captain stated the crew completed the Before Takeoff checklist while waiting for the airplane to clear their taxi path. Additionally, the crew stated that taxiways G and H1 were closed due to construction, and men and equipment were present and working on taxiway H1. Once the company airplane taxied out, the first officer informed ATCT that they were clear.
About 0929, the flight crew was issued a clearance for takeoff on Runway 17R at H2 while they were in the ramp area holding short of H2. Subsequently, the flight data recorder (FDR) data showed N1 for both engines increased to 38.8%. Subsequently, FDR data indicated that both engines N1 increased to at or above 40% for the remainder of the taxi and commencement of the takeoff roll. The event flight turned left on taxiway H2 from the airside 2 ramp area with a recorded ground speed of 9 kts. The event flight taxied on taxiway H2 crossing taxiway G. The first officer stated that as they were crossing taxiway G, the captain stated that the final approach was clear and that runway 17R was verified.
According to the flight crew, about this time the captain asked the first officer to confirm they had run the Before Takeoff checklist. The first officer stated that the airplane was still headed straight towards the runway 17R and taxiway H2 intersection and momentarily looked up to scan the overhead panel to ensure that the bleed switches and packs were in the proper position, and confirmed that the checklist was completed. As the first officer finished his scan, the first officer felt the airplane turning as the captain turned the airplane onto taxiway H. The captain stated that before he finished the right turn, he announced that he was setting takeoff thrust and selected the take-off/go-around (TOGA) switch while advancing the thrust levers.
About 0930, when the flight approached taxiway H and subsequently made a right turn onto taxiway H, the recorded ground speed was 14 kts, the engine N1 speed increased to about 90.6%, and the takeoff roll began. The captain stated that after the turn the airplane wasn’t centered on the surface, and he applied rudder to maintain the centerline. The captain stated that maintaining the centerline required full attention and he didn’t notice the airplane was on a taxiway.
The first officer stated that he had momentarily looked down, saw the thrust levers moving up, and then looked outside the aircraft and realized that the airplane was on a taxiway. The first officer stated he was startled when he saw this, and it took a few seconds for the first officer to vocalize “we are on the taxiway-reject.” About the same time as the first officer commanded the reject, the ATCT controller instructed “southwest 3278 stop, southwest 3278 stop, stop stop southwest 3278 stop cancel takeoff clearance you’re on hotel taxiway southwest 3278.”
The highest recorded automatic dependent surveillance broadcast (ADS-B) ground speed the flight obtained was 66 knots, the crew stated that the flight’s airspeed did not exceed 80 kts, and the flight data recording indicated the maximum speed of 71 kts computed airspeed. FDR data also showed the airplane had traveled about 800 feet down taxiway H before the groundspeed began to rapidly decrease. After the flight crew aborted their takeoff, they turned right on to taxiway H3.
After turning right on to taxiway H3, the ATCT queried if the crew wanted to taxi back and takeoff.
The crew informed the ATCT controller that they would need to return to the gate after the brake cooling time had completed. About 0931, the flight turned right onto taxiway G, and about six minutes later the flight taxied onto the Airside 2 ramp at taxiway G1.
In post-accident statements and interviews, the captain stated that as they had turned onto taxiway H2, he did a scan of the final approach to 17R for traffic, and he noted an airplane landing on 17L. Both crew confirmed that the airplane in sight was landing on 17L, after which he stated final is clear, and recalled seeing the 17R sign straight ahead. The captain stated that after clearing and passing taxiway G, he had mistakenly turned right onto taxiway H thinking it was runway 17R. The captain also stated after turning, he was occupied with centering the airplane on the surface and did not realize they were on a taxiway until the error was identified by both the first officer and ATCT.
The captain was asked in a post-accident interview how he verified the surface he was on. He stated that for a H2 departure he would not be able to see the numbers on the runway itself but could use the lighting and magnetic course. He also mentioned that he had been using a moving map display during the taxi out to identify the taxi route but was not referencing it while approaching the runway.
The Southwest Airlines Aircraft Operating Manual provided the following guidance, in part, as it pertained to taxiing onto the departure runway:
Both Pilots crosscheck all available references and confirm that the aircraft’s location is in agreement with the assigned departure runway.
Use all available references to confirm that the aircraft is at the assigned departure runway.
The references may include:
- Aircraft heading indicators (including HGS) Navigation display
- Runway signage
- Painted runway designation (may not be visible for displaced thresholds or intersection takeoffs)
- Jeppsen -9 page
- Runway lighting (expected lighting versus actual lighting)
- Verify the aircraft is on the assigned runway for takeoff using all available references.
(CA) Verbally verify the aircraft is on the assigned runway.
Verify that the aircraft is on the assigned runway and state, “Runway _____, Verified.”
Warning: If there is any doubt that the aircraft is on the correct runway, do not takeoff and notify ATC immediately…
The captain failed to follow these standard operating procedures when he did not verbally verify the aircraft was on the assigned runway and initiated the takeoff without verifying the aircraft was on the assigned runway. The captain exhibited a plan continuation error when he entered the taxiway, thinking it was the assigned runway, and ignored several cues that indicated his incorrect location; to include the presence of a yellow taxi centerline, a narrow pavement surface compared to a runway, not crossing a hold short line, and signage inconsistent with the correct runway. Additionally, the FO was distracted by the captain’s action to ask about the checklist items as they turned onto the taxiway. As a result, the FO proceeded to look back into the cockpit to confirm that the checklist item was complete. This was also contrary to Southwest procedures for taxiing, which in part include the following:
Direct attention outside during taxi, except for momentary flight deck crosschecks.
While the aircraft is moving, the intention is to have both Pilots focused outside
And
Treat the runway environment as a critical zone. When entering the departure runway, direct your attention outside. Do not perform flight deck tasks, except for momentary items such as turning on exterior lighting.
Metars:
KMCO 201453Z 22010KT 10SM BKN250 23/08 A3004 RMK AO2 SLP172 T02330083 50011=
KMCO 201353Z 23008KT 10SM FEW015 SCT250 21/08 A3005 RMK AO2 SLP172 FU FEW015 T02060083=
KMCO 201253Z 23006KT 10SM SCT250 16/12 A3003 RMK AO2 SLP166 T01610117=
KMCO 201153Z 21003KT 10SM FEW250 12/12 A3001 RMK AO2 SLP161 T01220117 10144 20106 53004=
KMCO 201053Z 19004KT 10SM CLR 12/11 A3000 RMK AO2 SLP158 T01170111 $=
KMCO 200953Z 20005KT 10SM CLR 11/11 A3000 RMK AO2 SLP158 T01110106 $=
Aircraft Registration Data
Incident Facts
Date of incident
Mar 20, 2025
Classification
Incident
Airline
Southwest Airlines
Flight number
WN-3278
Departure
Orlando, United States
Destination
Albany, United States
Aircraft Registration
N8315C
Aircraft Type
Boeing 737-800
ICAO Type Designator
B738
Airport ICAO Code
KMCO
This article is published under license from Avherald.com. © of text by Avherald.com.
Article source
You can read 2 more free articles without a subscription.
Subscribe now and continue reading without any limits!
Read unlimited articles and receive our daily update briefing. Gain better insights into what is happening in commercial aviation safety.
Send tip
Support AeroInside by sending a small tip amount.
Related articles
Fleet type match
Southwest B738 at San Antonio on Jan 27th 2026, rejected takeoff due to runway incursion
A Southwest Airlines Boeing 737-800, registration N8563Z performing flight WN-4996 from San Antonio,TX to Dallas Love,TX (USA), was accelerating for…
Southwest B737 at Omaha on Jan 6th 2026, bird strike
A Southwest Airlines Boeing 737-700, registration N246LV performing flight WN-1230 from Omaha,NE to Phoenix,AZ (USA), was climbing out of Omaha's…
Fleet type match
Southwest B738 near Las Vegas on Nov 26th 2025, indication prompts diversion
A Southwest Airlines Boeing 737-800, registration N8513F performing flight WN-651 from San Diego,CA to Indianapolis,IN (USA) with 141 people on…
Fleet type match
Southwest B738 at Atlanta on Nov 21st 2025, cabin pressure problems
A Southwest Airlines Boeing 737-800, registration N8691A performing flight WN-171 from Atlanta,GA to Chicago Midway,IL (USA), was climbing out of…
Fleet type match
Southwest B737 at Cleveland on Oct 29th 2025, loss of separation with helicopter
A Southwest Airlines Boeing 737-700, registration N280WN performing flight WN-1333 from Baltimore,MD to Cleveland,OH (USA), was on final approach to…
Newest articles
El Al B738 at Amsterdam on Feb 12th 2026, rejected takeoff due to malfunction
An El Al Boeing 737-800, registration 4X-EKN performing flight LY-46 from Amsterdam (Netherlands) to Tel Aviv (Israel), had lined up runway 18L and…
Fleet type match
KLM A332 at Amsterdam on Feb 13th 2026, hydraulic leak
A KLM Airbus A330-200, registration PH-AOF performing flight KL-765 (dep Feb 12th) from Bonaire (Bonaire) to Amsterdam (Netherlands), landed on…
Subscribe today
Are you researching aviation incidents? Get access to AeroInside Insights, unlimited read access and receive the daily newsletter.
Pick your plan and subscribePartner
ELITE Simulation Solutions is a leading global provider of Flight Simulation Training Devices, IFR training software as well as flight controls and related services. Find out more.
SafetyScan Pro provides streamlined access to thousands of aviation accident reports. Tailored for your safety management efforts. Book your demo today
AeroInside Blog
Popular aircraft
Airbus A320Boeing 737-800
Boeing 737-800 MAX
Popular airlines
American AirlinesUnited
Delta
Air Canada
Lufthansa
British Airways