Route Calculator (Beta) - Still returning a completely invalid FRA routes

Hi, I know that it’s still in Beta, so please consider it primarily as an effort to iron out the issues.

The Route Calculator is still returning an absolutely nonsense routes, which are no way FRA and Eurocontrol compliant.

For example, LKPR - LGIR:
VOZ ABETI PEROT RAMAP MAKED UL617 MIL UM749 EPALO
which even completely denies the Czech FRA rules, where there are clearly outlined FIR exit points.

PROF204: RS: TRAFFIC VIA LOVVCTA:F355..F999 IS ON FORBIDDEN ROUTE REF:[LO2236A] LOVVE17

PROF204: RS: TRAFFIC VIA LOVVE17:F335..CEL IS ON FORBIDDEN ROUTE REF:[LO2254A] ANNEX 2B LOVVE17

PROF205: RS: TRAFFIC VIA LKPR GR IS OFF MANDATORY ROUTE REF:[LK2478A] ANN2B LANUX

PROF205: RS: TRAFFIC VIA LOWWAPP LOVVE17 IS OFF MANDATORY ROUTE REF:[LK2483A] ANN2B PISAM

PROF204: RS: TRAFFIC VIA LYBACTA:F205..F999 IS ON FORBIDDEN ROUTE REF:[LYLD1000A] ANNEX 2B LYBACTA

PROF204: RS: TRAFFIC VIA LDZOCTA:F205..F999 IS ON FORBIDDEN ROUTE REF:[LDLY1000A] LDZOCTA

PROF204: RS: TRAFFIC VIA LHKRCTA IS ON FORBIDDEN ROUTE REF:[LYLH1000A] ANNEX 2B LYBACTA

PROF205: RS: TRAFFIC VIA LYBACTA|LWSSCTA IS OFF MANDATORY ROUTE REF:[LW2009A] AZBUX, RAVAK, IBISI(…)

PROF205: RS: TRAFFIC VIA KEA IS OFF MANDATORY ROUTE REF:[LG2222A] ANNEX 2B GENDO L/UL607 GIVIS

PROF205: RS: TRAFFIC VIA LGIR IS OFF MANDATORY ROUTE REF:[LG2130A] XAVIS

ROUTE52: THE DCT SEGMENT ABETI (NOT AN ALLOWED FRA EXIT POINT BORDER BETWEEN SEEFRA AND SECSI:245:999 RESTRICTION:SEESEC500A)..PEROT (NOT AN ALLOWED FRA POINT BORDER BETWEEN SEEFRA AND SECSI:245:999 RESTRICTION:SEESEC500A) IS FORBIDDEN. RESTRICTION: SEEFRA100A

ROUTE52: THE DCT SEGMENT ABETI (NOT AN ALLOWED FRA POINT BORDER BETWEEN SEEFRA AND SECSI:245:999 RESTRICTION:SEESEC500A)..PEROT (NOT AN ALLOWED FRA ENTRY POINT BORDER BETWEEN SEEFRA AND SECSI:245:999 RESTRICTION:SEESEC500A) IS FORBIDDEN. RESTRICTION: SECSI100A

ROUTE52: THE DCT SEGMENT RAMAP (NOT AN ALLOWED FRA EXIT POINT BORDER BETWEEN SECSI:205:999 AND LHKRCTA RESTRICTION:SECLHK500A)..MAKED (NOT AN ALLOWED FRA EXIT POINT BORDER BETWEEN SECSI:205:999 AND LHKRCTA RESTRICTION:SECLHK500A) IS FORBIDDEN. RESTRICTION: SECSI100A

ROUTE165: THE DCT SEGMENT RAMAP..MAKED (155 NM) IS TOO LONG FOR LHKRCTA. MAXIMUM IS 0 NM [LHKR1A]

ROUTE52: THE DCT SEGMENT RAMAP (NOT AN ALLOWED FRA ENTRY POINT BORDER BETWEEN LHKRCTA AND SECSI:205:999 RESTRICTION:LHKSEC500A)..MAKED IS FORBIDDEN. RESTRICTION: SECSI100A

Another example:
LKTB - LEPA
MIKOV DCT LIMRA DCT DETSA DCT OTKEK DCT TALEP DCT ZETCO DCT MAXOS UT250 RIXOT

PROF204: RS: TRAFFIC VIA LFD54A2Z:F195..F999 [202505220615..202505221345] IS ON FORBIDDEN ROUTE REF:[LFD54A2ZRA] RAD ANNEX 2C / ACTIVATION BY AUP/UUP

PROF204: RS: TRAFFIC VIA LFD54A4Z:F195..F999 [202505220615..202505221345] IS ON FORBIDDEN ROUTE REF:[LFD54A4ZRA] RAD ANNEX 2C / ACTIVATION BY AUP/UUP

PROF204: RS: TRAFFIC VIA TALEP:F195..F999 IS ON FORBIDDEN ROUTE REF:[LFLI1071A] TALEP

PROF205: RS: TRAFFIC VIA TALEP IS OFF MANDATORY ROUTE REF:[LF2240A] TALEP

EHAM - LHBP
ARNEM L620 PIKIB T620 LALUK BITSI TEKVI ARFOX
Again, complete nonsense.

PROF204: RS: TRAFFIC VIA NOMKA L620 BIRKA IS ON FORBIDDEN ROUTE REF:[ED2136A] L620 NOMKA BIRKA

PROF204: RS: TRAFFIC VIA DRN T620 LALUK IS ON FORBIDDEN ROUTE REF:[EDLK1012A] DRN T620 LALUK

PROF205: RS: TRAFFIC VIA LKAACTA IS OFF MANDATORY ROUTE REF:[LK2440A] LKAACTA

PROF204: RS: TRAFFIC VIA BITSI IS ON FORBIDDEN ROUTE REF:[LK2324A] BITSI

PROF204: RS: TRAFFIC VIA ARFOX BP870 BP871 BP872 ULPAX BP874 NICRA LHBP ARFOX BP786 BP785 BP784 ULPAX BP774 CATUZ LHBP IS ON FORBIDDEN ROUTE REF:[LZ5540A] ARFOX STARS FOR LHBP ARR


So it appears that the Route Calculator still needs a lot of work, because the routes have zero sense with regards to Eurocontrol, FRA, and even just a basic common sense, that it should include waypoints on FIR boundaries.

1 Like

Hi, thanks for the detailed reports. They will be noted for future updates.

It is expected at the moment that the route calculator does not do a great job at respecting RAD/FRA by default. Some manual tuning is often required, mainly consisting of IFPS validation and then including/avoiding waypoints based on the validation results.

Future updates will hopefully improve this, but the main goal of this latest update was to revamp the UI and provide us with a solid base to improve upon.

Cheers,