Program ActivePart 107 CertifiedRemote ID BroadcastingSF Admin Code 19B
Aerial Support for Public Safety.
The San Francisco Sheriff's Office operates unmanned aircraft in support of search and rescue, emergency response, public-safety events, and tactical operations — in accordance with FAA regulations and San Francisco Administrative Code Chapter 19B.
Deployments are conducted consistent with Sheriff's Office policy, applicable law, and documented authorization requirements.
Program pilots hold FAA Part 107 Remote Pilot Certificates — the federal credential required for professional drone operations — and complete quarterly proficiency training (classroom plus hands-on) per SFSO Military Equipment Policy. Flight data and mission records are maintained in accordance with Sheriff's Office policy and applicable retention requirements.
Governing Principles
I.
AuthorizationUAS deployment requires approval from the Field Operations Division (FOD) Chief or their designee. Tactical-incident use requires Incident Commander authorization. When exigent circumstances require immediate response, documentation is completed as soon as practicable.
II.
Civil LibertiesPublic-gathering operations are conducted solely for public safety purposes consistent with SF Admin Code 19B and agency policy.
III.
Data GovernanceUAS data is not shared outside authorized governmental use except as required by legal process or statutory authorization.
IV.
TransparencyDeployment data is published per SF Admin Code 19B. Each operational deployment is included in the Annual Military Equipment Report submitted to the Board of Supervisors and reviewed by the Chief Deputy within 30 days.
Program Limits
What the Program Does Not Do
Community trust depends on clear limits. The SFSO UAS program does not engage in the following practices.
✕
No Facial RecognitionFacial recognition technology is not used on UAS video or imagery at any time.
✕
No Individual Surveillance Without Court OrderThe UAS is not used for surveillance of an individual without a court order or search warrant.
✕
No Targeting Based on IdentityThe UAS shall never target a person based on race, religion, gender, or any individual characteristic.
✕
No WeaponizationSFSO UAS aircraft are not armed, are not used as a force option, and have no offensive capability — including no weapon, munition, or chemical agent.
✕
No Persistent SurveillanceNo ongoing monitoring of First Amendment activity, protests, or lawful assembly unless the situation becomes objectively dangerous and unlawful.
✕
No Data Sales or BrokerageFlight data and imagery are not sold, traded, or shared with private third parties.
✕
No Immigration EnforcementSFSO UAS aircraft are not used to enforce federal civil immigration law, consistent with SF sanctuary policy.
Use Cases
Program Operations
Imagery in this section is illustrative and does not depict actual SFSO personnel or operations.
01
Search & Rescue
Aerial search support for missing persons across urban, waterfront, and wilderness terrain. Thermal imaging extends search capability into low-light and nighttime conditions, reducing time-to-locate and limiting exposure to ground searchers. Thermal and other vision-enhancement tools are used only where there is no reasonable expectation of privacy, or under a search warrant or court order.
02
Tactical Support
Real-time aerial situational awareness for the Special Response Team during barricaded-subject incidents, high-risk warrant service, and perimeter containment. Live video routes to the incident commander to support decisions that protect deputies, subjects, and uninvolved persons.
03
Disaster Response
Rapid post-incident damage assessment after earthquakes, structure fires, and infrastructure failures. Coordinates with city emergency management partners to identify hazards and direct ground response without committing personnel to unstable structures.
04
Public Safety Events
Overwatch for permitted gatherings, parades, and city events under SF Admin Code 19B. Provides crowd-safety situational awareness, fire-perimeter monitoring, and officer-safety support.
05
Training & Exercises
FAA-mandated proficiency flights to maintain Part 107 currency and crew skill across day, night, and complex airspace operations. Includes joint exercises with allied agencies for mutual-aid readiness and scenario-based coordination drills.
Deployment Preview
Where We've Flown
Every SFSO UAS deployment is logged and published per SF Admin Code 19B. Open the full Transparency Dashboard to filter by mission type, neighborhood, date range, and time of day — and to download CSV records.
Live Preview · Generalized Pins
Public FAQ
Common Questions
Quick answers about how the program operates, what data is collected, and how the public can request records or file a complaint.
How precise are the flight locations shown on the public map?
Pins reflect the general neighborhood of each flight, not the exact launch coordinates. Specific addresses, building-level locations, and property boundaries are withheld to protect operational security, ongoing investigations, and individual privacy.
What data is retained, and for how long?
Flight log entries (date, general location, mission type, duration, outcome) are retained as part of the agency UAS records system per the SFSO records retention schedule, and published on this dashboard. Flight video and imagery are retained per applicable agency policy and California Penal Code § 832.18: recordings tied to use-of-force, officer-involved shootings, detention or arrest, or a complaint against the Sheriff's Office are retained for a minimum of two years; recordings with evidentiary value in a criminal prosecution are retained for any additional period required by law; all other recordings are retained for no less than 90 calendar days. Logs of access and deletion are retained permanently.
Can I request footage or records from a specific flight?
Members of the public may submit a California Public Records Act request through the SFSO Public Records portal. Requests are reviewed under CPRA, SF Admin Code Chapter 19B, and applicable law-enforcement exemptions. For retention periods by record type, see the question above. Flight log entries are always retained and published on this dashboard.
Why are some flights labeled "Maintenance / Firmware Check"?
Maintenance and firmware-check flights are non-operational test launches conducted indoors or at training facilities to verify aircraft software, calibration, and airworthiness after firmware updates or component changes. They are typically very short (often under a minute) and produce no investigative or surveillance imagery. They appear in the public log to provide a complete record of all aircraft activity in service of full transparency under SF Admin Code 19B — even routine maintenance.
What does "Remote ID Broadcasting" mean?
Remote ID is an FAA requirement (14 CFR Part 89) that all drones over 0.55 lb broadcast a digital "license plate" during flight — including a unique ID, position, altitude, and the operator's takeoff location. It functions like an aviation transponder for drones. Anyone nearby with a compatible app (the FAA publishes a list) can verify that an SFSO drone overhead is registered, authorized, and operating lawfully. The program complies with Remote ID on every flight.
How do I file a complaint or raise a concern?
Complaints and concerns about UAS operations can be submitted through the Sheriff's Office main site or by public records request. All complaints are reviewed by the UAS Program Manager and referred for investigation where appropriate.
Have a question not answered here? Submit a records request or contact the Sheriff's Office directly — we respond per CPRA timelines.
For media inquiries, public records requests, policy questions, or inter-agency UAS coordination, contact the SFSO through the main Sheriff's Office website.
San Francisco Sheriff's Office · Public Disclosure
UAS Program — Transparency Dashboard
Program ActiveSF Admin Code 19BFAA Part 107Public Record
Annual surveillance reporting·SF Admin Code Chapter 19B·Data current as of —
—
Total Flights
—
Flight Hours
0✓
Safety Events
Overview
Flight Map
Flight Log
About the Data
i
This dashboard contains only unclassified, public-safe information consistent with applicable agency policy and SF Admin Code Chapter 19B. Specific operational records — including personnel information, incident/case numbers, evidence identifiers, and exact location data — are excluded as law enforcement sensitive and/or exempt from public disclosure under the California Public Records Act (Gov. Code § 7923.600). Location coordinates are generalized to the neighborhood level to protect operational security and individual privacy.
⚑
Neighborhoods
0
Distinct areas of operation
📄
Flight Activity Span
—
First flight → latest flight
🔒
Redaction Rate
0
0 of 0 flights redacted
⏱
Avg Duration
0
Minutes per flight
Flights by Month
Flights by Mission Type
Flights by Neighborhood
Outcome Summary
Reading This Data
⚑
Map pins represent the general neighborhood of each flight. Location coordinates are generalized to protect operational security and individual privacy — exact launch sites, addresses, and GPS coordinates are not disclosed. Select any pin for public mission details.
—
Neighborhoods Covered
Pin Colorby Mission Type
Public Flight Log
0 of 0 flights
No flights match the current filters.
About this Dashboard
Public Disclosure Methodology & Compliance Reference • San Francisco Sheriff's Office
This dashboard is the San Francisco Sheriff's Office Unmanned Aircraft Systems (UAS) Program public disclosure published under San Francisco Administrative Code Chapter 19B (Acquisition of Surveillance Technology Ordinance), which requires Annual Surveillance Reporting on the use of surveillance technology by city agencies.
For the program's mission, capabilities, governing law, and operating principles, see the main program site. For frequently asked questions about retention, records requests, privacy, and complaints, see the FAQ.
Reporting Period
Current reporting period: January 1, 2026 – June 23, 2026. The flight log is updated monthly as new operations are completed and cleared for public release. The "Data current as of" timestamp at the top of this dashboard reflects the most recent flight published.
Methodology
Location. Flight pins reflect the general neighborhood of each operation. Exact launch coordinates, street addresses, and building-level locations are withheld to protect operational security, ongoing investigations, and individual privacy.
Duration. Reported in whole minutes, computed from the original flight log start and end times.
Mission Type. Standardized labels from the agency UAS records system. Subcategories (e.g., "Event Security / Overwatch," "Maintenance / Firmware Check") preserve the operational classification while enabling consistent filtering and aggregation.
Dashboard Inclusions
Flight date, general neighborhood, supervisor district, mission type, duration, aircraft model, outcome, night/day operation, and privacy measures applied.
Dashboard Exclusions
Personnel names, badge numbers, and unit assignments
Exact street addresses and building-level locations
CAD, case, and incident numbers
Axon Evidence IDs and other evidence identifiers
Subject identifiers (names, dates of birth, addresses)
Information that would identify individuals observed during flights
Active investigation details
Aircraft tail numbers and serials
Compliance Attestation
This dashboard is published in support of the public reporting requirements of San Francisco Administrative Code Chapter 19B for the SFSO Unmanned Aircraft Systems Program. All entries are reviewed for redaction consistency before publication. A UAS-specific operational policy is currently in agency review and will supplement these requirements.
Maintained by: UAS Program Manager • San Francisco Sheriff's Office
Last reviewed: —
