Chapter 17 of 17

Account and data6 min read

Pilot EFB on the web

The same product at a desk - the Overview desk, Duty & FTL console, logbook, weather and NOTAM workbenches, and the full-screen Ops Map.

Verified against Pilot EFB 1.0.0 · Updated 27 Aug 2026

On this page

Pilot EFB's other cockpit is a browser. The web edition is the same product - the same modules, the same local-first database, the same disclaimers - laid out for a desk: a sidebar instead of a tab bar, multi-pane workbenches instead of stacked screens, a command palette instead of a thumb. This chapter is the tour.

Pro-only, up front

The web edition is for Pro subscribers, and it says so at the door. The order is: sign in with your Pilot EFB account, accept the disclaimer (recorded once per account, so it carries across browsers and devices), then the web plan - a separate subscription at 99.99 US dollars per year, yearly only, alongside the iOS plan described in Free vs Pro. There is no read-only guest mode on the web; until all three gates are passed, nothing else loads.

One product, two cockpits

Everything you know from the app carries over. The database is local to your browser (the app works through connection drops the same way the phone does), and Cloud Sync is the bridge: with Auto-sync on, a duty logged on the phone is on the desk when you sit down, and an entry corrected at the desk is on the phone when you leave - Settings, Backup & Sync covers how that works and what stays free. The sidebar groups the product the way you work: Overview, then Operations (Duty & FTL, Logbook), Planning (Weather, Flight Brief, NOTAMs, Airports, Ops Map), Library (Tools, Checklists), with Community and Settings at the foot. The Learn & Reference library is on the web too, reached through Settings > Help & about. And the desk adds desk things: Cmd+K (or Ctrl+K) opens a palette that searches airports, pages and actions, number keys jump between sections, and panels that earn it - the station board, the Duty console - can pop out into their own window for a second monitor.

The Overview desk

The web Home is built around one question: what changed since you last looked?

The web Overview desk: a top strip reading watching EGTB home plus 4 recent, fetched 22:30Z, not synced on this device, since last look 26 Aug with 1 alert unread, an FDP stat strip, an Active duty panel showing sector 2 of 2 with 6:15 remaining and an End duty now button, a Today timeline with duty and sector lanes, a station board listing EGTB with no data available and EGLL EHAM EDDF LFPG with live METAR readouts, and a NOTAM alerts rail with runway closure headlines, footed by Source SADIS UK Met Office and Reference only verify officially
The Overview desk: since-last-look, the live duty, the station board and the NOTAM rail - sources and framing on every panel.

The since-last-look strip counts what arrived while you were away and holds an unread-alert chip; the station board watches your home base and recent stations with category, wind, visibility and TAF trend per row - and an honest "No data available" line when a field publishes nothing, never a blank pretending otherwise. The active duty panel mirrors the phone's FDP ring ("Personal planning only." included), the Today timeline lays the day out in duty, sector and rest lanes, and the NOTAM alerts rail headlines what is new at the stations you watch. Every panel names its source and carries the same verbatim framing as the app: "Reference only - verify officially." on weather, "May be incomplete - verify officially." on NOTAMs.

The Duty & FTL console

The web Duty and FTL console: an On duty banner reading EGLL 2 sectors, a stat strip with FDP elapsed 2:50, FDP remaining 6:15 of max 11:00, duty 7 days 23:15 of 60:00, duty 28 days 51:45 of 190:00, block 19:40 of 100:00, rest required 12:00 and sectors 2, then a Current duty panel with a remaining FDP ring, report 20:00Z, planned duty end 01:15Z, a night duty note citing the WOCL window, and flight time and duty time ladders each labelled with their ORO.FTL rule reference
The Duty & FTL console mid-duty: the ring, the cumulative ladders, and the rule references on the panels themselves.

The Duty & FTL engine is the same pure calculator the phone runs - the console just gives it room: a stat strip across the top, the live FDP ring with the regulatory notes written out (the frame above is flagging a night duty against the WOCL window, with the rule paragraph cited), and the cumulative flight-time and duty-time ladders labelled with the ORO.FTL references they implement. The segments you know - Dashboard, Roster, History, Calendar, Reserve, What-if - ride across the top, and the same honesty line closes the panel: cumulative totals use the duties recorded in Pilot EFB, so confirm imported history is complete before treating them as compliance evidence.

The logbook at desk size

The web logbook: a header with the pilot profile, career total 15:50, PIC night and landings counters, currency trackers reading not tracked, and a Class 2 medical due chip, segments for Entries, Totals and Career, Currency and Credentials, and Map, a search and filter row, and a month-grouped entries table with date, route, out and in times, aircraft, total, function and landings columns, footed Personal record only
The logbook as a table: filterable entries, career counters and currency chips in one view - Personal record only.

