Twin turboprop Cargo Pilot reported a critical ground conflict after landing.

Date: 2021-12 · Aircraft: Small Transport; Low Wing; 2 Turboprop Eng

Anomalies: atc-issue-all-types|conflict-ground-conflict|critical|deviation-discrepancy-procedural-clearance|ground-incursion-runway

Synopsis

Twin turboprop Cargo Pilot reported a critical ground conflict after landing.

Narrative

During normal landing at ZZZ on Runway XXR as Aircraft X; ATC had sequenced an Airbus ([Company] hereafter referred to as Airbus) at approximately 1.5 - 2.0 miles behind Aircraft X. After touchdown; ATC instructed Aircraft X to turn left on Taxiway XX; then changed their instruction to left on Taxiway XY. Aircraft X obliged and began accelerating past Taxiway XX to make an expedited exit on Taxiway XY. ATC then told Aircraft X to expedite off due to Airbus on 1 NM final. During the acceleration; and the urgency conveyed by the Controller; Aircraft X missed Taxiway XY due to low illumination of the taxiway exit and moonless night time conditions. ATC instructed the Airbus to go around; and the Airbus responded 'unable' (according to the airbus Pilot over Tower frequency after the conclusion of the incident; this was due to the late issuance of the instruction). ATC then instructed Aircraft X to accelerate down and turn right on Taxiway XC (which was not briefed and the pilot was not intimately familiar with this particular taxiway). The Pilot accelerated as much as practical in order to comply but was unable to identify or exit on Taxiway XC (or any taxiway in particular to the right). The Pilot did; however; identify Taxiway XA to the left and exited as quickly as practical. The Airbus decelerated and exited the runway at Taxiway XZ. ATC instructed Aircraft X to taxi to the ramp and issued a phone number to call for 'possible pilot deviation'. The Airbus pilot queried if he needed anything from them; but ATC responded that they were good and no additional action needed on their part. Aircraft X parked at ZZZ and the flight concluded without further incident. Suggestions - ATC Instructions and communications. The following are contributing factors to this incident. Dark Moonless Night Conditions; ATC poor spacing technique with following aircraft; ATC Poor landing rollout instruction issuance techniques (multiple fast changes to exit instructions with rising urgency and demand for rushing and Pilot to fix their spacing issue); Pilot loss of situational awareness regarding proximity to desired exit taxiway leading to missing it and delay on runway; Following Aircraft lack of situational awareness and judgment to execute go around with aircraft still occupying active runway; ATC poor judgement on timing of issuing go around instruction. Pilot attempted to comply with rapidly changing and ever increasing urgent instructions from ATC. ATC needs to improve spacing and command go around of following aircraft if spacing is lost.

Second reporter narrative

On approach to Runway XXR in ZZZ; we were told to reduce to 150 kts. We were following Aircraft X and were approximately 3 nm behind that aircraft. We explained that was the slowest we could go; due to winds. At 500 ft.; we could barely see the aircraft down the runway; and it appeared it was exiting the runway to the left. At 300 ft.; it appeared he had cleared the runway because we couldn't see him. The Tower Controller asked the aircraft to expeditiously exit the runway; and when we were flaring; we were told to go around. My Captain; the Flying Pilot; stated it he felt it was safer to land and quickly stop on the runway; versus potentially doing a touch-and-go with maximum thrust and risking a hard bounce and/or tail strike. We were able to slow the aircraft to less than 60 kts just prior to reaching Taxiway XB' and slowly approached Taxiway "XZ' where we exited safely to the right. Had the go around instructions happened sooner; we could've safely performed a go around.Minimal aircraft spacing and night operations helped contribute to this event.Had the go around instructions happened sooner; we could've safely performed a go around."

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.