RAD restriction BREST_GROUP

Explain
Candidate screen (advisory)
Search Results (4 found)
RAD V1.6
(Annex 1) Area Definitions (1 found)

BREST_GROUP

Area ID

BREST_GROUP

Valid From

2303 [23 MAR 2023]

Valid Until

UFN

Definition

(LFRB, LFRU, LFRO, LFRJ)

Remarks

CACD ID: LFRBTMA

Owner

LF

Release Date

08 FEB 2023

(Annex 2A) Flight Level Capping Rules (1 found)

LF4392((BREST_GROUP,JERSEY_GROUP) → TOULOUSE_GROUP)

RAD Code

LF4392

Valid From

2604 [16 APR 2026]

Valid Until

UFN

From ADEP

(BREST_GROUP,JERSEY_GROUP)

To ADES

TOULOUSE_GROUP

Crossing Airspace

(EG, LF)

Flight Level Capping

RFL FL355

Time Applicability

00:00-23:59

Categorisation

C

Operational Goal
To offload LFRRNIU sector
Release Date

20 FEB 2026

(Annex 2B) Local and Cross-border Capacity and Structural Rules (2 found)

LF3591

RAD Code

LF3591

Change Indicator

AMD

Valid From

2609 [03 SEP 2026]

Valid Until

UFN

Point or Airspace

TUPAR

Time Applicability

1. a. (LFT90NLZ, LFT90NHZ, LFT9A, LFT9C, LFT9D) ACT 1. b. (LFT90NLZ, LFT90NHZ, LFT9A, LFT9C, LFT9D) ACT 1. c. (LFT90NLZ, LFT90NHZ, LFT9A, LFT9C, LFT9D) ACT 1. d. (LFT90NLZ, LFT90NHZ, LFT9A, LFT9C, LFT9D) ACT 1. e. (LFT90NLZ, LFT90NHZ, LFT9A, LFT9C, LFT9D) ACT 1. f. H24 1. g. H24 1. h. H24 1. i. H24 1. j. H24 1. k. H24 1. l. H24 1. m. i) H24 1. m. ii) 22 SEP 2026- 24 SEP 2026 H24 1. n. H24 1. o. MON-THU 22:00-05:00 (23:00-04:00) & FRI 11:00 (10:00)-MON 06:00 (05:00) & HOL LF H24 1. p. 22:00-05:00 (23:00-04:00) 1. q. 22:00-05:00 (23:00-04:00) 1. r. 22:00-05:00 (23:00-04:00) 1. s. 22:00-05:00 (23:00-04:00) 1. t. H24 1. u. (LFT90NLZ, LFT90NHZ, LFT9A, LFT9C, LFT9D) ACT

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.VIA TUPAR AND-THEN VIA LFFRASW EXC
a.VIA (TUPAR DCT DIDRU DCT BEBIX DCT GUERE)
b.VIA (TUPAR DCT DIDRU DCT BEBIX DCT VALKU DCT TIS)
c.VIA (TUPAR DCT DIDRU DCT BEBIX DCT VALKU DCT LABAL)
d.VIA (TUPAR DCT DIDRU DCT BEBIX DCT VALKU DCT LERGA)
e.VIA (TUPAR DCT DIDRU DCT ADATU DCT LERGA)
f.DEP (NANTES_GROUP, RENNES_GROUP, LFOO, LFOV)
i)VIA (TUPAR DCT DIDRU DCT BEBIX DCT GUERE)
ii)VIA (TUPAR DCT DIDRU DCT BEBIX DCT VALKU DCT TIS)
iii)VIA (TUPAR DCT DIDRU DCT BEBIX DCT VALKU DCT LABAL)
iv)VIA (TUPAR DCT DIDRU DCT BEBIX DCT VALKU DCT LERGA)
v)VIA (TUPAR DCT DIDRU DCT ADATU DCT LERGA)
vi)VIA (TUPAR DCT DIDRU DCT ECKAP) & FLT-TYPE (M,X)
g.VIA (TUPAR DCT CNA DCT SECHE DCT AGN DCT ANETO)
h.VIA (TUPAR DCT CNA DCT SECHE DCT AGN DCT TOU DCT LOMRA DCT ROCAN)
i.VIA (TUPAR DCT CNA DCT SECHE DCT GAI)
j.VIA (TUPAR DCT CNA DCT SECHE DCT SOVET DCT FJR)
k.VIA (TUPAR DCT CNA DCT VAVIX DCT NETUK)
i)ARR LEMD
ii)DEP NANTES_GROUP AND-THEN ARR (LEMD, LEZG)
l.VIA (TUPAR DCT CNA DCT VAVIX DCT BTZ R10 URUNA)
i)ARR LESO
ii)DEP NANTES_GROUP AND-THEN ARR (LEPP, LERJ, LESO)
m.VIA (TUPAR DCT CNA DCT VAVIX DCT BTZ DCT URUNA)
i)ARR (LEBB, LEBG, LEVT, LEXJ)
ii)DEP (NANTES_GROUP, BREST_GROUP, RENNES_GROUP) AND-THEN ARR (LPFR, LPPR, LPPT, LPMA, LEZL, GCTS)
n.ARR BORDEAUX_AREA
o.VIA (TUPAR DCT CNA DCT SECHE DCT AGN DCT TOU DCT YACIM)
p.VIA (TUPAR DCT YACIM)
q.VIA (TUPAR DCT LACOU DCT ROCAN)
r.VIA (TUPAR DCT MAKOX DCT FJR)
s.VIA (TUPAR DCT ETENU DCT YAQEL)
t.VIA (TUPAR DCT CNA DCT UVELI DCT MIRBA) & FLT-TYPE (M,X)
u.VIA (TUPAR DCT DIDRU DCT ECKAP) & FLT-TYPE (M,X)
Operational Goal
to organise flow in LFBB UIR
Remarks
FRA rule, Entry
Reference Location= LFFRASW
In CACD define as per Annex3B:
VALKU DCT LERGA: MEA-UNL
Other DCTs: FL195-UNL
1a.b.c.d.e.t. Traffic should file via LEMKA when (LFT90NLZ, LFT90NHZ, LFTA9A, LFTA9C, LFTA9D) not active
ATC Unit

LFBBACC

NAS/FAB

LF

Release Date

22 JUL 2026

LF3504

RAD Code

LF3504

Valid From

20 DEC 2025 [2512]

Valid Until

UFN

Point or Airspace

LFRRVKIU

Time Applicability

1. AIRAC MAR - FIRST AIRAC OCT H24 2. H24

Categorisation

C

Utilization
NOT AVBL FOR TFC
1.ARR (EGHQ, EGTE, EGBJ, EGGD, EGFF, EGHH, EGHI, EGSY, EGDM, EGHR)
2.DEP (LFRH, LFRQ, BREST_GROUP)
Operational Goal
Traffic organization,
traffic should file below in LFRRVKS (at RFL 340 and below)
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 🗙