Narrative:

Our flight was issued a line up and wait (position and hold) clearance by tower while waiting for a previously landed heavy to clear the runway and another aircraft at approximately a 5 mile final. We taxied onto the runway and the captain set the brakes to park while we waited for the heavy to clear the runway. Once clear; tower issued us a takeoff clearance. The captain stated 'your aircraft' (to me) and then he responded to tower.I released the brakes and pushed the power up to the takeoff set while both engines continued to spool up to takeoff power. At a speed of 40-50 knots; I heard '[company] exit the runway and make the first available right turn.' the captain's hand was below the thrust levers and it prevented me from immediately reaching the idle thrust stop. I rejected the takeoff by attempting to pull the power to idle immediately expecting to hear him state; 'reject my aircraft.' he seemed very confused; stating 'what are you doing?' it felt as though he actually advanced the thrust levers from below as I was attempting to pull them to idle and reject the takeoff; but I cannot be sure as I never looked down. I stated we are rejecting and he made another inquisitive stammering statement 'huh; what?' and removed his hand from below the thrust levers. I realized he may not have heard what I heard and was still confused. I stated 'rejected takeoff; your aircraft;' as this seemed the most appropriate way to bring him back in the loop as to what we were immediately doing. We exited the runway to the right and talked about what had just occurred. He asked me to ask the tower to explain why we were given such an instruction after we began our takeoff roll; which I did and they responded to.the essence was that through multiple transmissions by the tower and us; our communications were being stepped on or blocked which led to confusion on the captain's part. The tower; realizing a loss of separation was possible; and not hearing a takeoff clearance read back; issued us instructions to exit the runway.since we were now busy rejecting the takeoff; the tower issued a go around to the aircraft of final. Upon reaching our destination; I asked the tower controller there for the control tower phone number and spoke first with [controller] and then the operations manager. I just wanted to debrief the event and see what we; as an aircraft crew could have done to prevent or mitigate a future occurrence; and to let the working controller know that I thought he had done an excellent job. It was at the point that the captain asked me to tell the operations manager that we would not be filing this as a rejected takeoff. On [another] flight (justified) his reasoning to not file the rejected takeoff as per company ops specs because 'he would have to file mountains of paperwork.' I disagree with that statement as he failed to follow company sops.

Related reports:

Google
 

Original NASA ASRS Text

Title: Flight crew of a large transport reported executing a low speed rejected take off in compliance with ATC instructions. There were difficulties in clearly understanding the Tower's intentions due to heavy simultaneous radio communications.

Narrative: Our flight was issued a line up and wait (position and hold) clearance by Tower while waiting for a previously landed heavy to clear the runway and another aircraft at approximately a 5 mile final. We taxied onto the runway and the Captain set the brakes to park while we waited for the heavy to clear the runway. Once clear; Tower issued us a takeoff clearance. The Captain stated 'Your Aircraft' (to me) and then he responded to Tower.I released the brakes and pushed the power up to the takeoff set while both engines continued to spool up to takeoff power. At a speed of 40-50 knots; I heard '[Company] exit the runway and make the first available right turn.' The Captain's hand was below the thrust levers and it prevented me from immediately reaching the idle thrust stop. I rejected the takeoff by attempting to pull the power to idle immediately expecting to hear him state; 'Reject My Aircraft.' He seemed very confused; stating 'what are you doing?' It felt as though he actually advanced the thrust levers from below as I was attempting to pull them to idle and reject the takeoff; but I cannot be sure as I never looked down. I stated we are rejecting and he made another inquisitive stammering statement 'huh; what?' and removed his hand from below the thrust levers. I realized he may not have heard what I heard and was still confused. I stated 'rejected takeoff; your aircraft;' as this seemed the most appropriate way to bring him back in the loop as to what we were immediately doing. We exited the runway to the right and talked about what had just occurred. He asked me to ask the Tower to explain why we were given such an instruction after we began our takeoff roll; which I did and they responded to.The essence was that through multiple transmissions by the Tower and us; our communications were being stepped on or blocked which led to confusion on the Captain's part. The Tower; realizing a loss of separation was possible; and not hearing a takeoff clearance read back; issued us instructions to exit the runway.Since we were now busy rejecting the takeoff; the Tower issued a go around to the aircraft of final. Upon reaching our destination; I asked the Tower controller there for the Control Tower phone number and spoke first with [controller] and then the Operations Manager. I just wanted to debrief the event and see what we; as an aircraft crew could have done to prevent or mitigate a future occurrence; and to let the working controller know that I thought he had done an excellent job. It was at the point that the Captain asked me to tell the Operations Manager that we would not be filing this as a rejected takeoff. On [another] flight (justified) his reasoning to not file the rejected takeoff as per Company Ops Specs because 'he would have to file mountains of paperwork.' I disagree with that statement as he failed to follow Company SOPs.

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.