LSGG outbound routes

[Rodeo314]

For some city pairs, there seem to be only routes starting at DIPIR (runway 22) or SIROD (runway 04) among the eurocontrol valid options, for example LSGG to EGLL.

But the corresponding route for the other runway can easily be derived programmatically:

DIPIR T37 IBABA ↔ SIROD Z124 IBABA

Similarly:

ARBOS ↔ DIPIR V25 ARBOS

MOLUS N871 […] ↔ KONIL Z63 SOSAL N871 […]
(there are MOLUS departures for both runways, but for runway 22, MOLU4A does a left turn on departure whereas the KONIL SIDs do a right turn instead, so there are cases where ATC will issue routings via KONIL instead of MOLUS – and routes via KONIL Z63 SOSAL N871 also pass CFMU validation)

DIPIR T37 IBABA UB37 DJL ↔ SIROD L615 DJL
(but SIROD Z124 IBABA UB37 DJL is on forbidden route as per LSLF1080 A)
(and SIROD UH10 DJL is off mandatory route as per LS5608 A)

In addition, between cycles 2405 and 2406, many previously eurocontrol valid routes are no longer offered by Simbrief due to renamed airways, which could also be fixed programmatically:

old DIPIR B37 IBABA → new DIPIR T37 IBABA
old SIROD A1 DJL → new SIROD L615 DJL

Other nearby airways that have been renamed and that are part of mandatory routes (from/to LSGG or surrounding airports):

LTP B16 → Z16 BELUS (affects a number of LSGG arrivals from SW)
SPR G5 → T544 DEPUL
SPR G5 → T544 PAS R226 → Q226 BALSI
SPR A1 → L615 SIROD
SPR G5 → T544 FRI
SPR B46 → Y51 GOLEB
GVA G5 → T544 SPR
FRI G5 → T544 SPR
BELUS B16 → Z16 PAS
PAS G5 → T544 GVA
PAS G5 → T544 SPR
GOLEB B46 → Y51 SPR
SPR A1 → L615 LISMO
SPR A1 → L615 SIROD
ROCCA B46 → Y51 VANAS
MABES J32 → Z32 MOREG
UKID B37 → T37 PAS
PAS J41 → Y21 VANAS
ESAPI J41 → Y21 VANAS
MABES J32 → Z32 MOLUS
PAS B16 → Z16 CBY
(the above can probably be streamlined into simple airway renames, I included the segments mentioned in the RAD without thinking)

Regards,

Tim

[SimBrief]

Thanks for the airway details, Tim.

This should hopefully sort itself out gradually over the next few weeks, as more users submit new routes. Unfortunately while I could do a blanket search/replace in the database for these airways, I’d rather not assume that simply by replacing the airway names, the entire route will be IFPS compliant. In many cases the routes might have become invalid for other reasons, and manually validating routes is a bit too time consuming for me right now.

As I said, it should sort itself out over the next few weeks anyways.

The alternate routings for different SIDs is actually on the list already, but there are 100 other things on that list too so… not sure when I’ll get to it yet. As an example, this is already done for departure airports in the UK, based on route segments from the UK SRD. But expanding it to the rest of the route database is a bigger job that will take a bit more time.

Cheers,