STRATOSENSE BEACON · ESTABLISHED
Independent
compliance visibility
Beacon observes flight activity, compares it against the flight-plan and authorization context available to it, flags what is unexpected and reports it through implemented communication and regulatory pathways.
Established
Independent
of the aircraft.
Beacon is mounted in the environment it monitors, not on an airframe and not in a control path. Nothing about it depends on the observed aircraft cooperating, which is precisely the condition it exists for.
What it can resolve about a given aircraft depends on what that aircraft makes available. Beacon reports what it observed and what it could identify — and is explicit about what it could not.
WHAT IT IS FOR
Visibility that does not
depend on the aircraft
Some operations cannot be reached through a controller interface — the aircraft is unknown, the link is proprietary, or nothing on the airframe is willing to talk. Beacon provides an independent view in those conditions, so an operational picture is not limited to cooperating aircraft alone.
StratoSense Beacon / Detection chain
Simulated feed- 01Observe — flight activity detected in the monitored area.
DETECTION SCENARIO
Same logic.
Two different outcomes.
An aircraft enters the monitored area. Beacon observes it, resolves what context it can, and compares that against the available flight-plan and authorization context. Whether it is flagged depends entirely on what that comparison finds.
Beacon / detection scenario
Simulated feedThe chain
Observe
Detect and observe flight activity in the monitored area.
Identify
Resolve available aircraft and operational context, where that context is broadcast or otherwise available.
Compare
Compare the observed activity against the available flight-plan and authorization context.
Flag
Mark activity that is unauthorized, unexpected or unplanned relative to that context.
Report
Report the event through the implemented communication and regulatory pathways.
THE BOUNDARY
What Beacon
does not do.
Beacon has no arm or control-chain interface. It does not sit in the RC path, it is not connected to a flight controller, and it therefore does not physically prevent an aircraft from arming or flying.
Beacon does not detect every aircraft. Coverage depends on the deployed devices, what the observed aircraft makes available, the communications in use and the authorized external data sources connected to the platform.
Beacon does not decide what is lawful. It compares observed activity against available authorization context and reports the difference.
IN THE OPERATIONAL PICTURE
A detected aircraft,
beside a connected one
Independently detected activity appears in the same operational picture as connected aircraft, and is labelled for what it is: a detection, with whatever identity and context could be resolved, and nothing more.
Authority view / detected activity
Simulated feedUnassociated activity · Zone C
- Source
- Beacon — independent detection
- Aircraft identity
- Not resolved
- Flight plan
- No plan associated
- Authorization
- No authorization context
- Observed
- 09:48:19 – 09:52:55
- Disposition
- Flagged and reported
Independent visibility,
honestly scoped.
We will tell you what Beacon can see in your environment and, just as plainly, what it cannot.