Skyrock 4 Posted May 11, 2020 Share Posted May 11, 2020 Hello, as far as my understanding is, you have to maintain a constant Mach number when overflying the North Atlantic (like .85). I noticed however, that for some reason on random routings across the North Atlantic, PFPX only gives a fixed mach number for the first half and from 30W it resumes with what I believe Cost index speed (at least in the flight plan it gives a TAS at 30W instead of a Mach No.). It doesn't matter if it's eastbound or westbound but it always occurs at 30W. And as far as I remember, it only affects random routings. On NAT Tracks it seems to be a fixed mach for the whole NAT from the entry to the exit and at the exit it goes back to TAS (or rather the corresponding speed for a certain CI). Does anyone know if this is correct behavior? I don't remember older versions of PFPX doing this. Example routing for today: EDDF-KORD OBOK1D OBOKA Z28 DIBIR DCT RAVLO Y70 OTBED L60 PENIL M144 BAGSO DCT RESNO DCT 56N020W 57N030W 58N040W 58N050W DCT AVUTI N716A TEALS DCT VANSI N760A SSM WYNDE1 In my example it says RESNO/M084F360 and for 57N030W/N0486F360. Thanks! Link to comment Share on other sites More sharing options...
srcooke 422 Posted May 11, 2020 Share Posted May 11, 2020 Set the additional oceanic data ? : Please login to display this image. Also set a fixed altitude if desired. (FPL-GSTBB-IN -B77W/H-SDE2E3FGHIJ3J5M1RWXYZ/LB2D1 -EDDF1220 -N0488F320 OBOKA Z28 DIBIR DCT RAVLO Y70 SUPEL/N0465F220 Y70 OTBED L60 MAMUL/N0485F320 L60 PENIL M144 BAGSO DCT RESNO/M084F320 DCT 56N020W/M084F340 57N030W/N0482F340 58N040W 58N050W DCT AVUTI N716A TEALS/N0495F360 DCT VANSI N760A SSM WYNDE1 -KORD0817 KDPA -PBN/A1B1C1D1L1O1S2T1 NAV/RNVD1E2A1 DOF/200511 REG/GSTBB EET/EDUU0012 EDVV0015 EHAA0022 EGTT0042 EISN0123 EGGX0146 RESNO0205 56N020W0227 CZQX0308 58N040W0348 58N050W0425 CZUL0520 CZYZ0644 KZMP0719 KZAU0741 SEL/GJDR CODE/40621C RVR/200 RALT/CYYR BIKF EIKN RMK/NRP HAR TCAS ADSB -E/0933) Link to comment Share on other sites More sharing options...
Skyrock 4 Posted May 11, 2020 Author Share Posted May 11, 2020 I know I can set it to a fixed Mach myself. I'm just wondering why PFPX doesn't do this by itself or why it does switch back to a TAS exactly at 30W all the time? Maybe there is a reason behind it and PFPX is correct or it is just a bug. Link to comment Share on other sites More sharing options...
Mike F 0 Posted May 17, 2020 Share Posted May 17, 2020 The Gander Oceanic FIR is set at kts instead of Mach in PFPX data...Even if Stephen's Example above with .84 to AVUTI, it changes to kts at 30W... Link to comment Share on other sites More sharing options...
Skyrock 4 Posted May 18, 2020 Author Share Posted May 18, 2020 On 17.5.2020 at 13:10, Mike F sagte: The Gander Oceanic FIR is set at kts instead of Mach in PFPX data...Even if Stephen's Example above with .84 to AVUTI, it changes to kts at 30W... Where can you find this? Link to comment Share on other sites More sharing options...
Mike F 0 Posted May 22, 2020 Share Posted May 22, 2020 If you hover over the FIR's name, you'll see it. I solved this by copying over the FIR file from my old 1.28 installation into the new 2.03 installation folder, have not encountered problems so far. Link to comment Share on other sites More sharing options...
srcooke 422 Posted May 22, 2020 Share Posted May 22, 2020 Thanks for the pointer Mike, some of the entries in the FIR.dat did not match the Cruise Table. If you wish give the attached a try, backup the original first ! FIR.zip Link to comment Share on other sites More sharing options...
Kalshi95 1 Posted May 23, 2020 Share Posted May 23, 2020 20 hours ago, srcooke said: Thanks for the pointer Mike, some of the entries in the FIR.dat did not match the Cruise Table. If you wish give the attached a try, backup the original first ! FIR.zip 230.36 kB · 1 download Hello, Where can we replace the file ? Regards, Link to comment Share on other sites More sharing options...
srcooke 422 Posted May 23, 2020 Share Posted May 23, 2020 8 minutes ago, Kalshi95 said: Hello, Where can we replace the file ? Regards, Located in the main PFPX program folder ( maybe program files (x86) if that is where you installed ), NOT public documents\PFPX Data Link to comment Share on other sites More sharing options...
Kalshi95 1 Posted May 23, 2020 Share Posted May 23, 2020 Thanks srcooke, you make my PFPX better ! Link to comment Share on other sites More sharing options...
danimaestro444 0 Posted May 23, 2020 Share Posted May 23, 2020 On 22.5.2020 at 17:10, srcooke sagte: Thanks for the pointer Mike, some of the entries in the FIR.dat did not match the Cruise Table. If you wish give the attached a try, backup the original first ! FIR.zip 230 kB · 7 downloads Thank you for the fix! Very much appreciated I have another problem. If I plan a route via the NATs (e.g. today NAT A from PIKIL to JANJO) and select .84 and OPT ALT in the fixed speed/altitude segment from LIPGO to JANJO, PFPX still shows MACH until waypoint TAFFY. However in the detailed plan the revert back to Cost Index Speed is occuring overhead JANJO, which is correct. Also should the fixed mach segment already show up overhead LIPGO, because the North Atlantic Transition Area requires the Mach technique. In the detailed flight plan this is also correct. Is there a way to fix this? Thank you very much for your help (FPL-AUA1-IS -B744/H-SDE3FGHIJ3J5J6M1M2P2RWXYZ/LB1D1 -EGLL1800 -N0490F360 CPT UL9 KENET N14 MEDOG L18 LIPGO/M084F360 should be there DCT PIKIL/M084F360 NATA JANJO/N0483F380 should be there N558A TAFFY/N0483F380 DCT ENE PARCH3 -KJFK0652 KEWR -PBN/A1B1D1L1O1S2 NAV/RNVD1E2A1 RNP2 DAT/1FANSP2PDC SUR/RSP180 DOF/200523 REG/GCIVL EET/EISN0036 EGPX0102 EGGX0103 57N020W0157 CZQX0242 58N040W0320 56N050W0401 JANJO0434 CZUL0506 CZQM0536 TAFFY0541 KZBW0545 KZNY0645 SEL/BHMP CODE/400614 RVR/075 OPR/BAW PER/D RMK/LAHSO NOT AUTHORISED TCAS -E/0758) Link to comment Share on other sites More sharing options...
srcooke 422 Posted May 24, 2020 Share Posted May 24, 2020 You'll need a dispatcher to confirm but my own understanding is that you are required to be at the designated speed ( Mach ) and flightlevel prior to the oceanic entry point, in this case PIKIL therefor recorded at the preceding point LIPGO. Similarly at the exit the speed ( Mach ) and flightlevel should be maintained to the landfall waypoint, in this case JANGO. I suspect that the boundary is incorrectly identified here in PFPX as JANJO is shown within the Gander Oceanic sector hence it retains the Mach entry. Speed entries can be in an approved format at any segment of the flight and recorded in the ICAO plan: " True airspeed for the rst or the whole cruise portion of the flight, set as: “N” for Knots followed by a four-digit figure, “M” for Mach followed by a three-digit figure, or “K” for Kilometers/H followed by a four-digit number. i.e. K0830, N0485, M082 " So I don't think there is anything technically wrong, but then again I am a novice Link to comment Share on other sites More sharing options...
Skyrock 4 Posted May 26, 2020 Author Share Posted May 26, 2020 On 22.5.2020 at 17:10, srcooke sagte: Thanks for the pointer Mike, some of the entries in the FIR.dat did not match the Cruise Table. If you wish give the attached a try, backup the original first ! FIR.zip 230 kB · 11 downloads Thanks for the file! Just out of curiosity: KZWY (New York Oceanic) is also set to kts, same with KZAK (Oakland Oceanic). I'm not sure if they also have to be in Mach or not. Does anyone know this? Link to comment Share on other sites More sharing options...
srcooke 422 Posted May 27, 2020 Share Posted May 27, 2020 8 hours ago, Skyrock said: Just out of curiosity: KZWY (New York Oceanic) is also set to kts, same with KZAK (Oakland Oceanic). I'm not sure if they also have to be in Mach or not. Does anyone know this? Can you post your routes using the amended FIR file, testing here looks ok provided you use a waypoint on the oceanic boundary. Link to comment Share on other sites More sharing options...
Skyrock 4 Posted May 27, 2020 Author Share Posted May 27, 2020 vor 3 Stunden , srcooke sagte: Can you post your routes using the amended FIR file, testing here looks ok provided you use a waypoint on the oceanic boundary. I was asking because I hovered over the FIR name and saw that New York was also set as kts. But I just calculated a flight plan and that looks fine. All Mach Numbers from Entry to Exit. Only for the Pacific region, it doesn't seem to give Mach numbers, but then again I don't know if that's correct or not. Example flight: RJTT-KLAS (flown yesterday) ROVE1A INUBO Y808 NOLAX Y814 AVBET OTR9 EMRON DCT 40N160E 41N165E 41N170E 41N180E 41N170W 41N160W 41N150W 42N140W 41N130W DCT TRYSH DCT AMAKR DCT PYE DCT MOD DCT FRA DCT BTY SUNST4 Link to comment Share on other sites More sharing options...
srcooke 422 Posted May 27, 2020 Share Posted May 27, 2020 KZAK entry to exit: -N0510F350 ROVE1A INUBO Y808 NOLAX Y814 AVBET OTR9 EMRON DCT 40N160E 41N165E/M086F370 41N170E 41N180E 41N170W 41N160W 41N150W/M086F390 42N140W 41N130W DCT TRYSH/N0497F390 DCT AMAKR DCT PYE DCT MOD DCT FRA DCT BTY SUNST4 Link to comment Share on other sites More sharing options...
Skyrock 4 Posted May 27, 2020 Author Share Posted May 27, 2020 vor 37 Minuten, srcooke sagte: KZAK entry to exit: -N0510F350 ROVE1A INUBO Y808 NOLAX Y814 AVBET OTR9 EMRON DCT 40N160E 41N165E/M086F370 41N170E 41N180E 41N170W 41N160W 41N150W/M086F390 42N140W 41N130W DCT TRYSH/N0497F390 DCT AMAKR DCT PYE DCT MOD DCT FRA DCT BTY SUNST4 Okay, that's weird. It's not doing that for me although I copied your updated FIR.dat into the folder. I remain at kts all the time. Link to comment Share on other sites More sharing options...
srcooke 422 Posted May 27, 2020 Share Posted May 27, 2020 Sorry my bad, I updated the file further, attached. FIR2.zip Link to comment Share on other sites More sharing options...
Skyrock 4 Posted May 27, 2020 Author Share Posted May 27, 2020 Perfect, thank you! Now it looks alright! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.