Skip to content

Pilot mode

Planning aid only. Results must be verified by a qualified airport engineer against manufacturer data and applicable regulations.

Pilot mode is a guided taxi-route builder for a flight crew briefing. You never draw. Dropdowns list stands, taxiways and runways that exist on the loaded OpenStreetMap extract. Aircraft types come from the FAA Aircraft Characteristics Database. Missing OSM tags are reported; they are never invented.

Open Pilot

  1. Load an airport so OSM aeroways are on the map.
  2. Tap Pilot in the planner bar.
  3. The map goes immersive: regular docks, toolbars, compass, legend and panels hide. A small Exit control stays in the safe-area corner. Legally required map attribution remains as a compact ⓘ chip.

Left sidebar

Selections sit in a collapsible left sidebar, the usual moving-map / EFB pattern.

  • iPad (portrait and landscape) and desktop: a docked left panel, about 320 px, over the map.
  • Phone: the same panel as a slide-over at about 85% width. Tap the dimmed map or swipe to close.
  • Collapse to a slim left-edge tab with a chevron so the map is fully visible. One tap reopens it.
  • When a replay starts, the sidebar auto-collapses. It does not cover the replay bar or the Exit control.

Steps

The stepper is vertical. Origin comes first for the operation; destination is last.

  1. Aircraft — one searchable combobox of FAA ACD types (ICAO or model). Width notes on taxiways are warnings, not invented ADG clearances.
  2. Operation — Takeoff | Landing segmented control.
  3. Stand (takeoff) or Runway (landing).
  4. Taxiways — only ways that connect to the previous pick. Unnamed OSM segments appear as Unnamed taxiway 1, 2, …
  5. Runway (takeoff) or Stand (landing).

Optional Use suggested route fills the shortest on-graph path when both ends are known. An optional text prompt such as A320 takeoff from stand 12 to runway 27L fills the same dropdowns locally — there is no AI service.

Simulation and replay

A complete chain draws the OSM centreline, runs the same swept-path and clearance checks as a hand-drawn taxi, and plays the aircraft. Arrivals taxi in with judgemental oversteer so the nosewheel tracks outside the centreline and the main gear stays on the pavement. Departures from a nose-in stand start with a pushback onto the taxilane (correct tail direction), then taxi to the runway — the aircraft never drives forward out of the stand. If a hitch cannot be planned, Pilot prompts; it does not invent a roll-out. Export PDF/DXF from the usual Export menu after you leave Pilot, or stay in Pilot and use the replay bar.

The replay bar is the existing play / pause, scrub, speed and restart control. It stays hidden until a replay exists, then auto-hides after a few seconds of idle playback. A tap on the map (or a pointer move) brings it back. It never hides while you are dragging the scrubber. prefers-reduced-motion keeps it visible.

Follow-cam is on when the replay starts, close enough to see the swept-path and wingtip lines (about zoom 17 on a phone, 16.5–17 on desktop). The map keeps its rotation. Pan or pinch-zoom to look around; the target button on the replay bar recentres on the aircraft.

Missing connection

If the OSM graph cannot complete the route, Pilot prompts. It never auto-exits.

  • Use manual simulation is the only way out: regular UI returns, the polyline taxi tool opens, and the current aircraft / operation / stand / runway are kept.
  • Change selection or dismiss stays in Pilot so you can pick another stand, runway or taxiway.

Data

  • Aeroways: © OpenStreetMap contributors (ODbL).
  • Aircraft: FAA Aircraft Characteristics Database (US Government work). Verify against the manufacturer Airport Planning Manual before design use.

This is a concept-planning aid, not surveyed validation.