RAD restriction EG3199

Explain
Candidate screen (advisory)
Search Results (1 found)
RAD V1.6
(Annex 2B) Local and Cross-border Capacity and Structural Rules (1 found)

EG3199

RAD Code

EG3199

Valid From

28 MAR 2026 [2603]

Valid Until

UFN

Point or Airspace

KELLY

Time Applicability

00:00-23:59

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.RFL ABV FL255 IN EG
a.VIA (AKIVO, AMLAD, AMTAP, APSOV, ETSOM, EVNAL, GINGA, IBROD, KUGUR, LUTOV, MIMKU, NIBOG, NINEX, ODPEX, ORTAV, RATSU) AND-THEN
i)VIA (KONAN, MOTOX, SITET, VABIK, XAMAB, XIDIL)
ii)ARR (MANCHESTER_GROUP, MIDLANDS_GROUP)
iii)ARR (EGCN, EGNM, EGNO)
iv)VIA LAMSO
v)VIA NAVPI EXC FLT-TYPE(M)
b.VIA KELLY AND-THEN VIA (DEGOS, ERNAN, NIMAT)
c.VIA ROTEV
Operational Goal
To split traffic flows and reduce workload.
1a.i. EGBB/BE arrivals shall pick up the STAR at MAKUX or file via VAMEB. Manchester Group, EGNX arrivals shall FL255+ shall file MAKUX DCT SOSIM Q38/L15 or via ASCOM.
1a.ii. This traffic shall file via MAKUX DCT SOSIM Q38/L15 or via ASCOM.
1.a.iii. To reflect operational procedures, this traffic shall file via an alternative waypoint such as BELOX.
1b. To reduce complexity and prevent traffic filing close to the FIR boundary. This traffic shall file via BAGSO.
1c. This traffic shall file via LIFFY/BOFUM/ENDEQ
NAS/FAB

EG

Release Date

28 MAR 2026

Advisory only. This screens your route against restrictions we could structurally parse — it can never tell you a route is clean. IFPS validation is the only authoritative check.

Get in touch with us

Subscribe to receive updates about new features and improvements.

Contact Information

Feel free to reach out with any questions or feedback.


© 2026 RAD Restrictions. All rights reserved. By subscribing, you agree to receive updates from RAD Restrictions.
An unhandled error has occurred. Reload 🗙