srcooke

The OFP would need to be formatted for the FAA type route, the only section that could be changed is the ATC ROUTE entry, the FPL would remain ICAO. You have a realworld OFP using the FAA entries ? Those I have seen are using ICAO format. I can modify a PFPX OFP if that entry is what you require.

Flightplan speeds can entered as: 'N' = Knots 'M' = Mach 'K' = Kilometers/hour The flightplan is informing ATC of your intended speed and should correspond to the Cost Index / Speed used by the crew.

Optimization method used to find the route track: MCT = Minimum Cost MFT = Minimum Fuel MTT = Minimum Time Definition HERE Correct, ST = Scheduled Time and ET = Estimated Time Estimated, can be used for a change to the scheduled departure, arrival takes into account head/tail wind etc. PLN time takes into account the planning adjustments compared to that scheduled, again wind etc will influence this. Wind component, H or + indicating headwind, T or - indicating tailwind. Minimum Safe Altitude LEG = planned time taken between waypoints ACC = Accumulated time ETO = Enroute Time Over ATO = Actual Total Your bold entries in the ATC flightplan, RBS/N0501F370, indicate a speed and/or altitude change at the given waypoint

I don't believe you can change the pressure configuration within Topcat. Using the main program you can see hPa as the main function with the inHg equivalent displayed: If you call up the results table you'll also see the hPa figure in use which is relayed back to PFPX: TAKE-OFF KORD/ORD RWY 10L TORA 3962M G-ZESA BOEING 747-400 RB211-524H CHICAGO OHARE INTL TEMP +2C QNH 1018 WIND 110/09 (08KT HW) ------------------ CONDITIONS ------------------- TOW 216523 KG FLAPS 10 THRUST TO2 RWY DRY AIR COND ON ANTI ICE ON OR OFF ------------------ FULL THRUST ------------------- +2C 271020 OBS(B) 114-121 121 141 2221M 1.57 ---------------- REDUCED THRUST ----------------- +69C 234034 OBS(B) 127-129 129 139 1054M 1.37 +70C 231976 CLIMB 129 129 139 980M 1.37 +71C 227989 CLIMB 129 129 139 902M 1.37 +72C 224001 CLIMB 129 129 139 823M 1.37 //+73C 220102 CLIMB 129 129 139 740M 1.37 *************************************************** DO NOT EXCEED MAX STRUCT TAKE-OFF WGHT OF 396894 KG *************************************************** ------------------ ENGINE OUT ------------------- "AT 2200' LT TO HP 'OBK' 113.0" (092 INBD RT) ---------------------- END -----------------------

And which AIRAC provider ?

Cannot be done to the best of my knowledge. Which airport ? Which AIRAC provider are you using ?

You cannot. What are you trying to achieve ?

Assuming that you are using the Navigraph FMS Data Manager set the path for PFPX to C:\Users\Public\Documents\PFPX Data in the Addon Mappings

Sent you a PM Charles.

Hello Jianmin, Unfortunately my lack of language skills prevents me from reading through it but well done for your efforts. You may wish to post the file to the PFPX download section of the forum, it will prevent it been lost in forum posts over time.

Correct

It is likely you are using the 744ER entry, the profile publisher has set the AircraftTypeShort description in the profile to 747-400 rather than including ER. You are using an old version of PFPX ? Currently v2.03

click the INFO button of your GALAXY registration screen and post a snapshot of the details

Open your aircraft registration in the aircraft editor, click the INFO button and post a snapshot of that screen

A snapshot of the Airport Data Charles rather than a flight entry, accessed via the Company Data icon or context menu via right click the airport on the map: Is your system clock displaying the correct offset to GMT ? As Brazil has suspended daylight saving time which would ordinarily be place at this time perhaps the issue is related. I have set both a WIN7 and WIN10 system clocks to that of Brazil and see the correct offset in use within PFPX.

Which aircraft performance file is in use Torben, can be verified from the aircraft editor 'info' button:

I see the same issue Torben, the climb/descents appear in the OFP also. The problem does not appear to be related to a specific performance file as I tested with alternatives and had the same outcome.

Hello David, Activation does not appear to be an issue here, if it were then PFPX would instantly close to the activation screen. The print function only becomes available after flightplan release. Please tick the 'Airport NOTAM' checkbox on the ribbon bar and I believe your flights will release.

Have a look at your Configuration/General tab, do you have an active subscription ?

You only have to adjust weights and capacities as every carrier will have different figures. However I have uploaded a full set of templates only to the forum download section

Performance files: AirlinerPerformance

Still not quite right Serge as it captures waypoints after oceanic exit. This is closer: <&OceanicSection_Begin>Oceanic Route: <&NavLog_Begin><&OceanicFix_Begin><&FixIdent[0]> <&OceanicFix_End><&NavLog_End><&OceanicSection_End>

Try: <&OceanicSection_Begin>Oceanic Route: <&NavLog_Begin><&OceanicFix_Begin><&NextFixIdent><&OceanicFix_End><&NavLog_End><&OceanicSection_End> returning: OCEANIC ROUTE: PIKIL 5620N 5630N 5540N 5350N RIKAL TOPPS ENE

Hello Colin, It is not possible to install every restriction to PFPX, some restrictions can vary hour-to-hour. Have you applied Davids RAD Restrictions and Directs files ? Dispatchers still exist for a reason