Air-risk evidence for drone operations · JARUS SORA
How busy is the sky where you want to fly?
Flight Density measures observed aircraft traffic in your exact operational volume, by altitude band and by hour, and turns it into evidence for your SORA air-risk assessment. No provider APIs, no GIS, no guesswork.
- Movements per hour by altitude band
- Coverage beside every number
- Reports built for SORA air-risk cases
Kingsdown corridor · SFC – 2,000 ft AGL
1–31 Aug 2026 · 06:00 – 22:00 · All days · Europe/London
Average observed traffic
2.7
movements/hour
Total movements
1,842
P95 hour
7
mvts
Peak hour
14
mvts
Traffic-free hours
39%
Data coverage
97.8%
97.8% data coverage · 12:00–12:37 unavailable and excluded from averages · airspace effective 12 Aug 2026.
Built for the specific category
Evidence for the air-risk steps of SORA
JARUS SORA lets an operator lower the air risk class by demonstrating, with data, that local traffic is lighter than the generalised assumption. Flight Density produces that data for the exact volume, altitudes and hours you intend to fly.
- SORA step 4
Initial air risk class
The generalised ARC assumes a typical density for your airspace class, altitude and proximity to aerodromes. Draw your operational volume and see that context on the map before you start.
- SORA step 5 · Annex C
Strategic mitigation with local density evidence
Show what actually flies through your volume, hour by hour and band by band, for the days and times you want to operate. Observed movements, percentiles and peaks, with coverage stated beside every number.
This is where Flight Density does the work
- Residual ARC · TMPR
A submission you can stand behind
Every report records the sources, deduplication, valid and missing hours, the airspace effective on the analysis date and the exact filters, so a reviewer can retrace every figure.
What your reviewer sees
Works alongside JARUS SORA 2.5 and the UK CAA's SORA-based assessments for the specific category. Flight Density supplies the observed-traffic evidence; the competent authority decides the mitigation credit.
- Movements per hour by altitude band, including 0–400 ft and 400–1,000 ft
- Average, median, P95 and peak hours for your daily window and weekdays
- Valid hours and missing intervals: missing data is never counted as zero traffic
- Airspace overlays and intersections as effective on the analysis date
- Versioned PDF, XLSX and CSV reports with provenance and methodology
Collect, analyse, explore, report
One saved configuration drives the map, the tables, the 3D view and the report, so the numbers always describe the same thing.
Capture live traffic
Set the volume, schedule and sources, then close the browser. Collection runs server-side with per-source health and an honest ledger of valid, missing and degraded minutes.
Analyse the archive
See what is already held for your volume before you collect anything. Coverage is checked first, and licensed backfill is offered where rights allow.
Explore in 3D
Traffic flows in true position and altitude, with altitude slicing, time playback and a colour scale that is always labelled with real values.
Report with provenance
Versioned PDF, XLSX and CSV reports carry the filters, sources, coverage, missing intervals and the airspace snapshot effective on the analysis date.
Three questions. One defensible answer.
Answer them once and every view reads the same configuration: map, tables, 3D and report.
- 1
Where?
Draw the operational volume
Point and radius, polygon, a corridor along your route, or import KML, KMZ or GeoJSON.
- 2
What altitude?
Set the floor and ceiling
SFC, AGL, AMSL or flight levels. Analysis intersects a true 3D volume, not a flat outline.
- 3
When?
Choose the period
Dates, daily window, weekdays and timezone. Then analyse the archive or start collecting.
Coverage is checked before you commit: “82% of the requested period is already in the archive.” Then analyse existing data, start collecting, or bring in records you already hold.
Data a regulator can trust
Observed traffic from ADS-B, FLARM and other feeds is not every aircraft that flew. Flight Density says so plainly, shows how much of your period was actually observed, and never fills a gap with a zero.
- Missing data is never zero traffic
- Averages use valid hours only. A feed outage is reported as missing, with the interval named, never as a quiet hour that flatters your case.
- Airspace as it was on the day
- Overlays and intersections are reconstructed for the date analysed, with vertical limits and validity dates shown.
- Provenance in every report
- Filters, sources, deduplication, data-through time, missing intervals, airspace snapshot and calculation versions, all recorded.
Build your air-risk evidence this week
Draw your operational volume, see what the archive already holds, and have a report ready for your SORA submission.