Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Suspect Incorrect Flight Level Clearance given during SID

Featured Replies

Hi,

I believe that P2A may not be handling flight levels clearances correctly during CPT6C and CPT3B SIDs for EGGW

Symptoms:

 Pilot2ATC is clearing me to FL120 at RODNI, then as I transit pass RODNI towards CPT,  it then informs me to expedite a descent back to 5000'! All very confusing, especially when you try to conform to the ATC request as when I then descend I get a expedite climb to FL120! Help!

The latest AIRAC 1807 iaw http://www.ead.eurocontrol.int/eadbasic/pamslight-B78C82181D2810677AC5CBEBE1E2D570/7FE5QZZF3FXUS/EN/Charts/AD/AIRAC/EG_AD_2_EGGW_6-4_en_2018-04-26.pdf does indeed show RODNI as having no Altitude Restriction, but it is part of a SID where the highest altitude is 5000' . So P2A should either clear me to a higher altiude and let me climb OR keep me at 5000' until I reach CPT where I can begin the climb out with no restrictions.

Have contacted the Navigraph boys (thinking that this may be a AIRAC error but they inform me that the AIRAC update 1807 Rev 1 is correctly reflecting the AIP procedure (at EG_AD_2_EGGW_6-4_en_2018-04-26.pdf). They suggest that it is a P2A bug. Any thoughts?
 

Their SID EGGW.txt shows following:
SID,CPT3B,26,2
FA,RW26,51.87703889,-0.35451944,0,BNN,39.8,11.6,256,2,1026,0,0,0,0,0,0
CF,BNN07,51.82472778,-0.44968333,0,BNN,33.3,7.0,213,3.00,0,0,0,0,0,0,0,1
CF,X344,51.79258889,-0.58364722,0,BNN,343.7,4.2,257,5.50,2,3000,0,0,0,0,0,0
TF,HEN,51.75974167,-0.79029167,0, ,0.0,0.0,0,0.00,1,5000,0,0,0,0,0,0
TF,RODNI,51.71569444,-0.86161944,0, ,0.0,0.0,0,0.00,0,0,0,0,0,0,0,0
TF,CPT,51.49157222,-1.21969167,0, ,0.0,0.0,0,0.00,1,5000,0,0,0,0,0,0

SID,CPT6C,08,2
FA,RW08,51.87201944,-0.38354722,0,BPK,306.8,12.6,76,2,1026,0,0,0,0,0,0
DF,ILTN3,51.89071111,-0.27691389,0, ,0.0,0.0,0,0,0,0,0,0,0,1
CF,X039,51.81372500,-0.44289444,2,BNN,38.2,6.6,258,8.00,1,4000,0,0,0,0,0,0
TF,X009,51.79945000,-0.53296389,0, ,0.0,0.0,0,0.00,1,5000,0,0,0,0,0,0
TF,HEN,51.75974167,-0.79029167,0, ,0.0,0.0,0,0.00,1,5000,0,0,0,0,0,0
TF,RODNI,51.71569444,-0.86161944,0, ,0.0,0.0,0,0.00,0,0,0,0,0,0,0,0
TF,CPT,51.49157222,-1.21969167,0, ,0.0,0.0,0,0.00,1,5000,0,0,0,0,0,0

Could you investigate please?

Many thanks
Paul Donohoe

 

My System:
WIN10
X-Plane 11.2r
Pilot2ATC
AIRAC 1807
Saitek Radio Panel, X-55 Pr-Flight Throttle and Joystick

  • Commercial Member

In this case, I assume your initial clearance was to "Climb via the CPT6C departure with the CPT transition.  Climb and maintain FL120..." or something like that.

This means that you are cleared to FL120, BUT following all the restrictions in the SID.  In this particular case, the highest altitude allowed in the SID is 5000 ft, so you must maintain 5000ft until you reach CPT and then immediately resume your climb to FL120.  The planned altitudes in the P2A Flight plan will indicate maintaining 5000 ft until CPT.

Dave

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.