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

compulsory reporting points: what points do you name for EST and NEXT?

Wikiposts
Search
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.

compulsory reporting points: what points do you name for EST and NEXT?

Thread Tools
 
Search this Thread
 
Old 21st Feb 2012, 18:09
  #1 (permalink)  
Thread Starter
 
Join Date: Oct 2008
Location: Wisconsin
Age: 52
Posts: 2
Likes: 0
Received 0 Likes on 0 Posts
compulsory reporting points: what points do you name for EST and NEXT?

In a position report you give three waypoint names.
In a string of five waypoints named A, B, C, D and E, with only A, C, and E being compulsory reporting points:
in your position report, would you mention B and D at all?

AIM 5-3-2.d leaves me with questions.

Jeppesen (INTRODUCTION, pp. 55, enroute chart legend) shows waypoints as either "compulsory reporting points" or "non-compulsory reporting points."

Is the answer different for different regions/FIRs?

PLEASE cite your answer.
VetsJetsnGuns is offline  
Old 21st Feb 2012, 18:19
  #2 (permalink)  
 
Join Date: Jan 2008
Location: The foot of Mt. Belzoni.
Posts: 2,001
Likes: 0
Received 0 Likes on 0 Posts
VetsJets,
just curious, but when I did the U.K Area Procedural control course in 1986, a/c had to give 2 positions;- where they were, and the estimate for the next compulsory reporting point.
What is the third one? Is it (..........), next?
On request reporting points were, i believe, ignored, unless ATC instructed otherwise.
ZOOKER is offline  
Old 21st Feb 2012, 18:20
  #3 (permalink)  
Thread Starter
 
Join Date: Oct 2008
Location: Wisconsin
Age: 52
Posts: 2
Likes: 0
Received 0 Likes on 0 Posts
yes, the 3rd one is the "next"
VetsJetsnGuns is offline  
Old 22nd Feb 2012, 13:00
  #4 (permalink)  
 
Join Date: Oct 2000
Location: Scotland
Posts: 64
Likes: 0
Received 0 Likes on 0 Posts
I agree with Zooker on this.

If your route has compulsory points then you report where you are then the estimate for the next compulsory point. The estimate or a report at a non-compulsory point would only have to be given if requested by ATC.

It would only be requested if the ATCO wanted an intermediate point to get a pass to climb or descend, to prove a separation or possibly if the time elapsed between the compulsory points was greater than that allowed for reporting action for operation normal checks.
BuzzLightyear is offline  
Old 22nd Feb 2012, 16:07
  #5 (permalink)  
 
Join Date: Sep 2001
Location: In the sun
Posts: 129
Likes: 0
Received 0 Likes on 0 Posts
Are you talking about domestic reports or oceanic? If oceanic then you will have three positions in the report i.e. Present position, estimate and coords for the next position followed by the next pis after that. All positions will have been included in your oceanic clearance and used. Any intermediate positions not included in the clesrance should not be given unless specifically requested. In oceanic terms, all positions in a clearance are compulsory positions
WetFeet is offline  
Old 24th Feb 2012, 10:19
  #6 (permalink)  
 
Join Date: Aug 2010
Location: South Africa
Posts: 1
Likes: 0
Received 0 Likes on 0 Posts
RE:

An example of an acft flying through oceanic airspace with no ADS/CPDLC:

"BAW43, crossed position 'AAA' 1200 F370, estimate position 'CCC' 1255, 'DDD' next"

In this instance, ATC will not be able to verify the flight status of the acft for almost an hour, but our requirement is to ascertain ops normal every 30 min. If there is an intermediate waypoint that will reduce this gap that is not a compulsory reporting point ( i.e FIR boundary etc.), atc may reply:

"BAW43, Copy estimates, report 'BBB' FL370".
boBegnopS 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



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.