37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1740345 |
Time | |
Date | 202004 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PHL.Airport |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 557 |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict Ground Conflict Critical Ground Incursion Runway |
Narrative:
I was ca (captain) flying [the] visual approach to runway 27R tracking ILS 27R. Daylight/dusk VMC. We were cleared to land and no traffic in sight as previous landing traffic had cleared. After landing in the rollout phase tower said go around! My initial thought was that [there was] someone landing behind us and was too close. I then happened to look down the runway and see an aircraft taxi onto the runway further down about 2000 ft. I was in reverse with full flaps and spoilers at about 80 kts. When my first officer stated I think tower said go around. Almost immediately I keyed the mic and said we have november (north) taxiway; just before my planned exit K4. As I exited at november; I saw the aircraft continue to slowly cross 27R from the vicinity of tango taxiway.tower instructed us to monitor a frequency for a phone number to call after arrival at [the] gate. The gravity of the situation did not appear evident until after both myself and my first officer debriefed the situation and agreed that we were cleared to land and there was no traffic in sight until after landing. We both agreed that we could not 'go around' from a landing configuration with full flaps; in reverse; and spoilers deployed after landing.this safety error/event happened either due to an excursion by another aircraft onto the active runway by mistake or misunderstood ATC clearance. We were cleared to land and [with] no traffic visible on [the] runway; we landed normally. While we were in the rollout decelerating; tower either by mistake or confusion told us to go around with traffic on the runway less than 2000 ft. Ahead. This runway excursion event happened by error. I believe either the flight misunderstood hold short or was not familiar with the taxiway configuration. Or; ATC gave a clearance that was incorrect and or got distracted with the taxiing aircraft movement. In any case; I saw the aircraft on the runway in time to slow and exit early. There was no way to do a go around from full landing configuration while in reverse; slowing; with full flaps; spoilers and on brakes.the remaining distance 2000 ft. Or less would not be enough to reconfigure to a take off condition. If so; there is no way to get safely airborne and clear intruder traffic in that distance. We did the safest action which was to stop and clear the runway.
Original NASA ASRS Text
Title: Flight crew reported that as they were landing Tower told them to go around for an aircraft crossing the runway but the crew could not comply as they were already configured on their landing roll.
Narrative: I was CA (Captain) flying [the] visual approach to Runway 27R tracking ILS 27R. Daylight/Dusk VMC. We were cleared to land and no traffic in sight as previous landing traffic had cleared. After landing in the rollout phase Tower said go around! My initial thought was that [there was] someone landing behind us and was too close. I then happened to look down the runway and see an aircraft taxi onto the runway further down about 2000 ft. I was in reverse with full flaps and spoilers at about 80 kts. when my First Officer stated I think Tower said go around. Almost immediately I keyed the mic and said we have November (N) Taxiway; just before my planned exit K4. As I exited at November; I saw the aircraft continue to slowly cross 27R from the vicinity of Tango Taxiway.Tower instructed us to monitor a frequency for a phone number to call after arrival at [the] gate. The gravity of the situation did not appear evident until after both myself and my First Officer debriefed the situation and agreed that we were cleared to land and there was no traffic in sight until after landing. We both agreed that we could not 'go around' from a landing configuration with full flaps; in reverse; and spoilers deployed after landing.This safety error/event happened either due to an excursion by another aircraft onto the active runway by mistake or misunderstood ATC clearance. We were cleared to land and [with] no traffic visible on [the] runway; we landed normally. While we were in the rollout decelerating; tower either by mistake or confusion told us to go around with traffic on the runway less than 2000 ft. ahead. This runway excursion event happened by error. I believe either the flight misunderstood hold short or was not familiar with the taxiway configuration. Or; ATC gave a clearance that was incorrect and or got distracted with the taxiing aircraft movement. In any case; I saw the aircraft on the runway in time to slow and exit early. There was no way to do a go around from full landing configuration while in reverse; slowing; with full flaps; spoilers and on brakes.The remaining distance 2000 ft. or less would not be enough to reconfigure to a take off condition. If so; there is no way to get safely airborne and clear intruder traffic in that distance. We did the safest action which was to stop and clear the runway.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.