Jump to content

Problems - strange altitudes, alternate data and CTDs


Recommended Posts

Hi all,

 

I am wondering if anyone is experiencing the following problems:

 

1) Strange altitudes (see picture attached).

For the stock Boeing 747-400 RB211-524GH2 aircraft on a SIN-LHR flight, I get bizarre altitudes planned:

FL300/320/300/280/320/360/300/180.

No optimisation is turned on, and even with "MIN FUEL" set, it doesn't seem to make any difference.

These altitudes are ocurring in airspace outside of Europe without a tone of restrictions.

Within Europe, the flight plan validates with an altitude of FL380 set, so I do not understand what is going on here.

 

2) Alterate data (see picture attached).

I usually have alternates set to "None" but the OFP calls for a list of the fuel required anyway.

PFPX does this, but stops doing it once it thinks the alterate is too far away.  This did not happen anywhere near as often in the previous 1.28.8 version.

For example, EDDL is cut off from the list on this particular plan.  On a SYD-SIN flight, it will not display WBGG or WIII (only the first two WMKJ and WMKK).

 

3) Regular CTDs.  It doesn't seem to have any rhyme or reason, but I have frequent CTDs (probalby 2-3 an hour using the program).  This can be very frustrating - anyone else experiencing these?

Faulting application name: PFPX.exe, version: 2.0.3.0, time stamp: 0x5c0e3189
Faulting module name: mfc140.dll, version: 14.16.27012.6, time stamp: 0x5bc12bb7
Exception code: 0xc0000005
Fault offset: 0x0011c173
Faulting process ID: 0xfd8
Faulting application start time: 0x01d4a00206788fc7
Faulting application path: D:\Programs\Professional Flight Planner X\PFPX.exe
Faulting module path: C:\Windows\SYSTEM32\mfc140.dll
Report ID: 3ddb99bb-770c-4f68-a51b-332c67ccb43d
Faulting package full name:
Faulting package-relative application ID:

 

Thanks for any advice,

Cheers,

Rudy

 

Please login to display this image.

Please login to display this image.

Link to comment
Share on other sites

Hello chaps, thanks for your replies!

 

1) Here is the routing of the flight (also pretty much the routing of the actual flight for the last few days):

AROSO Y339 GEMAS B466 GUNIP N571 AGELA B466 BBB V1 KARKU P518 PG L124 KEBUD UL124 SODOK T216 DAR UL125 RADAL L125 BUDED UL333 DASIS UL746 ODERO L746 NEPOT L851 DEGET ABETI RENKA INBED BOMBI ADKUV UL610 BATTY UL608 COA UL179 SASKI UL608 INLOD L608 LOGAN

 

The routing validates through IFPS with a departure time of 15:55Z and with my modified altitudes.

 

