RAD restriction LS2406

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

LS2406

RAD Code

LS2406

Valid From

14 MAR 2025 [2502]

Valid Until

UFN

Point or Airspace

LSAGUAC

Time Applicability

1. H24 2. H24 3. H24 4. 01 MAY 2025 - 30 SEP 2025 06:00-20:00 5. 01 MAY 2025 - 30 SEP 2025 06:00-20:30 6. 01 MAY 2025 - 30 SEP 2025 06:00-20:30 7. 01 MAY 2025 - 30 SEP 2025 06:00-20:30 8. 01 MAY 2025 - 30 SEP 2025 06:00-20:30 9. 01 MAY 2025 - 30 SEP 2025 06:00-20:30

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.VIA LFMMBB AND-THEN VIA LSAGUAC AND-THEN VIA (LIMMW, LIMME) EXC FLT-TYPE (M)
2.DEP LI** & LSAGUAC AND-THEN VIA LFMMBB EXC FLT-TYPE (M)
3.VIA LSAZUTA & LSAGUAC AND-THEN VIA (LFEE4EH, LFFFUJ, LFEEKD)
4.DEP (LFP*, EG) & ARR (AJACCIO_GROUP, BASTIA_GROUP, NICE_GROUP, LFKT)
5.VIA (LFMMYY, LFMNND) & LSAGUAC AND-THEN VIA (DJL, LFFFUJ, LFEEKD)
6.VIA LFMMBB & LSAGUAC AND-THEN VIA (LFFFUJ, LFEEKD) EXC FLT-TYPE (M)
7.DEP (EB**, ED**, EH**, EL**, LFPG) & ARR (LIMC, LIME, LIML) EXC FLT-TYPE (M)
8.DEP (LG**) & ARR (LFR*) & VIA LSAGUAC AND-THEN VIA LFMMYY
9.DEP (LFR*) & ARR (LG**) & VIA LFMMYY AND-THEN VIA LSAGUAC
Operational Goal
1.To prevent traffic filing creative routes
2.To prevent unsafe turn for traffic departing LI** crossing LSAGUAC and then crossing LFMMBB sectors
3.To prevent traffic filing creative routes
4.To force specific traffic via a specific route
5.To prevent traffic filing creative routes
6.To avoid traffic complexity in the peak hours
7.To avoid traffic complexity in the peak hours.
8.9. To avoid traffic complexity in the peak hours
Remarks
Except in case of French strike
4.DEP LFP*, EG**
With ARR Ajaccio Group, Bastia Group, Nice Group, LFKT
5.Via (LFMMYY, LFMNND)
Then via (DJL, LFFFUJ, LFEEKDH)
After LSAGUAC
6.Via LFMMBB sectors
Then via LFFFUJ / LFEEKD sector
After LSAGUAC
7.DEP EB**, ED**, EH**, EL**, LFPG
With ARR LIMC/ME/ML
Except type Mil
ATC Unit

LSAGACC

NAS/FAB

LS

Release Date

12 MAR 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 🗙