RAD restriction LFLE1019

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

LFLE1019

RAD Code

LFLE1019

Valid From

09 JAN 2026 [2513]

Valid Until

UFN

Point or Airspace

(LATEK, PIPOR, ERAKI)

Time Applicability

00:00-23:59

Categorisation

C

Utilization
NOT AVBL FOR TFC
1.DEP TOULOUSE_GROUP & ABV FL335 AT (LATEK, PIPOR, ERAKI)
2.ARR (LEPP, LERJ, LESO)
3.VIA GAI & ARR LEMD
4.ARR (LEBB, LEBG, LEVT, LEXJ) & ABV FL275 AT (LATEK, PIPOR, ERAKI)
Operational Goal
1.Profile information, departure level cap
LoA between LFBB/LECM
2.This traffic should file via BTZ
3.To avoid crossing flows, this traffic shall file via TIVLI
4.Vertical priofile t be compliant with LECM-LEBB LOA
ATC Unit

(LFBBACC, LECMACC)

NAS/FAB

LF,LE

Release Date

08 JAN 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 🗙