A drone is one of the cheapest force multipliers in physical security. One operator can cover a perimeter that would take three people on foot, see over a wall that no camera is mounted on, and put eyes on an alarm in ninety seconds instead of nine minutes. That is the appeal. The reason most private drone programmes stall is not the hardware and not the pilot skill. It is that two entirely separate rulebooks apply at the same time, and a flight that satisfies one can still be a crime under the other.
Two rulebooks, not one
The first rulebook is federal. The Federal Aviation Administration owns the airspace, and commercial drone flight in the United States happens under 14 CFR Part 107. The second is Arizona’s own criminal statute on unmanned aircraft. Neither one substitutes for the other, and neither one is optional.
Most operators know Part 107 exists. Far fewer have read A.R.S. § 13-3729, which is where a bad flight in Arizona stops being a paperwork problem and becomes a felony.
What Part 107 actually requires
Part 107 is the certification and operating rule for small unmanned aircraft flown for anything other than pure recreation. The operator needs a Remote Pilot Certificate, which means passing an aeronautical knowledge test and keeping the currency requirement live. The aircraft has to be registered. And the operating limits are real limits, not guidelines: the aircraft stays within visual line of sight of the remote pilot or a visual observer in direct communication with them, it stays at or below 400 feet above ground level, and it does not fly over people who are not participating in the operation unless the aircraft and the operation qualify under the operations-over-people categories.
Night flight is permitted, but only with anti-collision lighting visible for three statute miles and after the updated knowledge requirements have been met. The FAA’s own summary of the rule and its waiver categories sits on the Part 107 waivers page, and a waiver is the correct route for anything the base rule prohibits — beyond visual line of sight work, operations over people, multiple aircraft flown by one pilot.
Airspace: LAANC is the part people get wrong
The 400-foot ceiling is not the constraint that bites most often. Airspace class is. In uncontrolled Class G airspace, a Part 107 operator can launch without asking anyone. In the controlled airspace that surrounds an airport — Class B, C, D and the surface-level E areas — prior authorisation is mandatory, and flying without it is a violation of a federal aviation regulation.
The mechanism for getting that authorisation quickly is LAANC, the Low Altitude Authorization and Notification Capability. The FAA describes it on its UAS Data Exchange page as a collaboration between the agency and industry that shares airspace data between the two. In practice it means a request submitted through an approved UAS Service Supplier can be approved in near real time, rather than through a manual process measured in weeks.
Two things about LAANC matter operationally. First, it is an airspace authorisation and nothing else — it does not waive any other part of Part 107, so a LAANC approval does not let anyone fly beyond visual line of sight or over a crowd. Second, LAANC approvals are bounded by the altitude ceilings drawn on the UAS Facility Maps for each grid square. Around a busy airport that ceiling can be zero. Where a mission needs to exceed the mapped ceiling, a Part 107 operator can submit a further coordination request, and those can go in up to ninety days ahead. Airports that are not on LAANC require a manual request through FAA DroneZone, which is slow enough that it has to be planned into the job rather than discovered on the morning of it.
For a security operation this changes how a site is quoted. A warehouse in a Class G pocket outside Casa Grande is a same-day capability. The same warehouse three miles off a runway threshold under a zero-foot grid is not a drone site at all until the further coordination is granted.
Arizona’s statute, and the felony hiding in it
A.R.S. § 13-3729 does four things worth knowing.
It makes it unlawful to operate a drone in a way that is prohibited by federal aviation regulation. That is the sentence that turns a Part 107 breach into a state criminal offence — a class 1 misdemeanour — rather than an administrative matter with the FAA. It separately makes it unlawful to interfere with a police, firefighting or emergency services operation, which is why the correct response to arriving on scene alongside first responders is to land, not to hover and film.
It then creates the serious offence. Operating a drone to intentionally photograph or loiter over or near a critical facility in furtherance of a criminal offence is a class 6 felony, and a second or subsequent violation is a class 5 felony.
The statutory definition of “critical facility” is long and it is not limited to obvious targets. It includes electrical transmission and distribution substations and any transmission line of at least sixty-nine thousand volts; water and wastewater treatment facilities and conveyance systems including dams; natural gas compressor, regulator and city gate stations; petroleum and chemical production, storage and processing facilities; electronic communication stations and towers; energy control centres; railroad infrastructure; federal, state, county and municipal courts; jails and prisons; military installations; and any hospital that receives air ambulance services.
Read that list against a map of Pinal or Maricopa County and it becomes clear how much Arizona ground sits near something on it. A perimeter patrol at an industrial estate can drift within photographing distance of a substation without the pilot ever intending to.
The preemption clause is a genuine advantage
Subsection C bars cities, towns and counties from enacting any ordinance, policy or rule regulating the ownership or operation of unmanned aircraft, and voids any such rule whether adopted before or after 6 August 2016. There are narrow carve-outs: a municipality can still regulate its own publicly owned aircraft, and can restrict model aircraft takeoff and landing in a specific park where alternatives exist.
The practical effect is that an operator in Arizona answers to the FAA and to this statute, and not to a patchwork of city rules that differ between Chandler, Tempe and Casa Grande. That is unusual and it is worth knowing, because a client who has been told “the city does not allow drones” is almost always repeating something that is void as a matter of state law.
What a defensible drone programme looks like
Certification and registration are the entry ticket, not the programme. The parts that actually keep an operation clean are procedural.
- An airspace check before every flight, not before every site — grid ceilings change.
- A LAANC authorisation captured and retained for the flight record, or a further coordination request filed with enough lead time to be answered.
- A written scope from the client that names the property being surveyed, so intent is documented in advance.
- A critical-facility screen of the flight area, treating the statutory list as a checklist rather than relying on the pilot to recognise a substation from the air.
- A standing rule to land on the arrival of police, fire or medical units.
- A retention and access policy for the footage, because aerial imagery of neighbouring property is the complaint that ends most private drone programmes.
None of that is exotic. It is the difference between a capability that survives its first complaint and one that does not.
Honeybadger Solutions runs drone operations as part of a wider physical security practice rather than as a standalone service, and pairs them with autonomous drone systems where a site justifies permanent coverage. Where aerial work supports a protective assignment, it is planned alongside the ground element in executive protection rather than bolted onto it.
This article is general information about Arizona and federal law, not legal advice. Statutes change, and the facts of a specific operation matter.