Panman 0 Posted April 3, 2015 Share Posted April 3, 2015 . Link to comment Share on other sites More sharing options...
Panman 0 Posted April 3, 2015 Author Share Posted April 3, 2015 I have had a few flights where PFPX seems to ignore RADS restrictions and thus the flightplan does not pass CFMU validation. For example I am currently trying to plan BIKF-EDDK. PFPX seems to be ignoring EBED1002 and thus failing validation. I tried adding it to see that the restriction (EBED1002.1) already exists in the RADS database and is correct as written (UM170 LNO-NOR Only available for traffic ARR ED** Except ARR EDDK/GS/KB) It used to work fine with 1.19 but now... Any others that I receive from now, I shall post in this thread. Panman Link to comment Share on other sites More sharing options...
srcooke 421 Posted April 3, 2015 Share Posted April 3, 2015 What was your route and the CFMU rejection? Link to comment Share on other sites More sharing options...
srcooke 421 Posted April 3, 2015 Share Posted April 3, 2015 Tried planning the airport combination with the same result although some level of RAD filtering is occurring: EL B1 METIL G3 MY G11 GONUT UM125 SUM UL7 SPY UL193 LEKKO N872 NIK UM624 BUB M624 GILOM L607 LNO UM170 NOR Link to comment Share on other sites More sharing options...
Panman 0 Posted April 3, 2015 Author Share Posted April 3, 2015 Yes. I forgot to say that in my original post. Some RAD filtering is happening and some isn't. Noticed this first last week planning an arrival into EGPH. Panman Link to comment Share on other sites More sharing options...
Panman 0 Posted April 6, 2015 Author Share Posted April 6, 2015 Trying to route EDKK - LTBA. PFPX finds KUMI6B KUMIK L603 TESGA UL603 BESNI UL605 STEIN DCT INVED UM747 NEKUL UL605 BULEN L605 RIXEN UG1 TETSA TETS1B However LH2086 states Not available for traffic1. Via BABIT/DIMLO/INVED/KEROP/KOPRY/PARAK/VEBAL 2. Via OVDOT if via TEGRI 3. Via M174 Except DEP LHPA I added this restriction manually to the RADs editor (well except the second restriction) as it did not exist and it still plots the above route. Panman Link to comment Share on other sites More sharing options...
srcooke 421 Posted April 6, 2015 Share Posted April 6, 2015 Hello Panman, LH2086 is currently not included in the PFPX RAD restrictions, you could add the entry: Link to comment Share on other sites More sharing options...
Panman 0 Posted April 6, 2015 Author Share Posted April 6, 2015 I gather you didn't see the part where I said I added it manually? And it's still being ignored. Link to comment Share on other sites More sharing options...
srcooke 421 Posted April 6, 2015 Share Posted April 6, 2015 I added the LH2086 restrictions, used quick find and only had to clear one other restriction not related related to LHCC Link to comment Share on other sites More sharing options...
Panman 0 Posted April 19, 2015 Author Share Posted April 19, 2015 I added it and it was ignored. Were you using 1.20 or 1.19? Link to comment Share on other sites More sharing options...
srcooke 421 Posted April 19, 2015 Share Posted April 19, 2015 I'm currently using v1.20.1 Without LH2086 I get: Adding the LH2086 restriction back in: Applying the level cap to OSBIT and the route clears: Link to comment Share on other sites More sharing options...
Panman 0 Posted April 25, 2015 Author Share Posted April 25, 2015 For some reason, when I added the time restriction, everything worked as you had it. My mind boggles. Thanks for your help anyway. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.