The Logbook becomes what a logbook wants to be on a big screen: a real table. Month-grouped rows with sortable columns, filter chips (this month, night, cross-country, sim), bulk edit, column presets, H:MM or decimal display, CSV export, and the same career, currency and credential readouts the phone carries - with "Not tracked" said plainly where evidence is missing, and "Personal record only." at the foot.

Weather and NOTAM workbenches

The web weather workbench: a stations rail with a flight route group holding EGLL and a watch-list holding EGLL and EHAM, and the EGLL station open with the raw SADIS METAR, decoded wind visibility cloud and QNH cells, a worsening trend chip, an observation detail table, and a forecast column with a TAF validity timeline, the raw TAF text and decoded base and becoming groups
The weather workbench: raw first, decode beside it, the TAF timeline on the right - source and fetch time in the header.

The Weather workbench pairs a stations rail (your watch-list, plus a flight-route group when a duty or briefing names stations) with a three-column station view: raw METAR and decoded cells, the observation detail, and the TAF with its validity timeline

  • the same validity-window grading as the app, with the trend chip ("Worsening" above) computed from the forecast in force. The raw text always leads, and the header names the source and fetch time.
The web NOTAM workbench: a stations rail with EGLL showing 43 NOTAMs, a centre console with search, severity sort, status and window filters, counts reading 2 critical 4 high 16 medium 1 low, the note that 20 more NOTAMs sit outside the current time window, and the line showing fetched NOTAMs only, the absence of a NOTAM here is not an all-clear, then the EGLL group with critical runway NOTAMs, and a detail pane with NOTAM A2876/26 raw text, source NOTAM Management System, and decoded effective expires Q-code and a validity timeline
The NOTAM workbench: triage in the middle, the full raw text and decode on the right - and the no-all-clear line in the console itself.

The NOTAMs workbench is triage plus reading room: filters and severity counts in the console, the station's grouped cards in the middle, and a detail pane that shows the complete raw NOTAM with its decoded validity timeline, Q-code and classification. The workbench states its own limits in the frame: "Showing fetched NOTAMs only - the absence of a NOTAM here is not an all-clear.", and every group names "Source: NOTAM Management System" with the fetch time.

The Ops Map

The web Ops Map filling the window: an aviation chart of south-east England with airport labels EGLL EGKK EGSS EGGW EGLC and VOR labels with frequencies such as LON 113.60 and BIG 115.10, a layers control reading 10 on, zoom search and fullscreen controls, a 10 nautical mile scale bar, a credit line reading Not for navigation and OpenStreetMap contributors, and a time bar reading 26/22:48Z LIVE with Play and Now controls and a scrubber
The Ops Map workbench: the chart engine full-bleed, layers and time scrub included - permanently badged Not for navigation.

The web edition's Ops Map gives the aviation chart what the phone cannot: the whole window. It is the same chart engine and the same rules - "Not for navigation" pinned with the data credits - with a layers panel, search, a time bar that scrubs weather layers through the day and snaps back to LIVE, and a share panel for a PNG of the current view. A permalink carries your view (camera, layers, time) so a colleague opens exactly what you see.

Community and settings

The sidebar's foot holds Community - the same feature-request board, with browsing open and posting behind sign-in - and Settings, which arranges the same folders as the app (Settings, Backup & Sync) into desk panes: the same rows, the same honesty surfaces, the same verbatim disclaimers.

Web things worth knowing

Two behaviours are specific to running in a browser, and both are stated on screen when they matter:

  • It keeps itself up to date. The web app updates itself - no update banner, no manual step. A new build is adopted the moment it cannot cost you anything: instantly on an untouched or hidden tab, never while you have unsaved work or a field focused, and after a quiet pause when you are active - with a short notice so the reload reads as intended.
  • One tab at a time. The local database takes an exclusive lock, so Pilot EFB runs in a single browser tab. Open a second and it tells you plainly that the app is already open in another tab - and that closing the other tab lets this one take over on its own.

It also installs from the browser as an app, so it can live in your dock like everything else on the desk.

Where next

Pilot EFB

Try it with the app in hand

The fastest way through this chapter is with Pilot EFB open on your own phone or iPad. Informational reference only, not a certified EFB.

Pilot EFB

Pilot EFB

A flight companion for pilots

Azimuth Labs Ltd · Registered in England and Wales, Company No. 17289059. · ICO No. ZC178458.
Registered office: 82A James Carter Road, Mildenhall, Suffolk, IP28 7DE, United Kingdom.
Contact: support@pilotefb.com

© 2026 Pilot EFB. All rights reserved. Pilot EFB is not a certified Electronic Flight Bag and is not affiliated with any aviation authority, airline, or aircraft manufacturer. Apple, the Apple logo, iPhone, iPad and iPadOS are trademarks of Apple Inc. App Store is a service mark of Apple Inc.