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

Position Report along FIR Boundaries

Wikiposts
Search
Questions If you are a professional pilot or your work involves professional aviation please use this forum for questions. Enthusiasts, please use the 'Spectators Balcony' forum.

Position Report along FIR Boundaries

Thread Tools
 
Search this Thread
 
Old 11th Mar 2015, 01:50
  #1 (permalink)  
Thread Starter
 
Join Date: Mar 2015
Location: dc
Posts: 1
Likes: 0
Received 0 Likes on 0 Posts
Position Report along FIR Boundaries

I’m rather new to NAT operations but I’m still trying to tie up some what if scenarios. If my NAT clearance was 45/20 45/25 45/30 etc. , from who would I get my Oceanic clearance from? Santa Maria or Shanwick. I’ve been reading the NAT DOC7 and all it says is:

“6.3.11 Position reports for aircraft operating on tracks through successive points on the mutual boundary of two OCAs (e.g. when routing along the 45ºN parallel), should be made to both relevant OACs. (In practice this only requires an addition to the address. (e.g. “Shanwick copy Santa Maria”.)

How can I make two position reports with one CPDLC without having to keep logging on and back off, switching between the two?
Rnmd is offline  
Old 14th Mar 2015, 11:49
  #2 (permalink)  
 
Join Date: Apr 2012
Location: In Space
Posts: 683
Likes: 0
Received 0 Likes on 0 Posts
Shanwick will tell you when to make a position to contact the next FIR.

For example.

T16 routing to TFS at position Gonan contact Santa Maria on HF XXXX,XXXX
B737900er 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.