Go Back  PPRuNe Forums > Ground & Other Ops Forums > ATC Issues
Reload this Page >

North Atlantic Tracks & Gross Navigational Errors

ATC Issues A place where pilots may enter the 'lions den' that is Air Traffic Control in complete safety and find out the answers to all those obscure topics which you always wanted to know the answer to but were afraid to ask.

North Atlantic Tracks & Gross Navigational Errors

Old 9th Sep 2009, 13:36
  #1 (permalink)  
Thread Starter
 
Join Date: Nov 2003
Location: In la la land.......
Age: 45
Posts: 174
Likes: 0
Received 0 Likes on 0 Posts
North Atlantic Tracks & Gross Navigational Errors

would anybody have any links that explain Gross Navigational Errors on NATs? Is there a CAA or FAA reference that I could use to determine the process for how they are monitored or reviewed?

I've found some material via google on events which led to a GNE but I'm looking for the laws or what ATC guys are taught..

Many thanks
zoink..
zoink is offline  
Old 9th Sep 2009, 21:22
  #2 (permalink)  
 
Join Date: Mar 2007
Location: yes
Posts: 14
Likes: 0
Received 0 Likes on 0 Posts
A GNE is defined as one of the following (at least in Shanwick airspace):

An observation which differs from a report by 25nm or more laterally,
An observation which differs from an estimate passed by Shawick by 25nm or more laterally or
A report which differs from an estimate by 25nm or more laterally.

Responsibility for monitoring GNEs in NAT airspace is delegated to the
North Atlantic Central Monitoring Agency (NAT CMA), you can read a bit about them here:
CMA

Hope that helps.
G-OFUK is offline  
Old 10th Sep 2009, 12:35
  #3 (permalink)  
Thread Starter
 
Join Date: Nov 2003
Location: In la la land.......
Age: 45
Posts: 174
Likes: 0
Received 0 Likes on 0 Posts
this is perfect. thank you G-OFUK!!
zoink is offline  
Old 12th Sep 2009, 16:42
  #4 (permalink)  
 
Join Date: Feb 2006
Location: -
Posts: 508
Likes: 0
Received 0 Likes on 0 Posts
In addition to the above, Shanwick procedures and the NATCMA requires any occasion where ATC takes action to prevent a GNE to be logged. Such "Interventions to Prevent GNEs" are far more frequent than actual GNEs and crews often don't realise that the very act of stating an intention to route to a position not specified in the Oceanic Clearance will result in reporting action being taken.
rab-k is offline  
Old 12th Sep 2009, 21:32
  #5 (permalink)  
 
Join Date: Jan 2008
Location: Dark side of the moon
Posts: 93
Likes: 0
Received 0 Likes on 0 Posts
rab-k

Oceanic airspace is patently more anally retentive nowadays than it was when I worked it if every error has reporting action taken on it. H/F comms are diabolical, the pilot reports his current position, his estimate for the next position and then the subsequent position after that, the last one probably being the 'error'. Even if the pilot gives his next position as incorrect who is to say the pilot did that? Because H/F is so crap, perhaps Ballygirreen misheard it therefore it is not the pilots fault. Aircraft GPS systems are highly accurate, yearly, how many real GNE's occur, bearing in mind the volume of modern aircraft that fly trans-Atlantic? probably one or two.
WhatMeanPullUp is offline  
Old 13th Sep 2009, 01:38
  #6 (permalink)  
 
Join Date: Feb 2006
Location: -
Posts: 508
Likes: 0
Received 0 Likes on 0 Posts
WhatMeanPullUp

You "worked" Oceanic? Then surely you would know that...

  1. Confirmation is sought by ATC of any reported discrepancy between the cleared route and intended route prior to any corrective and subsequent reporting action being taken, precisely so as to discount any mis-hear due to poor HF. The exception to this being where the discrepancy is immediate, e.g. the crew reports at the Oceanic Entry Point stating they're routing to 55N020W when the cleared route is via 56N020W. In such circumstances, the delays in HF comms require that the cleared route be confirmed in the first instance, rather than confirmation of the crew's intentions; which will be done subsequent to the confirmation of route.
  2. ADS Waypoint Event Contracts are commonplace in the NAT region and are needless to say not subject to the shortcomings of HF; the route held in the FMS being downlinked directly to ATC ensuring that any discrepancy is actual rather than perceived.
  3. The most common reason for such occurrences is for the cleared route to differ from the flight planned route and for that difference, for whatever reason, not to be reflected in the FMS. GNEs are seldom as a result of failures on the part of the INS but rather what is programmed into the FMS. These account for the vast majority of GNEs and Interventions to Prevent GNEs.
  4. The reason for such "anal" behavior as you put it is for procedures and training to be improved to the point that no GNEs occur. This is not only on the part of operators, who without the reporting procedure may well be oblivious to such events, but also ATC providers. In our case, we have altered the phraseology used for the issue of clearances whose route differs from that of the flight plan, and have also incorporate such indicators of reroutes in our automated clearance delivery system, in order to assist crews in ensuring that they fly the cleared route as opposed to the flight plan. The only means of identifying the need for such changes in RTF and datalink comms was via a reporting procedure overseen by the NAT CMA which highlighted the true extent of the problem.
Am I to assume that for an ATC provider or airline operator to turn a blind-eye to such things would be acceptable to you?
rab-k is offline  
Old 13th Sep 2009, 18:28
  #7 (permalink)  
 
Join Date: Jan 2008
Location: Dark side of the moon
Posts: 93
Likes: 0
Received 0 Likes on 0 Posts
No, not acceptable but I am not anal enough to go into the depths that you have done to reply to a basic response.

Last edited by WhatMeanPullUp; 13th Sep 2009 at 18:30. Reason: wrong word
WhatMeanPullUp is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Thread Tools
Search this Thread

Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.