The San Francisco Bay Area packs three international airports, a dozen regional airfields, and some of the country’s most valuable real estate into one metro. That combination makes it one of the most complex places in the United States to fly a drone legally — and one of the most common reasons commercial projects stall.

Here’s how the airspace actually works, and what it means for your project timeline.

The three-airport problem

Bay Area airspace is layered like a wedding cake, and the layers overlap:

  • SFO (Class B) — San Francisco International anchors a large Class B structure whose shelves extend over San Francisco itself, the Peninsula, and parts of the East Bay. Most of downtown San Francisco sits beneath a Class B shelf, which means authorization is required even at low altitudes.
  • OAK (Class C) — Oakland International’s Class C airspace covers southern Oakland, Alameda, and the airport’s approach corridors. The Port of Oakland area adds maritime security considerations on top.
  • SJC (Class C) — Mineta San Jose International’s Class C sits directly over central San Jose, with Reid-Hillview (Class D) to the east and Palo Alto and Moffett adding more Class D surfaces up the Peninsula.

If your property is anywhere in the urban Bay Area, assume controlled airspace until proven otherwise.

What LAANC changes (and what it doesn’t)

The FAA’s LAANC system (Low Altitude Authorization and Notification Capability) grants near-real-time authorization for flights in controlled airspace, up to a published ceiling for each map grid square. For most commercial shoots in San Francisco, Oakland, or San Jose, a certified operator can obtain LAANC authorization in minutes.

What LAANC doesn’t do:

  1. It doesn’t cover zero-altitude grids. Some grid squares near runways authorize nothing at all. Flights there require a manual FAA authorization, which can take weeks — this is the single most common cause of schedule surprises.
  2. It doesn’t override TFRs. Temporary flight restrictions — including the standing stadium TFR that activates around Oracle Park and the Coliseum during MLB and NFL games — trump any LAANC grant.
  3. It doesn’t grant permission to launch from restricted land. More on that below.

The no-fly zones that catch people off guard

Airspace authorization is federal; where you stand when you launch is often governed by someone else:

  • National Park Service lands — launching or landing a drone in the Presidio, Crissy Field, Alcatraz, or any GGNRA property is prohibited. Marina District shoots have to be staged carefully because of this.
  • University campuses — UC Berkeley and Stanford both restrict drone operations over campus without institutional approval.
  • State parks and regional open space — many East Bay Regional Park District and California State Parks properties prohibit or restrict drone use.

A pilot who flies the Bay Area every week knows where these lines fall to the block. A pilot who doesn’t will find out mid-project.

What this means for your schedule

For most commercial work — real estate, construction documentation, inspections — here’s the realistic authorization picture:

  • Standard urban sites (LAANC-eligible): authorization same day; the schedule is driven by weather, not paperwork.
  • Near-runway sites (zero grids): allow 2-4 weeks for a manual authorization, or ask whether the deliverable can be captured from an adjacent authorized grid.
  • Event-adjacent sites (Oracle Park, Chase Center, the Coliseum): flights are planned around game and event calendars.

The takeaway: airspace is a solved problem when it’s handled early. Tell your drone provider the exact address at the quoting stage — not the week of the shoot — and none of this will ever cost you a deadline.

We fly the Bay Area’s controlled airspace daily and handle every authorization ourselves. If you have a site in a tricky grid, we can usually tell you what’s possible within a few hours.