AN ACR TAKES OFF FROM DENVER WITHOUT RECEIVING THEIR RTE CLRNC THROUGH PDC OR VOICE.
Synopsis
AN ACR TAKES OFF FROM DENVER WITHOUT RECEIVING THEIR RTE CLRNC THROUGH PDC OR VOICE.
Narrative
DURING PREFLT AND COCKPIT SETUP; FO REQUESTED ACARS DATALINK PDC (IFR CLRNC). RESPONSE RECEIVED WAS THAT PDC WAS NOT STORED AND TO CONTACT CLRNC DELIVERY BY VOICE. THIS WAS NOT UNUSUAL; BUT DUE TO THE NORMAL SOPS AND A COUPLE OF IRREGULAR PROBS; NEITHER OF US CONTACTED CLRNC DELIVERY FOR THE IFR CLRNC. AT THIS POINT I WAS UNAWARE OF THE ACARS MESSAGE RESPONSE. PROB WAS IDENTED AFTER TKOF WHEN DEN TWR INSTRUCTED US TO SQUAWK XXX (WHICH WAS NOT SET) DURING TAXI-OUT NEITHER DEN GND NOR TWR QUESTIONED OUR IFR CLRNC (OR LACK OF). ONCE THE PROB WAS DISCOVERED; I VERIFIED OUR ALT AND RTE WITH ZDV (WHICH WAS AS FILED AND NOTED ON OUR FLT PLAN FORECAST). NO CONFLICT OCCURRED; NO ALT OR RTE/VECTOR CLRNC WAS VIOLATED. NOTE -- SOMETIMES DURING OUR PREFLT BRIEFINGS; THE IFR CLRNC IS DELAYED AND WE TAKE NOTE OF THAT. THIS TIME HOWEVER IT WAS FORGOTTEN. ALSO; I WAS UNDER THE IMPRESSION THAT GND CTL WOULD HAVE QUESTIONED OUR REQUEST FOR TAXI; HAD THEY NOT HAD OUR CLRNC. SINCE THEY DIDN'T; I'M ASSUMING THEY IN FACT DID HAVE OUR CLRNC; AND ALLOWED US OUR TAXI REQUEST.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.