Use your sfgov.org email and your UAS portal password. It is not your City computer password.
📍 New official address
Please use and bookmark app.sfso-uas.org going forward.
Needs a data connection to sign in.
A new password is required before you continue.
At least 10 characters, including a letter and a number.
Having trouble signing in? Contact Deputy Mendoza.
What's New
Launch point recorded automatically when you set the start time. Allow location when your phone asks — it puts your flight on the portal's map exactly. If you say no, the flight still logs normally
Auto light/dark: the app now follows your phone, Day in daylight and Night after dark. Tap ◐ in the switch to return to Auto after picking a mode yourself
New look: glass header, Log/Review switcher and a floating Review bar. The form itself stays solid and easy to read. If your phone is set to Reduce Transparency, you get solid panels
My flights on the Review tab: your last five flights marked Pending review or Approved, plus anything still waiting on this phone. Tap the "queued" badge to jump there
Check before you submit. The Review screen now opens with Operating Rule, Supervisor, VO and retention. Anything the app filled in is tagged — if the flight was under the CoW, change Part 107 before submitting
You'll be signed out 24 hours after you sign in (only when you have signal — never mid-shift offline). Anything queued is sent first and your draft is saved
Less to fill in. Operating Rule starts at Part 107, VO at None, and Supervisor at the last one you picked. Change any that are wrong for this flight
Retention date fills in automatically: 2 years from the flight date. Set a later date if the flight is evidence or tied to an open case
Operational flights need two names: the Incident Commander who authorized the flight and the FOD Chief or designee who approved it. The fields appear when you pick Operational
Reminder: sign in on Wi-Fi or cell at the start of your shift — the app then works offline for 12 hours
