Fixed-wing survey and inspection teams
Plan terrain-relative surveys and infrastructure inspections against your aircraft's declared limits, then review the predicted path, airspace findings, and radio coverage before the field day.
Flightdeck · Design-partner alpha · v0.1.0-alpha.1
Browser-native operations environment for UAVs.
Plan missions against the aircraft you actually fly, see the path it is expected to take, assess airspace and radio coverage before launch, then operate it from an authenticated cockpit in the same private workspace.
Flightdeck is built for teams developing and operating custom aircraft, currently centred on ArduPlane fixed-wing systems: manufacturers, integrators, survey and inspection operators, and flight-test teams whose aircraft do not fit inside a vendor-controlled ecosystem.
01 / Evaluation profile
ArduPlane.
The current cockpit and command model are oriented around custom fixed-wing aircraft using ArduPlane.
Current alpha profile · Fixed-wing
02 / Planning
Aircraft-aware.
Missions are planned against a declared aircraft profile, with predicted flight paths, airspace findings, and radio coverage.
Flight-path prediction · Airspace · RF coverage
03 / Deployment
Private per vehicle.
Each supported aircraft receives one isolated, self-hosted Flightdeck runtime, linked to the vehicle by MAVLink over QUIC.
Self-hosted · MAVLink over QUIC
04 / Command authority
Identity-scoped.
SPIFFE mTLS identifies production operators, while one exclusive write lease gates commands sent toward the aircraft.
SPIFFE mTLS · vehicle.write lease
01 / Who it is for
Built for aircraft that need their own operating environment.
Flightdeck starts with the vehicle, payload, operator, and operation rather than a universal feature matrix, and is aimed at the programme and operations leads responsible for that whole chain.
UAV manufacturers and integrators
Provide customers with an operator environment built around your aircraft, payload, and links, deployed privately, rather than sending them into a generic ground station.
Flight-test and field engineers
Configure radios, RTK, firmware, parameters, and vehicle files in the same workspace used to plan, predict, and fly the test.
Autonomy and payload teams
Integrate perception, companion computers, camera feeds, visual guidance, and custom MAVLink interfaces without building the complete operator shell from scratch.
02 / Why it matters
Understand the operation before the aircraft is airborne.
A conventional ground station draws waypoints and flies them. Flightdeck also estimates how the aircraft will fly them, where terrain, airspace, and the radio link constrain the route, and carries that context from preparation into operation.
Plan with aircraft context
Estimate the flown path from declared performance, turns, climb limits, and forecast wind, then check it against terrain, obstacle clearances, airspace, and predicted radio coverage. The result is an estimate to reason with, not a guarantee of aircraft behaviour.
Operate with context and control
Instruments, telemetry, mission progress, traffic, weather, and video share one operating picture. Commands sent toward the aircraft pass through one exclusive, identity-scoped authority lease.
Build toward reproducible operations
Missions record the aircraft-profile revision, predicted trajectory, operational window, and ground-radio setup they were planned with. A durable, reviewable mission record is being built on that foundation; it is not complete today.
03 / Available today
What Flightdeck does today.
Grouped by the operational question each capability answers. Predictions and assessments are advisory: they estimate, visualise, and highlight constraints. They do not approve a flight.
Aircraft-aware planning
Build terrain-relative surveys against a declared aircraft profile. Flightdeck estimates the flown path from turn performance, climb and sink limits, and forecast wind, flags terrain and obstacle-clearance conflicts, and binds the mission to the profile revision it was planned with. QGroundControl plans import and export.
Airspace assessment and mission review
Submit the predicted trajectory to the Airspace assessment API and review geozone, obstacle-clearance, and A3 separation findings alongside the operational window and weather. Full deployments also persist review processes and immutable review records.
Radio coverage planning
Predict link margin from your antennas, link budget, and tracker setup over terrain, land cover, and Earth curvature, including the lowest usable altitude along the route. The ground-radio setup is saved with the mission and opens with it in the planner and cockpit.
Cockpit and live operation
Primary flight instruments, mission progress, tactical map actions, manual control, and acknowledged commands in an ArduPlane-oriented cockpit, with WebRTC video feeds, ADS-B, Remote ID tracks, radar returns, wind, and forecast weather in the same picture.
Field engineering
Configure SiK radios, operate a u-blox RTK base, flash ArduPilot and PX4 firmware, inspect MAVLink, edit parameters, and retrieve vehicle files without leaving the browser.
Identity, authority, and deployment
One isolated runtime per vehicle, privately deployed. Operators and rover authenticate with SPIFFE X.509 mutual TLS, MAVLink reaches the aircraft over the fleetd QUIC link, and one exclusive, identity-scoped vehicle.write lease gates operator commands.
Design-partner conversations open
Start with one supported configuration.
We start with one vehicle, one autopilot, one payload, and one operation, and agree up front which configuration is supported, which operational requirements apply, and where integration ends. The engagement ends with an installed operating environment, a compatibility and acceptance report, an operator runbook, and a defined support boundary.
To evaluate planning, flight-path prediction, and live airspace assessment first, use the public standalone planner. It runs in the browser without a vehicle deployment and keeps missions in local browser storage.
Engagement deliverables
- 01Supported configuration and integration boundary
- 02Aircraft profile and autopilot integration
- 03Private deployment and PKI
- 04SITL or hardware-in-the-loop acceptance
- 05Contained field evaluation against your operational requirements
- 06Operator runbook, known limitations, and support record
Flightdeck / Supported deployment
Tell us what you fly.
Describe the aircraft, payload, operating environment, and outcome you need. We will identify what Flightdeck already covers, what requires integration, and what evidence is needed before field use.