US Drone FAA vs State Permits 2026

US drone operations require navigating two distinct authorization layers: federal FAA Part 107 / § 44809 compliance (pilot certification, aircraft registration, airspace authorization, Remote ID) and state and local permits (privacy, surveillance, trespass, launch/landing locations). The two layers operate in parallel under the federal preemption framework of 49 U.S.C. § 40103, which gives FAA exclusive authority over navigable airspace while preserving state authority over ground-level activities.

This article delivers a side-by-side comparison of FAA and state permit requirements, the federal preemption boundary, and the operator's practical workflow for cross-jurisdiction operations.

1. The Federal Preemption Principle

Under 49 U.S.C. § 40103, the FAA holds exclusive authority over navigable airspace in the United States. States and localities cannot regulate airspace itself.

49 U.S.C. § 40103: https://www.law.cornell.edu/uscode/text/49/40103

What states and localities can regulate:

• Launch and landing locations (private property, parks, government property)
• Privacy and surveillance (capturing imagery of individuals or private property)
• Trespass (drone landing on private property or hovering at low altitude)
• Critical infrastructure protection (state-designated, must not conflict with FAA airspace rules)
• Noise ordinances at ground level
• Penalty provisions for state-prohibited offenses

This division creates a layered compliance architecture.

2. Federal FAA Permits — Comprehensive

2-1. Pilot Credential

eCFR Part 107: https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107

2-2. Aircraft Registration

Under § 107.13, aircraft registration via FAA DroneZone:

• Commercial: $5 per aircraft, 3-year validity
• Recreational: $5 per owner, 3-year validity
• Required for all aircraft ≥ 0.55 lb (250 g); commercial Part 107 requires registration regardless of weight

Reference: https://faadronezone-access.faa.gov/

2-3. Remote ID

Under 14 CFR Part 89 (effective broadcast enforcement since 2023-09-16), virtually all registered drones must broadcast Remote ID. Reference: https://www.faa.gov/uas/getting_started/remote_id

2-4. Airspace Authorization

Under § 107.41, controlled airspace (Class B/C/D/E) requires authorization. Mechanism: LAANC at 726 airports.

Reference: https://www.faa.gov/uas/getting_started/laanc

2-5. § 107.200 Waivers

For deviations from standard Part 107 rules (§ 107.31 BVLOS, § 107.25 moving vehicles, etc.), waiver applications via FAA DroneZone. Typical processing time 90+ days.

3. State Permit Categories

State drone permits fall into several categories. Each state varies; common patterns:

3-1. Privacy and Surveillance Permits

Some states require permits or specific consent for drone operations near private property:

• California Civil Code § 1708.8 — physical invasion of privacy by drone
• Florida Freedom from Unwarranted Surveillance Act — comprehensive drone-specific privacy statute
• Texas Gov't Code Ch. 423 — itemized prohibited surveillance targets

3-2. Critical Infrastructure Permits

Several states require permits for operations near:

• Oil refineries
• Electrical generating facilities
• Electrical substations
• Water treatment facilities
• Military installations
• Sports venues
• Concentrated animal feeding operations (CAFOs)

Texas Gov't Code Ch. 423 is illustrative. Permits typically require demonstration of legitimate need plus liability insurance.

3-3. Government Property Permits

State and local governments frequently restrict drone launches and landings on government property:

• State parks and recreational areas
• City parks
• State and local government facilities
• Public schools

Permits or specific authorizations are typically required.

3-4. Local Business Licensing

Many cities and counties require local business licensing for commercial drone operations:

• City business license
• County business license
• State business registration
• Sales tax registration if applicable

4. Side-by-Side Comparison

5. The Multi-Jurisdiction Compliance Workflow

For each operation, the operator should verify compliance across all applicable jurisdictions:

Step 1 — Federal Compliance Verification

1. Part 107 Remote Pilot Certificate (or TRUST for recreational)
2. Aircraft registration current under § 107.13
3. Remote ID broadcast active under 14 CFR Part 89
4. LAANC authorization for controlled airspace under § 107.41
5. § 107.200 waivers if applicable
6. Pre-flight inspection per § 107.49
7. Operating within § 107.51 limits

Step 2 — State Law Verification

