Every feature of the app, explained the way a crew briefing would.
Nimble Preflight — Pilot's Complete Guide · Edition 1, July 2026 · Covers app version 1.0.0 · © 2026 Nimble Aero.
Nimble Preflight is NOT an Electronic Flight Bag (EFB) and is NOT certified for navigation. All data is FOR SITUATIONAL AWARENESS ONLY. Verify against official sources before operational use.
Unauthorized reproduction, modification, or commercial distribution of this manual or any revisions is strictly prohibited.
Data sources: NOAA Aviation Weather Center · FAA NMS-API · Deutscher Wetterdienst (DWD) / WAFC London & Washington · ECMWF (CC-BY-4.0) · Flightradar24 · NOAA Solar Calculator · OurAirports · Natural Earth.
Fourteen feature guides, in the order a pilot meets them.
How the app is built, how you move through it, and how to make it open where you want.
↑ ContentsOne place for the whole pre-flight picture
Nimble Preflight is an independent aviation reference tool that gathers weather, NOTAMs, advisories, charts, flight tracking and a full set of pilot calculators into a single, fast, offline-capable app. It is built to sit beside your official briefing workflow — never to replace it.
Think of it as the app you open in the crew room, on the bus, at the gate: everything you want to glance at before you ever touch a certified source is one or two taps away, and most of it keeps working when the signal doesn't.
The line that never moves. Everything in the app is for situational awareness. It is not an Electronic Flight Bag, not a certified weather briefing source, and not a navigation or operational-planning tool. Always obtain an official briefing before any flight.
The very first time you open the app, two screens appear in order and never again:
One frame around every screen
Almost every screen in the app renders inside the same slim header. Learn it once and you always know where you are, what time it is in Zulu, and how to get to the menu.
Why the Zulu clock is always there. Every report you read — METAR, TAF, NOTAM, advisory — carries a Zulu timestamp. Keeping the current Zulu time in the header means you can judge the age of anything on screen at a glance, without converting from local time.
What this foundation makes possible
Before any single feature, the app itself gives you a way of working. Here is what the shell, the navigation and the global settings let a pilot actually do.
Combine a personal Watchlist with the Dashboard grid so the airports and tools you use every trip are always in the same place.
From the Dashboard, every one of the 21 modules is a single tap; from home, the bar covers your three most-used actions.
Start on the Watchlist for a weather-first day, or on the Dashboard for a calculations-first day — your call, changed in seconds.
Airport data, runway geometry, VOLMET and calculators need no signal; cached weather stays visible and honestly aged.
The voice-briefing button reads raw reports aloud, prefixed with a clear "not an official briefing" reminder.
Three text sizes adapt the whole app to a dark flight deck, reading glasses, or a bright ramp.
The feedback form routes typed, module-tagged reports directly to the pilot who builds the app.
A permanent UTC clock in the header lets you judge the age of any report without doing time math.
Make the app open where you work
The single most useful thing to set up first: which screen greets you on launch. By default the app opens on the Airports Watchlist. If you spend more time in the tools, point it at the Dashboard instead.
Good to know — the drawer follows your choice. The Home Screen entry in the menu isn't fixed to the Watchlist: it goes to your landing screen. Set the Dashboard as your landing page and Home Screen takes you to the Dashboard too — one consistent "home" everywhere.
| Pick… | If your day looks like… |
|---|---|
| Watchlist (default) | Weather-first. You watch a set of airports and want raw METAR/TAF/NOTAM counts the instant the app opens — line flying, standby, monitoring a network. |
| Dashboard | Tools-first. Your day is calculations and decoders (Limitation, Tankering, SNOWTAM, Wind Component) and you'd rather start on the grid. |
Three global preferences worth knowing early
Most settings belong to individual features (and are covered in those guides). Three of them, though, change how the entire app looks and behaves.
Under Visual Preferences, Text Size offers S / M / L (default M) and rescales the whole interface — smaller for a dense overview, larger for a dark cockpit or reading glasses. Save to apply.
Under Privacy, Send crash reports (on by default) shares anonymized diagnostics that help fix problems fast. Its subtitle states the rule plainly: "Share anonymized diagnostics to improve reliability. Opt-out applies going forward." Turn it off any time — the change applies from that point on.
At the bottom of Settings, App Version shows the exact build you're running — the first thing to quote if you ever send feedback about a bug.
Saving works the same everywhere. Settings don't apply until you tap SAVE. While you have unsaved edits the bar reads ● UNSAVED CHANGES; after saving, ✓ PREFERENCES SAVED. (Full Settings coverage — data, watchlist, aircraft profiles, backup — is in the Settings & Backup guide.)
Announcements & feedback
The Announcements entry in the menu is an in-app news feed from the developer — new features, data-source notes, known issues. A badge counts unread items, so you'll notice when something new lands without leaving the app.
Because the app is built by a working pilot, feedback isn't a black hole. Open Send Feedback, then:
Most useful bug reports include the App Version from Settings and the exact screen and airport/ICAO involved — it turns a hunt into a fix.
Limits, habits & the safety frame
Every feature guide in this series inherits this frame. Individual features add their own specific disclaimers where they matter (charts, AI-free decoders, flight tracking, calculators) — but this one is always in force.
Built for pilots. By a pilot. Next in the series: the Airports Watchlist — your home base.
Your home base: the airports you care about, their raw weather and notice counts.
↑ ContentsAnatomy of the Watchlist
The Watchlist is the app's home screen. It holds the airports you fly to — up to a hundred of them — and shows each one's raw METAR, raw TAF and active NOTAM count without you opening anything.
What you will not find on a card — and why that matters. There is no colour-coded VFR/MVFR/IFR/LIFR dot and no decoded summary. The card gives you the raw report, exactly as published. A category dot is somebody's interpretation of a threshold; the raw group is the observation itself. Read the METAR, decide yourself.
What a pilot actually gets out of this screen
The Watchlist is deliberately boring in the best sense: it answers "what's the weather doing at the fields I care about?" in one glance, repeatedly, all day.
Base, common destinations, usual alternates, the technical stops your company keeps sending you to — up to 100 airports in one list.
Raw METAR and TAF side by side per field: spot the deteriorating trend across your route before you open anything.
The NOTAM count sits on every card. A field showing NOTAM (26) tells you where to spend your reading time.
Flying a multi-country roster? Group the list by country and jump to the block you need instead of scrolling a flat list.
Have the raw reports read aloud while you pack, drive or walk to the aircraft.
Cached reports stay on screen, tagged as offline, with their age shown — you always know how old the picture is.
Tap any card for the full airport page; the bottom bar reaches search, notes and the whole toolset.
METAR-only mode hides forecasts so twice as many fields fit on screen — useful on a long roster.
The five things you'll do every day
Swipe the card off the list. That's the only removal gesture, and the app reminds you of it if you ever hit the cap: "Maximum is 100 airports. Swipe-to-remove on home screen."
Tap anywhere on a card (outside the NOTAM chip and the speaker) to open Airport Detail — runway wind analysis, field data, communications, VOLMET coverage, sun times. Covered in its own guide.
Use the refresh control in the header, or pull down on the list. Everything reloads in the background and the data-age line updates.
A quiet 30-second cooldown. Refresh again within 30 seconds and nothing happens — no error, no greyed-out button, no message. It protects the shared weather sources from being hammered. If a refresh seems to do nothing, wait half a minute and try again.
Every element, and what it's telling you
| Element | Looks like | What it means |
|---|---|---|
| ICAO | EBBR | The airport, in the code every aviation source uses. |
| IATA badge | BRU | The commercial code — handy when your roster is written in IATA. |
| City / country | ZAVENTEM, BELGIUM | Confirms you added the field you meant, not a similar code. |
| NOTAM chip | NOTAM (26) | Active notice count. Tappable — goes straight to the NOTAM list. Shows NOTAM without a number when no count is available. |
| Speaker | 🔊 → ⏹ | Voice briefing. Red while speaking. |
| METAR panel | Raw observation | The report byte-for-byte. A shimmer means it's still loading. |
| TAF panel | Raw forecast | Same principle. Hidden entirely in METAR-only mode. |
| NO DATA | In place of a report | Nothing is available for that field right now — the app never invents or approximates a report to fill the gap. |
| [OFFLINE] | Appended to a report | You are reading cached data, not a fresh fetch. |
The one rule behind all of it. A missing report shows NO DATA — never a placeholder, never an estimate, never yesterday's observation dressed up as current. If you can see a report on a card, a source actually published it.
Two toggles change how the list feels
| Setting | Default | Effect |
|---|---|---|
| METAR Only Watchlist | Off | Hides the TAF panel from every card — "Hide TAF from airport cards on home screen". Roughly doubles how many fields fit on screen. |
| Group by Country | Off | Groups airports by country with flags and a per-country count — "Group watchlist airports by country with flags". |
Both live in Settings → Watchlist. Remember to tap SAVE.
Related, one level deeper. Persistent METAR Archiving and METAR History Depth (Settings → Data) don't change the Watchlist itself — they build the METAR archive you'll find inside Airport Detail.
The numbers and the habits
| Item | Value | What you see |
|---|---|---|
| Airports in the list | 100 | Dialog Watchlist Full — "Maximum is 100 airports. Swipe-to-remove on home screen." |
| Manual refresh | 1 per 30 s | Nothing at all — silent by design. |
| Stale-data threshold | 60 minutes | "Data is n minutes old. Verify current conditions from an official source." |
| Restoring a backup | 100 | A .NPF file holding more than 100 airports is refused cleanly, and the import is cancelled. |
What this screen is — and is not
The Watchlist shows raw METAR and TAF from NOAA's Aviation Weather Center and NOTAM counts from the FAA Notice to Air Missions System, displayed unmodified. That makes it excellent for awareness and useless as an authority: it is a mirror of a source, not the source itself, and it carries no guarantee of completeness or timeliness.
Built for pilots. By a pilot. Next in the series: Airport Detail — everything about one field.
Everything about one field on a single page — most of it working with no signal.
↑ ContentsOne field, top to bottom
Tap any Watchlist card and you land here. The page is one long scroll, always in the same order, so your eye learns the layout once and never hunts again.
What this page lets a pilot accomplish
This is the deepest single-field view in the app — and the part that stays useful when everything else needs a signal.
The METAR archive keeps recent observations in order. One glance shows whether the visibility is closing in or clearing — the thing a single report can never tell you.
The runway diagram draws the current wind across the actual runway layout. Before doing any arithmetic you already know which runway is favoured and roughly how much drift to expect.
The wind-component reference card sits right there — HW = V × cos(α), XW = V × sin(α) — with the ICAO reference, for when you want to check the maths by hand.
Phone numbers are tappable; frequencies are listed in MHz. Long-press any number to copy it.
The reverse VOLMET lookup tells you which stations read out this airport's weather, and on what frequency — before you ever need it in the cruise.
Sunrise and sunset in Zulu and local, computed on the device — including the polar cases most tools get wrong.
Runways, field data, frequencies, VOLMET coverage and sun times are bundled with the app. Airplane mode changes nothing for them.
Separate speaker buttons on METAR and TAF read the raw reports aloud.
The moves that matter
Tap an airport card on the Watchlist — anywhere except the NOTAM chip or the speaker button. To go back, use the arrow in the header.
Prefer a single current report instead of a trail? Turn Persistent METAR Archiving off in Settings — the block becomes CURRENT METAR with just the latest observation and its timestamp.
The TRUE / MAGNETIC trap — worth saying out loud. METAR winds are referenced to degrees TRUE. Tower and ATIS winds are given in degrees MAGNETIC. Any component you derive from a METAR is therefore in the true frame — make sure your reference matches your runway heading before you compare the result against AFM/POH crosswind limits. At high latitudes, where variation is large, the difference is not academic.
Scroll to VOLMET COVERAGE: every station that broadcasts this ICAO, each with an HF or VHF badge and its frequencies (kHz for HF, MHz for VHF). This is the reverse of the VOLMET directory — instead of asking "what does this station cover?", you're asking "who covers my field?".
The page in display order
Always the same seven blocks, always in this sequence.
| # | Section | What it gives you · empty state |
|---|---|---|
| 1 | METAR or CURRENT METAR | With archiving on: a scrollable archive of recent raw observations, newest tagged LATEST — empty state No archived reports yet. With archiving off: the single latest raw METAR with its timestamp — empty state No METAR available. Speaker button in both cases. |
| 2 | TERMINAL AERODROME FORECAST (TAF) | The raw TAF, unmodified. Empty state No TAF available. Speaker button. |
| 3 | Runway wind analysis | Scaled runway layout with the current wind vector and the source METAR. When the field has no bundled runway geometry: Runway data not available for [ICAO]. |
| 4 | ADDITIONAL INFORMATION | Country · Elevation in feet · Coordinates · Time Zone as UTC±h, DST-aware, marked (est.) when estimated. |
| 4a | COMMUNICATIONS | ATIS / AWOS / ASOS frequencies in MHz; phone numbers tap-to-call, long-press to copy. |
| 4b | VOLMET COVERAGE | Stations broadcasting this ICAO — name, HF/VHF badge, frequencies in kHz or MHz. |
| 4c | SUNRISE / SUNSET | Two cards: time in HH:MMZ plus an approximate local time. Polar edge cases display POLAR NIGHT or MIDNIGHT SUN instead of a time. |
| 5 | WIND COMPONENT FORMULAS | Reference card: HW = V × cos(α) | XW = V × sin(α), with V = wind speed in knots, α = wind direction − runway heading. Ref: ICAO Doc 9157. |
| 6 | OPERATIONAL NOTES | "Cross-check weather data with official aeronautical documentation before any flight decision." |
| 7 | ⓘ About This Data | A button at the very bottom opening the app-wide data & limitations sheet. |
Why the local time says "approximate". The time zone is derived from a DST-aware database and marked (est.) where it is an estimate. Sunrise and sunset are computed on the device from the field's coordinates. Zulu is the reference; treat the local figure as orientation, not as a published schedule.
The METAR archive is yours to size
| Setting | Default | Effect |
|---|---|---|
| Persistent METAR Archiving | On | "Save fetched METARs to local history log" — turns the METAR block into a trail instead of a single report. |
| METAR History Depth | 5 reports | How many observations the archive keeps per airport. Slider, 1 to 5. |
| CLEAR METAR HISTORY | — | Wipes the stored archive for all airports; confirms with METAR History Cleared. |
All three live in Settings → Data. Tap SAVE to apply.
Which depth should you pick? Five reports covers roughly the last few hours at most fields — enough to read a trend across a deteriorating afternoon. Reduce it only if you prefer a shorter scroll; the archive is local and small.
What survives with no signal
| Block | Offline? | Why |
|---|---|---|
| Runway wind analysis | ✅ Yes | Runway geometry ships with the app. |
| ADDITIONAL INFORMATION | ✅ Yes | Airport database bundled on device. |
| COMMUNICATIONS | ✅ Yes | Frequency data bundled on device. |
| VOLMET COVERAGE | ✅ Yes | The VOLMET directory is bundled, not fetched. |
| SUNRISE / SUNSET | ✅ Yes | Computed on the device from coordinates. |
| METAR / TAF | ⚠️ Not guaranteed | These come from the network. Cached values may still be shown, tagged [OFFLINE] — but there is no guarantee a report is available offline. |
Where this page stops
Airport Detail is a reference page. It presents published reports unmodified, geometry from a bundled database, and two astronomical figures computed locally. It performs no aeronautical decision-making, offers no performance calculation, and asserts nothing about the suitability of a runway.
Built for pilots. By a pilot. Next in the series: NOTAMs — airport and FIR.
Aerodrome and FIR notices, displayed as issued, with every badge explained.
↑ ContentsAerodrome notices and FIR notices
Nimble Preflight splits NOTAMs the way your briefing does: what affects a specific aerodrome, and what affects the airspace you'll cross. Both come from the FAA Notice to Air Missions System and are displayed as issued.
| Screen | Header shows | How you get there |
|---|---|---|
| Airport NOTAMs | The ICAO, with the IATA code underneath | Tap the amber NOTAM (n) chip on any Watchlist card. |
| FIR NOTAMs | FIR NOTAM | Pilot Dashboard → the FIR NOTAMs tile. |
| From the Watchmap | LFPG NOTAM (your ICAO) | Tap an airport dot on the map, then the NOTAM 26 chip in the sheet that opens. |
Same screen, three doors. The view you reach from the Watchmap is the identical airport NOTAM screen — same count, same filter, same cards. Only the header differs. Back returns you to the airport sheet, still open on the map.
The airport NOTAM screen, top to bottom
What this gives a pilot
NOTAMs are where the surprises live. The value is triage: knowing which notices deserve your attention, and being able to reach the original message in one tap.
The count on each Watchlist card tells you where the notices are piling up. Read the field with thirty before the field with three.
Colour-coded badges separate international, domestic, military and FDC notices before you read a word of text.
Set a From/To in UTC and the list narrows to notices that overlap it — permanent ones always stay visible.
RAW opens the complete ICAO text with its Q/A/B/C/D/E/F/G lines, selectable for copying.
Long-press any card and the full NOTAM goes to your clipboard — ready to paste into a report or a message.
Add the FIRs along your route and their notices accumulate into one searchable list.
A keyword box scans notice text, numbers and FIR codes at once — find every mention of a navaid or a runway.
Notices that carry a polygon offer VIEW ON MAP — geography beats coordinates in a text block.
Every badge, in order
Each card packs a lot into two collapsed lines. Here is what every element means, top-left to bottom-right.
First on the card, when the notice carries a classification. The colour is the fastest filter your eye can apply:
International — the common case at most aerodromes.
Domestic distribution.
Military.
Flight Data Center — regulatory notices, including procedure amendments.
If a notice carries no recognised classification, no badge is drawn at all.
| Element | Looks like | What it tells you |
|---|---|---|
| ID chip | A2398/26 | The NOTAM number — what you quote when referring to it. |
| Age badge | 1hr · 4d | How long ago the notice was issued. Hours under a day, then days. A fresh notice is a notice worth reading first. |
| Validity row | 09 JUL 26 07:21Z → 09 JUL 26 16:00Z | Start and end, in Zulu. A permanent notice reads PERM in place of the end. |
| Schedule block (D line) | Amber block with a left bar | The active schedule inside the validity window. Only appears when the notice has one — and when it does, it is the line that decides whether the notice bites during your slot. |
| Body text | Monospace, 2 lines | The notice itself (item E), truncated until you expand. |
| F/G limits block | Purple block with a left bar | The vertical limits, shown as raw text from the message. On airspace notices this decides whether it concerns you at all. |
| Chevron | ⌄ / ⌃ | Collapsed or expanded. |
Tapping anywhere on the card header opens a drawer underneath with up to four extras:
The gesture nothing advertises: long-press to copy. Press and hold any NOTAM card and the full notice — its number and its complete text — goes straight to your clipboard. You'll feel a haptic tap and see NOTAM copied to clipboard. There is no button or icon for this anywhere on screen, and it works on both the airport and FIR screens.
RAW NOTAM
Every notice with raw text offers a RAW chip in its expanded drawer. It opens a dedicated page titled RAW NOTAM, with the notice number underneath and its classification as a pill.
Above the message, a card of labelled rows — each one omitted entirely when the notice doesn't carry that field:
| Row | Contains |
|---|---|
| LOCATION | The ICAO location of the notice. |
| FIR | The Flight Information Region affected. |
| ACCOUNT | The issuing account. |
| EFFECTIVE | Start, with a four-digit year: 12 MAR 2026 08:00Z. |
| EXPIRES | End, same format. |
| SCHEDULE | The D-line schedule, if any. |
| Q-CODE | The selection code, e.g. QMXLC. |
| TYPE | The notice type. |
Below the metadata, the complete ICAO message in monospace on a dark panel — including the Q line and items A) through G) as published. The text is selectable: press and drag to select any part of it and copy exactly what you need.
Why the raw view exists. The published message is the authoritative artefact — the one your operator, your authority and any subsequent investigation will refer to. Everything the app draws around it is there to help you find it faster, never to replace it.
Narrow the list to the hours you're flying
Chosen values display as 12 MAR 26 0800Z. If you set a From that is after your To, the app refuses with "From" must be before "To" and keeps the panel open.
The bar collapses to a single line showing your window — ⏱ 12 MAR 26 0800Z — 12 MAR 26 1800Z — beside a pill reading 4 of 37. A small ✕ clears the filter and restores the full list.
It keeps every notice whose validity overlaps your window. Two deliberate exceptions:
If your window matches nothing, the screen says so and reminds you of the first rule: No NOTAMs in this time window · Permanent NOTAMs are always shown above.
The two numbers work together. The heading always shows the field's full total — Active NOTAMs (32) — while the pill spells out the relationship: 7 of 32. One tells you how many notices the aerodrome has, the other how many your window keeps.
Read the caveat while you're choosing. The filter disclaimer — "Filter based on published effective dates. Verify complete NOTAM coverage with your approved briefing provider." — sits inside the expanded panel, below the Apply button. Once you apply, the panel collapses and the line is no longer on screen. It applies just as much then.
Building an airspace picture
The FIR screen works by accumulation: you add regions one at a time and their notices merge into a single list you can search.
If nothing happens when you search. The box silently ignores anything that isn't 2 to 4 letters, A–Z — no error message is shown. A typo with a digit or a five-letter entry simply does nothing. Check the code and try again.
Under your FIR chips, a line summarises the state: the total notice count, how many FIRs are loaded, how long ago you refreshed (just now, 5m ago, 2h05m ago), CLEAR ALL, and a refresh button.
The Filter by keyword… box scans four things at once — the notice text, the raw text, the notice number and the FIR code — and keeps anything that matches. It's the fastest way to answer "is there anything about this navaid, this runway, this danger area?" across several regions at once.
The date/time filter works exactly as on the airport screen, and both filters combine.
Opening FIR NOTAMs from Brief. If you reach this screen from the Brief module, it temporarily shows Brief's FIR list instead of your own. Going back restores your list. There's no on-screen indication while it's swapped, so if your usual FIRs look wrong right after using Brief, that's why — go back once and they return.
How old is what you're reading?
This is the most important section in this guide. The two NOTAM screens tell you about data age in different ways, and one of them tells you much less than the other.
Under the source line, Last synced: … carries a dot whose colour encodes the age:
Just now or 3 min ago — effectively live.
Recent, but worth a refresh before a decision.
From 31 min ago through 2 hr 15 min ago to > 1 day ago. Treat as historical.
Not yet synced.
And when the app had to fall back to stored data because the network failed, a yellow banner appears above everything: OFFLINE — Showing cached data from 23 min ago, and the source line switches to its [OFFLINE] variant.
Freshness lives in the status strip. The FIR screen reports data age as text beside your FIR chips — just now, 5m ago, 2h05m ago — rather than as a banner. It only advances when a fetch actually brought back newer data, so it will not reset itself on a failed refresh. Read it before you work the list, and use the refresh button when it has drifted.
One toggle, two reading styles
| Setting | Default | Effect |
|---|---|---|
| Expand NOTAMs by Default | Off | "Show full NOTAM text when opening" — every notice arrives already open instead of truncated to a couple of lines. |
In Settings → NOTAMs. Tap SAVE.
Which suits you? Collapsed (default) is faster on a field with thirty notices — you scan, then read. Expanded suits short lists you intend to read fully. Changing the setting affects the next screen you open, not the one already in front of you.
Where these screens stop
Both screens are a reading surface over a third-party feed. They fetch notices and display them; they do not certify coverage, do not guarantee a feed is complete or current, and do not replace the NOTAM section of an official briefing.
Built for pilots. By a pilot. Next in the series: Advisories — SIGMET, AIRMET and the hazard map.
A worldwide directory of meteorological broadcasts, bundled with the app.
↑ ContentsThe radio fallback, catalogued
VOLMET is meteorological information broadcast continuously to aircraft in flight — a voice loop of aerodrome weather, transmitted on HF for oceanic and remote areas and on VHF around terminal areas. Nimble Preflight carries the directory: which station broadcasts which airports, on which frequencies, and when.
Know exactly what the app gives you. This screen is the catalogue, not the broadcast. The weather itself comes over the radio, from your receiver. What the app answers is the question you can't answer from memory at 0300Z: "who reads out this field, and on what frequency?"
The station list ships inside the app — there is no server call behind this screen. That pairing is deliberate: the moments you actually reach for VOLMET are the moments you have no data connection. Mid-Atlantic, out of ATIS range, datalink unavailable. The directory works in airplane mode because it was never online to begin with.
Anatomy of a station card
Open Volmet from the Pilot Dashboard. Stations are grouped by region, each group headed by the region name and a count.
What a pilot gets out of it
Note the HF VOLMET stations covering your destination and alternates before you lose VHF coverage — while you still have time to write them down.
Type an ICAO and find every station that broadcasts it. You don't need to know which station serves which region.
Working VHF in a terminal area? Filter to VHF. Planning long-range HF? Filter to HF. The count updates as you filter.
Descending toward a field still out of ATIS reach, VOLMET often carries it — the directory tells you where to listen.
Stations are grouped by region with a count on each header — useful when you're building a picture of an area rather than chasing one field.
The whole directory is bundled. Airplane mode, no signal, mid-ocean — it behaves identically.
From an airport's own page, the VOLMET COVERAGE block answers the reverse question: who broadcasts this field?
When a station transmits in another language, the card says so — worth knowing before you commit to copying a report.
Three ways to find what you need
The same search box also accepts a station name, a location or a region — useful when you know roughly where you are but not which station serves the area. If nothing matches, the screen says so plainly: No stations matching your search.
A habit from long-haul. Copy the HF frequencies for destination and alternates onto your flight log before departure. Reading them off a phone at cruise is possible; having them already written is better.
Every field, and the ones that stay hidden
| Field | Shown as | Meaning |
|---|---|---|
| Station name | Plain text | The broadcast identity you'll hear. |
| Type badge | HF / VHF | Which band. HF for long-range and oceanic, VHF for terminal-area coverage. |
| Location | In capitals | Where the station transmits from. |
| Frequency header | FREQUENCIES (kHz) or OPERATIONAL FREQUENCIES | The first form is used on HF cards, the second on VHF cards. |
| Frequency chips | 5505 kHz · 126.4 MHz | kHz on HF, MHz on VHF. Multiple frequencies are common on HF. |
| Schedule: | Text line | Shown only when the broadcast is not continuous. No schedule line means continuous. |
| Language: | Text line | Shown only when the broadcast is not in English. No language line means English. |
| BROADCAST AIRPORT ICAOS | ICAO chips | Every field carried on that station's loop. |
Silence means "normal" — read the absences. Three fields only appear when something is different from the norm. No status badge = the station is active. No Schedule: line = continuous broadcast. No Language: line = English. Once you know that, a card with nothing extra on it tells you a great deal at a glance.
VOLMET coverage from an airport's page
The same data powers a second, quieter feature. On any Airport Detail page, the VOLMET COVERAGE block lists every station that broadcasts that field — name, HF/VHF badge and frequencies.
| You're asking… | Go to… |
|---|---|
| "Which airports does this station carry?" | Volmet — the directory (this guide). |
| "Who broadcasts my destination?" | Either: search the ICAO here, or open the field's page and read VOLMET COVERAGE. |
Both views read the same bundled directory, so they never disagree.
What bundled data means for you
The footer states the rule for this screen, and it is not decoration:
Built for pilots. By a pilot. Next in the series: Advisories — SIGMET, AIRMET and the hazard map.
SIGMET, AIRMET, GAMET, volcanic ash and tropical cyclone — list, map and decoded sheet.
↑ ContentsFive families, five colours
The Advisories tile gathers every in-flight hazard message the app carries. The screen header names them all: SIGMET · AIRMET · GAMET · VA · TC. Each family keeps one colour everywhere in the app — on the chips, on the cards, on the polygons.
Significant meteorological phenomena hazardous to all aircraft — thunderstorms, severe turbulence, severe icing, volcanic ash, tropical cyclone.
Phenomena hazardous chiefly to lighter aircraft and low-level operations — moderate icing, moderate turbulence, mountain obscuration, widespread reduced visibility.
Area forecasts for low-level flight, issued in plain-language abbreviated form.
Volcanic ash advisories, carrying the volcano name and position when the message provides them.
Tropical cyclone advisories.
Sources: Deutscher Wetterdienst (DWD) Data Server and NOAA Aviation Weather Center. Messages are displayed as issued.
What this gives a pilot
The list opens on everything currently in force — no route, no setup, no selection required.
One tap on SIGMET or AIRMET strips everything else away, with a live count on each chip.
Pin the regions along your route and the list keeps only their advisories — the fastest way to turn a world list into a route list.
The keyword box scans FIR codes, raw text, phenomena and volcano names at once — type ETNA and find every message that mentions it.
The map draws real polygons, so you can judge whether a SIGMET sits across your track or well off to one side.
The detail sheet shows a live countdown — 2h 05m left — refreshing itself every half minute.
The sheet expands codes into plain language: EMBD TS becomes Embedded thunderstorms, SEV MTW becomes Severe mountain wave.
Flight-level band, direction and speed of movement, and whether the phenomenon is intensifying, weakening or unchanged.
Header, filters, then the list
| # | Element | What it does |
|---|---|---|
| 1 | Title block | ADVISORIES with the family list underneath, and a refresh button that becomes a spinner while loading. |
| 2 | Add-FIR row | A short field hinted Add FIR — letters only, four characters maximum — and an ADD button. |
| 3 | FIR chips | One chip per region you've added, each with a ✕, plus CLEAR ALL. |
| 4 | SHOW ADVISORIES MAP | Opens the world map (§6). |
| 5 | Type chips | All · SIGMET · AIRMET · GAMET · VA · TC — each with a count badge. |
| 6 | Search field | Hinted FIR or keyword (e.g. GMMM LECM or ETNA). |
| 7 | Stats bar | How many advisories you're seeing, how many are hidden, how many FIRs are pinned, the source, and the data age. |
| 8 | The list | One card per advisory, non-expired first. |
They are mutually exclusive — picking one replaces the previous choice rather than adding to it. All applies no family filter. The number on each chip counts what you would actually see if you tapped it, so a chip showing nothing has nothing behind it.
A single line under the search field summarises the state, for example:
Turning a world list into your list
The field accepts 2 to 4 letters, A–Z only. Anything else — a digit, a five-letter entry — is silently ignored with no error message, as is a duplicate.
The keyword box does more than it looks. Your text is split into words and an advisory is kept if any word matches any of: the FIR code, the raw message text, a phenomenon code, a volcano name, or the message header. That means:
| Type this | To find |
|---|---|
| GMMM LECM | Everything in either of those two FIRs — separate words are ORed, not ANDed. |
| ETNA | Every advisory naming that volcano. |
| TS | Every message whose text or phenomenon codes mention thunderstorms. |
They stack: each one narrows what the previous one left. If a search returns nothing, work backwards — clear the keyword, then the FIRs, then set the chip back to All.
Refreshing. The refresh button carries the app's standard silent 30-second cooldown — tap it again too soon and nothing happens, with no message. Note too that a failed refresh when you already have data shows no error at all: the spinner simply stops and the previous list stays on screen. The age in the stats bar is how you tell.
Every element on an advisory card
| Element | Looks like | Meaning |
|---|---|---|
| Type badge | Icon + SIGMET | The family, in its colour, with an icon: storm for SIGMET, wind for AIRMET, layers for GAMET, volcano for VA, cyclone for TC. |
| FIR code | LECM | The region the message was issued for. |
| Sequence | #3 | The message's sequence number within that FIR. |
| Fetched stamp | 1435Z | When the app retrieved it, right-aligned. No colon in this format. |
| Validity | VALID 121200/121800 | The window, passed through exactly as the message states it. |
| EXPIRED | Red badge | Past its validity. The whole card is also dimmed. |
| Phenomenon chips | EMBD TS · SEV ICE | The coded phenomena, verbatim from the message. |
| Volcano line | ETNA (3743N01500E) | VA advisories only — name and position when provided. |
| Header line | WSSP31 LEMM 121130 | The WMO bulletin header, or the words RAW TEXT when the message has none. |
| Raw panel | Monospace block | The first two lines, then SHOW FULL TEXT ▼ to open it and COLLAPSE ▲ to close. Expanded text is selectable for copying. |
| Source line | Source: DWD/NOAA · Fetched 1435Z | Attribution and retrieval time. |
| VIEW ON MAP | Gold button | Only when the message carries a polygon. Opens the affected area. |
Expired advisories sink, they don't vanish. After every refresh the list is sorted so live messages come first and expired ones follow, dimmed and badged. If you have hide-expired switched on you won't see them at all — see §8.
The card does not show a flight-level band. Levels appear on the map labels and in the detail sheet, not in the list. In the list, the only altitude information is whatever the raw text itself contains — so expand the text when levels matter.
Seeing the shape of the hazard
SHOW ADVISORIES MAP opens a full-screen world chart titled ADVISORIES MAP, with every drawn advisory as a translucent polygon in its family colour.
Two things about this map that will save you confusion.
1. It plots SIGMET and AIRMET only. Advisories issued as GAMET, as dedicated volcanic-ash advisories or as tropical-cyclone advisories are not drawn here, whatever the toggles say. Note the distinction: a SIGMET whose phenomenon is volcanic ash does appear — you'll see VA CLD labels in SIGMET red — because it is a SIGMET. Filter the list to the VA family, though, and the map will be empty. That's its scope, not a fault.
2. Its toggles are independent of the list. The map has its own SIGMET/AIRMET switches, both on by default. Narrowing the list to AIRMET and opening the map still shows SIGMETs. Set what you want to see on the map, on the map.
There is no refresh control on the map — it uses the advisories already loaded, and fetches once by itself only if it was opened with nothing to draw.
The single-advisory zone view
The gold VIEW ON MAP button on a card opens a different, focused map: that one advisory's area, alone. Its header names the phenomenon — for a volcanic-ash advisory, a VOLCANIC_ASH badge beside the title VA ZONE.
A volcanic-ash advisory doesn't describe a single area — it describes an area moving through time. This view draws each forecast step as its own outline:
The observed cloud, at the time of issue.
Forecast position six hours on.
Twelve hours.
Eighteen hours.
A line at the bottom counts what's drawn — Volcanic ash · 4 zones — and reminds you of the controls: Pinch to zoom · drag to pan.
Three map views, three jobs. SHOW ADVISORIES MAP shows the whole world's SIGMETs and AIRMETs together. VIEW ON MAP on a card shows one advisory in detail — including the time steps a world view could never render legibly. And the Watchmap puts advisories alongside your route, your watchlist and the SIGWX picture.
The decoded view — and how to reach it
Where the sheet lives. The decoded sheet opens by tapping a polygon on a map — either the advisories map or the Watchmap's advisory layer. It is not reachable by tapping a card in the list; the card's VIEW ON MAP button opens a single-advisory map view instead. If you want the decoded breakdown, go through a map.
| Field | Example | Notes |
|---|---|---|
| Sequence | #FOXTROT 24 | The message's sequence identifier. Many issuing centres use phonetic letters rather than plain numbers — the sheet shows whatever the message carries. |
| Phenomenon | EMBD TS → Embedded thunderstorms | The code in large type with its plain-language name underneath, from a table of common phenomena. An unrecognised code simply appears twice. |
| Validity + countdown | Valid 121200 → 121800Z · 2h 05m left | A green pill while live, red when expired. It updates itself every 30 seconds while the sheet is open — leave it open long enough and you'll watch it flip to Expired in place. |
| FIR | LECM | The issuing region. |
| Levels | FL100/450 · TOP FL450 · SFC/FL100 | Read from the message text where possible, otherwise built from the structured fields. |
| Movement | MOV NE 05KT · STNR | Direction and speed, or stationary. |
| Evolution | INTSF (intensifying) | Expanded for you: NC (no change), INTSF (intensifying), WKN (weakening). |
| Observation | OBS AT 1200Z · FCST AT 1800Z | Whether the information is observed or forecast, and at what time. |
| Raw text | Monospace block | The complete message, unabridged, at the bottom of the sheet. |
Any field the message doesn't provide is simply not drawn — the sheet shows what exists rather than a grid of blanks.
One setting, three surfaces
| Setting | Default | Effect |
|---|---|---|
| Hide Expired Advisories | On | Removes advisories past their validity from the list, the advisories map and the Watchmap. |
It lives in Settings → Advisories. With it on, the stats bar tells you how many were removed — 5 hidden — so you always know the list is being trimmed. Turn it off to keep recently-expired messages visible for trend awareness.
The same setting behaves more cleverly on the Watchmap: with a timeline cursor set, an advisory is shown only while the cursor sits inside its validity window. Scrub forward and messages expire one by one; scrub back and earlier ones return. Switch the setting off and every advisory in scope is drawn regardless of time.
When validity can't be determined, the advisory is shown — never hidden. Some messages carry no usable window (certain area advisories, for instance). Rather than guess, the app keeps them visible on every surface. The consequence worth knowing: such an advisory looks identical to one with a confirmed live window, and there is no "validity unknown" marker. When timing matters, open the raw text and read the window yourself.
What the screen tells you when things go wrong
| State | You see |
|---|---|
| Loading, nothing cached | Fetching advisories from DWD/NOAA… under a spinner. |
| Fetch failed, nothing cached | FETCH FAILED with the reason, and a RETRY button. |
| Fetch failed, data already on screen | No message at all. The spinner stops and the previous list stays. Check the age in the stats bar. |
| Nothing matches | No advisories matching your search or No advisories matching current filters, with a green check icon. |
| Working from stored data | No banner. Cached advisories render normally; the age in the stats bar is the only indication. |
This screen mirrors two meteorological services. It parses alongside the message, never instead of it — the raw text is always one tap away, and the detail sheet shows it complete.
Built for pilots. By a pilot. Next in the series: Pilot Reports — what crews are actually encountering aloft.
Worldwide AIREPs — what crews are actually encountering right now.
↑ ContentsObservations, not forecasts
Everything else in this app comes from a model, a forecast or an official bulletin. Pilot Reports comes from crews in the air — AIREPs and PIREPs transmitted by aircraft actually encountering the conditions they describe.
That makes this the screen you check when the forecast and reality might be diverging. A SIGWX chart tells you where turbulence is expected. A pilot report tells you that at 2233Z, at FL370, at a specific latitude and longitude, an aircraft got moderate turbulence. Those are different kinds of knowledge, and the second one is the kind you can act on with confidence.
Reports arrive through the Deutscher Wetterdienst global AIREP stream and are displayed with their original message intact.
Use it the way you use the frequency. A ride report from the aircraft ahead of you is worth more than any forecast for the next twenty minutes. This screen is the same instinct, scaled to the world.
The screen
What a pilot gets out of it
Filter to Turb and see who has reported what, at which level, in the last hour.
An AIRMET says icing is possible; a pilot report says an aircraft got it. Very different weight in a decision.
Every card carries the reporting aircraft's flight level. A moderate turbulence report at FL240 may say nothing about FL370.
A colour-coded age chip on every card: green under an hour, amber beyond.
Expand a report and it gives decimal coordinates — enough to see whether it's on your track or two hundred miles away.
A dedicated Volcanic Ash filter — the reports you most want to know about before anyone issues anything formal.
The origin filter lets you focus on reports issued by one station rather than reading the world.
Every card carries the raw AIREP text, selectable for copying into a report or a message.
Every element on a card
First on the card, and the fastest read: how bad the crew said it was. The card's left accent bar carries the same colour.
Light.
Moderate, or light-to-moderate.
Severe, or moderate-to-severe. Read these first.
No severity in the message — not "no turbulence". The report may still describe something significant in its text; the intensity simply wasn't coded in a way the app could extract. Read the raw line.
| Element | Looks like | Meaning |
|---|---|---|
| Callsign | UAL1769 | The reporting aircraft. UNKNOWN when the message carries none. |
| Flight level | FL340 | Where the report was made. Always check this against your own level. |
| Age chip | 4m · 3h07m | How long ago it was processed. Green under an hour, amber beyond, grey when it can't be determined. |
| Phenomenon tag | TURBULENCE | What was encountered, colour-coded (see below). |
| Header line | UAUS31 KWBC 312230 | The bulletin header, or the words RAW TEXT when the message has none. |
| Raw panel | Monospace block | The first two lines, then SHOW FULL TEXT ▼ to open it and COLLAPSE ▲ to close. Expanded text is selectable. |
| Position (expanded) | 48.85°N, 2.35°E | Decimal coordinates, when the message carries a position. |
| Origin (expanded) | Origin: KWBC | The station that issued it. |
| Source line | Source: DWD AIREP · Parsed 4m ago | Attribution and processing time. |
The tags on the cards show the full token as transmitted; the filter chips at the top use short forms (Turb, TS). Same thing, two lengths.
Worked example. ARP UAL1769 3605N 08501W 2225 F340 TB MODERATE SK IC= — aircraft UAL1769, position 36°05′N 085°01′W, at 2225Z, flight level 340, turbulence moderate. The app pulls the callsign, level and phenomenon onto the card; the message stays underneath so you can read the rest yourself.
Two controls, in sequence
Six chips, mutually exclusive — picking one replaces the previous choice. Each carries a live count, and a chip with no number has nothing to show.
| Chip | Keeps reports of |
|---|---|
| All | Everything. |
| Turb | Turbulence. |
| Icing | Icing. |
| TS | Thunderstorms. |
| Wind Shear | Wind shear. |
| Volcanic Ash | Volcanic ash encounters. |
Type up to four letters and the list keeps reports whose originating station starts with what you typed. Two things to know:
There is no sort control, and no ordering by time. Reports appear in the order the source returned them. Don't assume the top of the list is the newest — read the age chips.
What the screen tells you
| State | You see |
|---|---|
| Loading, nothing cached | Fetching pilot reports from DWD… under a spinner. |
| Fetch failed, nothing cached | FETCH FAILED with the reason, and a RETRY button. |
| Fetch failed, data on screen | Nothing at all. The spinner stops and the previous list stays. The age in the stats bar is your only cue. |
| Origin filter matches nothing | No reports for KAWN + Try a different filter or tap "All" to see everything. |
| Phenomenon chip matches nothing | No Turb reports + the same suggestion line. |
| Genuinely nothing available | No active pilot reports + No pilot reports are currently available from DWD. |
| Working from stored data | No banner. Cached reports render normally; the age in the stats bar is the only indication. |
Refresh carries the app's standard silent 30-second cooldown — tap again too soon and nothing happens, with no message.
Age matters more here than anywhere else in the app. A METAR an hour old is still a useful picture of a field. A turbulence report an hour old describes air that has moved on. Read the green and amber chips, and treat anything amber as history rather than as a ride report.
How to weigh a pilot report
Pilot reports are observations by other crews, relayed through a meteorological service and displayed here as transmitted. They are not verified, not standardised between operators, and not a forecast of what you will find.
Built for pilots. By a pilot. Next in the series: WX Charts — the big picture.
Choosing the right chart
The WX Charts tile opens a five-tab screen. They are not variations on the same picture — each answers a different question, and knowing which one to reach for is most of the skill.
| Tab | Answers | Animated? |
|---|---|---|
| SIGWX | "What significant weather is forecast at cruise levels across my region?" | No — one chart per valid time. |
| WIND/TEMP | "What wind and temperature should I expect at my flight level?" | No. |
| ECMWF RAIN | "Where will the precipitation be over the next two days?" | Yes — play, scrub, four speeds. |
| SATELLITE | "What is the cloud actually doing right now?" | Yes — recent frames looped. |
| IWXXM SIGWX | "How does the significant weather evolve over the next two days, layer by layer?" | Yes — vector layers on a live map. |
Observation versus forecast. Only SATELLITE shows you what is happening. The other four are forecasts — issued by a world area forecast centre or produced by a numerical model. Keep that distinction in mind when they disagree.
What these charts let a pilot accomplish
The SIGWX chart for your area: jet streams, CB areas, turbulence boxes and tropopause heights on one sheet.
Pick the region, pick the flight level, read the barbs and temperatures — no scrolling through levels you're not flying.
Play the precipitation forecast forward and see whether a system reaches your destination before you do.
The infrared loop shows cloud-top temperature — the colder the top, the taller the build-up.
On the vector tab, switch off everything except icing, or turbulence, or jets — and read a clean chart.
Scrub from now to T+48 and watch hazards form, move and decay rather than reading one frozen snapshot.
Charts open in a viewer you can pinch and pan — read the small print on a busy sheet.
The vector SIGWX tab caches its frames and tells you plainly when you're looking at stored data.
The classic significant weather chart
The WAFS high-level significant weather chart, covering FL250 to FL630 — the sheet every long-haul briefing pack contains.
New to the symbology, or want a refresher? How to read SIGWX charts opens a built-in reference.
Pick the valid time that brackets your flight. A SIGWX chart is a snapshot at one hour, not a period average. For a long sector, look at the chart either side of your time over the area.
Upper winds and temperatures at your level
The level list is real, not generic. The app asks the source which flight levels exist for the region you picked, rather than showing a fixed list and failing on request. If a level you expect is missing, it isn't published for that region — not a fault in the app.
Two days of precipitation, animated
A precipitation-rate forecast from the ECMWF model, animated from now to T+48.
A SYNCED chip shows how fresh the data is; refresh has the standard silent 30-second cooldown. While frames download you'll see Loading 6/17.
This is a model, not a radar — the distinction is operational, not academic. The tab's own footer says it plainly: "ECMWF forecast - model output, not observed radar. Not for tactical avoidance. For pre-flight situational awareness only. © ECMWF, licensed CC-BY-4.0."
Use it to answer "will there be weather over my destination this evening?" — never to answer "how do I get around that cell?". Tactical avoidance is your onboard radar's job, and nothing else's.
If a region fails to load you'll see Could not load forecast for [region] or No frames available, with a Retry button.
The global infrared loop
A single global product — no region to choose. The colourised infrared mosaic plays over a pannable, zoomable basemap with the same controls as the rain tab: play/pause, four speeds, a scrubber and a frame counter. Each frame is labelled with its valid time.
Legend opens the Satellite IR Legend sheet, noting: "Source: Deutscher Wetterdienst (DWD). Cloud-top temperature (°C)."
A SYNCED chip carries the data age; refresh shares the 30-second cooldown.
Reading infrared like a pilot. The colours are cloud-top temperatures, not rainfall. Colder tops mean higher tops, and higher tops mean deeper convection — an area of very cold tops is telling you about vertical development you would want to avoid, even though the picture says nothing directly about precipitation.
Significant weather as switchable layers
The modern counterpart to the PNG chart: the same WAFS significant weather rendered as vector layers on an interactive map, steppable through time.
Toggle each one independently. This is the tab's real advantage over the printed chart: on a busy sheet, switching off everything except ICE turns an unreadable tangle into a clear answer.
| Badge | Opens |
|---|---|
| EXPERIMENTAL | SIGWX — Experimental: "SIGWX is for situational awareness only. NOT an approved weather briefing source. Source: WAFC London, redistributed by DWD." |
| ⓘ | IWXXM SIGWX — data: "Coverage: 85°N–85°S · FL100–600" |
Take the EXPERIMENTAL badge at face value. This tab is the newest rendering in the app and is explicitly not an approved briefing source. When it matters, cross-check what you see here against the SIGWX chart on tab 1 — same underlying product, different rendering path.
Coverage has edges. 85°N–85°S and FL100–600. Below FL100 and in the polar caps, this layer has nothing to say — an empty map there means "outside coverage", not "no hazard".
If data can't be loaded you'll see No SIGWX data available offline or Could not load SIGWX forecast, with a Retry button.
Who produced what you're looking at
| Tab | Attribution shown on screen |
|---|---|
| SIGWX · WIND/TEMP · SATELLITE | "Source: Deutscher Wetterdienst (DWD) Data Server. For situational awareness only. Not a substitute for official weather briefing." |
| ECMWF RAIN | "ECMWF forecast - model output, not observed radar. Not for tactical avoidance. For pre-flight situational awareness only. © ECMWF, licensed CC-BY-4.0." |
| IWXXM SIGWX | "© WAFC London / DWD — WAFS SIGWX · For situational awareness only. Not a substitute for official weather briefing." |
Built for pilots. By a pilot. Next in the series: Watchmap — everything on one chart.
Your airports, your route and the hazards on one chart, driven by a single Zulu timeline.
↑ ContentsEverything on one chart
The Watchmap is the app's synthesis screen. Where every other feature answers one question, this one puts the answers side by side — your stations, your route, the hazards and the sky — and lets you move all of them through time together.
It works in landscape. The Watchmap is the only screen in the app that rotates. Turn the phone sideways for a wider chart — labels shorten automatically to keep the bars readable.
What the Watchmap makes possible
Load a saved route and the great circle appears over the advisories and the SIGWX picture — the single view that tells you whether a hazard is on your track or beside it.
Scrub the timeline and the SIGWX, the satellite and the advisory validity all move together. Watch a hazard develop over your ETA rather than reading one frozen frame.
Five independent ages behind one chip. No guessing which layer is old.
Twelve toggles. Turn everything off except icing and your route, and read a clean chart.
Tap a station dot for its full weather page and NOTAM count, in a sheet over the chart.
Switch the satellite on and compare what is actually there against what was predicted.
Advisories, satellite frames and the SIGWX manifest are restored from disk at open — honestly aged by the chip.
Any advisory polygon opens the full decoded sheet with its live countdown.
Five sources, one dot — worst wins
This chip is the most important control on the screen. The Watchmap pulls from five independent feeds, and rather than show you five ages it shows you the worst one.
Every source is under 5 minutes old. The number shown is the age of the oldest of them: <1m, 12m, 3h, >1d.
How many sources are in that band, not the total. 2 aging means two sources are between 5 and 30 minutes old.
Also what you see when a source failed to load at all — see the warning below.
Nothing has been fetched yet this session.
Tapping the chip opens a small menu listing all five sources with their individual ages:
| Source | Covers |
|---|---|
| Weather | METAR/TAF for your watchlist and route airports. |
| NOTAM | Notices for the same set of airports. |
| Advisories | SIGMET and AIRMET polygons. |
| Satellite | The infrared frames. |
| IWXXM SIGWX | The vector significant-weather frames. |
Ages read Just now, 12 min ago, 2 hr 15 min ago, > 1 day ago, or Not yet synced. The rows are informational — tapping one just closes the menu. It updates itself even while open.
Red can mean "old" — or it can mean "never arrived". This screen never shows an error.
The Watchmap deliberately has no error message, no dialog and no failure badge. If a source cannot be fetched, it simply has no age — and the chip counts it as stale. So 1 stale may mean one layer is half an hour old, or it may mean that layer failed entirely and is not on your map at all.
The habit that matters: when the chip is red, tap it. A source reading Not yet synced after a refresh is a source you are not seeing — and an empty area of map is then telling you nothing, rather than telling you there is no hazard.
The refresh button beside the chip fetches all five in parallel — one failing source never blocks the others. It carries the app's usual silent 30-second cooldown and is never greyed out.
Two rows of pills, twelve switches
Your watchlist airports as green dots. ICAO labels appear as you zoom in. Tap a dot for the airport's full page in a sheet.
SIGMET polygons, with labels from zoom 4 up. Tap one for the decoded detail sheet.
AIRMET polygons, same behaviour.
The great circle in magenta with its airports. The pill isn't drawn at all until you load a route.
The vector significant-weather overlay. Turning it on also reveals the Tier-2 row.
The infrared overlay — the only layer that starts switched off. Switching it on adds an opacity slider (§6).
All six start on. They appear only while the Tier-1 IWXXM pill is on; switch IWXXM off and the whole row disappears, keeping your choices for when you switch it back.
Toggling is instant — nothing is re-downloaded. Every one of the twelve switches redraws from data already on the device. Declutter as aggressively as you like: it costs nothing and never makes you wait.
One cursor, three layers
The slider at the bottom is what makes the Watchmap more than a stack of overlays. Drag it and three things move together.
| Layer | What the cursor does to it |
|---|---|
| IWXXM SIGWX | Shows the forecast frame for that time. |
| SAT | Re-snaps to the satellite frame nearest the cursor — or hides, if none is close enough (§6). |
| SIGMET / AIRMET | With Hide Expired Advisories on, each polygon is drawn only while the cursor sits inside its own validity window. Scrub forward and advisories expire one by one; scrub back and earlier ones return. |
| WATCH · ROUTE | Unaffected — your airports and your track are fixed geography. |
The line above the slider tells you where you are: T+48 · 10 JUL 12:00Z (15/15) — the forecast step, the valid time in Zulu, and your position in the sequence. In landscape the date is dropped to save room. With IWXXM off, the label shows just the time the cursor represents.
Honest about time, not just about place
Switch SAT on and the infrared imagery is drawn under the other layers, with an opacity slider so you can balance it against them.
Satellite imagery is an observation at a moment, while the timeline cursor often points into the future. Rather than stretch old imagery across a forecast, the Watchmap applies a strict rule:
| You see | Meaning |
|---|---|
| SAT 14:15Z | Imagery is available within 30 minutes of the cursor, and that's its time. |
| SAT — no imagery | No frame is within 30 minutes of where the cursor sits. Nothing is drawn, and the opacity slider disappears — there is nothing to adjust. |
Why this matters more than it looks. Scrub the timeline six hours into the future and the satellite goes quiet. That is the app refusing to show you six-hour-old cloud as though it described the forecast hour. If you want the current picture, bring the cursor back to now.
And the reverse trap: an area with no imagery is not an area with no cloud.
The opacity slider runs from 20% to 100% and shows its value beside it. It is the one Watchmap setting that is remembered between sessions.
Your track on the weather
No routes saved yet? The app says so — No saved routes found. You can create one in the Brief section. — and offers Go to Brief to take you there.
Ringed magenta markers — always drawn on top, never hidden behind another symbol.
Orange.
Magenta — the fields you ticked in the Brief.
Green. A corridor airport already on your watchlist keeps its green label rather than being redrawn magenta.
Loading a route pre-warms its weather. The app quietly fetches METARs, TAFs and NOTAMs for every airport on the route as soon as you load it — so tapping any of them later opens instantly, even offline.
Two things worth knowing before you rely on it
Tap the attribution line at the bottom — the whole row is a button — and Map legend & sources opens, subtitled Layers currently available on this map.
Three blocks, in order:
Then SOURCES & DISCLAIMERS names the provenance of each product in full — satellite, SIGWX and advisories — closing with "For situational awareness only. Not a substitute for an official weather briefing." and FOR SITUATIONAL AWARENESS ONLY.
The satellite scale is DWD's own image, not a redrawing. The app reproduces the published legend rather than approximating it, so the colours you read here match the colours the service defined — no interpretation in between.
| Restored at open | Reset at open |
|---|---|
| Advisories from disk | Every layer toggle — back to the defaults |
| Satellite frames from disk | The loaded route — you must load it again |
| SIGWX frames from disk | The timeline cursor — back to "now" |
| All five freshness ages | — |
| Satellite opacity | — |
The Watchmap does not remember your setup. Turn SAT on, switch ROUTE off, load a route — close the screen and all of it is back to default next time. Opacity is the only preference that persists. Worth knowing before a long briefing: build your view, and finish the job before you leave the screen.
Offline, it still opens with something to show. Advisories, satellite frames and the SIGWX manifest come back from the device, and the freshness ages are restored with them — so a map opened in airplane mode is honestly labelled rather than blank. Your watchlist dots are always rebuilt live, so they are there regardless.
What this map is not
The Watchmap draws published data over a schematic basemap. It has no navigation database, no terrain, no airspace structure, no traffic and no aircraft position. It is a briefing aid, and the great-circle line is a drawing, not a flight plan.
Built for pilots. By a pilot. Next in the series: Brief — building the route and the briefing pack.
Build a route, gather everything the app knows about it, export a briefing pack.
↑ ContentsOne route, five views, one pack
Every other feature in the app answers a question about a place or a phenomenon. Brief answers a question about a flight: given this departure, this destination and these alternates, what does the app know?
| Tab | Holds |
|---|---|
| ROUTE | Where you build it: airports, corridor settings, the great-circle result, and the buttons that generate everything else. |
| AIRPORTS | Weather for departure, destination, alternates and the corridor fields you selected. |
| FIR NOTAMS | Notices for the regions your route crosses. |
| ADVISORIES | SIGMET, AIRMET and the rest, for the route. |
| CHARTS | The significant-weather charts for the regions and levels you chose. |
What Brief deliberately does not do — and why it matters. There is no time en route, no fuel figure, no weight, no ETA. Not because they'd be hard, but because a supplementary reference tool producing numbers that look like flight-planning outputs is exactly how a pilot ends up cross-checking the wrong document. Distance and bearing are geometry; everything downstream of them belongs to your OFP and your dispatch release.
What Brief lets a pilot accomplish
Great-circle distance in NM or KM with the initial true bearing — a sanity check against the OFP before you read another line of it.
Set a corridor width and the app lists every airport inside it that meets your runway criteria — the en-route options you might not have thought of.
Set a minimum runway length so a 600 m grass strip doesn't clutter a widebody's corridor list.
The FIRs along the great circle are suggested for you, and you can add any the route logic missed.
One tap fills four tabs: weather, FIR notices, advisories and charts, all scoped to this flight.
A PDF you can send to the other crew member, keep for the trip, or read offline.
Up to fifty, reloadable in one tap — and loadable straight onto the Watchmap.
VIEW ON MAP puts the same route on the Watchmap, under the advisories and the SIGWX picture.
The ROUTE tab, step by step
Three more controls sit alongside: LOAD ROUTE and SAVE ROUTE for your saved set, and RESET to clear everything and start again.
Deciding which fields count as "along the way"
The corridor is a band either side of the great circle. Anything inside it that passes your filters becomes a candidate for the brief.
| Setting | Default | What it changes |
|---|---|---|
| Corridor Width | 50 NM | How far either side of the track to look. Widen it on a sector with few fields; narrow it when the list is overwhelming. |
| Min Runway | 0 (no filter) | The shortest runway you'd consider. Enter it in FT or M — the unit toggle is beside the field. |
| Include Helipads | Off | Add helipads to the candidates. |
| Include Military | Off | Add military fields. |
Collapsed, the card summarises your choices as chips — ±50 NM, 6000 FT, and HELI or MIL when those are on — so you can see the settings without opening the panel.
Set the runway filter to your aircraft, not to the airport. The corridor list is only as useful as its filter. A widebody crew leaving Min Runway at zero will get every airstrip within fifty miles; setting a realistic minimum turns the same list into a set of fields you could actually use.
Distance, track, and what to include
Every field inside your corridor that passed the filters, each with its ICAO and name. Tick the ones you want in the brief; the chip beside the header counts your selection, e.g. 4/15, and repeats the corridor width you used.
| You can select | Maximum | Shown as |
|---|---|---|
| Corridor airports | 15 | 4/15 beside the list header |
| SIGWX flight levels | 5 | 2/5 |
| SIGWX regions | 2 | 1/2 |
At the limit, further taps simply do nothing — no dialog, no message. If a tick won't take, check the counter.
The app suggests the FIRs your great circle crosses, and you can add others. Each carries a badge showing where it came from — automatically derived, or added by you.
Two things about the geometry, both stated on screen.
1. The bearing is TRUE. 23°T is the initial great-circle track in the true frame — it is not a magnetic heading, and it changes along the route.
2. FIR boundaries are reference data. The app tells you plainly: "FIR boundaries are for reference only and may not be current. Verify against your OFP." A route that clips a corner may show a FIR your flight plan doesn't, or miss one it does.
Filling the tabs, and exporting the pack
GENERATE BRIEF gathers the weather, FIR notices, advisories and charts for your selections and fills the other four tabs. GENERATE PDF BRIEF additionally produces a document you can share.
While the PDF runs the button reads GENERATING... and the app warns: "Generating briefing — may take up to 2 minutes on weak signal."
| Action | Limit | At the cap |
|---|---|---|
| GENERATE BRIEF | 10 per UTC hour | Button reads LIMIT REACHED, chip shows 10/10, inline note Resets at next :00Z. Message: "Hourly brief limit reached. Resets at next :00Z." |
| GENERATE PDF BRIEF | 6 per UTC day | Button reads LIMIT REACHED, chip shows 6/6, inline note Resets at 00:00Z. Message: "Daily briefing limit reached. All live app data remains available. Resets at 00:00Z." |
The caps never lock you out of data. The message says it explicitly: "All live app data remains available." Hitting a cap stops pack generation, not access — every airport, NOTAM, advisory and chart in the app is exactly as reachable as before. The limits exist to protect the shared upstream services, not to ration your briefing.
The two counters are independent, and both reset on Zulu boundaries: the brief counter at the top of each hour, the PDF counter at 00:00Z.
Fifty routes, one tap away
Saving your regular sectors pays off twice. Once in Brief, where the corridor settings come back with the route; and once on the Watchmap, where the same saved route loads onto the weather picture and pre-warms the weather for every airport on it.
What a Brief is, and what it is not
A Brief is a collection of published data, scoped to a route you described. It is not a flight plan, not an operational briefing, and not a navigation product. Everything it contains comes from the same third-party sources the rest of the app uses, with the same limits.
Built for pilots. By a pilot. Next in the series: Flight Watch — tracking the aircraft you care about.
One aircraft, followed properly
Flight Watch is not a radar screen and not a fleet display. It follows one aircraft at a time — the one you actually need to know about — and keeps its progress on your lock screen while you get on with something else.
The situations it was built for are the ones every crew knows: the inbound aircraft you're taking over, the positioning flight that decides when your duty starts, the aircraft carrying the crew you're waiting on, a family member's arrival.
Why one flight, not a map full of them. Live tracking data is metered — every lookup costs. Rather than burn that on a picture you'd glance at once, the app spends it on the single aircraft you care about and then keeps the estimate alive locally, for free, between updates.
The tracking view
Finding your aircraft
The tip that saves your budget — it's on screen for a reason. "Each search uses 1 credit. To avoid wasting credits, make sure your aircraft has already departed before searching."
Search too early and you spend a credit on an aircraft with nothing to report. Wait until it's airborne and the same credit buys you a live position, a real progress figure and an estimate that keeps working afterwards.
If nothing matches, the app says so plainly: "No flights found for [query]. Check the identifier and try again."
Reopen Flight Watch and your aircraft is still there, with a banner reading Restored from saved pin — tap refresh for live data. The figures you're seeing are extrapolated from the last snapshot — SYNC when you want the real thing.
What costs, and what's free
| Action | Cost |
|---|---|
| A search | 1 credit — confirmed before it's spent |
| A SYNC | 1 credit |
| Progress advancing between syncs | Free — computed on your device |
| Reopening the screen | Free — restores from the saved pin |
| The lock-screen notification updating | Free |
You get 10 credits a month. A bar reads Credits: 1 / 10 used this month, and the SYNC button carries the remainder — SYNC • 9 left. When the budget is gone the bar reads No credits left — resets on the 1st of next month and the SYNC button disappears.
This is the most important design decision on the screen. Between syncs, the app keeps the progress bar and ETA moving by advancing the last snapshot with elapsed time — dead reckoning, once a minute, at no cost.
And it tells you it's doing exactly that. The banner reads CALCULATED ESTIMATE, with Snapshot 7s ago — advancing by time underneath.
Read the snapshot age, not just the percentage. 55% complete with a 7-second-old snapshot is essentially live. The same 55% complete with a snapshot from forty minutes ago is arithmetic — the aircraft may have been held, rerouted or diverted, and nothing in the extrapolation would know. The app never hides which of the two you're looking at.
The credit budget resets on the 1st of each month.
Progress on your lock screen
Flight Watch is the only feature in the app that can send you a notification. Nothing else — not weather, not NOTAMs, not advisories — will ever interrupt you.
| Platform | What you get |
|---|---|
| Android | A persistent notification with live progress: the flight and percentage in the title, the route and remaining time in the body, refreshed every minute. Silent and unobtrusive — it sits there and updates. |
| iOS | Banner alerts on status changes — departed, landed. The first time you pin a flight, an explanation appears: Flight Watch on iOS, noting that iOS does not support persistent live-progress notifications for third-party apps, and telling you where to enable notifications if the alerts don't appear. |
On both platforms an arrival alert fires when the aircraft lands: [FLIGHT] ARRIVED — "Your aircraft has arrived or will arrive soon." It clears itself after a few minutes.
What each block tells you
| Card | Contents |
|---|---|
| Status badge | EN-ROUTE · DEPARTED · LANDED, or the status as reported when it's something else. |
| Progress | Departure and arrival codes, a bar with the aircraft on it, the percentage, and an ETA pill. Near arrival the pill becomes Landing shortly; afterwards, LANDED. |
| CALCULATED ESTIMATE | The snapshot age and a plain statement that the figures are advancing by time. |
| SCHEDULE | DEPARTURE and ARRIVAL in Zulu, with the estimated arrival underneath. A late departure is called out: Departure delay: +25 min. |
| LAST KNOWN DATA | ALTITUDE in feet, SPEED in km/h, HEADING in degrees — from the last live snapshot, with its age in the corner. These do not extrapolate. |
Two clocks on one screen — don't mix them up. The progress bar and ETA keep moving between syncs; the altitude, speed and heading do not. If the last known data is thirty minutes old, that's a thirty-minute-old altitude — the aircraft has almost certainly changed level since. The age in the corner of that card is the number to read.
What this is not
Flight Watch shows commercially available flight-tracking data, delayed and incomplete by nature, extrapolated between updates. It is a convenience — the answer to "roughly when will they be down?" — and nothing more.
Built for pilots. By a pilot. Next in the series: the Pilot toolkit — ten calculators and decoders.
Learn it once, read all ten
The toolkit borrows a convention from the flight deck: colour tells you where a number came from, and whether it constrains you. Once you have it, you can read any of the ten calculators without instructions.
Imported from the aircraft profile you selected in Settings. You didn't type it — the app did.
You typed this yourself, overriding what the app would have used.
The app worked it out — a derived value, or a figure you can use.
The constraining value — the number you must not exceed.
Something applies: a restriction, a correction, a value worth a second look.
Plain white on a neutral field means raw input — a number you typed that carries no special status.
Where the convention earns its keep. Limitation of the Day shows a Dry Operating Weight that can arrive four ways. Magenta means it came from the profile, blue that you overrode it, green that the app added your basic weight, crew and pantry, neutral that nothing is entered. One glance tells you which — no need to remember what you did five minutes ago.
What each one is for
| Tool | Answers | Saves to Notes |
|---|---|---|
| Limitation of Day | "What's my maximum take-off weight today, and what traffic load does that leave?" | ✅ |
| Fuel Uplift | "Does the metered volume match the fuel I actually needed?" | ✅ |
| Tankering Calc | "How much extra fuel can I legally carry, and how much do I need for two sectors?" | ✅ |
| ACN/PCN Calc | "Can this pavement take my aircraft at weight?" | ✅ |
| Cold Temp Correction | "What altitudes should I fly on approach in this cold?" | — |
| Wind Component | "What are my headwind and crosswind components?" | — |
| Timing | "What do all these times add up to, in hours and decimal?" | — |
| Unit Converter | "What's that in the other unit?" | — |
| SNOWTAM Decoder | "What does this winter message actually say?" | — |
| Decibel Meter | "How loud is it in here?" | — |
Four save, six don't — and four remember, six forget. The four weight-and-fuel calculators offer Save to Notes and keep their state between sessions. The other six are deliberately transient: leave Cold Temp, Wind Component, Timing, the converter, SNOWTAM or the decibel meter and their contents are gone. Finish the job before you navigate away.
The daily weight analysis
The calculation every line pilot runs before the load sheet arrives: build the operating weight, enter the limits, and read what the day allows.
This one field is the clearest expression of the colour convention, and it explains itself on screen: "DOW: magenta = profile · blue = manual · green = computed."
| Colour | Badge | Means |
|---|---|---|
| Magenta | PROFILE | Imported from the selected aircraft. |
| Blue | MANUAL | You typed it. This is the only state with a ✕ to undo. |
| Green | AUTO | Computed from basic + crew + pantry. |
| Neutral | AUTO | Nothing entered yet. |
The states are mutually exclusive and the app keeps them honest: type in the chain and any manual DOW is cleared; type in DOW and the chain is cleared. The ✕ re-imports the profile value, or clears the field if there isn't one.
Choosing an aircraft. The Aircraft: dropdown at the top applies a saved profile — importing MZFW, MTOW, MLW and, when present, DOW. Selecting a different aircraft wipes the basic/crew/pantry chain deliberately, so the imported DOW can't be silently mixed with the previous aircraft's figures. With nothing saved you'll see No profiles — add one in Settings.
Two fuel questions, two tools
Start by choosing your unit combination: KG / LTR, KG / USG, LBS / USG or LBS / LTR. Each carries a sensible default density, and a tile holding earlier work is badged SAVED DATA.
Then the chain, in two sections — MASS CALCULATIONS and VOLUME & VERIFICATION — each field tagged so the arithmetic is visible:
Compare (F) against the metered figure (E) and the app gives you the discrepancy twice: in volume (G = E − F) and in mass (H = G × D), each signed and each labelled with its own unit.
No hidden conversions — and the app says so. The info box states it plainly: "Volume = Mass ÷ Density. All values stay in your chosen units. No hidden conversions."
This is not a design flourish. A fuel figure that silently changes units between one line and the next is precisely the error class that has emptied tanks in flight. Every number here stays in the combination you chose; the only cross-unit figure is drawn separately with a ≈ sign and its own unit label.
Two sections. A — MAXIMUM PERMISSIBLE TOW works from Maximum Landing Weight and Trip Fuel to the max permissible TOW (red — the limit), then subtracts Actual Zero Fuel Weight to give the max fuel you can carry (green — usable). B — REQUIRED FUEL FOR TANKERING adds block fuel sector 2, trip fuel sector 1 and taxi.
The formulas are printed on screen under TANKERING FORMULAS, with the reference line "All masses in kg | Ref: Operator fuel policy."
Both tools remember their state; both offer Save to Notes.
Will the pavement take you?
PCN exceeds your ACN at max weight. A PCN margin figure is shown.
An interpolated maximum allowable mass, with the Interpolation ratio and the Required offload.
The pavement cannot take the aircraft even at minimum weight.
The method is printed on screen as a typeset formula under FORMULA · ICAO DOC 9157 — linear interpolation between the two ACN/weight pairs. Until every field is filled the result card reads Fill all fields above to compute M_adm.
The disclaimer on this one is not boilerplate — read it.
"ACN and weight values must be taken from the official Aircraft Flight Manual or manufacturer pavement tables for the specific aircraft configuration and pavement type/subgrade. This tool applies linear interpolation as defined in ICAO Doc 9157. Results are for planning purposes only. The Pilot in Command bears sole responsibility for PCN compliance."
The arithmetic is only as good as the ACN figures you feed it — and those depend on pavement type and subgrade category, not just on the aircraft.
One difference worth knowing: this is the only calculator that genuinely converts between kg and lbs. The others relabel the unit and leave your numbers untouched.
Two tools with real consequences
Subtitled with its own method — ICAO Doc 8168 Vol I, Table 2-4-1 b. Enter OAT (°C) and Airport Elevation (ft), then the published altitudes for five fixes in order: IAF, IF, FAF, Minima (DA/MDA), Go-Around.
Each row returns the corrected altitude in green with the delta in amber underneath. The APPROACH PROFILE panel draws the descent, so a mistyped altitude shows up as a kink.
| Condition | You see |
|---|---|
| OAT above 0 °C | OAT is above 0°C — corrections not required; every row reads Not required. |
| OAT below −50 °C | OAT below −50°C is outside ICAO table range; rows read Outside range. |
| Working | OAT -10°C | Aerodrome elev 200 ft — corrections active |
| Fix above 5000 ft AAL | N/A — above table limit |
| Fix below 200 ft AAL | The correction is computed at 200 ft and marked (clamped to 200 ft HAA). |
Cross-check only, and the app is explicit about why. "This tool is for reference and cross-check purposes only. It is not a substitute for your operator's approved cold temperature correction procedure. Some states and operators publish different correction methods or tables. Always follow your company SOP and the applicable AIP." Corrections round up to the nearest 10 ft.
Standard trigonometry, printed on screen: HW = V cos(θ) XW = V sin(θ). Gust components appear as a second pair whenever the gust exceeds the steady speed.
The TRUE / MAGNETIC trap, stated on screen twice. Under the inputs: "Wind direction is per METAR convention (degrees TRUE north). Tower / ATIS winds are magnetic." And in the disclaimer: "Ensure you are using the correct reference for your runway track before comparing results."
Nothing auto-fills here — you type all four values, so the reference frame is entirely your responsibility.
Two small tools you'll use constantly
Add and subtract times without mental arithmetic. Toggle between + and −, type HH and MM (the field advances by itself after two digits) and tap ADD — or use a preset chip: 0:15 · 0:30 · 0:45 · 1:00 · 1:30 · 2:00 · 4:00 · 8:00 · 14:00.
The tape lists every entry; the result shows TOTAL in large HH:MM with the decimal hours underneath — ready for the tech log. A negative total renders coral, a positive one green.
Nothing is saved: leaving the screen clears the tape. Its footer reads simply "Reference tool only."
Twelve conversions in a grid — pick one (it turns blue), type a value, read the result in green:
| Mass | Volume | Pressure | Distance |
|---|---|---|---|
| Lbs to Kg Kg to Lbs | Gal to Liters Liters to Gal | hPa to inHg inHg to hPa | Meters to Feet Feet to Meters SM to Meters Meters to SM SM to NM NM to SM |
The factors are printed under CONVERSION FACTORS, with the reference line "1 NM = 1852 m (exact) | Ref: ICAO Annex 5 / NIST."
Winter operations, decoded
The decoded view is assembled in a fixed order: a severity banner, the summary, one card per runway with three columns (Touchdown Zone, Mid-point, Stop-end), the SITUATIONAL AWARENESS list, and finally RAW MESSAGE, collapsed but always there.
Dark green.
Green — good braking action.
Amber.
Orange — medium.
Deep orange — medium to poor.
Red — poor.
Dark red — less than poor.
Grey — not reported. Not the same as "good".
Each third also carries its contaminant, Coverage as a percentage and Depth in millimetres — or NR where the message doesn't report them. When the runway has a reduced applicable width, a line flags it.
Two limits, both stated on screen.
Format: "Supports ICAO GRF format (post-Nov 2021) only. Pre-2021 and US FICON formats not supported." Paste an older message or a US FICON and you will not get a sensible decode.
Authority: "Decoder output is for reference only. Verify against the original message." The raw text is one tap away for exactly this reason.
A closed aerodrome gets its own unmissable card: AERODROME CLOSED DUE TO SNOW — SNOCLO.
How loud is it in here?
Tap START MICROPHONE and the gauge shows the ambient level in dB SPL, with PEAK for the session and an EXPOSURE word: SAFE, MOD or HIGH. A pill at the top reads LIVE while listening and OFFLINE otherwise. STOP MONITORING ends it; the peak resets on every start.
The gauge colours at 60 dB and 85 dB; the exposure word changes at 70 dB and 85 dB, so a reading in the sixties can show a yellow gauge alongside the word SAFE.
Uncalibrated, and the app says so in the strongest terms it uses anywhere. "Readings are approximate, uncalibrated, and for reference only — not for safety, medical, or regulatory use. Nimble Aero accepts no liability for any injury or damage resulting from use of this feature."
A phone microphone is not a sound level meter. Treat this as an indication of relative loudness — useful for comparing one cabin to another, useless as evidence.
Keeping a calculation, and weighing what it's worth
Limitation of Day, Fuel Uplift, Tankering and ACN/PCN each offer Save to Notes once they have a result. The app confirms with Saved to Notes ✓ and a VIEW action that jumps straight to the repository. Saved notes are titled with the calculator and a Zulu timestamp — LOD — 14MAR / 1435Z.
Those same four remember their inputs between sessions. Return the next day and a chip tells you the values are old: Restored from 14MAR2026 / 1435Z — a reminder to check them against today rather than trusting yesterday's numbers.
Every one of these tools does arithmetic on numbers you supply, using published methods. None of them knows your aircraft, your configuration, your operator's policy or the conditions of the day beyond what you typed.
Built for pilots. By a pilot. Next in the series: Notes & Repository.
A scratchpad one tap away, and a repository that keeps your calculations.
↑ ContentsWrite it down, find it later
The module has two sides. Notes is where you write; Repository is where everything you kept ends up — including the calculations you saved from the Pilot toolkit.
| Half | What it does | How you reach it |
|---|---|---|
| Free Text Note | A blank, date-stamped pad. Type anything. | Notes on the home bottom bar, or the Notes tile on the Pilot Dashboard. |
| Repository | Everything saved — free-text notes and calculator records together, filterable. | The Repository tile on the Pilot Dashboard. |
One tap, no chooser. Tapping Notes takes you straight into the editor — there is no menu asking what kind of note you want. The design assumes that when you reach for a notepad you already know what you're about to write.
What pilots actually use it for
The fastest pad on the phone — open, type, done. No formatting, no fields to fill.
Limitation, Tankering, Fuel Uplift and ACN/PCN save formatted records here, each with its Zulu timestamp.
Three filters split the repository into everything, your own notes, or calculator records only.
Swipe and share — the note leaves as plain text, into any app on your phone.
Notes and calculations accumulate in date order — a lightweight log of what you worked out and when.
Nothing syncs, nothing uploads. Your notes go nowhere unless you share them yourself.
Notes travel inside the .NPF backup with your watchlist, routes and aircraft profiles.
Swipe to delete, with a confirmation — nothing disappears by accident.
The Free Text editor
At a hundred notes the app stops you before you start: Notes Full — "Maximum is 100 notes. Delete some before adding new."
Finding what you kept
| Chip | Shows |
|---|---|
| All | Everything, newest first. |
| Free Text | Only the notes you typed. |
| Calc | Only the records saved from the calculators. |
Four tools in the Pilot toolkit — Limitation of Day, Fuel Uplift, Tankering and ACN/PCN — offer Save to Notes once they have a result. What lands here is the whole computation: the inputs you entered and the figures the app derived, formatted as a record.
Each is titled with its calculator and a Zulu timestamp — Fuel Uplift — 14MAR / 1435Z — so a day's records read in order without you naming anything.
Saving confirms with Saved to Notes ✓ and a VIEW action that brings you straight here.
Why saving a calculation is worth the tap. A figure you worked out an hour ago is only as good as your memory of what you fed into it. The saved record keeps the inputs alongside the result — so if the load sheet disagrees with your Limitation of the Day, you can see immediately whether the difference is in the arithmetic or in the assumptions.
What to know before you rely on it
| Item | Value | What you see |
|---|---|---|
| Notes in the repository | 100 | Notes Full — "Maximum is 100 notes. Delete some before adding new." |
| Restoring a backup | 100 combined | An import that would push you past the limit is refused cleanly and cancelled, telling you the totals involved. |
| Where notes live | On the device | No cloud, no sync, no account. |
Notes are included in the .NPF export alongside your watchlist, saved routes and aircraft profiles — the way to move them to a new phone. Full detail is in the Settings & Backup guide.
On the device means on the device. There is no server copy and no account to recover from. Lose or wipe the phone without a .NPF export and the notes are gone. If any of them matter beyond the trip, export a backup — or share the note out to somewhere that does have a copy.
Built for pilots. By a pilot. Next, and last in the series: Settings, backup & restore.
Nine sections that shape the whole app, plus the file that carries it to a new phone.
↑ ContentsNothing applies until you save
Settings in this app are explicit. Flip a switch and nothing happens yet — a bar at the bottom of the screen tracks your edits and waits for you to commit them.
| The bar reads | Meaning |
|---|---|
| No pending changes | What you see is what's in force. |
| ● UNSAVED CHANGES | You've edited something. It is not active yet. |
| ✓ PREFERENCES SAVED | Committed. |
The one habit to form. Change what you need, then tap SAVE and watch for the confirmation. Leaving the screen on ● UNSAVED CHANGES discards the lot — which is exactly what you'd want if you'd been experimenting, and exactly what catches people out otherwise.
The nine sections, in order
| § | Setting | Default | What it changes |
|---|---|---|---|
| 1 | Text Size | M | Font scale for the whole app — S, M or L. |
| 2 | Watchlist / Dashboard | Watchlist | Captioned WHICH SCREEN OPENS WHEN YOU LAUNCH THE APP. Also redirects the drawer's Home Screen entry. |
| 3 | Persistent METAR Archiving | On | "Save fetched METARs to local history log" — turns the METAR block on Airport Detail into a trend trail. |
| 3 | METAR History Depth | 5 reports | How many observations per airport the archive keeps. Slider, 1 to 5. |
| 3 | CLEAR METAR HISTORY | — | Wipes the archive for every airport; confirms with METAR History Cleared. |
| 4 | METAR Only Watchlist | Off | "Hide TAF from airport cards on home screen" — a denser list. |
| 4 | Group by Country | Off | "Group watchlist airports by country with flags". |
| 5 | Send crash reports | On | "Share anonymized diagnostics to improve reliability. Opt-out applies going forward." |
| 6 | Expand NOTAMs by Default | Off | "Show full NOTAM text when opening". |
| 7 | Hide Expired Advisories | On | "Hides SIGMET/AIRMET/GAMET past valid time" — on the list, the advisories map and the Watchmap. |
| 8 | KG / LBS + profiles | KG | Global weight unit and your saved aircraft (§3). |
| 9 | Export / Import Data | — | "BACK UP OR RESTORE A .NPF FILE" (§4). |
| — | App Version | — | The build you're running. Quote it in any feedback about a bug. |
About crash reports. The sub-label is precise: opting out applies going forward. Diagnostics already sent aren't recalled, and diagnostics stop being collected from the moment you save the change. Leaving it on is how a solo developer finds the crash you hit before you have to describe it.
Teach the calculators your aircraft
With nothing saved the section reads No profiles saved. Add one below. The sheet notes exactly how your figures are treated: "Values stored as entered, in kg."
The selected profile feeds Limitation of the Day, which imports MZFW, MTOW, MLW and DOW in magenta. Tankering and ACN/PCN read the unit setting but not the profile weights.
Switching KG ↔ LBS is destructive, and deliberately so. The confirmation says exactly what will happen: Change unit system? — "This will DELETE all aircraft profiles and CLEAR all calculator data (Limitation, Tankering, ACN/PCN). Continue?"
The app will not silently convert your stored weights. A converted MTOW that quietly gains or loses a factor of 2.2 is a far worse outcome than being asked to re-enter it from the AFM. Choose your unit once, at the start.
Everything in one file
A single .NPF file carries your whole setup: watchlist, saved routes, notes and aircraft profiles.
Open Export / Import Data from Settings and export. Share the file wherever you like — cloud storage, e-mail to yourself, a cable to a laptop.
Point the app at a .NPF file. Before anything is written it checks the contents against the app's capacities, and refuses cleanly rather than importing part of a backup:
| If the backup holds | You see |
|---|---|
| More than 100 airports | Watchlist Limit Exceeded — the count, the limit, and "Import cancelled." |
| More than 50 saved routes | Saved Routes Limit Exceeded — same pattern. |
| Notes that would push you past 100 combined | Notes Limit Exceeded — it tells you how many you have, how many the backup adds, and asks you to delete some first. |
| A file larger than 1 MB | Refused — the screen states • 1 MB maximum size. |
The notes check is on the total, not the file. Airports and routes are compared against the backup alone; notes are compared against what you already have plus what the backup adds. A 40-note backup can be refused if you're already holding 70.
If the backup was made in the other weight unit, the app asks before adopting it — and adopting it triggers the same profile-and-calculator reset as a manual unit switch. Worth knowing before you restore onto a phone you've already set up.
Setting the app up the way you fly
| If you… | Consider |
|---|---|
| Fly a large multi-country roster | Group by Country on, METAR Only Watchlist on — a much denser, faster list. |
| Live in the calculators | Landing page → Dashboard, and set up an aircraft profile first. |
| Read NOTAMs thoroughly on short lists | Expand NOTAMs by Default on — one less tap per notice. |
| Want to watch weather trends | Keep archiving on at depth 5 — the METAR trail is what shows a deteriorating afternoon. |
| Track hazards over time on the Watchmap | Leave Hide Expired Advisories on, so the timeline shows each advisory only while it's valid. |
| Are about to change phones | Export a .NPF before you wipe the old one. There is no cloud copy. |
Settings change what you see — and therefore what you might miss. METAR Only Watchlist hides forecasts. Hide Expired Advisories hides messages past validity. Neither is dangerous, but both mean the screen is showing you less than the app holds. When something looks unexpectedly quiet, check whether a setting is trimming it.
Everything configured here lives on your device. There is no account, no sync and no server copy — which is why the .NPF export exists.
Built for pilots. By a pilot. That completes the feature guide series.
Log a turnaround, see honestly where every late minute went, and copy a clean report — a personal aide-mémoire, never an official one.
↑ ContentsAnatomy of the turnaround card
Delay Allocation is a turnaround delay-attribution tool. You give it the block times for one turnaround and the events that happened during it; it works out, minute by minute, where the delay went — and hands you a plain-text report you can copy. It answers the question every captain is asked on a late departure: “so what actually held us?” Reach it from the Pilot Dashboard.
All times are Zulu, and it remembers. Every field is UTC — the Z suffix is there to remind you. The tool also keeps your last turnaround silently: reopen it and your numbers are still there, no “restored” banner, ready to finish or to clear.
What this tool actually settles
It turns a vague “we were late” into a defensible breakdown you can read back — and keep.
The minutes forced by a late inbound aircraft are split out from the minutes that happened on your stand.
Boarding, ATC, fuelling, a late crew bus — record each event and see exactly how many minutes it added.
Two things happening at once don’t get counted twice. Only the minutes an event actually pushed the departure later are charged to it.
An overlap strip lays the whole turn on one timeline against STD, ETD and off-blocks.
Minutes the events don’t explain are shown as unexplained — never quietly blamed on the nearest event.
A plain-text report you can copy into a message, or save to the Repository for later.
Three ideas, and the tool is obvious
The whole tool rests on three simple ideas: a reference time to measure from, a cascade that charges each event only for the minutes it added, and an honest residue for anything left over. Learn these three and every number on the screen explains itself.
Before you can attribute a single minute, the tool needs to know the earliest you could fairly be expected to leave. That is the ETD, and it is the later of two things:
The app takes whichever is later: ETD = max(on-blocks + allowed, STD). When the inbound is late, on-blocks + allowed wins, and the gap between STD and ETD is time already owed to the aircraft rotation — you never had a chance to leave on time. That gap is charged to Aircraft rotation / Late arrival, not to you. Precisely: rotation = max(0, min(ETD, AOBT) − STD) — the min means that if you beat the allowed turn and pushed before ETD, you are only charged up to the moment you actually left.
Why the reference matters. Everything downstream is measured from ETD, not from STD. That is what makes the split fair: the crew is never charged for the minutes the schedule itself made impossible.
From ETD onward, the tool walks your events forward in time and charges each one only for the minutes by which its end pushed the running clock later. That is the meaning of the banner END IS WHAT COUNTS: it is the moment an activity finishes that releases the aircraft, so the end time is what drives the delay — the start time is context for the picture, not the charge.
Say the running clock sits at ETD 1320. Boarding finishes at 1330 — it pushed you 10 minutes past where you were, so Boarding is charged +10 and the clock moves to 1330. ATC start-up then finishes at 1335 — another 5 minutes on top, so ATC is charged +5. Because each event is only charged for what it added beyond the previous one, two overlapping activities can never be billed for the same minute.
Sometimes the recorded events don’t account for every minute between ETD and the actual push. When that happens, the leftover is shown as an unexplained residue — and it is never automatically pinned on the last event or quietly folded into a total. If you know what caused it, you may choose to attach the residue to one event yourself; if you don’t, it stays honestly labelled as unexplained.
Honesty over tidiness (P-05). A tool that always makes the numbers add up to a clean total is lying to you somewhere. This one would rather show you a gap than invent a cause. If minutes are unexplained, that is information — go and find out what happened before you sign the number off.
From on-blocks to a copied report
Order of entry doesn’t matter. The cascade sorts your events by time itself — type them in whatever order you remember them.
The OVERLAP strip is the whole turn on one line; the WHERE THE MINUTES WENT panel is the same story as a stacked bar and a tally. The total there always equals actual off-blocks minus STD — the honest, door-to-door delay.
The report is deliberately plain. No drawn diagram, no alignment art — just text that reads correctly wherever you paste it, including the Repository’s note reader.
Every mark on the timeline
| Mark | Looks like | What it means |
|---|---|---|
| Axis labels | IN · STD · ETD · OUT | On-blocks (AIBT), scheduled off, computed ETD, and actual off-blocks (AOBT) — the four times the whole turn is measured against. |
| STD line | Solid white vertical | Scheduled off. Labelled “delay counted from here.” |
| ETD line | Green dotted vertical | The reference time — the earliest you could fairly be ready. |
| Filled bar | Blue bar with +n | An event with start and end recorded, drawn across its duration, tagged with the minutes it was charged. |
| End-only marker | Single vertical mark | An event where only the end was recorded — position, not duration. |
| +n chip | e.g. +10 | The minutes that event added to the departure under the cascade. |
The numbers behind the screens
The turn in the figures — LFPG · OZ123 — walked end to end.
| Step | Figures | Result |
|---|---|---|
| On blocks + allowed | 1230 + 50 min | 1320 |
| ETD = later of that or STD | max(1320, 1300) | 1320 |
| Rotation owed | min(1320, 1335) − 1300 | 20 min |
| Boarding ends 1330 | 1330 − 1320 | +10 min |
| ATC ends 1335 | 1335 − 1330 | +5 min |
| Total delay | AOBT 1335 − STD 1300 | 35 min |
Rotation 20 + Boarding 10 + ATC 5 = 35, and 35 is exactly off-blocks minus STD. Every minute is accounted for, and none is charged twice.
The habits and the small print
A private aide-mémoire, nothing more
Delay Allocation is a personal reasoning aid. It does not read any live data, it does not talk to your company’s systems, and its output is not a coding of delay under any official scheme. The report says so in as many words.
Built for pilots. By a pilot. The last word on where the minutes went — in your own hands, honestly counted.