Air carrier flight crew reported a rejected takeoff when ATC cancelled their takeoff clearance due to traffic taxiing across the runway.
Synopsis
Air carrier flight crew reported a rejected takeoff when ATC cancelled their takeoff clearance due to traffic taxiing across the runway.
Narrative
When departing full length off of Runway XXR in ZZZ we were cleared to line up and wait. The Captain handed over control as ATC cleared us for takeoff with instruction to climb via SID. I pushed the power up to 1.05 Engine Pressure Ratio (EPR) and before it had a chance to stabilize and before advancing thrust; ATC cancelled our takeoff clearance. We were no faster than 20 knots. I brought the power back down to idle as the Captain said Reject; my Aircraft". After I got through my startle reflex I saw a 737 crossing the runway in front of us. The tower then cleared us for takeoff again; but the Captain declined and had me ask to go somewhere where we could run a checklist. ATC instructed us to exit left and hold short of Runway XYR. There we debriefed each other; ran the rejected takeoff below 80 knots QRH and attempted to contact the Duty pilot to ensure we had complied with all procedures. We got the concurrence from all flight deck crew and maintenance that it was safe to continue and departed Runway XXR. It seemed to be an honest mistake by ATC. They acted professionally and responded immediately. Unfortunately I don't know what you do to prevent human error."
Second reporter narrative
Departed the gate and taxied to Runway XXR for departure. We were given a line up and wait" clearance for XXR; and we complied. Shortly thereafter; we received our "takeoff" clearance for XXR. Then; a short time after the "takeoff" clearance was given we received tower instruction to "cancel take off." Our engines were spooled and we were rolling; but were below 20 knots. We executed the "rejected takeoff" procedure. We did not reply immediately to the first "rejected takeoff" clearance due to us actively executing the "rejected takeoff" procedure. A few seconds later we were issued a second "cancel takeoff" clearance. We replied to the "cancel takeoff" clearance; and by then we were already stopped on the runway.We observed a aircraft crossing XXR; left to right; downfield approximately 5;000 ft. from our aircraft position. After the aircraft was clear of the runway we were given another "cleared for takeoff" clearance. We declined that clearance and elected to clear the runway to run QRH procedures and verify procedures were accurately followed. Complied with: operating manual sections; and QRH XX-XX. Additionally I reached out to our dispatcher; maintenance desk; and duty pilot (did not reply before we departed). All parties conferenced in and all flight deck crew agreed aircraft was safe to continue and legal to continue without returning to gate for a documented Maintenance Task Card (MTC) discrepancy. After a 15 minute delay; we departed XXR uneventfully. Without removing the magnitude of the obvious potential threat of a runway incursion; I would like to include in this report that ATC tower controller was professional; he acted with urgency when needed; and complied with our request to exit; and didn't rush us to complete appropriate checklists and procedures. I would like to add a recommendation to a procedure change and highlight a discrepancy in our manuals. In our QRH; in the index; the appropriate action is listed as "Rejected Takeoff." However when you go to QRH XX-XX; the title of the procedure to accomplish is titled "Takeoff After Rejected Takeoff Below 80 Knots." My suggestion is to have the procedure be called "Rejected Takeoff." Then the first question is; "Was the take off rejected above or below 80 knots? Note: Often pilots understate when a rejected takeoff was initiated. Was the 80 knot call made? Etc...If yes; Action: return to gate; discrepancy must be entered….Etc.' Ultimately I am suggesting you incorporate most FOM and AOM information and include all rejected takeoff's into the QRH; just low speed."
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.