|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||airport : cyyz.airport|
|Altitude||msl single value : 800|
|Controlling Facilities||tower : cyyz.tower|
tower : lit.tower
|Operator||common carrier : air carrier|
|Make Model Name||B737-800|
|Operating Under FAR Part||Part 121|
|Navigation In Use||ils localizer & glide slope : 5|
|Flight Phase||descent : approach|
landing : go around
|Route In Use||approach : instrument precision|
|Affiliation||company : air carrier|
|Function||flight crew : first officer|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
|Anomaly||conflict : airborne less severe|
non adherence : published procedure
|Independent Detector||other flight crewa|
|Resolutory Action||controller : issued new clearance|
flight crew : took precautionary avoidance action
flight crew : executed go around
|Miss Distance||vertical : 800|
|Problem Areas||ATC Human Performance|
|Primary Problem||ATC Human Performance|
|Air Traffic Incident||Intra Facility Coordination Failure|
We were inside meadowvale zlp, fully configured at approach speed on the ILS to runway 5 at cyyz with clearance to land from the tower. The controller then cleared a business jet for takeoff. As we approached the runway, the business jet was still in position and somewhat difficult to see because it blended in with the white runway markings. The captain asked the tower if the business jet would be rolling. The tower controller's reaction made it obvious he was oblivious to the status of his runway and the conflict he had created. He hastily asked us to go around and we executed a safe go around and followed his instructions. If this had been at night or if we had failed to see the small white business jet against the white runway markings, there is no doubt we would have hit this airplane, or landed over the top of this jet in position. It was obvious that the tower controller was not paying attention to the condition of runway 5. This operation is an accident waiting to happen. At other airports, the controller does not normally issue you landing clearance until the runway is clear or the aircraft cleared for takeoff has started the roll. The tower controller cleared this aircraft for takeoff without proper separation and then proceeded to ignore the developing situation he had created.
Original NASA ASRS Text
Title: B737 FLT CREW CHALLENGES A CYYZ LCL CTLR INSIDE OF 2 MI FOR RWY 5 WHEN CTLR CLRS A BUSINESS JET FOR TKOF WITHOUT MONITORING THE DEVELOPING CONFLICT.
Narrative: WE WERE INSIDE MEADOWVALE ZLP, FULLY CONFIGURED AT APCH SPD ON THE ILS TO RWY 5 AT CYYZ WITH CLRNC TO LAND FROM THE TWR. THE CTLR THEN CLRED A BUSINESS JET FOR TKOF. AS WE APCHED THE RWY, THE BUSINESS JET WAS STILL IN POS AND SOMEWHAT DIFFICULT TO SEE BECAUSE IT BLENDED IN WITH THE WHITE RWY MARKINGS. THE CAPT ASKED THE TWR IF THE BUSINESS JET WOULD BE ROLLING. THE TWR CTLR'S REACTION MADE IT OBVIOUS HE WAS OBLIVIOUS TO THE STATUS OF HIS RWY AND THE CONFLICT HE HAD CREATED. HE HASTILY ASKED US TO GO AROUND AND WE EXECUTED A SAFE GAR AND FOLLOWED HIS INSTRUCTIONS. IF THIS HAD BEEN AT NIGHT OR IF WE HAD FAILED TO SEE THE SMALL WHITE BUSINESS JET AGAINST THE WHITE RWY MARKINGS, THERE IS NO DOUBT WE WOULD HAVE HIT THIS AIRPLANE, OR LANDED OVER THE TOP OF THIS JET IN POS. IT WAS OBVIOUS THAT THE TWR CTLR WAS NOT PAYING ATTN TO THE CONDITION OF RWY 5. THIS OP IS AN ACCIDENT WAITING TO HAPPEN. AT OTHER ARPTS, THE CTLR DOES NOT NORMALLY ISSUE YOU LNDG CLRNC UNTIL THE RWY IS CLR OR THE ACFT CLRED FOR TKOF HAS STARTED THE ROLL. THE TWR CTLR CLRED THIS ACFT FOR TKOF WITHOUT PROPER SEPARATION AND THEN PROCEEDED TO IGNORE THE DEVELOPING SIT HE HAD CREATED.
Data retrieved from NASA's ASRS site as of July 2007 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.