Flight crew reported a runway incursion while taxiing and observed an air carrier landing after failure to comply with ATC go around clearance.
Synopsis
Flight crew reported a runway incursion while taxiing and observed an air carrier landing after failure to comply with ATC go around clearance.
Narrative
Approximately 10 miles to YAGGO (on the GRNCH3 STAR - expect Runway 18R); we were told to change landing runway to Runway 18L. Tower sounded saturated by the number of aircraft in the pattern and the unexpected runway change (apparently caused by a bird strike). Tower initially misspoke and cleared us to land on Runway 17L; but after we queried him he corrected it to Runway 18L. Visual approach and landing were uneventful. On landing rollout; Tower directed us to turn right onto Taxiway E and asked us to expedite due to an aircraft on short final. We complied with their directions and attempted to exit the runway as quickly as we could. Once we turned approximately 90 degrees we could see the air carrier flight behind us only a few moments from touching down. Tower saw the conflict and directed the flight to go around. The flight did not go around and landed before we could clear the runway (we were crossing the runway boundary line / entering Taxiway E at touchdown). Taxi to the ramp and shutdown were uneventful. Cause: Task saturation by tower personnel and decreased aircraft spacing on final led to the conflict. However; the air carrier crew should have gone around when directed.
Second reporter narrative
Arrival MCO; GRNCH3; expect Runway 18R. Day VMC conditions. Winds light. At approximately 10nm to YAGGO; descend via point on the arrival; heard that Runway 18R is closed. We were then given vectors to visual Runway 18L via heading and altitude. No speeds were assigned on the approach. Tower misspoke once clearing us to land on Runway 17L. The PM (Pilot Monitoring) queried the control which runway we were cleared to land and Tower replied cleared to land Runway 18L. Tower was seemingly task saturated for the last minute runway closure and heavy traffic. Landing was uneventful. Tower told us to exit Taxiway Echo; cross Runway 18R; expedite; air carrier traffic on short final. This was the first we heard of short traffic following us. As we made the right turn onto Echo; we could see the air carrier flight on short final (approximately 100 feet) landing on Runway 18L. Tower instructed the flight to GO AROUND. The flight did not GO AROUND and landed while we were on Runway 18L. We were not clear of the runway and were making our approximately 135 degree turn from the Runway 18L onto Taxiway Echo. There was some discussion from tower and the air carrier flight. Taxi to the ramp and shut down were uneventful. Overhead on ATC frequency while taxiing that Runway 18R was closed (assumed) due to bird strike.During our crew debrief; we discussed the flight and elected to call the Duty Officer and file a report due to the safety concerns; air carrier flight failure to follow ATC instruction; landing while we were on the runway. We referenced the FOM (Flight Operations Manual) elected to call the Duty Officer; explained the situation. The Duty Officer had no further input as this was FYI at this point for the company. Noncompliance of other aircrew; other aircrew failure to follow direction; other aircrew loss of situational awareness. Case study for training profile; go around in the flare short final
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.