Understanding Public Safety COA Authority
Public safety drone operations has gotten complicated with all the regulatory frameworks flying around. As someone who’s worked closely with law enforcement and fire departments setting up their UAS programs, I learned everything there is to know about COAs and how they differ from standard Part 107 operations. Today, I will share it all with you.
Here’s the key thing to understand — public safety agencies operate under a completely different set of rules than commercial Part 107 operators. The Certificate of Waiver or Authorization (COA) gives these agencies operational flexibility that the rest of us can only dream about, and for good reason. When there’s a missing child or a structure fire, you don’t want first responders waiting around for LAANC authorization.
Unlike Part 107, which came out of the push to integrate commercial drones, the COA process actually predates the whole civilian drone boom. It was originally built for government agency operations including military and border patrol, and it’s evolved to accommodate state and local public safety agencies running increasingly diverse missions. That’s what makes the COA framework endearing to us in the drone regulation space — it shows that the FAA can actually be flexible when mission requirements demand it.
Public Safety Certificate of Waiver or Authorization Explained
What is a COA?
A Certificate of Waiver or Authorization is basically FAA approval allowing public entities to operate aircraft for governmental functions outside the normal Part 107 or recreational flying rules. Public safety COAs specifically authorize law enforcement, fire departments, emergency management agencies, and related entities to conduct drone operations supporting their public safety missions.
COAs get issued for specific geographic areas, time periods (typically 2-4 years), and operational parameters. Each COA spells out:
- Geographic boundaries where operations are authorized
- Altitude limitations and airspace coordination requirements
- Operational scenarios covered (search and rescue, accident investigation, tactical operations, etc.)
- Pilot qualification requirements
- Aircraft specifications and equipment standards
- Safety protocols and emergency procedures
- Coordination procedures with air traffic control when operating in controlled airspace
Who Qualifies for Public Safety COAs?
Eligible agencies include:
- Municipal, county, and state law enforcement agencies
- Fire departments and fire districts
- Emergency medical services
- Emergency management and disaster response agencies
- State and local government agencies with public safety responsibilities
- Public universities with law enforcement or emergency response functions
One thing that catches people off guard — private contractors working for these agencies generally can’t operate under the agency’s COA. They’ve got to hold Part 107 certificates and operate under commercial rules even when they’re contracted for public safety work. I’ve seen this create some awkward situations where a department hires a commercial pilot for a specific operation and then realizes the contractor can’t use their expanded authorities.
How COAs Differ from Part 107
Operational Flexibility
The fundamental difference is scope. Part 107 gives you baseline rules for all commercial operations, with waivers available for specific additional capabilities. COAs can bake in broad operational authorities right from the start based on what the agency actually needs to do.
Key operational differences include:
- Altitude operations: COAs can authorize flights above 400 feet AGL when the mission justifies it
- Controlled airspace: Standing authorization for operations in controlled airspace within the COA geographic area — no individual LAANC requests needed
- Night operations: Authorized as part of the COA without the additional training requirements imposed on Part 107 pilots
- Beyond visual line of sight: Some COAs include limited BVLOS authority for specific scenarios
- Operations over people: Greater flexibility for emergency response scenarios
- Multiple simultaneous operations: Authorization for coordinating multiple drones at single incidents
Pilot Qualification Requirements
Probably should have led with this section, honestly. COAs let agencies establish their own pilot qualification requirements tailored to public safety operations rather than just defaulting to Part 107 certification:
- Agencies develop internal training programs that meet or exceed FAA standards
- Initial and recurrent training specific to public safety missions
- Scenario-based training for emergency operations
- Coordination with other aircraft and ground operations
- Privacy and civil liberties awareness
In practice, most agencies I’ve worked with require their pilots to hold Part 107 certificates as a baseline, then pile on agency-specific training. But technically, Part 107 certification isn’t strictly required if the agency’s training program meets FAA approval standards outlined in the COA.
Administrative Requirements
There’s a trade-off here that agencies need to understand going in. COAs come with significantly more documentation and oversight than Part 107 operations:
- Detailed operations manual approved by the FAA
- Maintenance and inspection programs for aircraft
- Pilot qualification and training documentation
- Operational logs and mission records
- Incident and accident reporting procedures
- Periodic reviews and COA renewal processes
This administrative burden reflects the expanded authorities being granted. Agencies have to demonstrate they’ve got sophisticated safety management systems that justify the flexibility they receive. It’s not a free pass — it’s a different kind of accountability.
Common Public Safety Waivers: Night Ops, BVLOS, Over People
Night Operations Authority
Nighttime operations are absolutely critical for public safety missions, and it’s not hard to see why:
- Search and rescue operations that extend past sunset (they don’t stop just because it gets dark)
- Criminal investigations and surveillance occurring at night
- Traffic accident scene documentation on roadways
- Wildfire monitoring and coordination
- Tactical operations where darkness provides operational advantage
Public safety COAs routinely include night operations authority without the additional training requirements imposed on Part 107 pilots. That said, agencies typically require their own internal certification including:
- Proficiency demonstrations in reduced lighting conditions
- Understanding of anti-collision lighting requirements
- Visual acuity assessments for night operations
- Procedures for operations with artificial lighting (spotlights, vehicle lights)
Beyond Visual Line of Sight (BVLOS)
Full BVLOS operations are still tough to get even for public safety, but COAs often include limited BVLOS provisions that make a real difference in the field:
- Extended visual line of sight (EVLOS): Operations beyond unaided visual range using visual observers, binoculars, or other aids
- Corridor operations: BVLOS along defined routes like river searches or road traffic monitoring
- Emergency response BVLOS: Limited authority during active incidents when maintaining visual line of sight just isn’t practical
- Controlled area BVLOS: Operations in secured areas where ground personnel ensure airspace separation
These provisions typically come with additional safety measures including:
- Visual observers positioned along the route
- Coordination with local air traffic control
- Restricted operating areas closed to other aircraft
- Enhanced pilot monitoring and emergency procedures
Operations Over People
Public safety operations almost always involve people — bystanders at emergency scenes, suspects in tactical situations, participants in search and rescue. You can’t exactly clear the area when you’re responding to an emergency. COAs generally provide broader authority for operations over people than Part 107, recognizing that:
- Emergency operations inherently involve people on the ground
- Public safety benefits may justify limited risk exposure
- Professional operators employ additional safety protocols
- Operational areas are often controlled by responding agencies
However, agencies still need to minimize risk through:
- Aircraft selection prioritizing reliability and redundancy
- Operational procedures maintaining safe distances when practical
- Coordination with ground personnel about overhead operations
- Contingency planning for equipment failures
Controlled Airspace Operations
Public safety agencies often operate near airports within controlled airspace — think about it, most urban areas have controlled airspace covering them. COAs provide standing authorization for operations within defined geographic areas and altitude blocks, eliminating the need for individual LAANC requests that could delay emergency response.
Typical controlled airspace provisions include:
- Authorization for operations below specified altitudes (often 200-400 feet AGL)
- Coordination procedures with air traffic control facilities
- Real-time notification protocols for active operations
- Contingency procedures if manned aircraft approach the area
Training Requirements for Public Safety Pilots
Comprehensive training is the backbone that justifies all these expanded authorities. Without it, the whole framework falls apart.
Initial Training Components
Public safety drone pilot training typically includes:
- Regulatory knowledge: FAA regulations, airspace, weather, radio communications
- Aircraft systems: Platform-specific operations, maintenance, troubleshooting
- Flight skills: Manual control proficiency across various scenarios
- Mission-specific operations: Search patterns, evidence photography, tactical support
- Emergency procedures: Equipment failures, lost link, flyaways
- Coordination: Integration with ground operations, manned aircraft, incident command
- Privacy and civil liberties: Legal constraints, policy compliance, data management
Training duration varies but typically ranges from 40-120 hours including classroom instruction, simulator training, and supervised flight operations. That’s a substantial commitment, but the expanded capabilities more than justify it.
Recurrent Training
Maintaining proficiency isn’t a one-and-done thing. Ongoing training requirements include:
- Annual or semi-annual recurrent training covering regulatory updates and skill maintenance
- Scenario-based training for complex or unusual situations
- New equipment and technology integration
- After-action reviews of actual incidents (these are incredibly valuable for improving operations)
- Cross-training with other public safety specialties
Specialized Training
Advanced missions need additional training on top of the baseline. These are the specializations I see most often:
- Thermal imaging operations: Interpreting infrared imagery, optimizing camera settings
- Tactical operations: High-risk warrant service, barricade situations, active threats
- Hazmat and CBRNE: Operating in contaminated environments, detection equipment
- Water rescue: Over-water operations, payload delivery, coordination with marine units
- Wildfire operations: Coordination with aerial firefighting, smoke operations, safety protocols
Privacy and Civil Liberties Considerations
Here’s where things get really important, and frankly, where a lot of agencies need to pay more attention. Expanded operational authorities come with heightened scrutiny regarding civil liberties, and rightfully so.
Legal Constraints on Public Safety Drone Use
Public safety agencies face real legal limitations including:
- Fourth Amendment: Constitutional protections against unreasonable searches absolutely apply to drone surveillance
- State privacy laws: Many states require warrants or restrict police drone surveillance
- Policy limitations: Agencies often adopt policies more restrictive than legal minimums — and they should
- Data retention rules: Limitations on storing and sharing drone footage
- Transparency requirements: Public reporting on drone usage frequency and purposes
Best Practices for Privacy Protection
The programs I’ve seen do this best implement comprehensive privacy safeguards:
- Clear use policies: Written guidelines defining authorized and prohibited uses
- Warrant requirements: Obtaining warrants for surveillance even when not legally required
- Data minimization: Limiting collection to information directly relevant to incidents
- Retention limitations: Deleting non-evidentiary footage within 30-90 days
- Audit trails: Logging all drone deployments and footage access
- Oversight mechanisms: Civilian review boards or privacy officers reviewing usage
- Community engagement: Public education about drone capabilities and limitations
- Bias prevention: Training to prevent discriminatory deployment or surveillance
Balancing Public Safety and Privacy
The departments that get this right balance operational capabilities with community trust:
- Deploy drones for specific missions with clear public safety justification
- Avoid indiscriminate surveillance or “fishing expeditions”
- Communicate transparently about drone usage and privacy protections
- Welcome oversight and accountability mechanisms
- Regularly review and update policies based on evolving technology and legal standards
Examples of Successful Public Safety Programs
Chula Vista Police Department (California)
Chula Vista runs one of the most sophisticated drone-as-first-responder programs in the country, and I’ve followed their progress closely:
- Drones deployed automatically to 911 calls, arriving before ground units
- Operations fully integrated with incident command and dispatch systems
- Over 6,000 deployments since program inception
- Documented reductions in response times and officer safety improvements
- Comprehensive privacy policy and community oversight
Their program really demonstrates how expanded COA authorities can enable innovative public safety applications while maintaining accountability. It’s become the model other departments look to.
Menlo Park Fire Protection District (California)
Fire service drone operations tend to focus on size-up, hazard identification, and resource coordination:
- Rapid aerial assessment of structure fires
- Thermal imaging to locate fire extension and hot spots
- Hazmat incident monitoring from safe distances
- Documentation for investigations and training
- Integration with mutual aid and regional coordination
Texas Department of Public Safety
This statewide program supports diverse missions across absolutely massive geography:
- Border security and surveillance operations
- Accident reconstruction on highways
- Search and rescue in remote areas
- Disaster response and damage assessment
- Tactical support for high-risk operations
Applying for a Public Safety COA
If you’re with an agency looking to get COA authorization, here’s what the application process actually looks like.
Application Requirements
- Organization information: Agency authority, mission description, operational need
- Aircraft specifications: Make, model, weight, performance characteristics
- Geographic operating area: Maps and descriptions of intended operational locations
- Operational scenarios: Detailed descriptions of missions and procedures
- Pilot qualifications: Training program outline and qualification standards
- Safety assessment: Risk analysis and mitigation strategies
- Maintenance program: Inspection and maintenance procedures
- Operations manual: Comprehensive procedural documentation
Processing Timeline
COA applications typically take 60-90 days for FAA review, though complex applications can drag on longer. My advice — apply well in advance of when you actually want to start flying. I’ve seen agencies get caught flat-footed because they assumed it would be faster.
Working with the FAA
The applications that get approved smoothly tend to share some common traits:
- Early consultation with FAA regional flight standards offices
- Reviewing successful applications from similar agencies (reach out to departments who’ve gone through it)
- Demonstrating robust safety management systems
- Leveraging industry best practices and standards
- Building relationships with FAA personnel responsible for COA oversight
The Future of Public Safety Drone Operations
Public safety drone use keeps expanding, and there are several trends I’m watching closely:
- Drone-as-first-responder programs: Expanding well beyond the early pioneers to more agencies nationwide
- Autonomous operations: Pre-programmed responses to specific call types
- Fleet operations: Multiple simultaneous drones coordinating at large incidents
- Specialized payloads: Chemical detection, cellular communications, defibrillator delivery
- Integration with smart city infrastructure: Coordination with traffic systems and surveillance networks
- Regional cooperation: Shared programs across multiple agencies
- Standards development: National standards for equipment, training, and operations
As technology and regulations keep evolving, public safety agencies will gain even greater capabilities while facing ongoing pressure to demonstrate accountability and respect for civil liberties. It’s a balancing act, but the agencies doing it well are proving it can be done.
Conclusion
Public safety COAs give law enforcement, fire, and EMS agencies the operational flexibility that’s essential for effective emergency response while maintaining safety standards appropriate to their professional missions. Understanding how COAs differ from Part 107 commercial operations, what training and oversight is needed to justify expanded authorities, and why privacy protections matter so much — all of that helps contextualize the growing role of drones in public safety. The successful programs I’ve observed balance operational capabilities with community trust, transparent policies, and robust accountability mechanisms. As drone technology continues advancing and regulatory frameworks mature, public safety applications will expand further, which means ongoing attention to both operational effectiveness and civil liberties protection isn’t optional — it’s the price of admission.
