What one flight leaves behind.
This page describes the data EnCor Command holds for every aircraft and every flight, so a component maker knows what its part must produce and a software maker knows what a model would receive. It also states plainly who can get at it today: the customer, and nobody else.
Telemetry, once a second
Each aircraft reports one record per second, on the ground and in the air. The software marks an aircraft as link-lost after eight seconds of silence.
| Group | Fields | Units |
|---|---|---|
| Position | Latitude, longitude, altitude above ground, altitude above sea level, home position | Degrees, metres |
| Motion | Heading, ground speed, vertical speed | Degrees true, metres per second |
| Power | Battery percent, voltage, temperature | Percent, volts, degrees C |
| Navigation | Satellites, fix type, dilution of precision | Count, class, ratio |
| Link | Signal strength, quality, round-trip delay | dBm, percent, milliseconds |
| State | Flight mode, armed, in flight, avoidance state, health, firmware, status text | Named values |
| Environment | Wind speed and direction at the aircraft | Knots, degrees |
| Video | Where the aircraft's stream can be played, and its type | Address and type |
Commands, from the software to the aircraft
Eleven commands: launch to an altitude, go to a point, orbit a point, hold, change altitude, return and land, land in place, abort, switch thermal palette, and start or stop the video stream. Each carries who issued it and when, and reports back received, executing, done, rejected, or failed, so the record shows what the pilot asked and what the aircraft did. The software refuses a launch, or a go-to into a keep-out zone, that would break the organisation's altitude limit, a geofence, the battery reserve, the satellite minimum, the link minimum, the wind limit, or the one-pilot-to-four-aircraft rule; the aircraft is expected to enforce its own limits as well.
Video
The aircraft pushes short segments of its camera stream over an ordinary outbound connection, which works behind a carrier network with nothing exposed on the aircraft; publishing a stream address for the software to play is supported as an alternative. Thermal cameras expose their palettes, and the palette command switches them. What the pilot saw can be replayed. Video has been verified with published footage, not yet from a camera on a flying airframe.
Flight records, missions, and reports
- Flight record: aircraft, pilot, start and end, track, maximum altitude, battery used, and how many aircraft that pilot had aloft at once, for every flight.
- Call or mission: what the flight was for, who requested it, priority, address, when it launched, and its status over time. Calls can arrive from a dispatch system or be entered by hand.
- Report: a record in its own right, not an export: call summary, inspection findings, counts. AI-produced reports exist today for one outcome, wildlife counts, with evidence-graded findings and a time for each sighting; the per-data-hour pricing is in development.
- Fleet and people: aircraft health and maintenance, pilot certificates and currency, training hours per airframe.
Who can get at it, on 2026-09-09
| Path | State |
|---|---|
| The customer, in EnCor Command | Built |
| The customer exporting records and footage by hand | Built |
| A public view link sharing one aircraft's live video | Built; video only, no data |
| Dispatch systems sending calls in | Built, generic; per-agency adapters to follow |
| Outside software receiving telemetry, video, records, or reports | Not available |
| Partner interface for outside models and tools | Designed, not built; no date stated |
Customers own their data. The aircraft-to-software contract that produces all of the above is shared with hardware partners by arrangement, described in words on the component page.
Questions partners ask
Can I get this data from an EnCor customer today?
Only if the customer exports it and gives it to you. There is no interface through which EnCor Command sends telemetry, video, records, or reports to an outside party. A public view link exists that shares one aircraft's live video with a recipient, and nothing else.
What is the latency of the video?
The recommended path is the aircraft pushing short video segments over an ordinary outbound connection, which adds a few seconds and works behind a carrier network with nothing exposed. A lower-latency streaming path is supported as an alternative where the network allows it. Video has been verified with published footage, not yet from a camera on a flying airframe.
Is the telemetry standard?
It is a plain set of named fields, listed above, sent once a second. It is produced by a small program on the aircraft's companion computer from a MAVLink link to an ArduPilot or PX4 autopilot. Another autopilot can be supported by implementing six vehicle methods against its own kit.
Does EnCor keep the data?
Customers own their data. What EnCor may retain or learn from is governed by the customer contract, which is EnCor's to set.
Will there be a public interface?
One is designed and not built. EnCor will not state a date. This page changes when it ships.