CRJ50 Flight Crew landing Runway 23 at CYYZ is told to expedite of on Runway 15R for landing traffic. Captain turns early at Taxiway F which is closed and the landing traffic is sent around.

Date: 2010-08 · Aircraft: Regional Jet CL65; Undifferentiated or Other Model · Phase: taxi

Anomalies: conflict-ground-conflict|less-severe|deviation-discrepancy-procedural-clearance|ground-incursion-taxiway

Synopsis

CRJ50 Flight Crew landing Runway 23 at CYYZ is told to expedite of on Runway 15R for landing traffic. Captain turns early at Taxiway F which is closed and the landing traffic is sent around.

Narrative

We landed on Runway 23 at Toronto with the First Officer the flying pilot. At about 50 KIAS we were transferring control from First Officer to Captain so that I could taxi off the runway. We were planning a normal rollout to Taxiway H2. In the middle of transferring control; the Tower called us and requested that we EXIT IMMEDIATELY on Runway 15R. I believe that they said there was traffic on short final behind us. We looked to the left and saw much construction. There were two exits for the runway. The first was Taxiway F; and the second exit was 15R. Both Taxiway F and 15R were not blocked by cones (or anything else) for the construction. I was focusing on the construction and turned were I thought there were no workers. I saw what appeared to be an open exit from the runway; but evidently the workers were too close for us to be allowed to use Taxiway F. The Tower said; 'Stop'. I believe that they told an aircraft to go around after that. The First Officer read back that we were stopping. With the events happening very quickly; we were trying to verify our location. We noticed the sign for Runway 15R a short distance to our right. We had accidentally exited the runway on Taxiway F instead of Runway 15R. We waited for several seconds. The Tower then asked us to do a 180 and back taxi on Taxiway F and make a right turn on Taxiway J. We complied and had a normal taxi to the ramp after that. I called the Tower on the telephone after arriving at the gate; and left a message twice (there was nobody answering the telephone on the number we have in our green sheets; only answering service). I left my cellular number; and requested that they call me to verify that they didn't need any more information. They never asked us to call them on the taxi in. I am not sure if Canadian procedures require Toronto Tower to complete any paperwork or reports for the incident. They didn't ask any questions; and didn't appear that they wanted any more information. I talked to the Chief Pilot on duty; and we agreed that I should put in a report in case any more information was requested by Toronto Tower.I should not have reacted quickly to try and comply with ATC's instructions. With the confusing construction near the runway; I should have told ATC that we were continuing to our original Exit Point on the runway; Taxiway H2. The other aircraft should have had enough separation from us to land after we taxied off the runway if we continued to Taxiway H2. Also; if cones (or other devices) were in place; we would have known that workers were there; and would not have exited the runway at that location. It was unfortunate that we were given instructions at a high workload moment in the rollout; and we were unable to react quickly enough to correctly comply with there requests.

Second reporter narrative

After landing on Runway 23 in CYYX the Captain and I exchanged controls; and ATC told us to exit the runway on 33L without delay due to landing traffic behind us. Captain applied additional braking to make the turn off at what he thought was 33L. Instead the Captain exited at Taxiway F by mistake. 33L was a little bit further down the runway. As the Captain turned we both realized that he had not turned on to 33L and the taxiway he had turned on to was closed due to construction. To avoid this event in the future we should not let the pressure of exiting the runway quickly impair our situational awareness and make sure that we comply exactly with air traffic controls instructions.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.