Jump to content
chkl

Route Restriction error on real plan

Recommended Posts

This is a real plan HECA to ELLX. PFPX says Route restriction errors

IuuQySx.png

CVO A727 NOZ UL607 GESAD L551 ANTAR/N0469F360 UN133 KOROS/N0470F380 UN133 PEREN/N0481F400 UN128 RUGAS DCT RAXAD DCT VAL DCT DIMSI DCT OBUTI DCT RENKA UL610 UPALA Z744 LEPSA Z104 AGBUL T894 BITBU Z110 BETEX

 

Share this post


Link to post

First of all, the error doesn not come from PFPX but Eurocontrol.

From where did you get that real plan? Maybe it is already outdated or the cycle on which the plan is based does not match witrh the one you use in PFPX.

Share this post


Link to post

Post a complete snapshot the validation screen following IFPS submission.

Share this post


Link to post

Several points here as to why your validation of a "real" flightplan might fail:
I assume you got the flightplan from edi-gla.co.uk. I just found the same one there and it was flown on the 25th of December. That means it comes from an old AIRAC, namely 1813 while 1902 is active by now.

Even if it came from a current AIRAC there could still be many reasons why validation might fail:
1) You're trying to validate it at different altitudes than the real one. The one on edi-gla got very different flightlevels. The route might be valid at those levels used in real life, but not on those your are trying to use.

2) Many routings in Europe are only valid at certain times of the day. If you're validating the route at a different time than the real one you might end up with different restrictions being active, etc. While you might be allowed to fly direct XYZ at 2am you might not be allowed to fly that at 2pm.

3) You might be validating at a different date. If a real flight was flown for example on a weekend it might have been allowed to fly through military areas which are inactive during weekends, but are active monday-friday.

 

These are just a couple of examples, there are many, many, many more reasons why you might not be able to validate a flightplan anymore which was flown in real life.

Share this post


Link to post

Flight today. 0730z departure

FPL-CLX8512-IS -B744/H-SDE2E3FGHIJ3J7M3RWXYZ/LB1D1

HECA0730

N0481F360 DCT CVO A727 NOZ UL607 GESAD L551 ANTAR/N0469F360 UN133 KOROS/N0470F380 UN133 PEREN/N0481F400 UN128 RUGAS DCT RAXAD DCT VAL DCT DIMSI DCT OBUTI DCT RENKA UL610 UPALA Z744 LEPSA Z104 AGBUL T894 BITBU Z110 BETEX

ELLX0405 EBLG

PBN/A1B1C1D1L1O1S2 NAV/RNVD1E2A1 DAT/1FANS DOF/190212 REG/LXSCV EET/LGGG0044 LWSS0151 LYBA0159 LQSB0224 LDZO0230 LJLA0246 LOVV0249 EDUU0310 EBBU0358 SEL/HQBC OPR/CARGOLUX ITALIA RMK/TCAS ADSB

Share this post


Link to post
5 hours ago, srcooke said:

Post a complete snapshot the validation screen following IFPS submission.

 

Share this post


Link to post
1 hour ago, chkl said:

Flight today. 0730z departure

FPL-CLX8512-IS -B744/H-SDE2E3FGHIJ3J7M3RWXYZ/LB1D1

HECA0730

N0481F360 DCT CVO A727 NOZ UL607 GESAD L551 ANTAR/N0469F360 UN133 KOROS/N0470F380 UN133 PEREN/N0481F400 UN128 RUGAS DCT RAXAD DCT VAL DCT DIMSI DCT OBUTI DCT RENKA UL610 UPALA Z744 LEPSA Z104 AGBUL T894 BITBU Z110 BETEX

ELLX0405 EBLG

PBN/A1B1C1D1L1O1S2 NAV/RNVD1E2A1 DAT/1FANS DOF/190212 REG/LXSCV EET/LGGG0044 LWSS0151 LYBA0159 LQSB0224 LDZO0230 LJLA0246 LOVV0249 EDUU0310 EBBU0358 SEL/HQBC OPR/CARGOLUX ITALIA RMK/TCAS ADSB 

 

Works perfectly fine here:

image.png.07a918c8f29231fe2175348a90e54669.png

Share this post


Link to post
13 hours ago, Emanuel Hagen said:

 

Works perfectly fine here:

image.png.07a918c8f29231fe2175348a90e54669.png

But why the route restriction error messages?

Share this post


Link to post

Understand that it passes validation my question is why the yellow message prompts and warning about the router restriction, 2 telling me that route is only for ELLX (my destination, so why a warning?) and 1 says not for ELLX but that is a real route.

 

3i4WXTo.jpg

Share this post


Link to post

These are not route errors, it informs you of the internal RAD restriction files PFPX is considering and may be acting upon.

 

If necessary the user can identify and modify the internal restriction if required.

 

RAD restrictions are not updated per AIRAC cycle, David issues some updates in the main part to accommodate FRA.

 

As can be seen no IFPS errors are returned.

Share this post


Link to post
12 minutes ago, srcooke said:

These are not route errors, it informs you of the internal RAD restriction files PFPX is considering and may be acting upon.

 

If necessary the user can identify and modify the internal restriction if required.

 

RAD restrictions are not updated per AIRAC cycle, David issues some updates in the main part to accommodate FRA.

 

As can be seen no IFPS errors are returned.

One route it says invalid for my arrival airport but this is not correct. And if ELLX is my arrival airport the other route restriction messages shouldnt display. A preference for me is not to see the yellow exclamation marks on this routing.

Share this post


Link to post

I disagree, the RAD restrictions are not updated per AIRAC cycle and it indicates what files PFPX is considering allowing you to update them if necessary.

 

Without that you would find it very difficult to identify/modify an incorrect or outdated entry.

 

The only ERRORS to be acted upon are those returned by IFPS validation.

 

 

Share this post


Link to post
4 hours ago, srcooke said:

I disagree, the RAD restrictions are not updated per AIRAC cycle and it indicates what files PFPX is considering allowing you to update them if necessary.

 

Without that you would find it very difficult to identify/modify an incorrect or outdated entry.

 

The only ERRORS to be acted upon are those returned by IFPS validation.

 

 

Not liking yellow exclamation marks because the route restriction messages 7xeF87I.jpg

Share this post


Link to post

 

On 12.2.2019 at 07:39, chkl sagte:

This is a real plan HECA to ELLX. PFPX says Route restriction errors

IuuQySx.png

CVO A727 NOZ UL607 GESAD L551 ANTAR/N0469F360 UN133 KOROS/N0470F380 UN133 PEREN/N0481F400 UN128 RUGAS DCT RAXAD DCT VAL DCT DIMSI DCT OBUTI DCT RENKA UL610 UPALA Z744 LEPSA Z104 AGBUL T894 BITBU Z110 BETEX

 

 

Hi,

not sure, why PFPX complains about the first restriction, as airway T161 is not even used. It just shares a few miles with Z104 from LEPSA to PSA. 

 

But for the second one, if I put NONKO into "Via" text field, it passes without complaint on this rule. This change will be included in update for RAD and Restrictions 1903.

 

image.png.7967db589cf967fd6fd630cdb5e80b34.png

 

 

Regarding the third restriction, maybe PFPX wants to use Z104 MISGI T894 BITBU Z110 BETEX instead of 

Z104 AGBUL T894 BITBU Z110 BETEX. With this adaption only ED3468 is left.

 

IMO, regardless the changes that need to be taken here, it's more important the route passes IFPS validation for the day of flight, which it does.

 

 

Regards

David

Share this post


Link to post

I believe the T161 entry is listed David as it is considered, not available for the route planned and therefor T161 not used.

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...