No warnings on altitude with this route (see attached picture #1) apart from overflying some restricted areas (which PFPX warns of on virtually any flight now).

 

Turbulence looks fine, only a bit of green (see attached picture #1).  No matter what day or weather, it still gives me a very strange vertical profile (SIN/280 IGOGU/300 BIKEN/320 RADAL/280 BUDED/340 BAMLA/360 DENUT/300 INLOD/180)/

 

This has defintely started happenning since v2 - never had this problem with 1.28.8.

 

2) I tried your suggestion of looking in the PFPX template for the previous YSSY-WSSS flight, Steven, unfortunately that did not work (see attached picture #2 & #3).  All my alternates for the SIN-LHR flight were close enough to be accepted by PFPX.  Also, even if I planned the most distant one on the YSSY-WSSS flight, the extra fuel would not have put the aircraft over MLW or exceeded RTOW or anything like that.

 

A copy of my modified plan is attached at the bottom (with manual altitudes).

 

If you guys find anything thats works, let me know, otherwise I can submit a support ticket to let the developers know (along with the ActiveSky historical WX retrieval problem) :)

Cheers,
Rudy

 

Please login to display this image.

 

Please login to display this image.

 

Please login to display this image.

 

18-12-30_QFA0001_SIN-LHR.pdf

Link to comment
Share on other sites

seems strange but i checked real flightplans here is what i got for that route a while ago but still:

 

N0502F300 AROSO Y339 GEMAS B466 SUKAT A457 VPG Y337 GIVAL/M083F300 P628 KAGUL/M083F320 P628 PUKES/M083F340 P628 VIKIT/N0500F340 P628 ASLUM/N0499F340 P628 PAROD/N0499F340 P628 PAMTU G792 GIRUN/K0921F340 B375 NENIS/K0916F360 B375 BODKA/N0494F360 M747 LUSAL M11 EDATA/K0914F360 M11 REBLO/N0493F360 UM11 TBN UW71 CRM UM688 EKSUK UL852 NEGEM Q8 DOLAP/N0463F320 UL615 NAKIT UN606 BABAG Q333 RESIA UP131 ARGAX UL613 RLP/N0445F320 UL613 DIDOR UT10 ALESO/1243
Remarks
PBN/A1B1D1L1O1S2 NAV/RNVD1E2A1 RNP2 DOF/170807 REG/GSTBJ EET/WMFC0007 VOMF0139 VECF0228 VABF0352 VIDF0416 OPKR0454 OPLR0521 OAKX0532 OIIX0619 UTAA0655 UTAK0700 UBBA0725 UDDD0759 LTAA0810 LTBB0925 LBSR0932 LYBA1013 LQSB1032 LDZO1056 LIMM1112 LSAS1132 LFFF1150 EGTT1232 SEL/EQFH CODE/406A35 OPR/BAW RALT/VAAH RVR/075 RMK/LAHSO NOT AUTHORISED TCAS

 

 

N0506F300 AROSO Y339 GEMAS B466 SUKAT A457 VPG/M083F300 B579 PUT/N0507F300 L515 OBMOG/M083F320 M770 MEPEL/M083F300 M770 BUBKO/N0509F300 M770 KAKID M875 BUTOP/M083F320 A589 ASARI A466 SAMAR/N0503F320 L509 HANGU/N0499F340 L509 LAJAK/N0498F340 L509 TAPIS M875 AMDAR/K0901F340 A466 TMD A66 ODIVA B824 UDATO/K0882F360 B824 URL G3 FV R11 UK B102 ASKIL/K0893F360 L735 BADUS/N0479F360 DCT VABER L735 SUW T727 ELKAR DCT GRUDA L29 ALUKA DCT HLZ DCT GORLO UL980 LOGAN/1308
Remarks
PBN/A1B1C1D1L1O1S2 NAV/RNP2 DAT/1FANS DOF/160525 REG/9VSWK EET/WMFC0007 VTBB0058 VYYF0128 VECF0225 VIDF0417 OPLR0518 OAKX0556 UTSD0631 UTTR0705 UAII0717 UATT0747 UWWW0858 UUWV0937 UMMV1029 EYVL1053 EPWW1102 EDUU1145 EDVV1159 EHAA1218 EGTT1241 SEL/FPKQ CODE/76CEEB OPR/SIA RMK/UKRAINIAN AIRSPACE AVOIDANCE ACASII EQUIPPED TCAS

 

 

N0502F340 AROSO Y339 GEMAS B466 SUKAT A457 VPG/M084F340 B579 PUT/N0501F340 L759 ONATI/N0500F360 L759 AGG L760 DPN/M084F360 A589 ASARI A466 SAMAR/N0500F360 L509 LAJAK/N0501F360 L509 TAPIS M875 AMDAR/K0926F380 A466 TMD A66 ODIVA B824 GERLI/K0925F400 B824 URL G3 FV R11 UK/K0894F320 R11 KOLED/K0912F400 R11 OPOKA/N0494F400 M869 LEP M864 KOLJA M611 CDA Z701 GOBOT UZ701 GORLO UL980 LOGAN/1252
Remarks

PBN/A1B1C1D1O1S2 NAV/RNVD1E2A1 SUR/TCAS DOF/150719 REG/GXLEG EET/WMFC0007 VTBB0058 VYYF0132 VOMF0151 VYYF0212 VECF0215 VABF0347 VIDF0407 OPLR0507 OAKX0540 UTSD0611 UTTR0643 UAII0654 UATT0721 UWWW0827 UUWV0909 ULLL1010 EVRR1025 EYVL1106 ESAA1109 EKDK1134 EDVV1143 EHAA1205 EGTT1234 SEL/BPCD CODE/406B20 OPR/BAW RALT/WSSS VIDP UTTT UUDD EGLL RVR/075 RMK/LAHSO NOT AUTHORISED TCAS

 

so there is a pattern about the yoyo ...

Link to comment
Share on other sites

Hello Rudy,

 

Your flightplan route utilizes L125 ( DAR UL125 RADAL L125 BUDED ) which has a narrow FL range available FL250 - FL280, replacing that with UL125 results in the attached.

 

Still no issue with EDDL as an alternate.

 

Planned using AS historic weather

744AS WSSS-EGLL (31-Dec-2018) #1.pdf

Link to comment
Share on other sites

Damn, must have made a typo doing that route, as was checking the airway info.  Thanks, Steven.  That would explain that.

 

However, I still notice that for some reason it's given you a step straight from 320 to 360 which would seem a bit unusual?

 

Don't want to be a pain, but when you're next planning a flight - could you try an alternate perhaps 500 miles away or so for info purposes, and see if it still gives you info?  

 

Regarding to ActiveSky weather - it will work fine for MOST flights.  However, oceanic flights can get a bit funny.  I planned a Sydney-Santiago flight a while back, and the winds were way out.  You can see the problem by using ActiveSky weather in PFPX, and comparing the oceanic waypoint winds in PFPX to the winds that ActiveSky gives when you import the flight plan into the ActiveSky program.  In this case it was completely different and I ended up having a headwind of 20 when I should have had a tailwind of 50.  There is another thread a while back about how Hifi changed the way programs need to look for the wind info, and unless PFPX has been updated to do that in the last version, I don't think it does that yet.  I did speak to Judith a while ago about it.  For now, I try and save PFPX weather once daily so I have a historical database of PFPX weather - which is a bit of a pain.

 

While we're at it - do you know what/how to use the terrain clearance section in PFPX?  I am not sure what it is?

 

Again, thanks Steven and Philippe.

 

 

Link to comment
Share on other sites

here is your alternate in the 500nm range ...

 

ALTERNATE PLANNING
--------------------------------------------------------------------------------
ALTN/RWY DIST ALT/FL MSA  COMP  TIME   FUEL   DIFF ROUTE
LFBO/32R  538 FL330  045 TL026 01:16  11246      - MID4F MID UL151 SITET UN859
                                                   NARAK NARA6L
EGCC/23R  140 FL180  036 HD035 00:32   5215  -6031 UMLA1F UMLAT T418 WELIN T420
                                                   TNT DAYN2A

 

Link to comment
Share on other sites

Thanks, David, I'll try that!

 

Hmmm yeah your altitudes appear pretty spot-on there, Stephen in the latest plan you posted.  You didn't do any manual edit?  And yes, distant alternate showing too.

 

Perhaps I'll try making a new aircraft from scratch to check that isn't somehow causing it.

 

Thanks again guys :)

Link to comment
Share on other sites

The aircraft profile is as supplied by AirlinerPerformance for the 744RR, only adjustments would be to match the PMDG capacities/weights.

 

No edits from copy/paste of your plan except the L125 correction.

Link to comment
Share on other sites

Rudy,

 

i think  the differences between the default rr profile and John one is the extra perfs. may worth to try it to see the differences not on the fuel burn but more on the perf on his own. more detail give a better result but i do nor know if pmdg actual version is refine as John profile ...

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use