NoMAC

Scenario workspace

Define geofence layers

Draw geofences, adapt the probabilistic traffic map, then simulate local blue-disk conflicts.

Satellite Dn overlay

Select a geofence in the list to edit it. Drag corners, or select one and press Backspace to remove it.

Geofences

Geofences 0

Altitude levels 0

Analyzed clear area 0 m²

Analyzed area / active drone 0 m²

Moved Dn mass 0

Receiver edge cells 0

U-plan checks

Planned routes are checked separately from the background traffic simulation. Editing or rerouting them does not change the background A/n metric.

Route conflict intervals 0 No U-plans drawn

Planned flight preview

0:00 0:00–0:00 min:sec

Time from scenario start (minutes:seconds)

Speed Show drones

0 planned drones airborne · 0 active pair conflicts

Numbers identify airborne U-plans; amber marks conflicts. A selected plan's original route is dashed. Playback follows planned paths, including exact departure/arrival instants; it does not execute avoidance maneuvers.

Conflict details

One entry per continuous pair conflict. Times and durations describe a separation conflict, not an avoidance maneuver.

U-plan vertical separation

Defaults for new routes

Speed

m/s

Altitude

Departure

min

Random route count

0 U-plans · 0.00 km planned · 0 geofence-band crossings

Scenario model

Configure safety evaluation

Daily operations Average flight duration

min

Simulated days Random seed (optional) Comparison target / flight hour DAA radius

Operational flight hours/day 0

Average active drones 0

Selected DAA threshold 0 m²

Inverse comparison target 0 fh/classification

The same seed, inputs and traffic dataset reproduce the same background snapshots. Export saves the seed used for this run.

A/n research model

Background traffic simulation

Independent five-minute traffic snapshots. Geofences and traffic demand affect these results; U-plans are evaluated separately.

r = 50 m

Mean NMAC-classified blue-disk observations/day 0.00 mean per simulated day

Level-of-safety KPI 0.00 estimated NMAC classifications per 10,000 operations

NMAC per flight hour —

Estimated classified-event interval No events operational flight hours per classified blue disk

Probability of at least one NMAC classification 0% during one day

NMAC share of blue disks 0% binary rule positives

Multi-drone groups

Groups with 3+ drones/day—mean snapshot observations per day

Largest observed group—drones in one connected component

Group counts across this run

Drones in group	Observed groups

U-plan results

Planned-route checks

Add U-plans in Scenario to see route results here.

Pair conflict intervals0

Routes crossing geofences0

Planned distance0 km

Changed from original0includes manual edits and rerouting

U-plan	Conflicts	Geofences	Distance	Arrival shift

Compare runs

0 runs

Run name

Add the current run or select multiple exported JSON files to compare.

Per-layer output

Geofence results

Each geofence changes the adapted traffic map by pushing blocked probability mass toward nearby edge cells.

r = 50 m

A/n research-hypothesis decision map

The dashed contour is the proposed boundary. On the low-A/n side, blue disks are NMAC-classified.

Live demo

Inspect your scenario

One simulated hour of background snapshots and planned flights.

Waiting for the traffic map.

00:00/ 60:00 min:sec

Scenario time

Dn sets where background drones appear; geofences redistribute it. Drones within 2r form groups, classified when A/n < πr². Blue-disk logic ↗

Current scenarioAirborne in this snapshot—

U-plans

Background droneConflict groupA/n classifiedPlanned flight