Small data glitch: L/UL613

Navigation Data General non MSFS data
1

Hello.
The small problem I have appeared in SIMBRIEF dispatch, but it is AIRAC related, so I post it here.
I planned a flight between LIML and EGPF. The CFMU valid plan is
(FPL-N319SB-IS
-A319/M-SDE3FGHIRWY/LB1
-LIML0950
-N0452F360 ABESI N851 ELMUR DCT RIPUS DCT DITON DCT HOC UL613 SOVAT L613 HALIF UN590 APPLE
-EGPF0245 EIDW
-PBN/A1B1C1D1O1S1 DOF/221231 REG/N319SB RMK/TCAS)

SIMBRIEF complains that UL613 uses invalid waypoints. From EAD Basic LS data, I get that the last three points of UL613 are DITON, HOC and NATLI. From SIA AIP I get that the first point of UL613 is NATLI. So I think that HOC shold be part of UL613.
Thanks in advance for any explanation.

2

You will need Richard to confirm but it may be a late amendment hasn’t made it into the 2213 cycle:

A0782/22/LSAS [AIRSPACE]
REF AIRAC AMDT 010/2022 WEF 01 DEC 2022:
ATS RTE UL613 ESTABLISHED BTN HOCHWALD DME (HOC) 472759.6N0073955.6E
AND NATLI 472931N0073026E.
TRACK TO/FM: 102/282
DIST: 6.6NM
LOWER LEVEL: FL195
UPPER LEVEL: FL660
CONTROLLING UNIT: ACC ZURICH
(01-DEC-2022 00:00 - PERM. CREATED 26-NOV-2022 13:23)

3

Thanks for you answer. I didn’t know it was a very recent amendament. Maybe it is related to the introduction of LSFRA, which has an exit point at HOC.
As to flight path, I will insert a direct to NATLI in the FMS and everything will be sorted out. So no big deal.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.