Somewhere above your operation, one aircraft is becoming relevant.
AERVALE is airspace assurance for professional drone and BVLOS operators. It shows when surrounding cooperative aviation activity matters to your declared operation — and keeps a record you can reconstruct afterwards.
- Track state
- Observed
- Time to volume
- —
- Margin over ceiling
- —
- Last observation
- —
Simulation · illustrative terrain, volume and traffic
Flight tracking was built to show aircraft. An operation needs to know which ones matter.
-
A few hundred feet is the whole question.
Low-level operations sit close to crewed traffic above, below and beside the declared volume. A flat map of dots does not say which aircraft is relevant to this operation, at this altitude, in the next few minutes.
-
The picture is never complete.
Cooperative data arrives late, in fragments, sometimes not at all. Pretending otherwise is how awareness turns into false confidence. The age and source of every observation has to stay visible.
-
Afterwards, memory is not evidence.
When a regulator, insurer or customer asks what you knew and what you did, a screenshot or a recollection will not do. The operation needs a record that can be reconstructed.
One operating volume. Everything around it, filtered by relevance.
-
01 Detect
Define the declared operating volume. Surrounding cooperative aircraft are observed and held as background until they matter.
-
02 Predict
A track is projected forward against the volume — altitude, trajectory and proximity — with its uncertainty shown, not hidden.
-
03 Respond
When a track becomes relevant, the operator sees why: margin, timing and source age. The decision stays with the operator and their procedures.
-
04 Record
The encounter is preserved as a structured timeline: what was observed, what was projected, what the operator did.
- Detect
- Predict
- Respond
- Record
- Investigate
- Report
Simulation · illustrative terrain, volume and traffic
When someone asks what happened, you can show them.
Every relevant encounter is kept as a timeline you can reopen, investigate and report from. Built to support the evidence that professional BVLOS operations are asked to provide.
| Time | Event | Kept with it |
|---|---|---|
| T−04:20 | Aircraft first observed | Source · observation age · reported altitude |
| T−03:05 | Observations drop out for 38 s | Gap recorded, not smoothed over |
| T−02:10 | Track projected toward the volume | Declared volume version · uncertainty at that moment |
| T−01:15 | Track becomes relevant | Altitude margin · time to volume · altitude reference |
| T−00:50 | Operator acknowledges, applies own procedure | Who · when · what was recorded |
| T+02:30 | Track clears the volume | Encounter closed · report generated |
05 Investigate
Replay an encounter against the volume and flight intent that applied at the time, with the observations as they were received.
06 Report
Generate a report that is fixed at the moment of generation, so later changes to settings cannot quietly rewrite what was known.
Where a few hundred feet matters most.
We are still validating which of these hurts first. Tell us which one is yours.
Linear infrastructure
Rail, pipeline and power-line inspection that runs for kilometres and crosses low-level routes.
Delivery & medical logistics
Repeated corridors near hospitals, airfields and helicopter landing sites, where the record matters as much as the flight.
Coastal & offshore survey
Long-range work in busy low-level airspace used by helicopters and general aviation.
Public safety & emergency response
Short-notice operations sharing the sky with crewed rescue and police aviation.
What it is not
Not a Detect-and-Avoid system. No guarantee of separation or complete coverage. Cooperative aircraft only — aircraft that do not broadcast are not seen. It supports, and does not replace, the operator’s own procedures and judgement.
See your operation differently.
Give us an operating area and we will show you how the surrounding airspace looks through your declared volume. Tell us a little about your operation and we will reply personally.
- 01You send the details on the right. Nothing else is needed.
- 02We read it and reply from [email protected] to arrange a private demo.
- 03In the demo we use your operating area, not a generic example.
Prefer email? [email protected]
General enquiries: [email protected]
Request received
Thank you. Your request has gone to [email protected] and we will reply to to arrange your private demo.