Česky
FRA - 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“
MAREM is not defined as a FRA (X) point. You have to enter FRA via FRA (E) point and exit via FRA (X) point. MAREM is defined as FRA (E) and this FPL is trying to exit FRA airspace at MAREM. Vice-versa it's the same for entering via not allowed FRA (E) 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 FRA 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 Annex 2B traffic flow rules
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EPKT0845
-N0269F260 … UTEVO DCT NIRGO …
-EDDM0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
IFPS Error:
„TRAFFIC VIA UTEVO IS OFF MANDATORY ROUTE REF:[LK2386A] UTEVO“
You are violating RAD traffic flow rule with ID LK2386 (ignore the last letter). Check RAD Annex 2B and find this ID.
FPL via UTEVO is not following any of these available routings. If you enter FRA via UTEVO, you have to exit via BAVRI, RUDAP, OKG, RAPET, VARIK, VEXIL, HDO or BEFRE. There might be compulsory (I) points along the way coded in other traffic flow rule. Check cell "Operational goal", there might be advice for you. To get rid of this error, comply with RAD „utilizations“.
The correct FPL via FRACZECH airspace:
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EPKT0845
-N0269F260 … UTEVO DCT VOZ DCT BAVRI …
-EDDM0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-LOWW0845
-N0269F260 LEDVA DCT BAVOK
-EPKT0100
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
IFPS Error:
„TRAFFIC VIA LEDVA IS OFF MANDATORY ROUTE REF:[LK2450A] KATQA“
You are violating RAD traffic flow rule with ID LK2450 (ignore the last letter). Check RAD Annex 2B and find this ID.
FPL via LEDVA and then REGLI has to file compulsory point KATQA. To get rid of this error, comply with RAD „utilizations“.
The correct FPL via FRA airspace:
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-LOWW0845
-N0269F260 LEDVA DCT KATQA DCT BAVOK
-EPKT0100
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
3) Violating DCT limit in Non-FRA ENV (mostly TMA Praha)
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F160 … DOLUP DCT APRAQ DCT LEGAZ DCT LAGAR …
-EPWR0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
IFPS Error:
„THE DCT SEGMENT APRAQ..LEGAZ (68 NM) IS TOO LONG FOR LKPRAPP. MAXIMUM IS 0 NM [LKAA2B]“
You are violating non-FRA airspace (LKPRAPP – up to FL165), and not using ATS route or RAD Annex 3B DCTs published to be plannable in the airspace. 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 Annex 3B DCTs. If the limit was higher, you would be able to plan any DCT lower than this limit.
Check RAD Annex 3B and find plannable DCTs through TMA Praha.
APRAQ DCT OKL and OKL DCT ARTUP is plannable through TMA Praha. To get rid of this error, follow the RAD DCT structure in the TMA Praha.
The correct FPL via TMA Praha:
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F160 … DOLUP DCT APRAQ DCT OKL DCT ARTUP DCT LAGAR …
-EPWR0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
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 ANNEX 2C / 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.
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/OFRA 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/OFRA 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 FRA airspace in the Czech Republic. To get rid of this error, file according to FRA rules.
The correct FPL via FRA airspace:
(FPL-FRA11-YG
-PC12/L-SBDFGM3RWY/E
-EDMO0845
-N0269F260 … AGNAV DCT SUPIL DCT KILNU …
-EDAD0130
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
6) Not following ARR/DEP connectivity traffic flow rules
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EDDM0845
-N0269F260 … DOLUP DCT APRAQ DCT BEKVI
-LKPD0100
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
IFPS Error:
„TRAFFIC VIA BEKVI IS ON FORBIDDEN ROUTE REF:[LK5555A] ARR LKPD/CV VIA BEKVI“
You are violating mandatory ARR connectivity with ID LK5555 (ignore the last letter) published in RAD Annex 3A. Check RAD Annex 3A and find this ID.
FPL arriving LKPD via BEKVI (beginning of STAR) is not following any of these available routings. Arrival LKPD/CV via APRAQ has to file APRAQ DCT OKL DCT BEKVI, as you can see in line 1. Vice-versa it’s the same principle for departures coded for the last point of SID. To get rid of this error, comply with connectivities.
The correct FPL via FRACZECH airspace:
(FPL-FRA11-IG
-PC12/L-SBDFGM3RWY/E
-EDDM0845
-N0269F260 … DOLUP DCT APRAQ DCT OKL DCT BEKVI
-LKPR0100
-PBN/A1B2D2O2S2 REG/OKFRA OPR/OFRA ORGN/LKPRAAAA)
