Air Navigation Services of the Czech Republic, AIM

Česky Contact

FRACZECH - Reasons for rejecting FPL

1) Not complying with FRA relevancy

(FPL-FRA11-YG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F260 … AGNAV DCT MAREM
-EDAD0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/LKPRAAAA)

IFPS Error:

„THE DCT SEGMENT AGNAV..MAREM (NOT AN ALLOWED FRA EXIT POINT BORDER BETWEEN LKAAFRA:245:315 AND EDMMFRAE RESTRICTION:LKEDME500A) IS FORBIDDEN. RESTRICTION: LK100A“

In FRACZECH, you shall enter via FRA (E) point and exit via FRA (X) point. FPL is trying to exit FRACZECH airspace via MAREM, however MAREM is only defined as a FRA (E) point. It’s the same principle for entering FRACZECH via FRA (X) point. To get rid of this error, comply with FRA relevancies published in AIP CZ ENR 4.1 and ENR 4.4.

The correct FPL via FRACZECH airspace:

(FPL-FRA11-YG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F260 … AGNAV DCT SUPIL DCT KILNU
-EDAD0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/LKPRAAAA)

2) Not complying with RAD flow rules

(FPL-FRA11-YG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F260 … AGNAV DCT KILNU
-EDAD0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/LKPRAAAA)

IFPS Error:

„TRAFFIC VIA AGNAV IS OFF MANDATORY ROUTE REF:[LK2315A] AGNAV

You are violating RAD flow rule with ID LK2315 (ignore the last letter). Check RAD PAN EUR and find this ID.

FPL via AGNAV DCT KILNU is not following any of these available routings. If you enter FRACZECH via AGNAV, you have to exit via KILNU, HDO, LAGAR or TOMTI. Also, according to point 1. if you want to exit via KILNU, you have to use mandatory FRA (I) point SUPIL. To get rid of this error, comply with RAD „utilizations“. Check column „Remarks“, there might be an advice for you.

The correct FPL via FRACZECH airspace:

(FPL-FRA11-YG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F260 … AGNAV DCT SUPIL DCT KILNU
-EDAD0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/LKPRAAAA)

3) Violating TMA Praha

(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F160 … DOLUP DCT GOSEK DCT LEGAZ DCT LAGAR
-EPWR0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/ LKPRAAAA)

IFPS Error:

„THE DCT SEGMENT GOSEK..LEGAZ (68 NM) IS TOO LONG FOR LKPRAPP. MAXIMUM IS 0 NM [LKAA2B]

You are violating TMA Praha (LKPRAPP – up to FL165), which is NOT part of the FRACZECH airspace, and you are not compliant with RAD Appendix 4 DCTs published to be plannable in the TMA. From the system point of view, you are violating DCT limit = 0, that’s why the error line is saying „the segment is too long“. Setting this limit to 0 basically means, that you can only plan via published ATS routes or RAD Appendix 4 DCTs.

Check RAD Appendix 4 and find plannable DCTs through TMA Praha.

GOSEK DCT OKL and OKL DCT ARTUP is plannable through TMA Praha. To get rid of this error, plan via published DCTs in the TMA Praha.

The correct FPL via TMA Praha:

(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F160 … DOLUP DCT GOSEK DCT OKL DCT ARTUP DCT LAGAR
-EPWR0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/ LKPRAAAA)

If you are Y/Z flight to/from aerodromes close to DCTs, you might get the same error because your profile is calculated below the lower limit of the DCT. To get rid of this error, change flight rule some point earlier for arrivals, or one point later for departures.

4) Violating TRA/TSA (FBZ)

(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-LOWK0845
-N0269F210 ... LANUX DCT VLM DCT LEGAZ DCT LAGAR
-EPWR0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/ LKPRAAAA)

IFPS Error:

„TRAFFIC VIA LKTRA30Z:FL095..FL245 [202103020830..202103021200] IS ON FORBIDDEN ROUTE REF:[LKTRA30ZR] RAD APPENDIX 7 / AREA ACTIVE BY AUP/UUP“

You are violating FBZ area of LKTRA30 activated in the AUP/UUP at time of crossing. To get rid of this error, avoid this area by planning FRA (I) points (examples of suggested routings can be found in FRAView – this new module of AisView will be available during February).

The correct FPL around LKTRA30:

(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-LOWK0845
-N0269F210 ... LANUX DCT VLM DCT BEKVI DCT LEGAZ DCT LAGAR
-EPWR0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/ LKPRAAAA)

5) Using not existing ATS route or using ATS route at wrong levels

(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F260 … AGNAV L132 KILNU
-EDAD0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/ LKPRAAAA)

IFPS Error:

„AGNAV L132 KILNU DOES NOT EXIST IN FL RANGE F095..F999“

Route L132 is published only up to FL95 and does not exist at FL260. There are no ATS routes in FRACZECH. To get rid of this error, file according to FRACZECH rules.

The correct FPL via FRACZECH airspace:

(FPL-FRA11-YG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F260 … AGNAV DCT SUPIL DCT KILNU
-EDAD0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/LKPRAAAA)

6) Not following ARR/DEP connectivity

(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EPWA0845
-N0269F240 … RASAN DCT GOLOP
-LKPR0100
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/ LKPRAAAA

IFPS Error:

„TRAFFIC VIA GOLOP IS OFF MANDATORY ROUTE REF:[LK5550A] ARR PRAGUE GR VIA GOLOP RAD APP.5

You are violating mandatory ARR connectivity with ID LK5550 (ignore the last letter) published in RAD Appendix 5. Check RAD Appendix 5 and find this ID.

The FPL for arrival to LKPR via GOLOP (beginning of STAR) is not following any of these available routings. Arrival PRAGUE_GROUP (LKPR/KB/VO) via RASAN has to file RASAN DCT ASTEL DCT GOLOP, as you can see on point 2. Vice-versa it’s the same principle for departures coded for the last point of SID. To get rid of this error, comply with the connectivity. Check section Planning on this website.

The correct FPL via FRACZECH airspace:

(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EPWA0845
-N0269F240 … RASAN DCT ASTEL DCT GOLOP
-LKPR0100
-PBN/A1B2D2O2S2 REG/OKFRA OPR/FRACZECH ORGN/ LKPRAAAA)


Back to RAD & rejected FPLs


Back to FRACZECH main page


Back to top