Jump to content

omendoza

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by omendoza

  1. 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. 

  2. 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.

     

     

  3. 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.

  4. 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

  5. First image taken from the Browser shows at least two or more SIGMETs (Isolated Embedded Cumulonimbus) over the UK and France

     

    image.thumb.png.732b128e95228da2f080f1dbb6f56cd7.png

     

    Now, second image shows the Flight Map where we see two SIGMETs that by a stretch could be considered a few of the above ones but for sure the dimensions nor the locations match.

     

    image.thumb.png.a4a7a6bd51fc242d4196d4da4dc71f4c.png

     

    Does this mean there is an issue reporting the SIGMETs above Europe or am I doing something wrong

     

     

     

     

×
×
  • Create New...