THE FLC OF A B767 CARGO FLT IS TAKEN TO TASK AND ISSUED NOTICE OF A PENDING VIOLATION WHEN RPTING AN INCORRECT INTXN FOR THEIR PLANNED 'NEXT POINT' AFTER THE UPCOMING LATITUDE; LONGITUDE POS TO EGGX; FO.

Date: 2001-11 · Aircraft: B767 Undifferentiated or Other Model · Phase: cruise

Anomalies: deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|other-amended-clrnc

Synopsis

THE FLC OF A B767 CARGO FLT IS TAKEN TO TASK AND ISSUED NOTICE OF A PENDING VIOLATION WHEN RPTING AN INCORRECT INTXN FOR THEIR PLANNED 'NEXT POINT' AFTER THE UPCOMING LATITUDE; LONGITUDE POS TO EGGX; FO.

Narrative

RECEIVED 2 OCEANIC CLRNCS FROM GANDER: 1) XA55Z 4850N 5040N 5330N 5420N DOGAL BURAK EXP 290 .80M. 2) XA57Z 4850N 5040N 5330N 5420N MALOT BURAK EXP 290 .80M. THE FIRST CLRNC WAS ACCORDING TO FLT PLAN. CAPT THOUGHT THE SECOND CLRNC WAS RESENT AT XB57Z BECAUSE HE HAD NOT ACKNOWLEDGED FIRST CLRNC (VIA ACARS). HE ACKNOWLEDGED SECOND CLRNC AND READ BACK THE NUMBER. HE MADE AN ERROR BY NOT NOTICING THAT DOGAL FIX WAS CHANGED TO MALOT. WE WERE BUSY CODING THE FIRST CLRNC WHEN SECOND ONE CAME ACROSS. SHANWICK OCEANIC NOTIFIED US OF DISCREPANCY DURING POS RPTS PRIOR TO REACHING 5420N. TIME WAS ALMOST 4 HRS LATER WHEN WE WERE NOTIFIED. THERE WAS NO DEV FROM ASSIGNED COURSE OR A TFC CONFLICT. THE SHANWICK CTLR SAID HE WAS GOING TO FILE A GROSS NAV ERROR RPT; (EVEN THOUGH NO DEV HAD OCCURRED). CAPT MADE AN ERROR IN RECEIVING SECOND CLRNC 3 MINS AFTER RECEIVING FIRST CLRNC. THE NUMBERS WERE IDENTICAL EXCEPT FOR 'A' ADDED TO THE SECOND CLRNC. THE 2 CLRNCS WERE ALSO THE SAME EXCEPT FOR SUBSTITUTION OF FIX MALOT FOR DOGAL. RECOMMENDATION: 1) GANDER SHOULD ASSIST BY INCLUDING THE WORD 'REROUTE' IN THE AMENDED CLRNC. I HAVE SEEN THIS BEFORE. 2) A COMPLETELY DIFFERENT CLRNC NUMBER WOULD HELP. 3) ANY TIME ANY NEW CLRNC IS RECEIVED BOTH CREW MEMBERS (OR 3 CREW MEMBERS) SHOULD READ/REVIEW THE CLRNC FOR ANY CHANGES OR DISCREPANCIES. IN THIS CASE; I WAS NOT AWARE THAT A SECOND CLRNC HAD BEEN RECEIVED.

More incidents for this aircraft family →

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