Flight Plan

🇮🇱 עברית

Flight Plan

The Flight Plan modal turns the map route into an editable per-leg table with distance, heading, time and fuel.

Open it with the 📋 Flight Plan button in the Charts menu.

This table is zero-wind, deliberately. Headings are the leg's own track and times come from the planned speed, so a printed plan never changes because a weather fetch landed. The wind triangle -- CAS, TAS, drift, compass heading -- is the flight planning form, a separate document.

Columns

Column	Meaning	Editable?
#	Leg index.	No
From	Source waypoint name.	Yes
To	Destination waypoint name.	Yes
Hdg	Magnetic heading (°M), derived from the leg geometry and the magnetic variation in force (5°E over Israel).	No
Dist (NM)	Leg great-circle distance in nautical miles.	No
Speed (kt)	Cruise speed for the leg.	Yes
Alt (ft)	Cruise altitude (MSL ft).	Yes
Time	Computed as Dist / Speed, formatted M:SS for sub-hour legs and H:MM:SS once a leg goes over an hour.	No
Fuel (gal)	Leg fuel burn = Time × GPH. The first-leg cell adds the Taxi/T.O. allowance and is marked with * when the departure waypoint is a known airfield.	No
Cum. time	Running elapsed time from the beginning of the route.	No
Cum. fuel	Running fuel total.	No
ETA	Clock time over the leg's To point: the departure time plus the time of every leg so far — legs inside the departure CTR included (the Cum. time column starts at the boundary; a clock does not). -- until a departure time is set.	No
Radial	Magnetic radial from the selected VOR to the leg's From point. Includes a per-leg VOR override dropdown.	Selector only
DME	DME from the selected VOR to the leg's From point, in nautical miles.	No

A Total row sums distance, time and fuel; its ETA cell is the arrival.

Departure time, ETA and last light

Beside Columns is the departure button — ETD 10:00 ▾ (or ETD --:-- when none is set) — and, always in view, Last light 20:21 for the destination.

• ETD opens the departure: a date and a time in quarter hours (hour and 00 / 15 / 30 / 45), with the other clock beside it. It is the same departure the filing dialog uses: set it here and the dialog starts from it (when it is still ahead of the filing lead); change it there and the plan follows.
• Times in UTC switches every clock — the departure you type, the ETAs, last light — to UTC (07:00Z). The departure is stored in local time either way.
• Last light is the end of evening civil twilight (sun 6° below the horizon) at the destination, on the departure date, computed offline from the sun; the full line in the popover also gives sunset.

Two findings, kept apart:

Mark	Meaning
⚠ red	A field is outside its published operating hours — the departure field at the ETD, or the destination at the arrival. Same AIP hours as the inspector's Hours section (15 fields; e.g. Herzliya closes to fixed wing 14:00–16:00 and at the earlier of twilight − 10 min or 19:30).
☾ amber	The ETA is after last light — a night landing. A caution, not a ban: night VFR is legal for some pilots, and some fields are open after dark.

Times use the planned speeds, like the rest of the plan — the forecast wind is not in it (it is in the inspector and the in-flight alerts). On a phone the ETA column starts hidden (the Columns menu brings it back) and the arrival is added to the summary line above the table. The return-route table has no ETAs: it is a separate flight.

Aircraft inputs

Above the table:

• Gallons per Hour — defaults to 8; persisted to localStorage['navaid.aircraft'].
• Taxi and Takeoff (gal) — startup + taxi + takeoff allowance; defaults to 1.1. Only added to the total when the origin waypoint matches an entry in airfields.json (by name OR by coordinates within ~100 m).
• The same two figures are in Settings (Gallons per hour, Taxi and takeoff (gal)): one profile, so a change in either place shows in the other at once.
• V/S (ft/min) above the vertical profile — shapes the departure climb on the profile and the TOC marker on the map; it does not change leg times or fuel (those are distance and speed only), and a line under it says so. Also in Settings, the same value.
• VOR — optional reference VOR for Radial/DME columns. It syncs with the toolbar's VOR ref selector and persists to navaid.vorRef.

Radial / DME

When a global VOR reference or a per-leg VOR override is selected, the table shows Radial and DME columns.

• Values are calculated to the leg's From point.
• The small dropdown inside each Radial cell overrides the global reference for that leg only.
• Blank per-leg dropdown = use the global VOR ref.
• With no global or per-leg VOR, the Radial/DME columns collapse.

Return route

Tick Show return path in the Edit menu to add a second table for the reverse leg, with its own per-leg outbound altitude / speed and totals. Off by default — the feature ships disabled; set featureShowReturn in the tuning gist to restore it.

The return table also shows Radial/DME when a VOR is active, calculated to the start point of each return leg.

Editing behaviour

• Edits commit on blur or Tab (change event, not input), so you can type freely without losing focus.
• Editing Altitude propagates along the same cruise level until a different altitude already exists — same behaviour as the leg inspector.
• Editing a From / To name updates the waypoint name in the route.
• Clearing Speed reverts to the leg's current speed (does not become zero). Clearing Altitude keeps the previous value.

Drag and persistence

• Drag the modal by its title bar. Position persists per language, to navaid.fpPos.en or navaid.fpPos.he — the RTL layout mirrors the LTR one, so a spot dragged in one language would be wrong in the other. The bare navaid.fpPos is only read once, to adopt a position stored before the split.
• The modal stays open across a language switch (sessionStorage['navaid.fpOpen']).
• Adding / removing a waypoint while the modal is open rebuilds the table in place — no need to reopen.

Printing

• Click Print to invoke the OS print dialog. The modal switches to a clean print-only layout (no app chrome). Save as PDF or send to paper.
• The flight-plan print view targets A4 landscape with compact columns so the Radial/DME table fits the page. You can still choose another paper size in the printer dialog.
• Only the plan prints — never the app around it (the phone's top strip, the Comm fail button, the tab bar), on a phone or a desktop. The last-light and opening-hours lines print with it.
• Nav log (PDF) goes straight to the print dialog too; it no longer opens a tab of its own.

Closing

• ✕ icon in the modal corner.
• Esc dismisses the Flight Plan modal (and any other open modal).

Tips

• Use the leg inspector for one-off edits, the Plan modal for bulk speed / altitude changes.
• The Fuel column totals the burn; it does not check it against anything. NavAid has no tank-capacity or reserve field and will never warn you that a route exceeds your endurance — compare the total against your own aircraft's usable fuel and your reserve minimum yourself. See Fuel Calculator.
• For long routes that span altitude changes, use Highlight diff in the Map menu so you can spot climb / descent legs at a glance on the map while you edit the plan.

Filing it

To file this plan with AIS, press ✈ Submit flight plan in the panel — see Submit a flight plan.