2024-06 · NASA ASRS report 2127348
A flight crew reported they attempted to taxi off the runway on a closed taxiway. They stopped when they saw cones but were still partially on the runway causing a subsequent arrival to go around.
On final approach to Runway XXR; Tower was contacted and landing clearance received. During crew transfer of controls (critical phase of flight) following landing rollout; Tower said 'plan to roll to the end' as we were making the turnoff at high speed exit [Taxiway] 1 with insufficient room. to turn back onto the runway. Tower contacted an airport operations vehicle who proceeded to the intersection and removed 4 'unlit cones' at the middle of the intersection. As we waited; approximately 3-4 minutes; while partially on Taxiway 1; the First Officer and I discussed we had not noticed the taxiway closure in the digital ATIS. We did notice it was in the updated ATIS. Neither of us recalled seeing it on the previous ATIS. We debriefed the incident at the gate and discussed crew and ATC factors. While it's possible we may have missed the closure in the previously obtained ATIS and review/briefing of appropriated runway exits; it would have been helpful to to have received the 'Plan to Exit at The End of The Runway' clearance from Tower during the initial contact along with the landing clearance; prior to actually making the turn. There was also no lighting on or near the cones located at the [Taxiway] 1 closure which would have which would have made the closure more visible earlier in the transition to exiting the runway. The aircraft following us was instructed to go-around as we were not completely clear of the runway. WE heard that crew querying the Tower for confirmation of the [Taxiway] 1 high-speed taxiway and being advised to 'Plan to Roll to The Endof Runway XXR' on subsequent approach. Careful review of the ATIS and closure may have helped if we both managed to overlook the ZZZ airport closures and taxi routing conditions. The timing of the updates received from the Tower did not allow for us to plan the exit at the end as we were already transitioning to exit at [Taxiway] 1 prior to stopping short. Also; the expectation bias to exit at [Taxiway] 1 from Runway XXR may have been a factor on my part.
The event occurred at ZZZ on Aircraft X. I was the First Officer (FO) and Pilot Flying. After landing on Runway XXR and while slowing the aircraft to a safe taxi speed; the Captain came on the brakes and announced he had control of the aircraft. As we decelerated; the Captain was already starting to aim left of centerline in order to exit at intersection [Taxiway] 1. What seemed like almost simultaneously as we started to make our turn off the Tower Controller announced to plan to taxi to the end; Taxiway 2 to the gate. I repeated the instructions; which I may have flubbed on read-back as I was caught off guard by 'taxi to the end' instructions and whether she meant end of 2 taxiway or the end of the runway. As we exited the runway we could barely make out a set of cones in the darkness closing the taxiway at the typical hold short line and we stopped immediately. Tower asked if we could turn back to the runway but we were unable to turnaround given how far in we had taxied and were fouling the runway. This caused the Tower to instruct a go-around to the landing aircraft in trail. Tower contacted airport operations and they quickly removed the cones in order for us to taxi to the gate without further incident.I did not recall [Taxiway] 1 being listed as closed in the NOTAMS. It was however listed in the ATIS information we had received; though I did not recollect reading it on earlier versions during the day. As I had previously landed in ZZZ with construction at this airport on-going with usual daily taxiway closures; I had missed that [Taxiway] 1 was now closed by ATIS. This highlights the necessity of emphasizing at airports with on-going construction that there may be temporary changes and closures which NOTAMs may not capture. Additionally; I was probably suffering from expectation bias as [Taxiway] 1 is a normal exit point for operations in ZZZ. In the future I clearly need to assess ATIS identified taxiway closures and how they may impact landing and taxi to the gate.Prevention this type of loss of situational awareness starts in the cockpit with processing the data. However; there should also be secondary safety measures. Had this occurred during the day; we could have clearly seen the cones and not attempted to exit there. While this occurred at night; there were no flashing or other lighted indications the taxiway was closed; only orange cones you could barely observe until in close proximity. A notification from Tower to expect to taxi to the end when given a landing clearance would also have been helpful; especially on a short landing runway. Incidentally; the next aircraft to land was given this notification to expect to taxi to the end of the runway when given a landing clearance; after which they quired if [Taxiway] 1 was inf fact closed. Since Tower and Ground Control were on the same frequency; I recall hearing the helpful instruction to plan to exit the runway at the end on subsequent landing clearances.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.