HDG TRACK DEV IN A NON ADHERENCE WITH ATC CLRNC INSTRUCTION. AMENDED CLRNC RTE CHANGE.

Date: 1993-04 · Aircraft: Widebody; Low Wing; 2 Turbojet Eng

Anomalies: aircraft-equipment-problem-less-severe|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|other-unspecified

Synopsis

HDG TRACK DEV IN A NON ADHERENCE WITH ATC CLRNC INSTRUCTION. AMENDED CLRNC RTE CHANGE.

Narrative

OUR ACFT; A 2 ENG WDB; WAS DISPATCHED NON ETOPS DUE TO A MAINT PROC THAT REQUIRES 5 LEGS TO BE FLOWN PRIOR TO RECERTIFYING IT FOR ETOPS. OUR FILED RTE WAS GIVEN TO US AS THE CLRED RTE AND HAD BEEN RECEIVED AS: FROM N6538 W060...SF...KK...N6523 W035...65N 030W...GIMLI...KEF...ALDAN...61N 01235W...60N 010W...BEN.... WE PROCEEDED ON THIS COURSE WHICH WAS SET UP FOR AIRWAYS THAT WOULD KEEP OUR RTE WITHIN 60 NM OF AN ARPT AT ALL TIMES; WHEN (ON HIGH FREQ) ICELAND RADIO RELAYED A NEW CLRNC FROM REYKJAVIK OAC THAT READ: FROM 6538N 060W...67N 050W...66N 040W...65N 030W...63N 020W...60N 010W...STN MAINTAIN 350 MACH .80. WE READ BACK THE CLRNC TO ICELAND RADIO AND ADVISED THEM THAT WE WERE NON ETOPS TODAY AND WOULD NEED TO CHK WITH CHICAGO DISPATCH PRIOR TO ACCEPTING THE CLRNC FOR LEGALITY. I LOADED THE NEW RTE INTO RTE 2 AND NOTICED IT WAS FAIRLY CLOSE TO THE ORIGINAL ROUTING BUT COULD NOT ASCERTAIN ITS LEGALITY FOR A NON ETOPS OP. WE TRIED TO SEND THIS ROUTING VIA ACARS TO DISPATCH BUT RECEIVED NO COM. WE THEN ASKED ICELAND FOR A PHONE PATCH TO CHICAGO DISPATCH AND GAVE HIM THE NUMBER. THE OTHER FO WAS TRYING TO GET THROUGH WHEN ICELAND CAME BACK AND SAID WE MUST PROCEED BY THE NEW ROUTING. WE TOLD HIM AGAIN THAT WE WERE NON ETOPS AND THEY BEGAN ASKING US ABOUT NAV CAPABILITY. WE CONFIRMED COMPLETELY OPERATIONAL NAV CAPABILITY BUT DISPATCHED NON ETOPS FOR MAINT CONSIDERATIONS. WE TOLD THEM WE WOULD PROCEED TO 67N 050W BUT STILL NEEDED TO VERIFY ITS LEGALITY; AFTER THEY INSISTED WE PROCEED. CHICAGO DISPATCH FINALLY WAS RECEIVED BY PHONE PATCH WHO ADVISED US THAT WE COULD NOT RERTE AND MUST STAY ON ORIGINAL ROUTING. WE ADVISED ICELAND RADIO THAT WE MUST RETURN TO THE ORIGINAL ROUTING. THEY HAD TO RELAY TO REYKJAVIK OAC AND WOULD CALL US BACK. WE PRODDED THEM AGAIN TO RECEIVE CLRNC ON THE ORIGINAL ROUTING AS WE WERE UNABLE THE RERTE AND THEY AGAIN SAID THEY WOULD CHK. PRIOR TO SF WE ADVISED THEM WE MUST PROCEED BY THE ORIGINAL ROUTING AND THEY AGAIN ASKED US ABOUT NAV CAPABILITIES; AND THEY WOULD CHK. AT SF WE ADVISED THEM WE WERE PROCEEDING BY THE ORIGINAL ROUTING AND TURNED. 95 MINS LATER WE RECEIVED ACARS MESSAGE THAT SAID THAT THE REROUTING WAS VALID AND THAT HE (THE DISPATCHER) WAS SORRY FOR ANY INCONVENIENCE. ICELAND HAD ADVISED US THAT A RPT WOULD BE FILED AS 067N 050W WAS WITHIN 50 MINS LEGALITY. SUPPLEMENTAL INFO FROM ACN 237816: WE WERE UNABLE TO ACCEPT THIS CLRNC DUE TO ACFT BEING DISPATCHED NON ETOPS DUE TO AN ERRATIC AUTO PRESSURIZATION CTLR. WE HAD GREAT DIFFICULTY COMMUNICATING OUR NEEDS TO REYKJAVIK OAC THROUGH ICELAND RADIO HIGH FREQ. WHEN WE INFORMED THEM WE WERE UNABLE ETOPS WE WERE REPEATEDLY QUESTIONED ABOUT OUR NAV CAPABILITY. IT WAS EXTREMELY DIFFICULT TO COMMUNICATE WITH BOTH THE ICELAND HIGH FREQ OPERATOR AND DISPATCH THROUGH THE HIGH FREQ PATCH. IN ADDITION THE LANGUAGE BARRIER PLUS A RADIO OPERATOR RELAYING CTL INSTRUCTIONS BTWN AN ACFT AND CTLR CREATES A CHAOTIC CONDITION WHEN ATTEMPTING TO COMMUNICATE ALL BUT ROUTINE INFO. ACFT IS TCASII EQUIPPED AND NO TFC WAS OBSERVED AT ALL DURING THIS INCIDENT.

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