B737 CREW FINDS THAT GND CTL FREQ IS NOT LISTED ON CUN; FO; CHART.

Date: 1999-02 · Aircraft: B737-300

Anomalies: deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-other-unknown|other-unspecified

Synopsis

B737 CREW FINDS THAT GND CTL FREQ IS NOT LISTED ON CUN; FO; CHART.

Narrative

CANCUN-NEWARK: WE REFED OUR 10-7 PAGE TO ACQUIRE INFO REGARDING PUSHBACK CLRNC. NO INFO EXISTED; BUT THE CAPT REMEMBERED FROM 4 MONTHS AGO THAT THERE WAS A GND FREQ 121.7 (NOT LISTED ON THE CANCUN PLATES) THAT WE SHOULD TRY ANYWAY. AS A COURTESY; I XMITTED 4 TIMES ON 121.7 AND NO ONE ANSWERED. AFTER WE PUSHED BACK FROM GATE; WE REQUESTED TAXI CLRNC ON TWR FREQ 118.6. THE FEMALE CTLR YELLED AT US THAT WE DID NOT CALL HER FOR PUSHBACK CLRNC. WE KINDLY APOLOGIZED AND EXPLAINED THAT WE DID CALL FOR PUSHBACK CLRNC ON 121.7 AS A COURTESY; 4 TIMES; BUT NO ONE ANSWERED. SHE SAID THAT FREQ IS ONLY OPERATIONAL FROM XA00 TILL XK00. WE EXPLAINED THAT WE DID NOT HAVE ANY INFO FROM OUR COMPANY NOR THE CHARTS REGARDING: 1) ANY GND FREQ; 2) ANY TIME OF OP OF THAT FREQ; 3) AND NO 'PUSHBACK CLRNC REQUIRED' STATEMENT ON OUR 10-7 PAGE (AS IS MENTIONED ON ALL OUR OTHER 10-7 PAGES) TO CONCUR WITH THEIR OP. THE CTLR SAID SHE WILL HAVE TO RPT US TO THE CIVIL AUTHS; WHATEVER THAT MEANS. I NOTIFIED THE COMPANY IN REGARDS TO THIS INCIDENT AND THE LACK OF INFO THAT FLCS NEED TO ENSURE A SAFE OP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATES THAT HE BROUGHT THIS PROB TO THE ATTN OF THE CHIEF PLT; AND IT HAS SINCE BEEN CORRECTED. THE NEW CHART HAS THE FREQ AND TIMES OF OP LISTED.

More incidents for this aircraft family →

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