RAD restriction EP2360

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

EP2360

RAD Code

EP2360

Valid From

2412 [28 NOV 2024]

Valid Until

UFN

Point or Airspace

VABER

Time Applicability

00:00-23:59

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.VIA VABER AND-THEN
a.VIA (GORPI, RUMAR, VADRU, IVGOR, LATMI, KUNER, RANOK, IPLIT, GOMED, GITOV, GOLAD, BOKSU, SOTET, ENOBI, GORAT, RUDKA, ABERO, BIGLU, TOLPA, IVNER, DIODA, INFUX, GOTIX, AMEDU, LUGOL, KEFIR, NAROX, LASIS, XIGRI, BANUB, BILRA)
b.VIA (POKEN, KOLOB, GOSOT, AMROR, LUSID) EXC DEP EYVI & VIA RATOR
Operational Goal
To eliminate unwanted traffic flows
Traffic departing EYVI via VABER is allowed to exit EPWW FIR only if planned via intermediate point RATOR; Bofore RATOR mandatory departure route starting on VABER is required
Remarks
Baltic FRA
ATC Unit

EPWWACC

NAS/FAB

EP

Release Date

24 OCT 2024

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 🗙