Incident at FORT LIARD NT (CYJF) (Conflict - potential, Communication error, ATS operating irregularity)
2003-03-26: Blower 120 was working on Runway 02/20 at Fort Liard. Upon turning around at the 20 end of the runway, the driver observed NCB 217, a Beech King Air 200, taxiing towards him. Blower 120 backed up on the pre-threshold area of Runway 20 and advised the CARS Observer/Communicator that he was off the runway and would hold at the threshold until the King Air departed. NCB 217 departed at 1838Z. The driver had not been given the departing a/c traffic. The driver of Blower 120 then requested permission back onto Runway 02/20. Shortly after proceding onto the runway, he was asked to leave the runway as VAL 600, a DHC-7, was on final for Runway 20. The driver of Blower 120 was only able to exit on the graded area on the side of the runway and VAL 600 landed without incident at 1843Z. Again, the driver was not advised by the CARS O/C of the approaching DHC-7 and did not have time to exit on a taxiway. Nav Canada reported that the CARS Observer/Communicator's certificate has been suspended and an investigation begun. This will include an on-site visit from NWT Arctic Airports officials, who administer the CARS O/C sites on behalf of Nav Canada. Their on-site investigation is scheduled for Thursday/Friday of next week.
2003-04-29: UPDATE NWT Airports Division reported that the driver of Blower 120 requested and was given permission by the CARS O/C to proceed onto Runway 02/20 to conduct snow removal. At the time, there were no indications that flights NCB 217 or VAL 600 were outbound and inbound respectively. The crew of NCB 217 then called the CARS O/C requesting the advisory and proceeded down Runway 02/20 to the threshold of Runway 20 while receiving the advisory. Blower 120 had just finished the northwest side of the runway and was proceeding back up the southeast side when he realized that NCB 217 was proceeding down the runway. The driver then backed up onto the pre-threshold area of Runway 20 and told the CARS O/C that he was off the runway and would hold until NCB 217 departed. The vehicle driver reported that the CARS O/C did not advise him to leave the runway. While holding in the pre-threshold areas is prohibited, there was no way for the driver to return to the apron as NCB 217 was on the runway. After NCB 217 was airborne, the driver requested permission to go back on the runway and he indicated that the CARS O/C gave permission. However, the CARS O/C stated that he did not give permission because VAL 600 was inbound. Blower 120 proceeded onto the runway and was blowing snow near the 400 foot runway lights when he was asked to vacate the runway. The driver then saw VAL 600 on final and because he did not have time to exit the runway on a taxiway, he backed up off the runway onto a graded area 200 feet from the threshold of Runway 20 and 32 feet off the runway surface. The a/c landed without incident, but the driver expressed concern that the vehicle might be hit by the wingtip. The driver stated that he was not advised of the approaching a/c in a timely manner. NWT Airports found that the CARS O/C was relatively inexperienced and was a recent graduate. He was also not completing aircraft data strips in the correct manner. It was recommended that the CARS O/C be re-certified before returning to duty; that he identify to all inbound aircraft traffic that vehicles are on the maneuvring area and that they will have to circle until the runway is clear; that all airport vehicles be equipped with radios that permit communication on the MF; that exit pads be constructed at each end of the runway to permit vehicles to exit the runway; that a low-cost recording device be evaluated as a means of having a record of audio communication.
|Occurred At||- 18:38|
|Day or Night?|
|TSB Occurrence Number|
|TSB Class of Investigation|