Guidance reviewed · 10 NOV 2026
Pre-flight planning workspace

Build a better flight briefing.

Locate your site. Review conditions. Record the checks that matter.

How data is saved · backups, recovery & evidence copies

Where your records are stored

Flightdesk keeps saved flight records, pilot/operator profiles, battery information and battery replacement history in this browser’s local storage on this device. Saved records normally remain when you close and reopen the browser. They are not automatically backed up to a cloud account or synchronised to another phone, computer or browser.

What is saved, and when?

  • Flight form: entering answers or ticking checks does not automatically save a flight record. Use Save flight record to capture the current mission, readings, checks and evidence. Each save creates a separate dated snapshot; it does not overwrite earlier snapshots.
  • Profiles and batteries: use Save profile or Save battery record to retain new or edited records. The app also stores recorded battery updates and replacement history as you use those controls. Unsaved editor changes are not retained.
  • Current work: unsaved form entries and live confirmations can be lost when you reload, close the app or apply an update. Save the mission before doing so. Downloaded backups contain saved records, not the unsaved current form.

Keep a separate backup on disk

Periodically download your data to disk—ideally after each fieldwork session, and before clearing browser data, changing devices or moving to a new app address. First save the current mission, then select Download all flight records above. Check that the JSON file has finished downloading and keep it in a safe folder outside the browser, with a second copy if these records are important.

Clearing site/browser storage, using Clear all app data, losing the device, or the browser removing stored data can delete your records. Private/incognito browsing may discard them when the session closes. Installing the app does not provide a separate backup. Another browser, browser profile or app address has separate storage; an installed app may also use separate storage on some devices. If records are deleted and no downloaded backup exists, Flightdesk cannot recover them.

Download all flight records saves a JSON backup containing every saved mission snapshot, including its recorded checks, notes, forecast, airspace information and readiness result, plus saved crew profiles, battery inventory and replacement history. Save the current mission first: unsaved form entries are excluded.

Upload past flight records accepts a downloaded all-data backup or an individual Flightdesk mission JSON. Restore a backup after browser storage is cleared or to move devices. Existing record IDs are retained, so uploading the same file again does not duplicate or overwrite them. Restored readiness is historical; complete fresh checks for a new flight.

Keep a copy outside this browser, for example on your computer or secure drive. Browser storage and installation alone are not a backup. These files contain private crew and site information.

For review by the CAA or others: open the HTML report, then use your browser’s Print / Save as PDF if required. It contains every saved snapshot and the information recorded at that time. These are pilot-recorded planning records, not proof a flight took place or independent verification of compliance. Review personal information before sharing. Keep the JSON backup for recovery; HTML/PDF reports cannot be imported.

Clear all app data

Permanent deletion on this browser/device. This deletes all saved flight records, pilot/operator profiles, battery information, active and removed battery inventories, battery replacement history, saved weather-service links and app preferences. It also clears the current form, live readings and retrieved briefing data when the app restarts.

If you have not first saved a backup to disk, deleted records will be lost forever. Save the current mission first if you want to retain it; unsaved form entries are not included in a backup. Other devices and files already downloaded to disk are unaffected.

  1. Download a complete JSON backup using the button below.
  2. Check that the file has finished downloading and is saved somewhere safe.
  3. Confirm the statement, then select Clear all app data. You will be asked once more before deletion.

Download a complete backup before enabling deletion.

Flightdesk UK · installable app

Preparing offline access…

Install on a phone or computer · backup & offline help
  1. iPhone/iPad: open this address in Safari, tap Share, then Add to Home Screen. Enable Open as Web App if offered.
  2. Android: open in Chrome and use Install Flightdesk when available, or the browser menu → Install app / Add to Home screen.
  3. Windows, Mac or Linux: open in Chrome or Edge and use the install icon in the address bar or the browser menu’s Install option. Supported Safari versions also offer File → Add to Dock.

