Flight plan: departure time, ETA, last light and airfield hours; in-flight hours/last-light alerts; quarter-hour departure; prints without a tab (#667, PR #2643)
Wiki sweep (EN): menu split into Map + Settings, phone tabs and red Comm fail, edit column, centred questions, SIGMET layer and lists, AIRMET/SIGMET decoder, movable hazard lists, aerodrome charts, NOTAMs in bubble/leg panels, symbols by zoom, LSA legend, sites and route types
Comm failure page; deck of six; airfield phone link; parking phone; GA mail counts
- New Comm-Failure page (EN/HE): the button, the card (7600, tower phone,
light signals), NOW following the aircraft, Cancel, Herzliya areas
3/8/9, and the transcribed entry/altitude table.
- Features, Phone layout, Toolbar: the Comm fail button and the sixth deck item.
- Inspector: the Phone row that dials the field.
- Submit a flight plan: parking phone numbers dial.
- FAQ: the three anonymous mail hand-off counts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016GmLy5kufzfY8roPqZUBeZ
Parking docs: the five fields the first scan missed, and the always-on button
Adds LLMZ, LLFK, LLES, LLRS and LLKZ to the table, and the operator numbers for
the phone-only fields. Replaces the unaddressed-draft note: the button is now
offered at every aerodrome, and says which of the three cases applies -- address,
phone only, or nothing on file -- while a non-aerodrome destination dims it.
Document the parking request: what the AIP requires, and where to ask
New section on Submit a flight plan (EN + HE): which fields require parking to be
arranged before departure, the published address for each, what the dialog asks
for that the plan cannot know, and why the expected departure is not prefilled.
Notes the LT/Z marking on times and the unaddressed-draft case for a field that
publishes only a phone. Airfields dataset gains the matching key.
Follow me, offline CVFR, NOTAM sorting, turn predictor — and correct NOTAM source
New Follow me pages (EN + HE): sharing, watching, the restart-surviving session,
persistent-link flag, who-sees-what, tunables, and the two Python tools.
Offline-and-PWA rewritten for the automatic whole-chart CVFR pack (zooms 7–13,
route-corridor first, waits for an unmetered connection) instead of the old
four-chart manual download.
Extra layers: NOTAM list now documents relevance sorting and the Sort dropdown.
GPS track recording: the curved in-turn heading predictor, and a pointer to
Follow me. Features pages gain Follow me. Tuning panel and LocalStorage schema
cover the new follow-me / offline / predictor keys and the device-local
followMeSession and notamModalSize.
Corrects the NOTAM source across Extra Layers (EN + HE) and Toolbar: the feed is
the IAA Mobile AeroInfo site, not autorouter/EAD.
Sidebar gains Follow me in both languages.
Align privacy sync and waypoint guidance
wiki: correct the API-key sync claim, the tile rule, and the interaction rules
Reviewed every page against the code.
- LocalStorage schema and the AI assistant page both said API keys never leave
the browser / are never synced to Drive. They ARE in GDRIVE_SETTINGS_KEYS, so
'Sync settings too' uploads them. Corrected in both languages, with the base
URL's genuine exclusion kept straight.
- Map layers described flight-maps.com as the display source. Only the live site
draws from it now; every other deployment uses our mirror.
- Settings and persistence: the shipped defaults now carry the deployed config,
and the gist is applied from cache before the first paint.
- Keyboard and touch: the inspector opens on release, drags never open it, the
drag threshold, and the in-flight layout lock.
- Submit a flight plan: the licence field takes digits.
- New localStorage keys documented: gistCache, headingUp, gpsFollow.
- Fixed a broken anchor (Tuning-Panel#navigation -> #in-flight-constants).
Wiki review: heading line, sim alerts, freq-change suppression, Advanced field resets
EN + HE kept in sync.
Wiki: frequency NOTAMs, the mail preamble, and the editor's new export shape
Sweep of all 81 pages against what shipped since the last one. Three real gaps, one
of them advice that had become wrong.
Frequency-Changes: documents the airfield-inspector marker for an active NOTAM that
mentions a frequency, and — more importantly — why it names the NOTAM and never a
value. A NOTAM frequency is true today, not in general, and a mis-parse would put a
pilot on the wrong frequency. The app points; the pilot reads and decides.
Submit-Flight-Plan: the filed mail now opens with a plain-language summary above the
ICAO block. Records the split that matters: the preamble follows the UI language, the
(FPL-...) block is never translated because its contents are codes. Also that a
landing time is dropped rather than invented when departure or EET is missing.
Hidden-Tools: the editor advice was WRONG, not merely stale. The page said point mode
"exports JSON for pasting back into a dataset"; it now exports a route-graph `nodes`
fragment that must be MERGED into the nodes map. Pasting it over a graph would destroy
the file. Also notes the ride-through of unedited fields, UNNAMED_n placeholders for
un-named points, and that edges are not exported.
Checked and clean: no page quotes the corrected 125.60, and nothing documents
closedHint (removed from CVFR) or the one-way corrections, so nothing there went
stale. Changelog left alone — it is generated.
Route-graph review overlay, dataset correction, and the clearance-leg refusal
Nav-Waypoints-Dataset: the page documented three files that no longer exist.
Reporting points are projected from the layer's route graph now
(navWaypointsFromGraph), not read from *-nav-waypoints.json. The CVFR count 172
was also stale: the graph holds 172 nodes of which 170 project, ZRANA and RANNO
being locality labels the chart-image rebuild misread as mandatory points and now
carrying active:false. Documents that active is absent-means-true (a missing flag
can only ever show a label, never hide a published point), and noSegmentsReason
for published points that legitimately have no segment, such as military-route
ones -- they look identical to a locality label in the data, which is why the
reason is required.
Hidden-Tools: adds ?graphlegs=1, the route-graph review overlay -- what the marks
mean, why arrow and altitude sit together at the end a direction starts from (the
chart prints the figure there, so the two read side by side), why a two-way leg
shows two figures, and what an em-dash means. Notes that it reads the same fields
routing reads, which is how `blocked` was found on the wrong entry of 7 of the 21
CVFR one-way legs.
Submit-Flight-Plan: army airways and ATC-approval corridors cannot appear in a
filed plan, so the app refuses rather than warns -- the plan would come back
rejected, so there is nothing to acknowledge. Also states plainly what is NOT
restricted: the legs stay on the map with their altitudes and a hand-placed point
is always kept; only the app's own choice changed.
The cache-bust line already on the dataset page is correct as written and left
alone -- deploy.yml rewrites every data/*.json?v= to the commit SHA.
Submit a flight plan: the mobile for queries is locked, not editable
Submit a flight plan: the landing acknowledgement, the mid-route refusal, and the filing address
docs: the form is the printable output, not a second place to type
The page still described two editable surfaces writing corrections back to each
other. The submit dialog is the only place anything is entered now, for either
plan, and the sheet shows the dialog's values greyed and read-only with its own
boxes outlined. Documents which boxes stay editable, what Clear form spares, that
the same required-details check runs for both plans and names what is missing,
the Mail-to-the-FPL-desk button and why it cannot attach the PDF itself, the
email being required for both plans, and the tables scrolling sideways on a
narrow screen rather than clipping.
docs: say that both plan types share one set of details
The aircraft and pilot details are entered once and serve both the ICAO message
and the cross-country form, and a correction made on the form writes back to the
shared profile.
docs: the cross-country form, and which plan the route lets you file
The page said a cross-country plan could not be submitted from NavAid; it now
fills the authority's own form (א׳-11 נספח ב׳), so that section says what the
form contains, what is prefilled from the route and profile, the signature pads,
and why saving goes through the print dialog.
Adds the flight-type rules -- an all-published route can only be an ICAO message,
a route with an off-network point can only be the form -- and the pilot email,
which is now required because the approval returns by mail and the sending
account may not be the pilot's. Normalises the AIP references to the geresh.
docs: mock details in the FPL example, not a real pilot's
The worked example carried a real registration, name, licence number and mobile
on a public page. Swapped for the placeholder identity the AIP's own sample uses
(4XHLH / ISRAEL ISRAELI / 1234 / 0541234567).
docs: add the Submit-a-flight-plan page (EN + HE)
Covers what comes from the route versus what the pilot fills once, the published
filing addresses and why the cross-country form is not offered, the AIP timing
rules the dialog checks, the two acknowledgements, the no-mail-app fallback, and
a worked example. Notes plainly that the mail subject is our own convention and
that NavAid never sends the plan itself.