regnaD kciN 2 Posted July 11, 2017 Share Posted July 11, 2017 PFPX customer here, currently running v1.28 (just installed it, previously running v1.23). I find myself utterly in the dark as to how to get a FL in routes. I've looked at YouTube instructional videos, and it appears that, in the "Aircraft" section of the New Flight page, you should enter OPT in the "initial Altitude/FL" field. In those videos, when you compute the flight, you get a flight plan where the FL is indicated right up at the top, along with the distance, CI, and the like. However, when I do the same, I get something like this... Quote RLS 1 N939UW 10JUL KSFO/SFO KLAX/LAX ELEVATION 128 ATS C/S AAL1151 2100/2110 2216/2211 CALC 11JUL 0705 CTOT .... ATC ...../..... ..../..... DIST 337 GCD 294 SPEED CI 31 AVGE FD 337 LOAD ZFW LM TOM AVGE WC 0 EST 41425 173365 MAL 198000 255000 PLN 41425 173365 PLN 194142 202480 ACT ...... ...... ACT ...... ...... FLIGHT PLAN ROUTE N0390A170 WESLA3 PORTE T257 CAATE T259 SNS DCT AVE DCT EHF WAYVE1 -------------------------------------------------------------------------------- ATIS DEP -------------------------------------------------------------------------------- CLEARANCE -------------------------------------------------------------------------------- DEP: KSFO/SFO 28R AWY WAYPOINT MT ALT WND/VEL TAS REM FUEL REM / USED LEG ACC NAME TMP FREQ GS DIST POSITION ETO / ATO -------------------------------------------------------------------------------- KSFO/28R 13 29.1 / 0.3 SAN FRANCISCO IN 337 N3736.8 W12221.4 ...../..... WESLA3 WESLA 284*CLB 000/000 7 27.9 / 1.5 :03 00:03 331 N3739.8 W12228.8 ...../..... WESLA3 PORTE 165*CLB 000/000 10 27.3 / 2.2 :02 00:05 320 N3729.3 W12228.4 ...../..... *TOC 15217000 000/000 390 11 26.8 / 2.7 :02 00:07 -19 390 309 N3718.4 W12224.9 ...../..... T257 CHAWZ 15217000 000/000 390 12 26.5 / 3.0 :02 00:09 -19 390 297 N3706.8 W12221.1 ...../..... T257 CAATE 13217000 000/000 390 24 26.0 / 3.5 :04 00:13 -19 390 273 N3646.5 W12204.1 ...../..... T259 SNS 09317000 000/000 390 23 25.5 / 4.0 :04 00:17 SALINAS -19 117.30 390 249 N3639.8 W12136.1 ...../..... T259 *BDRY 11417000 000/000 389 90 23.6 / 5.9 :13 00:30 -KZLA -19 389 159 N3544.7 W12007.9 ...../..... DCT AVE 11517000 000/000 388 10 23.4 / 6.1 :02 00:32 AVENAL -19 117.10 388 149 N3538.8 W11958.7 ...../..... DCT EHF 09017000 000/000 388 44 22.4 / 7.0 :07 00:39 SHAFTER BAKERSFI -19 115.40 388 105 N3529.0 W11905.8 ...../..... WAYVE1 LOPES 13217000 000/000 387 33 21.7 / 7.7 :05 00:44 -19 387 72 N3501.9 W11842.0 ...../..... WAYVE1 PAIDD 15117000 000/000 387 12 21.5 / 8.0 :02 00:46 -19 387 60 N3450.5 W11838.0 ...../..... *TOD 15117000 000/000 387 3 21.4 / 8.0 :00 00:46 -19 387 57 N3447.6 W11836.9 ...../..... WAYVE1 JEFFY 151*DES 000/000 3 21.4 / 8.0 :01 00:47 54 N3444.8 W11836.0 ...../..... WAYVE1 LHS 151*DES 000/000 4 21.4 / 8.1 :00 00:47 LAKE HUGHES 108.40 50 N3440.9 W11834.6 ...../..... WAYVE1 WAYVE 142*DES 000/000 7 21.4 / 8.1 :02 00:49 42 N3434.3 W11830.7 ...../..... WAYVE1 SAUGS 142*DES 000/000 5 21.3 / 8.1 :01 00:50 37 N3429.7 W11828.0 ...../..... WAYVE1 KIMMO 142*DES 000/000 6 21.3 / 8.2 :01 00:51 32 N3424.6 W11825.0 ...../..... WAYVE1 UPDOC 142*DES 000/000 13 21.2 / 8.3 :03 00:54 18 N3412.5 W11818.1 ...../..... WAYVE1 KLAX/25R 181128 18 20.8 / 8.7 :07 01:01 LOS ANGELES INTL N3356.3 W11822.9 ...../..... ARR: KLAX/LAX 25R -------------------------------------------------------------------------------- ALTN/RWY DIST LVL WC TIME FUEL VIA KBUR/33 19 5000 0 00:10 1342 DCT KONT/26R 50 9000 0 00:16 2143 DCT -------------------------------------------------------------------------------- ...which, obviously, shows nothing at all at the top. I first thought that the number that first appears at the TOC entry (390) might be the flight level, even if it did slightly decrease until TOD, but, to test it out, I tried planning a second flight in the other direction, which should have given me an even-numbered flight level. Instead, the number it gave between TOC and TOD was 457, which is not only not appropriate for a westbound flight, but is also considerably above the aircraft's flight ceiling of FL420. So, now, I'm completely confused. I'd really prefer to use PFPX instead of SimBrief to generate my flightplans (especially since I already own it), but at least I can figure out the flight level from the latter. Can anyone help me figure out what I'm doing wrong with PFPX here? Link to comment Share on other sites More sharing options...
srcooke 422 Posted July 11, 2017 Share Posted July 11, 2017 8 minutes ago, regnaD kciN said: N0390A170 WESLA3 PORTE T257 CAATE T259 SNS DCT AVE DCT EHF WAYVE1 N0390A170 = Altitude 17000ft Above transition altitude 'FL' will be used in place of 'A' for Flight Level There may be changes in altitude enroute which will be indicated in the ATC route also Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted July 11, 2017 Deputy Sheriffs Share Posted July 11, 2017 Just switch the OFP format from EDS to PFPX Please login to display this image. Link to comment Share on other sites More sharing options...
regnaD kciN 2 Posted July 11, 2017 Author Share Posted July 11, 2017 Thanks to both of you! However, I must admit to a bit of surprise -- I've replanned the same routes running both ways with the same aircraft (757-200). Running KLAX-KSFO, I always get FL360; in the opposite direction, I get FL170. Is that normal? I've never seen such a difference in assigned altitude before. Link to comment Share on other sites More sharing options...
srcooke 422 Posted July 11, 2017 Share Posted July 11, 2017 Not enough enough information. Post the full ATC flightplan outputs for both directions. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.