VIS/RVR < 500 m or ceiling < 200 ftVIS ≤ 1 000 m or ceiling ≤ 500 ftVIS ≤ 2 000 m or ceiling ≤ 1 000 ftVIS > 2 000 m and ceiling > 1 000 ftNo usable dataRing — the TAF forecasts worse than the METAR; its colour is the forecast level (next 3 h, or the hour selected)⚡CB in the METAR or the TAF↑Wind/gust 4–10 kts↑↑Wind/gust 11–20 kts↑↑↑Wind/gust 21–30 kts↑↑↑Wind/gust 31–40 kts⚠Wind/gust 41–50 kts⚠Wind/gust > 50 ktsLight turbulence at the chosen FLModerate turbulenceSevere turbulenceSIGMET TURB in force at that level and hour — outlined and hatchedModel index (clear air + convective proxy), smoothed between its ~25 km grid points; darker shade = stronger — not an official aviation product. The hatched areas are turbulence SIGMETs: forecasters' bulletins, drawn over the index and never merged into it.Rain — blue light, green moderate, yellow heavy, red and magenta the convective cores, white hail likely (radar; satellite estimate where no radar)SIGMET TS / convective SIGMET in force — outlined and hatched, tap for the bulletinImages dated in the cartouche, the last six playable. Radar wherever a public composite exists — Europe, North America, Japan; everywhere else a satellite rain estimate, which holds the convective cores and loses the drizzle. Guidance, not an official aviation weather product.⇡Dashed — TAF forecast (+1/+2/+3 h)Route line — the typical track flown on this city pair over 7 days (ADS-B); turbulence is read along it. The alternate search keeps the direct routeDotted — typical track, too variable from day to day (or partly inferred) to be used: indicative only, the route line stays on the great circleNOTAM downloaded — readable offline · tap to openNOTAM not downloaded · tap to download
---
---
Layout — —
How to use
Decision support only. Does not replace your company's official briefing.
The flight line
Fill it once: every card below opens on these aerodromes
and times.
FLIGHTAF6
→
Airline + flight number (or a callsign, AFR006). Tap the proposed leg
to fill the route and times — check the cities first.
ROSTER
→
A switch in Settings (gear), Roster, shows or hides it. On, in the
app, tap ROSTER, then Use the phone calendar: once you allow it, the phone
calendar is read for today and tomorrow at each opening, and a flight is recognised from its
two aerodromes and its time, with or without a flight number. Tap ROSTER to show the
legs. Off, nothing is shown and nothing is read. The other sources are in the
same place, under Other sources: share your roster file with the app or import it — the
.ics, or the HTML or CSV export of your crew portal (eCrew: My Schedule, Print, Export) —,
paste the schedule copied from the portal, or paste the calendar link (webcal) — downloaded
again at each opening. The legs are completed with
the flight number and times of the published schedule of the day, among the flights of your
airline; tap one to fill the route and the departure time. Several flights on the leg: tap one in
the list. Stays on this device only; Forget the roster clears the legs, and the phone calendar
is read again at the next opening.
Your roster is probably already in your phone
calendar, and the app never asks for your crew-portal login. On AIMS airlines (easyJet, Vueling,
Wizz Air, Volotea, flydubai…), the eCrew app can export your duties to the phone calendar: turn it
on there. RosterBuster, CrewLounge, BeCrew, Wingman, OffBlock or RosterX sync to the calendar too,
or paste RosterBuster's webcal link in Settings. Otherwise, export the roster as .ics and
share it with the app.
LFBO
→
A departure lists the departures of the day (UTC), filtered by the
destination if typed. Tap one to fill the route. Without a published schedule: destinations only,
no times.
FROMLFBO
→
ICAO or IATA code for FROM, TO and ALT. ⇄ swaps, Clear empties.
Leave ALT blank and one is proposed; tap it for two other choices.
HH:MMZ
→
UTC wheel times: take-off ≈ now + 1 h, arrival from the usual flight time on
the route. Tap to correct; clear to recompute.
→
Edit the route on the map.
★
→
Save an aerodrome, or the whole route (last star). Favorites and
Route bring them back.
The cards
NOTAM
→
NOTAMs by severity, filterable by phase and time.
WEATHER
→
METAR, TAF and runway wind.
MINIMA
→
Reports against the operating minima, phase by phase. No overall flight
verdict: the decision stays with the pilot.
MAP
→
Route, weather, wind, rain and turbulence.
TURBULENCE
→
Turbulence along the flight at your cruise level.
TIME / FUEL
→
Comparison of fuel per mile and speed by flight level.
Settings
⚙
→
Airline, base, aircraft, operation and default theme. Set once, kept on this
device, shared with Minima.
Route
Downloads the NOTAMs of the aerodromes along the way, for
reading offline.
FROMLFBO
→
FROM, TO, optional ALT. ⇄ swaps, Clear empties.
≥2400 m
→
Minimum hard runway length.
GO
→
Downloads the NOTAMs within ±200 NM of the great circle. Keep the app open.
LFBO
→
Tap to read its NOTAMs, even offline. Type a code in the empty box to add one.
MAP
→
Show the route on the map.
Aerodrome bar
ICAOLFBO
→
ICAO or IATA code, then the arrow. Route aerodromes are listed below — tap one.
★
→
Save the aerodrome or the route.
→
Airport info.
→
Aerodrome layout with the ground NOTAMs.
Filters
53CRITICAL
→
Tap to show that severity only; tap again to clear.
Critical — closed /
unserviceable
Caution — limited / work in progress
Information —
low priority
Z·UTC
--:--
→
NOTAMs active within ±1 h of that UTC time. Today / Tomorrow:
the whole day. No time: everything, upcoming included.
Ground12Departure4Flight7Arrival3
Filter by phase; combines with severity.
A NOTAM card
A1771/26QMXLCGROUND
CLOSED TWY : TWY W3 BTN TWY LP
Start 30 MAR 2026 21:30Z End 31 JUL 2026 03:30Z
Tap the Q-code or an underlined
abbreviation to decode it. A GROUND card opens the layout. Dates in UTC. A one-line summary is a
reading aid — the original text counts.
Other pages
ROUTE
→
Save the NOTAMs of a whole corridor.
FIR
→
World FIR map and en-route NOTAMs.
Weather
→
With a code typed, adds it on top; box empty, refreshes. The METAR age turns amber past 40 min, red past 60 min.
TAF
→
What applies at your time is in white; the rest of the METAR and TAF greys out.
METAR and TAF colours, read from the report alone — no
minima, no verdict.
1500Amber —
visibility or RVR ≤ 2 000 m, ceiling (BKN, OVC, VV) ≤ 1 000 ft, wind or gust ≥ 30 kt
TEMPOWhite —
what applies at your time: the METAR from 30 min before to 1 h after it (2 h with a trend), the
TAF groups in force
BECMGGrey —
not at your time; amber and red are dimmed
there
Runways
→
Head and cross wind per runway end: METAR now, and the worst of the TAF.
Runway in use
→
Estimated or observed (traffic; D-ATIS, US only). In green when observed, or single runway orientation and headwind
> 10 kt. An indication, never a clearance.
Day weather
→
Model forecast, not an aviation product — fly on the TAF.
Turbulence
Along your flight, at the hour you pass. Route and times are set on the home page.
Cruise FL
→
Pick the cruise level. ↻ Update recomputes.
→
The curve: light, moderate, severe, minute by minute — worst within 5 NM of your route. Tap to read a point.
→
Grey band: worst value within 20 NM at your level. Well above the curve =
turbulence forecast close by.
SIGMET
→
Turbulence SIGMETs in their own lane above the curve.
Model guidance, not an official product. Nothing drawn ≠ smooth air.
The map
Each dot's color shows the current observation (METAR):
Magenta —
visibility/RVR below 500 m or ceiling below 200 ft
Red —
visibility 1 000 m or less, or ceiling 500 ft or less
Amber —
visibility 2 000 m or less, or ceiling 1 000 ft or less
Green —
visibility above 2 000 m and ceiling above 1 000 ft
Grey — no
usable data
Ring
— the TAF forecasts worse than the METAR; the ring's color is the forecast level (next 3 h, or the
hour selected)
→
Tap a dot for the METAR, TAF, runway wind and minima. A larger dot marks a
favorite.
⚡
→
Cumulonimbus (CB) in the METAR or the TAF.
Runways under the code
08/26
→
Zoom in: each aerodrome's runways appear under its code, longest first. The
designator is the magnetic QFU, to the nearest 10°.
Runway end in green: runway
in use, shown when:
1.Observed — traffic on it, or the D-ATIS (US only), or
2.Single runway orientation and headwind > 10 kt — one
runway or parallels only, METAR less than 90 min old.
A mere estimate (preferential runway, ILS in light wind)
stays in the neutral tone: neutral does not mean not in use. No green without the aerodrome's
NOTAMs, since a guess blind to closures could name a closed runway. Premium. Worked out for up to 20
aerodromes in view; beyond that, only those already loaded turn green — zoom in. Hidden on the
Turbulence layer. An indication, never a clearance.
Layers (one at a time)
Wind
→
Surface wind arrows (wind or gust, whichever is stronger):
↑4–10 kt
↑↑11–20 kt
↑↑↑21–30 kt
↑↑↑31–40 kt
⚠41–50 kt
⚠above 50 kt
⇡dashed — TAF forecast (+1/+2/+3 h)
Zoom in on the map to compare the wind direction with
the runway headings. Offline, without the detailed map, runways appear earlier in the zoom as plain
bars: the real runway axis when the airfield plan has been opened before on this device, otherwise a
bar from the airfield database — true orientation and length; on single-runway airfields its position
is then approximate.
Turbulence
→
Forecast zones at the chosen FL and time; SIGMETs hatched; the route highlighted
where it meets them.
NOTAM
→
Shows which aerodromes have their NOTAMs on the device:
Grey — not
downloaded yet: tap to download the NOTAMs
Gold —
downloaded: tap to read the NOTAMs, even offline
Radar
→
Rain over the last hour (radar or satellite) and thunderstorm SIGMETs.
→
Edit the route: tap to add a point, ✓ keep, ✕ drop.
How the route is drawn
The green line takes the first of these that exists:
1.Your route points — the points you placed with the pencil, joined
by great-circle legs.
2.The typical track flown — over 7 days of ADS-B, the flight on
this city pair closest to all the others. Used only when it is reliable.
3.The great circle — the shortest route between the two
aerodromes.
Why some routes stay on the great circle. No typical
track is known for the pair (flown fewer than twice in the week, or no network); or an end of the
track was out of receiver coverage, so the aerodrome was only inferred from the callsign; or the route
changes too much from day to day. Over the North Atlantic, for example, the tracks follow the jet
stream of the day and spread 120 to 190 NM apart: last week's flight says little about yours. A
track known but not kept is still shown dotted, as a hint only.
While the pencil is on, the line goes back to the great circle, since you edit the direct route; the route
before your edit stays on screen, in a fainter green, under the dashed line.
Turbulence is read along the green line. The alternate search
and the flight time keep the direct route.
Guidance, not an official aviation weather product.
FIR map
Each FIR is colored by its en-route NOTAMs:
FIRRed
— don't go there: the whole FIR is closed, or a State warns of a danger (weapons, military activity) covering all of it
FIRAmber
— real restriction, but the FIR can still be crossed (contingency routes, ATC reduced or absent,
some operators or flights banned, a danger limited to some levels or to part of the FIR)
FIRGreen
— active NOTAMs with no access restriction (shown once you zoom in)
FIRBlue
outline — no restriction (shown when zoomed further in)
LFFF
→
Tap the FIR's name tag to read its en-route NOTAMs; the arrow brings you back to the
map.
→
Back to the world view.
→
Your route, drawn as on the route map: the FIRs it crosses at a glance.
Zoom in on the map to see every FIR and its name. Outlines are indicative.
Aerodrome layout
Red — closed
Amber hatched — closed for part
of the period
Amber — restricted, work in
progress
Green —
reopened
Now
→
Now / Today / Tomorrow: period drawn.
This NOTAM
→
This NOTAM / All ground NOTAMs / All: what is labelled.
+
→
Zoom. Tap a coloured surface for its NOTAMs.
Indicative, not for navigation. A missing surface can be reported.
Top of the screen
→
Online (red: offline — saved data shown with its UTC time).
Your operation, not today's flight — kept on this device and applied to every flight.
The Minima page reads exactly these settings, so setting them here sets them there.
Airline, base & aircraft
Posed on the flight line when the app opens — the number is all that is left to
type. Same list as the Flight box.
Fills Departure when the app opens on an empty line.
Roster
This device
Removes what Preflight Lens keeps about this device: its access
certificate and daily counters on the server, and every setting, favourite, route and offline pack
held here. Minima you entered stay — they carry no name and now count towards the shared consensus;
write to contact@preflightlens.com to have them removed.
Settings unavailable — the settings module could not be loaded.
Reconnect and reopen this window.
Preflight Lens
1Operation
2Aircraft
3Equipment
4Terms
Welcome aboard
Enter your flight number.
NOTAM, METAR and TAF are filtered according to your departure and arrival times.
VIS / RVR against your minima.
Check the turbulence along your route.
Step 1 of 4 · Operation
Your operation
The framework decides which rules are applied — and which boxes exist. The airline and the
home base are posed on the flight line each time the app opens.
Regulatory framework
Airline optional
Home base optional
Step 2 of 4 · Aircraft
Your aircraft
Picking a type fills the category, the wind limits and the equipment with typical values for
the family. Every value stays editable — yours is the one kept.
Wind limits aircraft data — gust included, on the QFU flown
Step 3 of 4 · Equipment
Equipment & approvals
Nothing here is a minimum — it decides which minima may be credited. Company floors only
raise a result that would come out below them.
Aircraft & crew
Company approved minima OM-B floors — leave empty if none
Warning margins they never move a minimum
Step 4 of 4 · Terms
Before the first flight
Two acknowledgements, asked once on this device.
Tick both boxes to finish.
Choose alternate
NOTAMs are read for runway closures and ILS, approach-light and LPV outages at the
estimated landing time only — not fuel, ATC hours or PPR — and the runway lengths come from the
airfield database. Verify against your briefing: the alternate remains your choice, and you can
always type another one in the box.
