Skip to content
Flight Deck
Start planning
Flight Deck

From an area on the map to a mission file you can fly.

Plan survey and waypoint missions, check every leg against zones and terrain, and export files Mission Planner and QGroundControl open as they are.

Start planningSee how it works

Free during beta. Runs in the browser. Built for ArduPilot vehicles.

Exports to

  • .plan
  • .waypoints
  • .kml
  • .geojson
  • .csv
  • .json

Opens in Mission Planner and QGroundControl

How a mission comes together

One map view, start to finish. No desktop install and no plugin chain.

  1. Draw

    Outline the survey area or drop waypoints on the map. Altitude, speed and overlap are set once as mission defaults.

  2. Check

    Every leg is tested against your zones, terrain and limits on each edit. Findings name the waypoint to fix.

  3. Export

    Download a .plan for QGroundControl or a .waypoints file for Mission Planner, then upload it as usual.

What it does for you

Planning tools that use real geometry, with checks that run on every edit.

  • Survey grids

    Draw a polygon and get lanes sized to your camera, altitude and overlap, at the angle with the fewest turns.

    Area
    6.8 ha
    Spacing
    24 m
    Side overlap
    70%
    Lanes
    9

  • Shorter routes

    Reorder scattered waypoints; takeoff stays first and return-to-launch stays last. See the saving before you apply it.

    Before4.82 km
    After3.61 km

    Saved1.21 km (25%)

  • Zones on every leg

    Keep-out and keep-in zones are tested along each leg, not only at the waypoints.

    Leg 7 → 8 crosses keep-out zone “Airfield”Route around adds 0.31 km

  • Terrain clearance

    Elevation along each leg is compared with your altitude, so a ridge between two waypoints shows up before the flight.

    Clearance 34 m between waypoints 4 and 5 (limit 40 m)

  • Exports that open

    Six formats from one mission, with zones and rally points carried into the .plan file.

    • .planQGroundControl and Mission Planner, incl. geofence and rally points
    • .waypointsQGC WPL 110 for Mission Planner and MAVProxy
    • .kmlRoute, waypoints and zones for sharing
    • .geojsonFor GIS tools
    • .csvOne row per item for review
    • .jsonFull re-importable backup

  • A checks list you can act on

    Each finding names the waypoint or leg, says why it matters and selects it on the map.

    • Error: Leg 7 → 8 crosses keep-out zone “Airfield”
    • Warning: Terrain clearance 34 m between 4 and 5
    • Pass: Altitude within 0–120 m on every item
    • Pass: DO_JUMP targets exist and terminate
    • Pass: Endurance 14 min of a 22 min budget

The numbers

Limits the editor and the API enforce today, and the model behind every time estimate.

ItemValue
Mission itemsWaypoints and commands per mission2,000
ZonesKeep-out, keep-in and no-fly, circle or polygon200
Export formats.plan .waypoints .kml .geojson .csv .json6
Import formats.plan .waypoints .json3
Check rulesStructure, limits, zones, terrain, endurance, DO_JUMP21
Time modelAcceleration per leg, 3 m/s climb, 1.5 m/s descent2 m/s²
Fig. 1 Limits and defaults in the current release

Pre-flight checks

They run on every edit, per leg rather than per waypoint, with fixed thresholds you set. Nothing to remember to press.

  • PassAltitude limitsEvery item between your minimum and maximumAll 7 legs pass
  • WarningTerrain clearanceGround sampled along the leg, against your AGL minimumLeg 4–5: warning
  • ErrorZonesEach leg intersected with keep-out and keep-in zonesLeg 7–8: error
  • PassSpeed limitCommanded speeds against your maximumAll 7 legs pass
  • PassBattery and timeEstimated flight time against rated endurance14 min of a 22 min budget
  • PassSequence and DO_JUMPTakeoff first, return last, jump targets valid and finiteValid
Example mission, eight waypoints. Warning: clearance 34 m, limit 40 m Error: leg crosses a keep-out zone

Questions

Something else? Sign up and use the feedback link in the app.

Flight Deck plans for ArduPilot vehicles. Export a QGroundControl .plan or a QGC WPL 110 .waypoints file, open it in QGroundControl, Mission Planner or MAVProxy, then upload it to your flight controller as usual.Yes, during the beta. Planning, checks and every export format are free. We will give plenty of notice before introducing any paid plan, and missions you have made stay yours.Each leg is tested against your keep-out and keep-in zones and the terrain along it, plus altitude and speed limits, the mission sequence and DO_JUMP targets, and an endurance budget. Findings appear in the Checks tab with the waypoint to fix.Yes. Import a QGroundControl .plan, a QGC WPL 110 .waypoints file or a Flight Deck .json backup, and keep editing from there.Yes, and it is optional. Describe the job and it drafts a mission; the same pre-flight checks run on the draft, and nothing changes in your plan until you approve it. It needs an API key. Everything else works without one.Passwords are hashed with Argon2id, sessions are stored as hashed tokens, and resetting your password signs out every other session.

Plan the next flight

Create an account, draw an area and export a checked mission file. No install, no card.

Start planning