RAD restriction LF3711

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

LF3711

RAD Code

LF3711

Change Indicator

AMD

Valid From

2609 [03 SEP 2026]

Valid Until

UFN

Point or Airspace

ROSPO

Time Applicability

H24 ---------- LFR270 NOT ACT

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.VIA LFFRANW EXC
a.VIA ROSPO AND-THEN VIA KORER
b.ARR (LFRB, LFRJ, LFRQ, LFEC, LFRL, LFRO, LFRU) & VIA BAGAD AND-THEN VIA ROSPO
c.ARR (LFRB, LFRJ, LFRQ, LFEC, LFRL) & VIA (DELOG, NENEM) AND-THEN VIA ROSPO
d.ARR (LFRO,LFRU) & VIA (DELOG, NENEM) AND-THEN VIA ROSPO
----------
NOT AVBL FOR TFC
ARR (LFRB, LFRJ, LFEC, LFRL) & VIA BAGAD AND-THEN VIA ROSPO
Operational Goal
1.a. To organize departing traffic flows in LFFRANW
1.b.c.To allow connectivity with lower airspace
1.d. To allow connectivity with lower airspace during military exercises
---------
When LFR270 is not active, traffic shall file via KORER and then ERCOZ
When LFR270 is active, traffic shall file via QPR,IDRIK and then ADSET
Remarks
Possible intermediate points:
From ROSPO to KORER : DEGEX
ATC Unit

LFRRACC

NAS/FAB

LF

Release Date

22 JUL 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 🗙