Airspace is federal. The noise isn't.
Everything residents actually feel from low-altitude aircraft happens at ground level — noise, privacy, amenity, hours of operation — and that is exactly where councils have no tools. Argon gives local government a way to set community expectations, publish them as rules the airspace system can act on, and show what actually happened.
Councils are accountable for a problem they have no instruments for
When a drone disrupts a neighbourhood, residents ring the council. The council has no way to have set an expectation beforehand, no way to measure what happened, and no standing to resolve it afterwards.
Australian councils. Before Argon, none of them had a purpose-built tool for community governance of low-altitude airspace.
No way to set expectations
Councils can't formally express community standards for noise, privacy, amenity or operating hours in a form anyone else can act on.
No way to monitor
When a drone disrupts a neighbourhood there is no channel to lodge, assess and resolve a complaint — or to prove what happened.
Caught in the middle
Residents blame the council. Operators and traffic management systems get no clear local rules. Regulators expect local input that doesn't yet exist.
The rules for low-altitude airspace are being written this decade
Three things are happening at once, and the window in which local government can shape the outcome is open right now.
Delivery drones are scaling
Commercial operations are expanding suburb by suburb. Approvals are accelerating and residents already feel the impact.
Traffic management is being built
Uncrewed traffic management systems will route and separate low-altitude flights. They need local rules to route around — and there aren't any.
Regulators want local input
The ground-level amenity gap is now visible, and councils are being asked to weigh in with nothing to weigh in with.
Author the rules, then monitor the outcome
Argon turns what a community expects into something the airspace system can act on — and turns what residents experience into evidence.
Councils draw the zones
Staff define ground-level expectation zones: what residents there can reasonably expect for noise, privacy, amenity and time of day.
Expectations become rules
Zones are published as machine-readable rules and handed to the traffic management layer that actually plans and separates flights.
Experience becomes evidence
A public complaints portal and an automated assessment pipeline turn what residents feel into defensible conformance data.
Impact is judged by where it is felt, not where the drone flew.
Expectation zones are two-dimensional footprints on the ground. A resident does not experience a flight path at an altitude; they experience noise in their backyard at seven in the morning. Argon assesses the footprint, which is the thing councils are actually accountable for.
What Argon is not
Argon does not plan flights and does not manage airspace. It is not a traffic management system and it does not compete with one. It is the civic governance layer the airspace stack is missing — it supplies local rules to traffic management systems and assesses whether what was expected was met.
From complaint to objective outcome
Every complaint is scored by a purpose-built pipeline, so the result is defensible and repeatable rather than a judgement call. Five dimensions, two of which always go to a person.
Noise
Perceived noise level modelled with ISO 9613 sound propagation.
Visual amenity
Density of distinct aircraft in sight over a time window near the resident.
Privacy
Proximity of camera-equipped aircraft that were actively recording.
Safety
Always escalated to a human reviewer. Never automatically closed.
Cultural
Always escalated to a human reviewer who can apply local context.
Start with your own suburbs
The clearest way to see what Argon does is to draw zones over an area you already know, and walk through what a resident complaint would look like from lodgement to outcome.