Introduction
On 20 March 2025, a Southwest Airlines Boeing 737-800, registration N8315C, operating flight WN3278 from Orlando International Airport (KMCO), Florida, to Albany International Airport (KALB), New York, initiated a takeoff roll from the parallel Taxiway H instead of the assigned Runway 17R. The tower controller identified the misalignment and promptly cancelled the takeoff clearance, prompting the flight crew to abort the takeoff. No injuries, damage, or conflicts with other aircraft were reported.
The FAA has launched a formal investigation into the runway incursion event, classifying it as a serious operational incident.
Flight & Incident Overview
• Aircraft Type: Boeing 737-800
• Operator: Southwest Airlines
• Registration: N8315C
• Flight Number: WN3278
• Route: Orlando (MCO) to Albany (ALB)
• Date: 20 March 2025
• Time of Incident: Approximately 09:30 local (13:30Z)
• Weather Conditions: Visual Meteorological Conditions (VMC), visibility 10SM, few clouds at 15,000 ft
• Persons on Board: Not publicly disclosed (typically 150–180 passengers + 5 crew)
• Injuries: None
• Damage: None
• Runway in Use: 17R
• Taxiway Entered in Error: Taxiway H (parallel to 17R)
• Final Outcome: Takeoff rejected; aircraft returned to the apron; replacement aircraft dispatched
Sequence of Events
1. Pre-Departure Taxi and Clearance
• The aircraft taxied from the terminal to the southern end of Orlando International Airport and was cleared for takeoff from Runway 17R.
• ATC provided standard instructions for departure, and weather conditions were favourable, with unrestricted visibility and calm winds from 220 degrees at 10 knots.
2. Taxiway Misalignment
• Instead of lining up on Runway 17R, the aircraft mistakenly lined up on parallel Taxiway H.
• Taxiway H is situated immediately east of Runway 17R and is used for ground movements—not takeoffs.
• The aircraft began the initial stages of the takeoff roll on the taxiway, reportedly accelerating.
3. ATC Intervention
• Orlando Tower identified the aircraft’s position and immediately cancelled the takeoff clearance.
• The flight crew rejected the takeoff and brought the aircraft to a stop without incident.
• The aircraft vacated the taxiway and taxied back to the gate for further inspection and procedural review.
4. Aftermath and Replacement
• The original aircraft, N8315C, was inspected and returned to service approximately four hours later.
• A replacement aircraft, a Boeing 737 MAX 8 (N8802Q), was dispatched to complete the flight, arriving in Albany with a delay of approximately 3 hours and 20 minutes.
Operational & Technical Analysis
1. Human Factors
• Initial reviews suggest the incident may be attributed to loss of situational awareness and confirmation bias, where the flight crew may have incorrectly identified the taxiway as the intended runway.
• The configuration of Taxiway H and Runway 17R—running parallel with similar markings and orientation—has historically contributed to similar incidents at other major airports.
2. Airport Layout Considerations
• Orlando’s southern complex features multiple parallel taxiways and runways, increasing the risk of misalignment without careful cross-checks.
• Enhanced surface markings, clear signage, and active runway guard lighting are standard, though their placement and condition will likely be reviewed during the FAA investigation.
3. Air Traffic Control Performance
• The prompt action of Orlando Tower prevented a potential catastrophic event.
• ATC surveillance and monitoring ensured the misalignment was identified within seconds of movement.
4. Flight Crew Actions
• Upon receiving the cancelled clearance, the crew executed a rejected takeoff (RTO) in accordance with operational procedures.
• There were no reported system anomalies or malfunctions onboard.
Investigation Status
• Lead Authority: Federal Aviation Administration (FAA)
• Type of Investigation: Operational runway incursion
• Key Focus Areas:
• Crew situational awareness and adherence to taxi and departure procedures
• Effectiveness of airport signage and surface markings
• Coordination and communication between ATC and flight crew
• Cockpit Voice Recorder (CVR) and Flight Data Recorder (FDR) data are expected to be analysed to confirm crew dialogue and aircraft positioning.
Safety and Regulatory Implications
• Runway vs Taxiway Confusion remains a critical safety concern in commercial aviation.
• Following this event, the FAA may issue Safety Bulletins or Airport Notices aimed at enhancing visual cues on Orlando’s airfield.
• Airlines may also review crew briefings related to hot spots and complex surface operations.
METAR Data at Time of IncidentKMCO 201353Z 23008KT 10SM FEW015 SCT250 21/08 A3005 RMK AO2
Conditions were ideal for visual operations with excellent visibility and minimal cloud cover, indicating this was not a weather-related incident.
Conclusion
On 20 March 2025, a Southwest Airlines Boeing 737-800 mistakenly began a takeoff roll on Taxiway H at Orlando International Airport instead of Runway 17R. The error was swiftly identified by ATC, and takeoff was aborted without incident. There were no injuries or damage, and the FAA has launched a formal investigation into the runway incursion. The incident highlights the ongoing challenge of maintaining situational awareness in complex airport layouts, even under ideal weather conditions.
Disclaimer
This report is based on publicly available information as of 21 March 2025. While every effort has been made to ensure accuracy, the findings are preliminary and subject to change pending the outcome of the official investigation. If you are the rightful owner of any referenced materials and wish them removed, please email: takedown@cockpitking.com.
