Air carrier flight crew reported the aircraft veered left during takeoff resulting in a rejected takeoff. Confusing taxi instructions during the reject caused them to taxi onto a parallel runway which was too small to accommodate them.
Synopsis
Air carrier flight crew reported the aircraft veered left during takeoff resulting in a rejected takeoff. Confusing taxi instructions during the reject caused them to taxi onto a parallel runway which was too small to accommodate them.
Narrative
I was the Pilot Monitoring on takeoff in ZZZ Runway XXC with strong winds. During initial takeoff roll; we experienced directional control difficulty which caused us to veer to the left. I took control of the aircraft with nose wheel steering and brakes to stay on the runway. We successfully rejected the takeoff roll then continued to taxi to clear the runway because there was an aircraft on short final; and we felt a bit rushed. We never exceeded 30 knots. While we were handling the after reject procedures and clearing the runway; we thought we heard (misunderstood) the Controller say; 'clear left on Taxiway 1 and left on XY left.' We turned left on Taxiway 1 then immediately left on Runway XXL and held our position. We then realized that we could not use Taxiway 2 to clear XXL since our wingspan was too big and I was not comfortable doing a 180 degree turn on XXL. The Tower was quick and professional to help us get a tug to push us backwards on XXL onto Taxiway 1. It took 30 minutes for the push back tug and for us to clear Runway XXL. We taxied back to XXC and took off uneventfully.Suggestions: During times of extreme workload; such as a RTO; issued instructions should be slow and methodical from the Pilot to ATC and ATC to the Pilot. We just finished an RTO; were busy completing the RTO procedures while clearing the runway for arriving traffic. We should have slowed our process down and clarified any taxi instructions.
Second reporter narrative
I was the Pilot Flying on takeoff Runway XXC in ZZZ. The takeoff weight was around 150.000lbs and the RCR (Runway Condition Reading) was 5 with strong winds. Performance data required a bleed off takeoff. After the aircraft lineup on Runway XXC; the Captain gave me control of the aircraft for takeoff. I applied initial thrust of approximately 40 percent and after stabilization of the engines; I advanced the thrust levers. The aircraft immediately started to veer to the left. I reduced the thrust and disengaged the auto throttles. The Captain took control of the aircraft and I made the transmission to Tower stating the takeoff reject. Tower instructed us to clear Runway XXC via Taxiway 1.On Taxiway 1 we immediately turned left on Runway XXL and realized that we were stuck on Runway XXL. Tower instructed us to hold our position and was very professional and helpful organizing a tug to move us back in order to taxi via Taxiway 1 to Runway XXC. After discussing the possible reasons for our directional problems during takeoff and contacting Dispatch; we both agreed to attempt another takeoff. We departed Runway XXC uneventfully. The feeling of self-induced rush to clear the runway for the landing traffic after the takeoff reject; the unaccustomed environment in ZZZ and the high workload after the reject procedure might have contributed to the expectation bias resulting in misinterpretation/ incorrect execution of the Tower instructions. Inappropriate task management and channelized attention has led to the situation. Proper workload prioritization would have been the key to handle the situation correctly.The feeling of self-induced rush to clear the runway for the landing traffic after the takeoff reject; the unaccustomed environment in ZZZ and the high workload after the reject procedure might have contributed to the expectation bias resulting in misinterpretation/ incorrect execution of the Tower instructions. Inappropriate task management and channelized attention has led to the situation. Proper workload prioritization would have been the key to handle the situation correctly.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.