RAD restriction EG2155

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

EG2155(P2)

RAD Code

EG2155

Valid From

2312 [30 NOV 2023]

Valid Until

UFN

Airway Code

P2

From

CAWZE

To

SIRIC

Time Applicability

H24 ---------- H24

Categorisation

S

Utilization
COMPULSORY FOR TFC
acft-eqpt (D1, D2, D3, D4, O1, O2, O3, O4)
Via YORQI
1.With RFL above FL105
ARR (EGKK, EGLD, EGLL, EGWU)
2.With RFL above FL175
ARR (EGKB, EGLC)
3.With RFL above FL175
ARR (EGGW, EGSC, EGSS)
Except TYP (PROP, PISTON)
DEP SEVERN_GROUP via NUCHU
----------
NOT AVBL FOR TFC
1.ARR (EGGW, EGKB, EGLC, EGSC, EGSS)
Except with RFL above FL175 in EG
2.ARR EGMC
3.ARR EGKK
Via (ADHAV, EVRIN, AMFUL)
Except
DEP EI
a.Crossing CAWZE 20:00..06:30 (19:00..05:30)
b.With RFL not above FL245 in EG
c.. Crossing CAWZE 06:30..20:00 (05:30..19:00)
01 NOV..28 FEB
4.DEP EIDW wIth ARR EGKK
Crossing CAWZE 06:30..20:00 (05:30..19:00) 01 NOV..28 FEB
Except not above FL245 in EG
Operational Goal
To ensure traffic files the standard arrival routeing.
3.RNAV1 jet traffic routeing from Severn Group to EGGW/SC/SS must file via SIRIC (max FL195). RNAV1 props/pistons may file via either SIRIC (max FL195) or via NUCHU (max FL145). RNAV5 traffic must file via NUCHU.
---------------------------------
1.Traffic inbound to the listed airfields with RFL below FL175 shall file via YORQI L607 NUCHU.
2.EGMC arrivals shall file via YORQI L607 NUCHU.
3.Between March and the end of October, outside of the night time/evening hours listed in 3.a., EI deps ARR EGKK FL245+ can only file this route if approved by the EGTTFMP. Alternative routeing for non-EI** deps and traffic FL245+ is via OTMET/GIBSO. The timing element of this restriction is relaxed between November and the end of February for EI deps, with the exception of EIDW deps. Traffic overflying (not departing EI) inbound to EGKK may not utilize this route at any time.
ATC Unit

EG**ACC

NAS/FAB

EG

Release Date

06 OCT 2023

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 🗙