Jump to content

Discrepancies between FL on ATC route and OFP waypoint to waypoint FL


Recommended Posts

Hi, All.

 

So, ATC route goes as:
"ATC ROUTE: N0440F360/N0440F380 DIPI6A ARBOS UL47 EPL UM624 JARNY/N0441F360
           UM624 ROUSY/N0441F370 M624 DIK/N0442F380 M624 BUB L608
           INLOD/N0465F180 L608 SUMUM Y6 IDESI IDES1A"

 

Just disregard the up and down typical of an automated generated route in European airspace.

 

However, if I were to follow this ATC route, I would expect to initially climb to FL360. However, the OFP as below shows initial of FL380 and then, somehow after the TOC, descend to 360, crossing NANCY at 360. 

 

The ATC route would indicate that ONLY AFTER JARNY, I would start descent to 360.

 

 

image.thumb.png.2600c8736e33a7eb059804682160c1dc.png

 

Same for ROUSY, ATC Route: "ROUSY/N0441F370" .. ATC could expect me to ask to CLB to 370 after ROUSY but the OFP is showing a continuous CLB to 380.

 

Not to speak of INLOD, where the ATC shows "INLOD/N0465F180", which means I would request to DES to FL180 after INLOD. Instead, the OFP shows I had started DES way to FL180 as early as 6 miles past DENUT (Boundary Waypoint), meaning I would have started DES 46 miles before INLOD.  

 

 

image.thumb.png.e409393222b86e63280a4698f72963d7.png

Link to post
Share on other sites

Hi, Thanks for the reply.

 

What kind of issues could there be re FL?

 

Issues like the following?

 

I see there is a short DES in CRZ to cross DIK but the predecessor route as well as the successor would have allowed for the same CRZ level to be maintained. Wonder what the reason is if the winds do not seem to be that much of a significant factor here.

 

image.thumb.png.cda032fc1e487cc0665ebddb46bf698b.png

Link to post
Share on other sites

Issues such as you have posted with the flight levels in ATC submission ( N0440F360/N0440F380 ) and missing flight level changes in the vertical profile map.

 

For the EGSS-LSGG route post your complete OFP

Link to post
Share on other sites

Alright. I think I will revert to 2.03 if that is the preferred approach.

 

 

For the LSGG to EGSS, I am attaching the first page and the relevant page where the DIK station is shown (where that small FL change occur just to be brought back to the INI CRZ LVL

image.thumb.png.6604a9108c76b09ddcad7368c91f87b1.png

 

image.thumb.png.8fd9a257aec90717a19948ab448c0c0c.png

Link to post
Share on other sites

The same glitch occurs at ROUSY using v2.03.

 

The cruise table of the airway changes with M624, would need to look closer at just what the levels are.

Link to post
Share on other sites

Thanks for your time. I've seen your contribution around the forum and I find it really nice from you to help.

 

Anything I can do to provide further input? lost me at the cruise table with the airway changes needs revision.

 

Can I slip one more question? After reverting to v2.03 the local times for the UK are now +2h ahead of UTC where it should be +1h vs UTC. I vaguely remember this issue back in '17 when I started using the program. Any help would be much appreciated.

Link to post
Share on other sites

I do recall some issues with time zones.

 

Here for EGSS mousing over the airport on the map shows UTC +1

 

capture_001_16052021_150807.thumb.jpg.18ff2e609a3ffb76160fec828bff6d7b.jpg

 

Timezone.dat file attached is from the PFPX Data folder bit I doubt it is different to your own.

Timezones.dat

Link to post
Share on other sites

My bad. I mistakenly took LSGG for EGSS. LSGG is actually +2 UTC. Thanks for clarifying.

 

Going back to the cruise table awy change... anything I can do here or it is down to the developer? 

42 minutes ago, srcooke said:

The same glitch occurs at ROUSY using v2.03.

 

The cruise table of the airway changes with M624, would need to look closer at just what the levels are.

 

 

Link to post
Share on other sites

I really don't understand why this route proves to be that tricky.

 

I have done another attempt LSGG-EGSS with v2.3 either at OPT FL or MAX FL and despite asking for High Level awys, PFPX will insist with this routing:

 

DIPI6A DJL A6 SOMDA T11 VATRI B3 RINTI L10 DVR L6 DET DET2A

 

Forcing it to stay around FL180

 

***edit: sorted now, just had to clear the route and request it again. 

Link to post
Share on other sites

To me it looks like the SO assigned table for the airway is incorrect for M624 ROUSY-DIK, should be even FL by the AIP yet the SO table assigns odd.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...