37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1708946 |
Time | |
Date | 201912 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ATL.Airport |
State Reference | GA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict Ground Conflict Critical Ground Incursion Runway |
Narrative:
We were instructed to line up and wait with traffic to cross down field on runway 27R. Tower instructed a host of aircraft to cross the runway. After all of the aircraft had crossed; tower then cleared us for takeoff. I was pm; the captain was PF. Around 80 knots I saw a air carrier Y edging out onto the runway and [I] verbalized this to the captain. Tower then said something like 'air carrier Y; what are you doing? Stop right there.' this; coupled with the fact that the air carrier Y continued moving out onto the runway was enough reason for the captain to call a rejected takeoff (now at around 100 knots). Tower did not instruct us to abort. We safely came to a stop and exited the runway and completed the QRH and appropriate checklists. It seemed as though tower assumed air carrier Y had crossed when we had been cleared for takeoff; but they had actually not even begun to cross the runway. Additionally; it's tough to see taxiway papa (where air carrier Y) while you're at the approach end of 27R. Regardless; we shouldn't have been cleared to take off or air carrier Y's clearance to cross the runway should have been cancelled. I do not know what happened in the tower; but we stopped as soon as we saw it was unsafe to continue.
Original NASA ASRS Text
Title: Air carrier flight reported a rejected takeoff at about 100 knots at ATL airport due to a ground conflict with another air carrier crossing their runway.
Narrative: We were instructed to line up and wait with traffic to cross down field on Runway 27R. Tower instructed a host of aircraft to cross the runway. After all of the aircraft had crossed; Tower then cleared us for takeoff. I was PM; the Captain was PF. Around 80 knots I saw a Air Carrier Y edging out onto the runway and [I] verbalized this to the Captain. Tower then said something like 'Air Carrier Y; what are you doing? Stop right there.' This; coupled with the fact that the Air Carrier Y continued moving out onto the runway was enough reason for the Captain to call a rejected takeoff (now at around 100 knots). Tower did not instruct us to abort. We safely came to a stop and exited the runway and completed the QRH and appropriate checklists. It seemed as though Tower assumed Air Carrier Y had crossed when we had been cleared for takeoff; but they had actually not even begun to cross the runway. Additionally; it's tough to see Taxiway Papa (where Air Carrier Y) while you're at the approach end of 27R. Regardless; we shouldn't have been cleared to take off or Air Carrier Y's clearance to cross the runway should have been cancelled. I do not know what happened in the Tower; but we stopped as soon as we saw it was unsafe to continue.
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.