Vincent14 0 Posted April 18, 2020 Share Posted April 18, 2020 Hello, I used PFPX (version 2.03) to,prepare a flight between Paris CDG (LFPG) and Singapore Changi (WSSS), to fly on A330 professional. PFPX and A330 are both updated with Airac cycle 2004 by NavDataPro. The route created (manual edition) was: BUBLI UG42 LUL UL613 SUXAN L613 VIC N503 LAREN Z122 LABIN DCT NISVA L614 SRT UG8 ALRAM G208 ZDN G452 RK P628 IBANI L510 GIVAL Y337 VPG A457 VKL A464 ARAMA I had 2 problems while entering this route on the A330. _ The first one is for LUL UL613 SUXAN. The airway UL613 is partally on one-way. I know there are some arrows to show if an airway is in one-way between 2 waypoints, but is there an option in PFPX to forbid to use airway on bad direction (on manual edition), or at least to get an error message. _The second problem was for GIVAL Y337 VPG A457 VKL On PFPX, Y337 and A457 are both in two-ways, but on the A330 Airac files (A3XX NavData\ats.txt), they are in one-way (and of course, not on the direction I wanted to take them). Can you have a look about this discrepancy. Thanks, Vincent Link to comment Share on other sites More sharing options...
srcooke 422 Posted April 18, 2020 Share Posted April 18, 2020 If you manually enter the route PFPX you are overriding the airway direction check, it will be for you to ensure compliance. The route find will adhere to direction. Both Navigraph and Skyvector and also the Malaysia AIP indicate Y337 as one way, A457 is only bi-directional VPG - TEPUS Link to comment Share on other sites More sharing options...
srcooke 422 Posted April 18, 2020 Share Posted April 18, 2020 Using NG2004 and David's RAD Restrictions and Directs PFPX returns a valid route on first pass: (FPL-OOSFL-IN -A333/H-SDE2E3FGHIJ3J4J5LM1P2RWXYZ/LB1D1 -LFPG0935 -N0471F350 RANUX UN858 LIMGO DCT BOMBI DCT BOREP UZ660 ENITA DCT ETVIS DCT ABUDO Z205 BUDEX DCT MAREG DCT ALAMU DCT EPARI DCT TEGRI DCT ZUBOK DCT DINRO/N0470F370 DCT UDROS UM859 KARDE UN644 ROLIN N644 LAGAS M747 SUBUT T923 ERLEV L850 BAKUV/N0461F390 N701 LARGI B701 KRS A240 INRAK B449 RANAH L750 ZB G201 BINDO L750 MERUN L333 JJP J1 KKJ L759 OTABA/N0468F410 L759 PUT B579 VPL W531 VIH A464 VKL/N0475F370 A464 ARAMA ARAM1B -WSSS1215 WMKJ -PBN/A1B1D1L1O1S1S2 NAV/RNVD1E2A1 COM/ULD DAT/SVM SUR/RSP180 DOF/200418 REG/OOSFL EET/EBUR0026 EDUU0028 LKAA0056 LOVV0109 LZBB0119 LHCC0126 LRBB0143 LBSR0224 LTBB0235 LTAA0237 UGGG0328 UBBA0352 UTAK0429 UTAA0453 UTAV0533 OAKX0546 OPLR0630 OPKR0646 VIDF0700 VECF0746 VYYF0942 VOMF0946 VYYF1007 VTBB1029 WMFC1105 WSJC1157 SEL/GRAM CODE/44CCCC RVR/200 OPR/BRUSSELS AIRLINES PER/D RIF/NISUN DCT VYYY -E/1318) Link to comment Share on other sites More sharing options...
Vincent14 0 Posted April 18, 2020 Author Share Posted April 18, 2020 Stephen, Thanks for your replies. There is a problem on the PFPX Airacs, which doesn't match with the reality. I noticed the same problem on P628 (VPL to GIVAL). I have submitted a ticket on Aerosoft support to ask them to check the Airac file for PFPX. Vincent, Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted April 18, 2020 Aerosoft Share Posted April 18, 2020 I looked at the file and did not notice any issues but I did alert Lufthansa Data Systems. As we are not allowed to edit the files (of course) that is all we can do. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.