RAD restriction LF2262

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

LF2262

RAD Code

LF2262

Valid From

2601 [22 JAN 2026]

Valid Until

UFN

Point or Airspace

LUMAS

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. H24 1. j. H24 1. k. H24 1. l. H24 1. m. H24 1. n. H24 1. o. H24 1. p. H24 1. q. 21:30-05:00 (20:30-04:00) 1. r. 22:00-04:30 (21:00-03:30) 1. s. H24

Categorisation

S

Utilization
NOT AVBL FOR TFC
1.VIA LUMAS AND-THEN VIA LFFRASE EXC
a.VIA (LUMAS DCT OBLAD DCT EPOLO DCT RAPUR G374 BTA L146 MOULE) & ARR (LIRS, LIRJ, LIQS)
b.VIA (LUMAS DCT UNANA DCT STP DCT (RAPED, MERLU))
c.VIA (LUMAS DCT NIBIK DCT STP DCT (RAPED, MERLU))
d.VIA (LUMAS DCT NIBIK DCT NETUP DCT STP DCT (RAPED, MERLU))
e.VIA (LUMAS DCT NEVIX DCT NETUP DCT STP DCT (RAPED, MERLU))
f.VIA (LUMAS DCT NEVIX DCT ODIXU DCT ADITA DCT RAPED)
g.VIA (LUMAS DCT NEVIX DCT ODIXU DCT ADITA DCT STP DCT MERLU)
h.VIA (LUMAS DCT SOSUR DCT SECON DCT ODIXU DCT ADITA DCT RAPED)
i.VIA (LUMAS DCT SOSUR DCT SECON DCT ODIXU DCT ADITA DCT STP DCT MERLU)
j.VIA (LUMAS DCT MAXIR)
k.VIA (LUMAS DCT NEVIX DCT MAXIR)
l.VIA (LUMAS DCT NEVIX DCT ODIXU DCT MAXIR)
m.VIA (LUMAS DCT SOSUR DCT SECON DCT ODIXU DCT MAXIR)
n.VIA (LUMAS DCT SOFFY)
o.VIA (LUMAS DCT SOSUR DCT JUSQO)
p.ARR (LFML, LFMI, LFMA, LFMY, LFMV, LFMO, LFMT, LFTW, LFNG, LFMQ, TOULON_GROUP)
q.VIA (LUMAS DCT NOSTA) & ABV FL245 AT (LUMAS DCT NOSTA)
r.VIA (LUMAS DCT LUSOL DCT OKTET DCT IRMAR) & ABV FL245 AT (LUMAS DCT LUSOL DCT OKTET DCT IRMAR)
s.VIA (LUMAS DCT PUZQU)
Operational Goal
LFMM FRA - Flow organization
1 b. if via MERLU: to bypass LFD54A2Z
1 c. to bypass LFD54A3Z
1 d. to bypass LFD54A1Z, LFD54A4Z, LFD540WZ
1 e, k. to bypass LFD54BSZ
1 f, g, l. to bypass LFD54NZ, LFD54NRZ
1 h, i, m. to bypass LFD54BNZ
1 q, r. Night-time fuel-saving route
1s. Change from GAT to OAT at PUZQU
ATC Unit

LFMMACC

NAS/FAB

LF

Release Date

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