Observe
See available traffic observations beside a defined drone operation.
Sentryn Airspace / Operations governance
Sentryn Airspace.
Airspace awareness.
Explainable warnings.
Traceable decisions.
Explore how airspace observations, own-drone telemetry and operational constraints can support a responsible operator — with the context behind each warning kept visible.
Illustrative scenario · Synthetic data · Operator-led decisions
SCHEMATIC REFERENCE · NO LIVE DATA · NOT TO SCALE
Current scope & engagement
Public demonstration of passive airspace monitoring, proximity warning and data-quality limitations using fully synthetic inputs. This is not a live service, measured deployment, flight authorisation or collision-prevention claim.
Airspace experience / Dynamic Airspace Protection
Understand the change.
Not just the alert.
Five narrative chapters use three unchanged reference snapshots. Map, warning basis, data quality and illustrative event detail stay linked to the same source state. Press Play or select a chapter.
SENTRYN / AIRSPACE EXPERIENCEILLUSTRATIVE · SYNTHETIC · OFFLINE
Explore the operation / Five chapters
Source: airspace-reference-01 / synthetic snapshotEnvelope follows UAV · Dashed site boundary stays fixed
Inspect illustrative event context ↗
- Scenario & schema
- airspace-reference-01 / schema v1
- Event type
- Proximity warning
- Data freshness
- Current in this scenario
- Assessment basis
- This predefined snapshot represents a proximity warning. The envelope is illustrative, not an operational separation minimum.
- Operator responsibility
- Operator assessment required. No acknowledgement or flight response is claimed.
- Representative event
- Representative warning event; not a measured audit record.
Synthetic example only. No measured timestamps, policy-rule version, cryptographically committed evidence, operator response or operational minimum is claimed.
A static warning snapshot is available. Interactive chapters load only when the synthetic scenario files can be validated. No connection to a live airspace feed is made.
The original three-state demonstration remains available: Open the original illustrative airspace scenario ↗
Why runtime governance matters
A warning is useful when its context is visible.
Evaluate
Assess a synthetic observation against the illustrated protection envelope.
Warn
Surface a bounded, explainable advisory warning to the responsible operator.
Preserve context
Keep the reason, source-state quality and representative event information inspectable.
Missing data is not clearance.
Operator clarity
Separate an observation, its interpretation and the decision that remains with the operator.
Data-quality limits
Identify stale observations and avoid treating a missing feed as a resolved warning.
Inspectability
Relate a synthetic warning to the corresponding source state and assessment basis.
Integration / Responsibility
Built around the operation.
Not another flight controller.
01 / Inputs
Available cooperative traffic data, own-drone telemetry and operation-specific rules. Suitability depends on source coverage, timeliness and data permissions.
02 / Sentryn layer
Evaluate a defined monitoring condition, express the warning reason and expose relevant context for review. Advisory monitoring does not imply execution authority.
03 / Operator
The operator assesses the warning and remains responsible for any flight decision. Flight commands stay in the existing control system.
Illustrative scenes only; no vendor coverage, customer endorsement, pilot acceptance, regulatory clearance or commercial SLA is implied.
From operating question to evaluation
Define a useful airspace pilot.
For drone operators, public-safety teams and system integrators evaluating advisory airspace monitoring. Begin with one operation and a warning condition that can be inspected.
The operating question
Which traffic observations or changing operating boundaries should prompt an operator review? Agree the monitored area, relevant traffic and the limits of the available data.
Inputs to establish
Own-drone telemetry, permitted traffic observations, timestamps and a defined operating envelope. Confirm coverage, freshness, usage rights and the meaning of missing data before relying on a feed.
Responsibility boundary
The proposed Sentryn layer evaluates the agreed condition and explains its basis. The operator decides what to do; flight commands remain in the existing control system.
Proposed acceptance evidence
A scenario set with expected warnings, stale-data cases and a traceable record linking inputs to each assessment. Distinguish synthetic replay, live observations and measured results in the acceptance report.
Current public evidence: an illustrative scenario using synthetic inputs. A live pilot, warning performance, data coverage and operational acceptance must be agreed and validated separately.
Read the governability assurance research ↗Scope an evaluation ↗
Define your airspace operation.
Agree the data inputs, warning conditions and evidence required for a bounded pilot.