StratoSense000
STRATOSENSE Request platform access

STRATOSENSE TETHER · IN DEVELOPMENT

The unit that rides
with the pilot

Tether connects to the remote controller. It carries the authorization state for the flight, acquires the telemetry the controller interface makes available, associates it with a known aircraft and operator, logs operational events and uploads them to the platform.

In development

Units built and bench-validated. Field validation in progress.

StratoSense Tether

Ground side.
Always.

The Tether joins the operation where the pilot is. It takes what the supported controller or ground station makes available, binds it to a known aircraft and operator, and carries it onward — so the record of the flight has an origin that can be checked later.

It is never installed on or inside the aircraft.

What it does

01

Authorize

Carries the flight-specific authorization state, before the aircraft leaves the ground.

02

Acquire

Takes telemetry from the supported controller or ground-station interface.

03

Associate

Binds the session to a known aircraft, operator and remote pilot.

04

Log

Records operational events as the flight runs.

05

Upload

Carries telemetry, events and the current compliance state to the platform.

TETHER AND AUTHORIZATION

It carries the permission,
not just the telemetry.

Tether brings the authorization state down to the controller, validates it for the specific flight, and carries the telemetry back up to the same record.

Authorization / the permission artifact

Simulated
StratoSense flight authorization UNVERIFIED
Flight ID
SS-2291
Aircraft
UAS-014
Operator
OP-042
Area
Operation Zone A
Altitude
Authorized band
Time window
14:30 – 15:00
Status
—
Signature
—
Received
Verified
Matched
Device authorized
—
Simulated authorization data · no real permission artifact, token or signature is published here

ACQUISITION, VISUALISED

Many protocols.
One record.

Whatever the source spoke, the record that reaches the platform has one schema, one time base and one device identity.

Acquisition / many protocols, one record

Simulated feed
MAVLink CRSF SBUS i-BUS MSP S.Port LTM OEM source protocol Decode framing + fields Normalise schema + time + id Intelligence state + history one operational record, whatever the source spoke
—
Availability depends on the aircraft, autopilot, controller and configuration in use

Telemetry / packet to dashboard

Simulated feed
Raw Decode Normalise Time align Identity Intelligence bytes on an interface a readable flight record
Altitude
—m AGL
Ground speed
—m/s
Heading
—deg
Battery
—%
GNSS
—
—
The dashboard updates only after normalisation · simulated values

ACQUISITION

What Tether
can acquire.

Supported and target integration pathways. Availability depends on the aircraft, autopilot, remote controller and configuration in use. Not every pathway listed is commercially released, and none implies universal compatibility.

Autopilot / telemetry

MAVLink Widely used open autopilot telemetry protocolIn development
CRSF Crossfire control and telemetry linkTarget integration
S.BUS Serial receiver busTarget integration
i-BUS Serial receiver busTarget integration
MSP Multiwii serial protocolTarget integration
S.Port Smart port telemetryTarget integration
LTM Lightweight telemetryTarget integration
OEM / proprietary Subject to the manufacturer making an interface availablePlanned

Positioning / time

NMEA Standard positioning sentence formatIn development
GNSS Global navigation satellite positioningIn development
UTC reference Common time base for the recordIn development

Physical / wireless interfaces

UART Serial interfaceIn development
USB Host or device interfaceIn development
Bluetooth Short-range wirelessTarget integration
Wi-Fi Local wirelessTarget integration
LTE / 4G Cellular uplinkIn development

THE DATA BOUNDARY

It records what the
interface actually publishes.

Tether can record telemetry and event records that are made available to and received through its supported controller interface.

It does not access internal variables that a specific controller or flight stack does not publish. If the interface does not expose a value, that value is not in the record — and the record says so rather than inferring it.

Tether is not a flight-controller replacement, not an aircraft steering system, and does not autonomously fly the aircraft.

Talk to us about
your controllers.

Tether is in development. Tell us what you fly and we will tell you exactly where your configuration sits on the list above.

Request platform access