• Content count

  • Joined

  • Last visited

  • Days Won


jpgmultimodal last won the day on November 24 2014

jpgmultimodal had the most liked content!

Community Reputation

26 Excellent

About jpgmultimodal

  • Rank
  • Birthday 04/06/47

Recent Profile Visitors

1966 profile views

    Hello Amit240, I think you misunderstood my posts. Jeppesen is supplying Navigraph and other providers with raw datas for FMS, Flight Planners, etc and it is then coded to suit each individual software. The datas used are the same than RW and It is why I am wondering, as the PFPX and FMS data supplier being exactly the same, how SID /STAR with PFPX do show shorter distances than the FMS (or the charts) and especially with ARC DME procedures. Quite some years ago (RW) on the OFP we were not entering the SID / STAR but instead the longest distances of the SID / STAR (or some extra time) to make sure the fuel calculations were right and my question was: Should we do the same with PFPX, instead of entering SID / STAR, should we enter OUT / IN to have the exact distance to get accurate fuel results. Regards, JP

    I am not sure it is a NAVIGRAPH fault as the FMS is correct and it is from the same origin (I think JEPPESEN).
  3. Hello, Is there a point to enter the SID / STAR on the OFP? For some airports like EMGC (STAR GEGMU1G) and other airports in the UK it would be advisable to do so due to to the lenght of the STAR (about 145 Nm) and also level constraints to get a precise fuel calculation. On most airports I would rather prefer to leave the SID / STAR blank and instead enter the CIRCUIT OUT / IN distance. Lets take LEAS SID Rwy 29 AMAK1F. If you enter that SID on the OFP you get an extra distance of 2.3 Nm compared to DCT AMAKA which is wrong. If you measure the real lenght of that SID with this 10 DME Arc for about 180° you'll find an extra distance of about 29 Nm compared to the DCT. In such a case I do not enter the SID but CIRCUIT OUT: 29. I do not feel there is a need to have few lines on the OFP showing AMAK1F which are no use anyway as when you follow a SID you do not look at the OFP. Another very important point is that if you enter the SID instead of the CIRCUIT OUT distance you'll be short of petrol in your calculation. However when you enter the SID in the FMS everything is correct so it is not a NAVIGRAPH fault. Is it a logic in PFPX not to show the precise SID / STAR distances, I do not know. Any ideas? Regards, JP
  4. Online Weather

    Hello, Just checking and it is working now and updated. JP
  5. Weather charts along FL like wind?

    Hello Michael, Do you mean that type of chart ? Regards, JP
  6. PFPX template commands

    You have another option if you do not like the ".." between each direct. Copy and paste the OFP in Word or another program, edit whatever you like and print. As I use listing paper which is not taken into account within PFPX it is that I do and it is as quick as printing through PFPX. Anyway it is a possibility. JP
  7. PFPX template commands

    Yes, I understand and the FMS Route that I enclosed was part of an OFP and not an ICAO FPL. And there you can replace the "DCT" by ".." as I do. if I remove the SID and live only the first waypoint of the route it will not include in the calculation the SID and only the direct route from the RWY to the WAYPOINT You are correct and it is why you have to add an extra distance in the CIRCUIT OUT. The first WP of the route would be the direct distance from the airport to that WP. It is why you should add a distance that you would have been measured or calculated which would be the extra distance if you were flying the longest SID. You enter this extra distance in the CIRCUIT OUT and when you calculate your flight it'll take automatically that extra distance into account each time. You do the same for the STAR. You should take the longest SID to your first WP to have no surprise. I.e. if your first WP is to the West of the airport, you take the distance of the SID considering you are taking off to the East. JP
  8. PFPX template commands

    Hello Amit, There is a way not to include "DCT" (on the FMS routing) if you prefer. In Europe we have to show "DCT" on the FPL. (see enclosed). I never show the SID/STAR (except few airports with long and complicated SID/STAR) on my OFP but only the first and last WP and add a distance in circuit OUT/IN. To do that just calculate the longest SID/STAR and substract the DCT distance, it would give you the values to add içn circuit OUT/IN. In your case it should be around 10 Nm OUT to play safe. Regards, JP
  9. Wrong Passenger Weight Calculation

    It is a bug and we discussed it before and we were told it would be change with a next patch. JP
  10. PFPX missing airways

    Yes Stephen, you are perfectly right as in this part of the world there are some regions FIS. In fact if we follow this particular route the suffix "G" does not apply all the time to this airway. JP
  11. PFPX missing airways

    I found it on Jeppesen chart JP
  12. Hello, This route is valid: MAG L986 DLE Z88 VERED When you plan you have to use a route which has to be accepted by Eurocontrol. Most probably you would be given a DCT EMBOX or POVEL. Even that today the DCTs are not yet implemented in all Europe, practically you would be given DCTs in most countries. Regards, JP
  13. I never enter the SIDs or STARs in the OFPs. Just the last point of the SID and the first point of the STAR and I add extra distances IN and OUT. You never follow a SID or a STAR with the OFP but with the charts and instruments. JP
  14. FL change in flight plan

    Jeppesen does agree. Please note that Jeppesen is a RW provider and, if I am not mistaken, Navigraph takes its data from Jeppesen. As Stephen states the French AIP (SIA) does not show the change of airway. It is quite normal as each country shows only its airspace and does not care about their neighbours. It is wrong but it is the way. It is why there are private companies like Jeppesen or Lido that provides informations for all the world. JP
  15. FL change in flight plan

    Taken from Jeppesen 2017-04: Regards, JP