1. Identify the state where operations will occur
2. Research state-specific drone statutes
3. Verify privacy/surveillance compliance
4. Verify critical infrastructure compliance (Texas Ch. 423, similar)
5. Obtain any required state-level permits

Step 3 — Local Ordinance Verification

1. Identify the city/county/township
2. Research local drone ordinances
3. Verify launch/landing location is permitted
4. Obtain any required local permits
5. Verify operating hours compliance

Step 4 — Property Owner Authorization

1. Obtain written property owner permission
2. Document the authorization
3. Verify the authorization covers the planned operation

Step 5 — Documentation

1. Save all federal compliance records
2. Save all state and local permits
3. Save property owner authorization
4. Save flight log entry with all jurisdictional documentation referenced

6. Common Cross-Jurisdiction Errors — A Gyoseishoshi Compliance Lens

As MmowW Drone is operated by a licensed Gyoseishoshi (行政書士) office, we observe these recurring errors:

Error 1 — Treating federal compliance as sufficient Federal Part 107 compliance is necessary but not sufficient. State and local compliance is independent.

Error 2 — Missing state critical infrastructure restrictions Texas Gov't Code Ch. 423 explicitly itemizes prohibited surveillance targets. Operators not familiar with the list may inadvertently violate.

Error 3 — Missing local ordinances Local launch/landing restrictions, hours-of-operation restrictions, and noise ordinances are easy to miss.

Error 4 — Using federal authority to override state law Federal preemption over airspace does not override state authority over privacy, trespass, or surveillance. The two layers are independent.

Error 5 — Failing to obtain property owner authorization State trespass law requires property owner consent. Operating without consent triggers civil exposure.

Error 6 — Operating in multiple states without state-specific research Each state's drone statute is different. Per-state research is required for cross-state operations.

7. Common State Permit Requirements — Quick Reference

8. The MmowW Service Scope

MmowW Drone provides federal FAA compliance tools: pilot certification tracking, aircraft registration management, LAANC integration, flight logging, and § 107.9 reporting workflow. State and local compliance is the operator's separate responsibility.

The MmowW Terms of Service and Disclaimer note that the platform does not constitute legal advice and does not address state/local regulatory requirements.

For state and local compliance, operators should engage state-licensed counsel and rely on state-published statutes and case law.

9. Best Practice Multi-Jurisdiction Workflow

For operators working across multiple states:

1. Maintain federal compliance baseline — Part 107, aircraft registration, Remote ID, LAANC
2. Research state law before each operation — California § 1708.8, Texas Gov't Code Ch. 423, Florida statutes, etc.
3. Maintain insurance valid in all operating states
4. Use written client contracts that address state-specific privacy and consent
5. Document compliance state-by-state — separate compliance memos for each major operating jurisdiction
6. Engage local counsel for complex operations near critical infrastructure or in privacy-sensitive contexts

A SaaS like MmowW Drone tracks federal compliance baseline — pilot certifications, aircraft registrations, Remote ID method, LAANC authorizations, and flight logs — supporting the federal foundation upon which state and local compliance is built.

10. Key Takeaways

1. Federal FAA compliance is necessary but not sufficient
2. State and local compliance is the operator's separate responsibility
3. Federal preemption over airspace does not override state authority over privacy, trespass, surveillance
4. Each state's drone statute is different
5. Document compliance across all applicable jurisdictions
6. Consult state-licensed counsel for cross-state operations

Comply with FAA Drone Regulations Using MmowW Drone

Track every Part 107 requirement automatically.

Pilot certification, aircraft registration, flight logs, incident reporting — all in one SaaS.

Start Free Trial →

Disclaimer

This article provides legal information, not legal advice. MmowW Drone is operated by a licensed Gyoseishoshi (行政書士) office in Japan. We are not US attorneys or licensed FAA legal counsel. For binding legal opinions on FAA compliance or state-specific law, consult a US-licensed aviation or state-licensed attorney.

Sources

1. 49 U.S.C. § 40103 (Cornell Law) — https://www.law.cornell.edu/uscode/text/49/40103
2. 14 CFR Part 107 (eCFR) — https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107
3. FAA UAS Main Portal — https://www.faa.gov/uas
4. FAA DroneZone — https://faadronezone-access.faa.gov/
5. FAA LAANC — https://www.faa.gov/uas/getting_started/laanc