FOR REMOTE PILOTS
Before, during
and after the flight
Plan the operation, see the airspace it sits in, carry the authorization state into the flight, watch the aircraft while it runs and keep a record you can return to afterwards.
BEFORE THE FLIGHT
A flight plan is
seven questions.
The plan is what everything else is checked against — the airspace evaluation, the authorization, and later the comparison between what was planned and what actually happened.
- Who
- Remote pilot, operator and organization identity
- What
- Drone / UAS identity and the details of the operation
- When
- Planned date, time and operating window
- Where
- Operating area, planned route and geographic limits
- Purpose
- Commercial, industrial, survey, training, hobby or other applicable purpose
- Parameters
- Planned altitude and other required operational parameters
- Authorization
- The result of the applicable UTM or authorized pathway
PERMISSION FIRST
The aircraft waits
for permission.
Before anything else: a request, an airspace evaluation, a permission issued through the applicable authorized pathway, and a device that verifies it. Only then is the aircraft flight enabled.
StratoSense / Permission before flight
Simulated feedPre-flight / readiness
Simulated feedTHE WORKFLOW
Sign in to airborne.
Every step below changes what the platform actually holds for the flight. Watch the record fill in.
Pilot / from sign-in to airborne
Simulated feed- Remote pilot
- —
- Aircraft
- —
- Flight plan
- —
- Operating area
- —
- Route
- —
- Time window
- —
- Purpose
- —
- Airspace evaluation
- —
- Authorization
- —
- Device validation
- —
AIRSPACE AWARENESS
See the airspace
the flight sits in.
Zones are shown with what they mean for the operation: otherwise permissible, subject to an authorization workflow, or requiring a specific authority. StratoSense evaluates operations against applicable rules and authoritative airspace data — it does not create or invent regulatory zones.
StratoSense / Live airspace
Simulated feed- Altitude
- 118m AGL
- Ground speed
- 9.4m/s
- Heading
- 074.0deg
- Battery
- 76%
- GNSS
- 3D / 14
Zone geometry shown on this website is illustrative. In use, airspace layers come from authoritative sources and carry their own source, sync time, age and version.
Altitude limits such as 120 m are an altitude concept — a ceiling above ground level, not a geographic radius.
AUTHORIZATION
From plan
to permission to operate.
The authorization state is not a label the pilot sets. It is carried from the applicable authorized pathway, validated against the device and the specific flight, and recorded.
Authorization / both outcomes
Simulated feedAuthorization / state machine
Select any stageFlight plan
Who, what, when, where, purpose and parameters are defined.
Airspace evaluation
The plan is evaluated against applicable rules and authoritative airspace data.
Applicable authorization
Authorization is sought through the applicable authorized pathway.
Flight-specific authorization
The result is bound to this flight, not to the account in general.
Device validation
The device validates the authorization it has been given for this flight.
Arm / operate
The operation proceeds with a recorded authorization state.
StratoSense does not itself grant regulatory authorization. It integrates with, carries, validates and records authorization state issued through the applicable authorized pathway.
Integration with DigitalSky is a target integration, subject to the appropriate authorized-service-provider and regulatory integration arrangements. Nothing on this website represents approval, endorsement, certification or partnership.
DURING THE FLIGHT
Watch a flight,
start to finish.
Press start. The simulation runs a complete flight — plan, evaluation, authorization, device validation, flight, telemetry, an event, the cloud record and the sealed historical record — and every readout below moves with it.
StratoSense / Live flight SS-2291
Simulated feed- Altitude
- 0m AGL
- Ground speed
- 0.0m/s
- Heading
- 058.0deg
- Battery
- 96%
- GNSS
- 3D / 9
- Elapsed
- 00:00
Flight plan created
Airspace evaluated
Authorization received
Device validated
Aircraft armed
Telemetry streaming
Position updating
Event detected
Cloud record updated
Flight completed
Historical record created
After the flight
Flight path
The route actually flown, beside the route that was planned.
Telemetry history
Position and altitude over the length of the flight, where available.
Event log
What happened and when, including advisories and device events.
Authorization record
The authorization state the flight operated under.
Audit record
A record that can be returned to and explained afterwards.
Fly with the record
already written.
Ask us for access and we will set up the platform against the airspace you actually operate in.