RAD restriction LF3297

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

LF3297

RAD Code

LF3297

Valid From

2513 [25 DEC 2025]

Valid Until

UFN

Point or Airspace

LFRREST

Time Applicability

00:00-23:59

Categorisation

C

Utilization
NOT AVBL FOR TFC
1.DEP (DEAUVILLE_GROUP, LFRM, LFJR, LFOP, LFOE, LFOT, LFOQ)
2.DEP LFQQ & VIA OKRUZ
3.ARR (LONDON_GROUP, FARNBOROUGH_GROUP, EGHH, EGHI, EGDM, EGHR)
4.ARR (LFFFFIR EXC LILLE_GROUP, LFRK, LFJR)
5.DEP JERSEY_GROUP & VIA AMB
6.DEP LFRRFIR AND-THEN ARR (LILLE_GROUP,LFOK, LFQA,LFQB, LFLA, EBKT, EBCV)
7.DEP LFP* AND-THEN ARR EH**
8.DEP BARCELONA_GROUP AND-THEN ARR EGJ*
Operational Goal
1.Traffic Organisation ; LoA between LFFF and LFRR ; to offload LFRRZS and LFRRXS sectors. Traffic should file below FL 295 until BAZOS/ARSAF/LEQOS/OQQAL/POGZI/PEKIM/OKASI/KETEX/DISAK/OBATO
2.Traffic organisation. Traffic should file below FL 295 until ARGED, GALBO, PEPON, DIDAK
3.Traffic organisation
4.Traffic organisation. Traffic should file below FL295
5.This traffic shall file via TUPAR UN863 AGN
6.LOA LFFF/LFRR
7.Traffic organisation. THis traffic should file below FL295
8.To orientate on shortest route. Traffic should file via LFRRN sector
Remarks
8.planif aberrante non resolue par LF
2280.Plusieurs evenements reportes.
ATC Unit

(LFRRACC, LFFFACC, LFEEACC)

NAS/FAB

LF

Release Date

27 NOV 2025

LF3460

RAD Code

LF3460

Valid From

20 DEC 2025 [2512]

Valid Until

UFN

Point or Airspace

CAN

Time Applicability

00:00-23:59

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.ARR (LONDON_GROUP, FARNBOROUGH_GROUP) & VIA OKRUZ & RFL BLW FL195 AT CAN
2.ARR NAT
3.ARR PARIS_GROUP EXC DEP (LFRRFIR, JERSEY_GROUP)
Operational Goal
1.Traffic should file via DIKRO
2.This-traffic-shall-file via LGL
3.This traffic should file via INGOR/GALBO/ARGED
Remarks
1.RAD measure working in coordination with LF3297
2.Replacement of former LF2213
ATC Unit

LFRRACC

NAS/FAB

LF

Release Date

10 DEC 2025

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 🗙