Open once online and wait for “Offline app ready” before relying on offline access. Offline mode supports forms and saved records; fresh weather, postcode lookup, maps and external guidance require internet. Offline planning remains NO-GO. Installation does not synchronise devices or guarantee permanent storage.

Save the current mission before applying updates: reload resets the live form. Saved snapshots and inventory remain. On shared devices, cached app content and local records may remain accessible after sign-out; install only on a trusted device.

Use the download and upload buttons beside Print / save PDF above to back up or recover saved records.

Backups include saved flight snapshots, pilot/operator details, active/removed batteries and replacement history; they exclude unsaved form edits and live weather. Keep them private. Restore merges records by their IDs without overwriting existing entries, resets live confirmations, and does not restore a historical GO as a current decision. Back up on the old address before moving hosting. Browser and installed-app storage may differ, especially on Apple devices.

Planning support · not a CAA approval or flight clearanceThis app supports ordinary Open Category planning. It cannot determine flight legality or verify credentials. Map layers and NOTAM collection are supplementary screening; obtain a current official briefing. The operator and remote pilot remain responsible. Specific, Certified and association-authorised operations require their own procedures.
Briefing readiness · operator decision support

NO-GO · planning incomplete

Complete the mission, crew, battery and evidence checks.

Outstanding items

    Green GO means the configured planning gates and your declarations are complete. Purple WARNING means forecast exceedances are acknowledged and require careful on-site assessment; cancel if applicable limits cannot be met. Red NO-GO means blocking items remain. It is not CAA approval, airspace clearance or a guarantee of safety. Reassess conditions at the launch site and throughout flight.

    Finish your briefing, review the GO/NO-GO result, then save this mission. You can also save an incomplete NO-GO plan. Each save creates a separate dated snapshot; it never overwrites an earlier record.

    New mission · not yet saved.

    Copy current form: saves a snapshot of the form you are filling in now, then uses its setup for a new mission. Use this for the next flight at the same site.

    Load setup from an earlier saved mission or file

    Use an earlier saved mission: select a record already saved in this browser, then click Prefill new mission. This uses that earlier setup rather than the current form.

    Upload a record: import a Flightdesk mission JSON or complete backup from a file, for example from another device. Upload only adds records to the selection list; choose one and click Prefill new mission to apply it. Save the current draft before replacing it.

    All routes copy project, site, aircraft, limits and reference notes for review. Enter a new mission title, check differences, select/update the flight battery and renew cell readings, weather, NOTAM checks and confirmations. Historical GO is never restored.

    Using a saved setup replaces the current draft; save it first if needed. Archived readiness is historical and is never restored as a live GO.

    Records stay in this browser/device, including saved crew details and site coordinates. Download important records as backups. Copies retain project/site and setup but reset weather, battery readings and confirmations. Devices do not synchronise.

    Operating location

    NATS reference layers + NOTAM screening
    ◎
    Select a site to load the map.
    Basemap features do not establish permission to fly.
    No site selected.

    Airspace layers & NOTAM briefing

    Reference visualisation and conservative screening—not flight clearance. NATS marks its KML visualisation “Not for operational use”. Confirm boundaries, activation and permissions in the authoritative AIP and a current official briefing. Map layer switches change visibility only; hidden layers still appear in the overlap screening.

    Mapped features potentially overlapping the mission area
    NOTAM candidates within two hours of the selected time

    Circles show Q-line screening extents, not actual restricted boundaries. The local shortlist screens out clearly identified overseas conflict-zone advisories and notices demonstrably above the stated height envelope; excluded items and reasons remain available below. Read schedules, the full text, valid dates and any cancellations/replacements. An empty result is not proof of unrestricted airspace.

    NOTAM screening pending.

    Optional height-screening detail · verified terrain elevation

    Only needed to screen explicit AMSL lower limits. Enter the highest terrain elevation anywhere in the operating area, not just launch elevation. Leave blank if uncertain; notices are then retained. Flight levels are not converted to AMSL.

    Notices with unparsed location · manual review required
    Outside the local/height shortlist · view notices and screening reasons

    The NOTAM source is refreshed on demand; the published NATS contingency collection is hourly and covers approximately seven days. An independently archived copy is labelled explicitly if the official feed is unavailable. Neither this screening nor an archive replaces an official pre-flight briefing.

    NATS restriction definitions/map ↗ · NATS full PIB / contingency notices ↗ · AIP Supplements / briefing sheets ↗

    Coverage gaps: local byelaws, landowner access, environmental designations, uncharted small airfields, obstacles and emergencies are not exhaustively mapped. Check separately. Reference data may include Crown Dependencies: confirm jurisdiction. NATS attribution: © NATS; aviation use only, not for resale. Curved boundaries are approximated and may show artificial gaps.

    Model forecast, not observations

    Conditions at the briefing hour

    No data
    Select a location to retrieve weather. No sample values are used.

    Hourly outlook

    Waiting for a site.
    Select a site and forecast time to see the flight-window outlook.
    Show hourly forecast data
    Wind: m/s · heights: above ground · times: Europe/London
    TimeWind 10 mGust 10 mWind 80 mPrecip. chanceVisibilityRain · mm/hTemp · °C
    Forecast limitations and freshness

    Model grid conditions may differ from your launch site, especially near terrain and buildings. 80 m wind is not the wind at any arbitrary flight height. No automated aircraft-limit or visibility safety decision is made. Compare forecasts with on-site observations, warnings and manufacturer limits. Data refreshes every 15 minutes while visible; refresh again before flight. Retrieval time is not model issue time. Sunset is not a legal determination of night.

    Weather map · regional forecasts and recent radar

    Open-source Leaflet map with Open-Meteo forecasts. Regional context only; forecast points are model samples, not weather stations or a continuous high-resolution survey. Map colours do not alter the GO/NO-GO checks.

    Select a site to load regional weather.

    Model point coordinates will appear after loading.

    Forecast follows the flight date/hour in Europe/London. Requests form a 5 km-spaced, approximately 20 × 20 km sampling area around launch; returned model locations may be offset; panning does not fetch more points. Local terrain, turbulence and wind at flight height can differ. Forecast data: Open-Meteo · CC BY 4.0. Public API is for eligible non-commercial use; commercial users need appropriate API access. Coordinates go to weather and map providers when loaded.

    Recent rain radar · optional

    RainViewer is a free-access service, not an open-source data service. Free use is limited to eligible personal/educational use; commercial use requires separate provider terms. Radar shows the recent past, independently of the selected flight date. It is not a rain forecast.

    Radar not loaded.

    Radar uses RainViewer’s Universal Blue reflectivity palette (scheme 2). View the dBZ colour legend. These are not calibrated surface rainfall rates. Black coverage shading means no radar coverage; missing data can also appear transparent. Maximum native tile zoom is 7. Weather data by RainViewer.

    Paid subscriptions and weather-service links · optional

    A consumer subscription does not automatically grant API access. Open your subscribed service in its own tab and sign in there. Saved links are shortcuts, not account connections; premium layers are not imported.

    Open Windy · Open Ventusky


    Use only your own Open-Meteo API subscription key. It is sent directly to customer-api.open-meteo.com for forecasts, held in page memory, excluded from saved missions/backups, and cleared on reload. It is not a secure shared server credential. This setting applies to both point forecasts and the regional map. Other providers’ keys are not supported. Service shortcuts are stored on this device and are not included in mission backups.

    GO/NO-GO required. This acknowledgement does not override weather limits or missing/stale forecast data. Reconfirm after changing the site, flight interval, weather limits or forecast.

    3Open Category guidance

    Incomplete profile
    Complete the operation profile to display relevant guidance.

    Guidance checked against CAA sources on 10 November 2026. Simplified scope: ordinary Open operations; no assessment of exemptions, association authorisations, class documentation, airspace approval or site-specific legality. Recheck original sources before flight.

    Battery management and health

    Manufacturer suggestions + pilot checks

    Battery selection, inspection and cell health

    GO/NO-GO critical fields must be completed or confirmed for a green result. Optional fields are supplementary records. Manufacturer suggestions are prefilled where verified; review your exact configuration. Current charge, condition and measured cell voltages cannot be prefilled.

    Manufacturer battery suggestions · view values and source
    No flight pack selected.

    Dual/multi-battery aircraft need a complete matched set. Record the lowest state of charge in the set, not an average. Compatibility, cell balance and physical condition must be inspected by the pilot.

    Battery / matched-set record

    Inspection instructions and manufacturer guidance
    • Not inspected: you have not completed the checks, or do not know the battery’s condition. No flight readiness is granted.
    • Serviceable · pilot inspected: all routine pre-flight checks in the applicable manual are complete for every fitted pack, with no unresolved damage, faults or maintenance concerns. Check the casing, contacts, secure fitting, current DJI app warnings and the charge/cell checks. A visual check alone does not establish internal battery health.
    • Storage / needs preparation: no known defect, but the battery is stored, needs charging or other manufacturer-prescribed preparation, or is not yet ready for this flight. Complete preparation and recheck it before changing to serviceable.
    • Quarantined / damaged / fault: suspected damage, swelling, leakage, a crash/heavy impact or an unresolved battery fault. Keep it out of flight use and follow DJI support instructions; do not attempt to clear a physical defect by charging or cycling it.

    These checks normally use visual inspection and the DJI app. Do not open or dismantle the battery. Any maintenance tools, training or service requirements come from the exact manufacturer procedure. If uncertain, leave it Not inspected; use Quarantined when damage or a fault is suspected. Only Serviceable can pass the app’s condition gate, and the other planning checks must still pass.

    Tick only if you have considered the notes and have nothing to add. This is saved with the record; it does not replace the condition inspection. If you enter a note, this tick clears. Clear the note before selecting Nothing to report.

    Controller readings · cell balance & take-off charge · GO/NO-GO critical

    Read the lowest and highest individual-cell voltage for each physical pack. Do not enter total pack voltage here. Cell spread = highest − lowest within that pack; paired-pack voltage mismatch is a separate check.

    Defaults use the available DJI source. To edit the voltage criterion or reference, select Override and record why. An override cannot relax a verified manufacturer ceiling for a green planning result. Unknown criteria require an explicitly documented operator procedure; an operator proposal is not manufacturer approval.

    Manufacturer voltage references · not measured values
    Nominal per-cell reference · not a minimumNot verified for this battery
    Derived per-cell charging ceiling · not a target readingNot verified for this battery

    References fill automatically where verified. Neither specifies the actual lowest or highest cell voltage at your present charge, temperature and load. Enter both measured readings from the DJI app below; reference values never complete the balance check.

    Cell balance: incomplete.

    Battery replacement history

    Saved in this browser and included in the printed briefing. Failed records cannot be reused to clear this replacement check. A recorded GO means planning gates were completed, not flight clearance.

    The status reports a completed balance screen only, not battery health or safe endurance. Charge state, temperature, load and rest time affect voltage. A balanced but deeply discharged or damaged battery is not serviceable; follow DJI warnings and the exact battery manual.

    Flight-time allowance · GO/NO-GO critical

    This sets a conservative total time from take-off to landing for this mission. The app adjusts a supported full-charge flight time for the charge actually available, preserves your landing charge, then subtracts any extra time margin. The result automatically sets the mission duration used by the weather and daylight checks.

    Start with the battery record above, then complete these three inputs. A manufacturer's maximum is shown as a reference below; it is not a validated time for your payload, battery condition and weather.

    Your calculated mission duration

    No calculate button is needed. The result updates as you enter values. It is a planning ceiling, not a target: finish earlier when the task is complete or conditions require it. Normal return and landing must fit within this time.

    Maximum possible total mission duration (take-off to landing)Not calculated yet

    Calculated automatically from the selected battery and the flight-time inputs above.

    Waiting for battery and flight-time inputs.

    The available duration is the largest whole minute strictly below the battery allowance (maximum 180 minutes). It includes take-off, return and landing. Weather and daylight checks use this calculated maximum duration. This estimate is not a guarantee of endurance.

    Select a battery record and enter the three flight-time values above.

    Example: 20-minute reference → 17-minute mission

    Example only: your comparable full-battery flight takes 20 minutes to reach 25%. Your selected battery is currently at 100%, and you keep an extra 2 minutes back. The planning allowance is 18 minutes (20 − 2). Your total flight, including take-off, return and landing, must be shorter than 18 minutes. The app therefore fills in 17 minutes automatically as the maximum planning duration.

    If that battery starts at 80%, the same simple estimate becomes 12.7 minutes: 20 × (80 − 25) ÷ (100 − 25) − 2. The app fills in 12 minutes. For a matched pair, the lower charge is used; two fitted batteries do not double the flight time.

    Formula: full-battery time to landing charge × (starting charge − landing charge) ÷ (100 − landing charge) − extra time kept back. This is a linear planning estimate. It does not predict nonlinear discharge, wind, temperature or ageing. If you lack supporting flight data or an approved procedure, leave the time blank: the plan stays NO-GO until reviewed.

    Confirm battery readiness · GO/NO-GO critical

    Saved battery inventory

    Select records to remove from the active inventory. Saved flight snapshots and battery replacement history are retained. Removed inventory records can be restored below.

    4Pilot’s evidence record

    0 / 10 recorded
    Checks remain outstanding.Self-recorded · not independently verified
    Final briefing readiness

    NO-GO · planning incomplete

    Complete the required inputs and checks.

    Outstanding items

      This repeats the live summary at the top. GO means the configured planning gates are complete; it is not CAA approval, airspace clearance or a guarantee of safety. The remote pilot makes the final on-site decision.

      Checks reset when site, schedule or operation profile changes. Weather refresh invalidates the weather check. Notes remain for revision. Save a flight record or export before closing; saved snapshots preserve the evidence at the time of saving.
      CAA Drone Code ↗Official Open Category guidanceNATS restrictions ↗Permanent restrictions; obtain a separate NOTAM briefingNATS AIS ↗Current AIP, supplements and briefing servicesMet Office ↗Weather warnings and forecast cross-check

      Review scope & remaining limitations

      10 NOV 2026
      What this review changed
      Finding in previous appChange made
      Aircraft names were shown without legal operating context.Explicit class, mass and intended category inputs; warnings for profile conflicts. Model names do not infer class.
      Six generic ticks omitted important requirements.Ten evidence groups cover credentials, airspace, land access, separation, height/VLOS, Remote ID, night lighting, insurance, weather, aircraft and emergency preparation.
      Forecast retrieval could be mistaken for an operational assessment.Data freshness, selected time, past-hour and outside-daylight prompts; no automatic “safe to fly” result.
      Long tables and uneven cards obscured the task.Mission sidebar, larger map, compact weather summary, scrollable hourly table, source-linked review and printable evidence record.

      Not a certification: This implementation has not been approved by the CAA. A software review cannot establish compliance for every aircraft, flight or authorisation. The app displays NATS reference layers and screens a UK NOTAM collection against a mission-area envelope. It cannot verify documents, exhaustively analyse a route/volume or assess Specific/Certified operations. The red/green result describes completion of configured planning gates, not legal flight clearance. It includes current forecast screening, saved-ID expiry, battery budget and pilot declarations. Known data gaps remain red until resolved or referenced manually. Class conformity, private-build eligibility, legacy market history and special exceptions require separate verification.

      Before operational reliance: complete an independent operator review against applicable regulations and your procedures, verify current official data and obtain any necessary permissions. Rules may change after the review date.

      Official sources used in the review