SFO · Signature Aviation
Signature Aviation operates the SFO private-aviation facility. The request should identify the FBO rather than the commercial passenger terminal.
PRIVATE AVIATION · FBO GEOGRAPHY
SFO, SJC, OAK and Peninsula FBO ground transportation
Private aviation removes one kind of airport friction. The ground plan should preserve that advantage by naming the actual FBO, tail number, passenger or crew movement and access requirements before the vehicle is dispatched.
Plan this airport transferTERMINAL & FBO CONTEXT
The facility is the first detail to confirm.
Private aviation requests are coordinated around the actual FBO or handler, not a commercial terminal assumption.
SJC · Signature / Atlantic
SJC has Signature Aviation and Atlantic Aviation facilities. Name the operator, arrival time and any crew or passenger split in the brief.
OAK · Kaiser Air / Signature
OAK has Kaiser Air and Signature Aviation options. The correct FBO and gate or ramp instruction should come from the aircraft operator or handler.
SQL · PAO · NUQ · HWD
San Carlos (SQL), Palo Alto (PAO), Moffett Federal Airfield (NUQ) and Hayward Executive (HWD) each require the exact airport and FBO or handler detail before dispatch.
THE FBO MAP
The airport code is only the first coordinate.
A private aviation request is organized around the FBO, not the commercial terminal. At SFO, that may be Signature Aviation. At SJC, it may be Signature or Atlantic Aviation. At OAK, the operating plan may point to Kaiser Air or Signature Aviation. The Peninsula and South Bay fields add San Carlos Airport (SQL), Palo Alto Airport (PAO), Moffett Federal Airfield (NUQ) and Hayward Executive Airport (HWD) to the geography.
This page is intentionally geography-first. It explains the FBO network and the information required to reach the right facility. The separate private aviation service page explains the service format, including how a ground leg can sit inside a larger flight plan. The two pages should be read together rather than repeating one another.
TAIL NUMBER COORDINATION
Use the aircraft detail that the handler actually recognizes.
The reservation brief should include the tail number when it is available, the arrival or departure time, the FBO operator, the passenger or crew names and a contact who can approve changes. A tail number is more useful than an airport code alone because one airport may contain multiple general-aviation facilities or operating areas.
For a departure, the ground plan can be built around the FBO’s requested arrival time. For an arrival, the team can monitor the expected movement and keep the final handoff aligned with the handler’s release of the passenger or crew. If the aircraft changes, update the tail number and FBO rather than assuming the original instructions still apply.
CREW & PASSENGERS
A crew transfer is not always the same as a principal transfer.
Crew may need an earlier hotel, airport or repositioning movement, while passengers may need a quiet direct transfer to Menlo Park, Palo Alto, Stanford, Atherton or a residence. Put the passenger and crew legs in the same brief when they are connected, and say whether the vehicle should remain available or complete a one-way handoff.
The vehicle category follows the group and luggage profile. An Executive Sedan can suit a principal traveling alone with a compact case; a Luxury SUV is often more flexible for several passengers, crew bags or a longer Peninsula itinerary. If multiple vehicles are required, identify which people and bags belong to each movement.
RAMP ACCESS & HANDOFF
Ramp access belongs to the airport and FBO, not the car service.
A chauffeur does not assume ramp access, gate access or direct aircraft-side pickup. Those permissions depend on the airport, FBO, handler, security procedures and the authorization attached to the flight. The reservation should therefore confirm the public FBO meeting point, any vehicle access instruction and the person authorized to meet the passenger before the vehicle arrives.
If the FBO or handler changes the meeting point, the transportation team should follow the updated instruction. A calm public-lobby or curbside handoff is preferable to promising access that has not been approved. For a deeper explanation of the service format, review private aviation ground transportation, then return here for the FBO geography and operator details.
TIMING & WAITING
Build around the flight plan, then keep the ground leg legible.
The ranges below use the existing Peninsula airport planning windows for the corresponding SFO, SJC and OAK corridors. They are a starting point to discuss an FBO route, not an aircraft movement guarantee. Road access to an FBO, handler instructions, passenger release and security requirements can change the final handoff.
Waiting and grace are confirmed around the request. The vehicle should not stage on a restricted ramp or assume that an FBO can hold a passenger indefinitely. If the flight is delayed, the coordinator should send the updated time, tail number and FBO instruction so the ground plan can be reviewed before the vehicle is committed.
PENINSULA TIMING
Use the nearest commercial corridor as the first timing reference.
These ranges reuse the SFO, SJC and OAK planning windows already shown across the location pages. FBO access, handler release and aircraft movements can add their own operational variables.
| Origin | Off-peak | Weekday peak |
|---|---|---|
| Menlo Park → SFO FBO | 25–35 min | 40–60 min |
| Palo Alto → SJC FBO | 20–30 min | 30–45 min |
| Redwood City → OAK FBO | 35–50 min | 50–75 min |
| Menlo Park → OAK FBO | 35–50 min | 50–75 min |
| Palo Alto → SFO FBO | 25–35 min | 40–60 min |
| Woodside → SFO FBO | 35–45 min | 50–75 min |
These are planning ranges, not a guaranteed arrival time. Traffic, terminal activity, construction, weather and the exact pickup point can change the drive.
FBO FAQ
Questions before the first approach.
The practical details that shape an airport request. Final instructions and availability are confirmed with each reservation.
Which FBOs do you coordinate around the Bay Area?
Common requests include Signature Aviation at SFO, Signature and Atlantic Aviation at SJC, Kaiser Air and Signature Aviation at OAK, plus movements at SQL, PAO, NUQ and HWD when the exact airport and handler details are supplied.
Do you need the aircraft tail number?
It is strongly preferred when available. The tail number helps align the ground plan with the correct flight, handler and arrival or departure sequence.
Can you drive onto the ramp or meet the aircraft?
Do not assume it. Ramp, gate and aircraft-side access depend on airport and FBO authorization. The confirmed request will use the approved public or authorized meeting point.
Can crew and passengers use separate transfers?
Yes. Include each leg, passenger group, luggage profile, timing and destination so the vehicle plan can be built without confusing crew movement with principal movement.
How does private-aviation waiting work?
The waiting window is confirmed around the flight plan, handler release and requested service. Delays should be communicated with updated timing and FBO information before the original plan is assumed to continue.
Where are private aviation rates shown?
The rates page provides general airport and vehicle references. FBO, crew, waiting and multi-vehicle requirements are confirmed in a written quote for the actual flight plan.