History of Flight
On February 16, 2023, about 2059 eastern standard time, Air Canada Rouge flight 1633 (ROU1633), an Airbus A321-200, registration C-GKFB, was cleared to take off on runway 14 at Sarasota-Bradenton International Airport (SRQ), Sarasota, Florida. At the same time, American Airlines flight 2172 (AAL2172), a Boeing 737-800, registration N826NN, was cleared to land on the same runway. The crew of AAL2172 self-initiated a go-around. There were no injuries to the 2 pilots, 4 flight attendants, and 188 passengers on board ROU1633, nor to the 2 pilots, 4 flight attendants, and 172 passengers aboard AAL2172. No damage occurred to either airplane.
ROU1633 was operating under 14 Code of Federal Regulations (CFR) Part 129 as a foreign scheduled international passenger flight from SRQ to Lester B. Pearson International Airport (CYYZ), Toronto, Canada. AAL2172 was a 14 CFR Part 121 scheduled domestic passenger flight from Charlotte/Douglas International Airport (CLT), Charlotte, North Carolina, to SRQ. Night visual meteorological conditions prevailed at the time of the incident.
The flight crew of AAL2172 stated that while on approach, about 3 nautical miles from Runway 14, Sarasota tower cleared ROU1633 for takeoff on runway 14 and notified them of the departing traffic ahead. The crew saw the flight ahead as a potential threat and their mitigation plan was to go-around if the departing aircraft was still on the runway when they transitioned from approach to landing. As they approached the threshold, it appeared that ROU1633 was still on takeoff roll and not yet airborne. They executed the go-around, notified SRQ ATCT, and complied with heading and altitude instructions before returning for a subsequent uneventful landing on runway 14.
The National Transportation Safety Board (NTSB) reviewed a summary of ATC communication services provided to ROU1633 and AAL2172 while operating in Tampa International Airport terminal radar approach control (TPA TRACON) and SRQ Air Traffic Control Tower (ATCT). Communications with TPA TRACON were routine. The runway incursion occurred while both flight crews were in communication with and operating in SRQ ATCT airspace. Two FAA controllers were on duty, but one was on break, and the local control (LC) controller was the only person in the tower. All ATCT positions, including operational supervisor, were combined; workload was stated as normal for the time of day and for a single controller in the cab.
At 2050:20, ROU1633's crew advised the LC controller they were ready to taxi. The controller instructed them to taxi to runway 14 via taxiway A and cross runway 22. At 2052:13, the crew asked to confirm crossing runway 22; the controller affirmed. At 2054:09, AAL2172's crew contacted SRQ ATCT and reported on a visual approach to runway 14. The controller provided wind and cleared them to land. ADS-B data indicated AAL2172 was about 12 nautical miles (nm) northwest of SRQ. At 2057:01, the controller asked ROU1633 if ready; they responded affirmatively. At 2057:07, the controller cleared ROU1633 for takeoff on runway 14, instructed them to fly runway heading, and advised of traffic on a 3-mile final. AAL2172 was then about 4.1 nm from the threshold. At 2057:20, the controller informed AAL2172 that an Airbus would be departing runway 14. At 2057:39, ROU1633 confirmed runway heading; AAL2172 was about 2.5 nm from the threshold. At 2058:35, AAL2172's crew stated they were going around; AAL2172 had crossed the runway threshold and was abeam taxiway A3, and ROU1633 was airborne abeam taxiway B. AAL2172 was then instructed to turn right to 270 degrees and contact TPA TRACON for resequencing; it landed uneventfully. ROU1633 continued to Toronto and landed uneventfully.
Meteorological Information
At 2053 eastern standard time, the weather at SRQ was wind from 230 degrees at 4 knots, visibility 10 statute miles, clear skies below 12,000 feet, temperature 22°C, dew point 18°C, altimeter 30.09 inHg.
Additional Information
FAA Order JO 7110.65Z, Air Traffic Control, states that the primary purpose of the ATC system is to prevent collisions involving aircraft. Duty priority gives first priority to separating aircraft and issuing safety alerts. Regarding same runway separation, an arriving aircraft must not cross the landing threshold until the departing aircraft has departed and crossed the runway end, or, if distances can be determined, minimum distances based on aircraft category must be met. This order was superseded by JO 7110.65BB on February 20, 2025, without changing the above information.