RAD restriction LF2249

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

LF2249

RAD Code

LF2249

Change Indicator

AMD

Valid From

2609 [03 SEP 2026]

Valid Until

UFN

Point or Airspace

OKIVA

Time Applicability

1. a. H24 1. b. H24 1. c. H24 1. d. H24 1. e. H24 1. f. H24 1. g. H24 1. h. H24 1. i. (LFT44D1Z, LFT44D2Z) ACT 1. j. (LFT44D1Z, LFT44D2Z) ACT 1. k. (LFT44D1Z, LFT44D2Z) ACT 1. l. (LFT44D1Z, LFT44D2Z) ACT 1. m. (LFT44D1Z, LFT44D2Z) ACT 1. n. (LFT44D1Z, LFT44D2Z) ACT 1. o. LFD540EZ ACT

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.VIA OKIVA AND-THEN VIA LFFRASE EXC
a.VIA (OKIVA P980 DIKEL DCT RATAP DCT MEGER)
b.VIA (OKIVA P980 DIKEL DCT ETAGI DCT OKROK DCT MEGER)
c.VIA (OKIVA P980 DIKEL DCT OKBON DCT RAPUR DCT MEGER)
d.VIA (OKIVA P980 DIKEL DCT OKBON DCT PIGOS) AND-THEN VIA (BARSO, BODRU, IDAVO, LOGNI, AGEVU)
e.VIA (OKIVA P980 DIKEL DCT OMEDA M622 LONSU) & ARR NICE_GROUP
f.VIA (OKIVA P980 DIKEL DCT MERLU DCT OMARD )
g.VIA (OKIVA P980 DIKEL DCT AJO DCT RUBAS DCT TINOT DCT AMFAC)
h.VIA (OKIVA P980 DIKEL DCT AJO DCT RUBAS Z154 TINOT) & ARR (LFML, LFMI, LFMA, LFMY, LFMV, LFMO, LFMT, LFTW, LFNG)
i.VIA (OKIVA P872 AJO DCT BEBEV DCT OKBON DCT RAPUR DCT TORTU)
j.VIA (OKIVA P872 AJO DCT OMEDA DCT MERLU DCT PIGOS) AND-THEN VIA (BARSO, BODRU, IDAVO, LOGNI, AGEVU)
k.VIA (OKIVA P872 AJO DCT OMEDA M622 LONSU) & ARR NICE_GROUP
l.VIA (OKIVA P872 AJO DCT OMEDA DCT MERLU DCT OMARD)
m.VIA (OKIVA P872 AJO DCT RUBAS DCT TINOT DCT AMFAC)
n.VIA (OKIVA P872 AJO DCT RUBAS Z154 TINOT) & ARR (LFML, LFMI, LFMA, LFMY, LFMV, LFMO, LFMT, LFTW, LFNG)
o.VIA (OKIVA P872 AJO M622 PIGOS) AND-THEN VIA (BARSO, BODRU)
Operational Goal
LFMM FRA - Flow organization
Traffic via OMARD is also limited by LF2289
1.b. To bypass LFT44BZ; 1.c. To bypass (LFT44C1Z, LFT44C2Z)
1.o. FL180 from OKIVA to MERLU to stay below LFD540EZ, climb at MERLU
Remarks
DCTs: FRA DCTs, LFFRASE
ATC Unit

LFMMACC

NAS/FAB

LF

Release Date

29 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 🗙