AN LR36 FLC EXPERIENCES A GROSS NAV ERROR AND IS SUBJECT TO INVESTIGATION AFTER CHANGING THEIR NEXT WAYPOINT FROM 52N15W TO 53N15W. THIS WAS SUPPOSEDLY IN ACCORD WITH THE WISHES OF SHANWICK RADIO (FSS) DURING THE POS RPT AT 53N20W. THE PIC WAS NOT CLR ON THE PHRASEOLOGY AS HE WAS NOT ON THE HF FREQ WITH THE FO. THE FLT WAS CHALLENGED BY SHANNON'S CTLR AFTER RADAR IDENT APCHING 53N15W.

1997-12 · NASA ASRS report 388609

Date: 1997-12 · Aircraft: Learjet 36

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|other-unspecified

Synopsis

AN LR36 FLC EXPERIENCES A GROSS NAV ERROR AND IS SUBJECT TO INVESTIGATION AFTER CHANGING THEIR NEXT WAYPOINT FROM 52N15W TO 53N15W. THIS WAS SUPPOSEDLY IN ACCORD WITH THE WISHES OF SHANWICK RADIO (FSS) DURING THE POS RPT AT 53N20W. THE PIC WAS NOT CLR ON THE PHRASEOLOGY AS HE WAS NOT ON THE HF FREQ WITH THE FO. THE FLT WAS CHALLENGED BY SHANNON'S CTLR AFTER RADAR IDENT APCHING 53N15W.

Narrative

WE WERE XING THE ATLANTIC OCEAN ENRTE TO PARIS; FRANCE. OUR FLT PLAN CALLED FOR THE LAST 3 FIXES ALONG THE OCEANIC RTE TO BE 53N20W; 52N15W AND DOLIP INTXN. I WAS LOOKING OVER THE ARR INTO PARIS; AND MY COPLT WAS WORKING THE RADIO. AT THE TIME THAT THIS INCIDENT OCCURRED; WE WERE ASSIGNED TO AND USING AN HF RADIO FREQ AND WORKING WITH SHANWICK OCEANIC CTL. AT 53N20W MY COPLT GAVE OUR POS RPT AND PROVIDED A TIME ESTIMATE TO 52N15W. BY NOW WE HAD PASSED 20 WEST AND WERE FLYING TO 52N15W. DURING THE COURSE OF THE POS RPT; THE CTLR GAVE THE INDICATION THAT WE SHOULD BE FLYING TO 53N. I DON'T RECALL THE EXACT CONVERSATION; BUT IT SEEMED CLR TO ME THAT HE WAS EXPECTING US TO FLY TO 53N INSTEAD OF 52N. MY FEAR AT THIS POINT WAS THAT MY COPLT MAY HAVE MISUNDERSTOOD THE CLRNC WHEN HE PICKED IT UP IN GANDER; NEW FOUNDLAND. THEREFORE; WE REMOVED 52N15W FROM THE GPS/FMS AND REPLACED IT WITH 53N15W. WE THEN TURNED L APPROX 20 DEGS TO HIT THE FIX. MY COPLT PROVIDED THE CTLR WITH A NEW ETA TO 53N15W. A SHORT TIME AFTER WE CHANGED COURSE; THE CTLR RECONTACTED US AND AGAIN ASKED FOR OUR TIME ESTIMATE TO 53N15W. WE AGAIN GAVE HIM THE ETA AND HE ACKNOWLEDGED. THERE WAS NO FURTHER COM WITH SHANWICK AFTER THAT AS THEY HAD GIVEN US A VHF FREQ TO CONTACT SHANNON RADAR ON PRIOR TO 15W. PRIOR TO REACHING 15W; WE WERE CALLED BY SHANNON ON VHF AND ASSIGNED A XPONDER SQUAWK. THE CTLR CONFIRMED THAT HE HAD RADAR CONTACT AND CLRED US FROM PRESENT POS DIRECTLY TO ANNET INTXN; SOME 400 MI TO OUR SE AND ON COURSE TO PARIS. HE THEN ASKED FOR AN EXPLANATION AS TO WHY WE EXITED THE OCEANIC AIRSPACE AT 53N INSTEAD OF 52N AS OUR FLT PLAN CALLED FOR. I EXPLAINED THAT WE UNDERSTOOD THAT WE WERE EXPECTED TO FLY TO 53N; SO THAT'S WHAT WE DID. HE SAID HE WAS SUBJECTING US TO INQUIRIES AND GAVE ME ANOTHER FREQ FOR SHANWICK. I PROVIDED THEM WITH THE SAME EXPLANATION THAT I GAVE TO SHANNON CTLR. HE TOLD ME THAT THERE WOULD BE AN INVESTIGATION FOR 'GROSS NAV ERROR.' SINCE I WAS DOING SOMETHING ELSE WHEN THE CONVERSATION BTWN THE SHANWICK CTLR AND MY COPLT BEGAN; I DON'T KNOW EXACTLY WHAT WAS SAID. I DO KNOW THAT WHATEVER IT WAS CAUSED ME TO REMOVE 52N15W FROM THE GPS AND REPLACE IT WITH 53N15W; THEN TURN L 20-30 DEGS TO HIT THE FIX. I ALSO KNOW THAT ON AT LEAST TWO; AND POSSIBLY THREE SEPARATE OCCASIONS 53N15W WAS READ BACK TO THE CTLR AND ACKNOWLEDGED BY HIM. THIS INCLUDED TWO TIME ESTIMATES TO 53N15W. IF THESE WERE INCORRECT; IT SEEMS HE SHOULD HAVE BROUGHT IT TO OUR ATTN. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR SAID THAT HE HAD NOT HEARD THE FO'S EXACT CONVERSATION AFTER THE POS RPT AT 53N/20W WITH THEIR ESTIMATE FOR 52N/15W. THE COCKPIT OF A LEARJET IS NOISY AND THE CREW WERE NOT WEARING HEADSETS; BUT WERE USING THE SPEAKERS INSTEAD. THE PIC STATED THAT THEIR GND SPD WAS VERY HIGH AND THERE WAS A SENSE OF URGENCY AS HE THOUGHT THAT PERHAPS THERE WAS NOW TFC AT THEIR ASSIGNED 52N/15W POS SO TURNED THE ACFT TOWARDS THE 53N/15W POS. IT WAS A TRUE 'CATCH 22' SIT. HE REMEMBERS THE SHANWICK OPERATOR SAYING SOMETHING LIKE: 'I BELIEVE WE SHOW YOU CLRED TO 53N/15W...' RPTR ADMITS TO NOT HAVING RECEIVED A 'FORMAL' AMENDMENT TO HIS CLRNC; JUST A LOT OF INFERRING. THE TRANSCRIPT OF THE TAPE HAS BEEN FORWARDED TO LONDON FOR REVIEW. THE FAA HAS BEEN NOTIFIED OF THIS ALLEGED VIOLATION. THE FO HAD NO STATEMENTS TO MAKE TO THE CAPT. THE RPTR IS A PART TIME COMMERCIAL PLT; HIS FULL TIME PROFESSION IS NON FLYING. HE HAS MADE AT LEAST 250 ATLANTIC XINGS SO IS NOT A NOVICE. THE PART 135 OPERATOR HAS ALREADY MADE A JUDGEMENT IN THIS CASE AGAINST HIM AND IS MAKING HIM FLY A 'FREE' TRIP TO EUROPE AS PUNISHMENT FOR THE 'VIOLATION.'

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.