An FBO request needs more than an airport code
A private aviation transfer is organized around the fixed-base operator, not the main passenger terminal. The request should name the airport, FBO and expected arrival or departure window. At SFO, that may mean SFO Signature details; at SJC, the request may reference Atlantic Aviation. The exact meeting instruction still needs to be confirmed because the useful curb, entrance and handoff can vary by itinerary.
If the request only says SFO or SJC, the transportation team has to clarify the operating point before a reliable pickup plan can be confirmed. Include the FBO name, the aircraft or tail number when available, the passenger count, luggage and whether the vehicle is meeting passengers, crew or both.
Tail number and timing create a better handoff
A tail number can help the team coordinate the ground movement when a flight schedule changes or when the arrival is managed through an FBO rather than a public terminal. It is not a substitute for the confirmed pickup window, but it gives the request a useful operational reference. Share the aircraft details as soon as they are available and update the team when the trip sequence changes.
Departure transfers should be timed around the passenger meeting the aircraft, not simply around the time the car reaches the airport. Arrival transfers should allow for taxiing, disembarkation and baggage. When the aircraft itinerary is fluid, an as-directed vehicle can be considered for a wider availability window.
Crew movement may be a separate request
Crew transfers often have different timing and vehicle needs from passenger transfers. A crew may need to move to a hotel, reposition to another airport or reach the aircraft before the passengers. If the ground plan includes both, list the groups separately with their pickup points, luggage profile, preferred timing and final destinations.
That separation helps avoid an itinerary that looks complete but does not account for the operational reality of the aircraft team. It also makes it easier to choose a sedan for a small crew movement and an SUV when cases, equipment or several passengers require more room.
Quiet service still needs visible instructions
Private aviation travelers often value discretion, but discretion does not mean leaving the meeting point vague. A useful brief can specify the preferred communication method, vehicle presentation, passenger name, FBO entrance and whether the chauffeur should meet inside or remain curbside. The right amount of visibility is the amount that lets the passenger move without searching for the next step.
For a hosted guest, the meet-and-greet service may provide a clearer welcome. For a principal, executive assistant or family office, a direct corporate reservation request can keep recurring FBO patterns and passenger preferences in one conversation.
Confirm the complete ground itinerary
Private aviation frequently connects to a larger day: a Peninsula residence, a board meeting, a hotel, a second airport or a hosted dinner. Send the complete route, not only the airport transfer. Include any return movement, intermediate stop, vehicle hold or changeover point. That makes it possible to decide whether a one-way transfer, hourly service or a larger vehicle plan is the right format.
The intention is simple: when the aircraft is ready, the ground leg should already be considered. A clean FBO brief gives the passenger a quiet arrival and gives the operating team the information needed to confirm availability.
Discretion is created through preparation
A discreet private aviation transfer is rarely silent because information was omitted. It is quiet because the right information was shared early enough for the handoff to feel natural. Confirm the passenger name, the preferred contact method, the vehicle description or presentation preference, the FBO meeting point and the final destination before the travel window begins.
For executive assistants and family offices, keeping those recurring preferences together can reduce repeated clarification. The contact form can carry the immediate itinerary, while a broader account conversation can address repeat passengers, FBO patterns and billing requirements.
The final confirmation should read like a handoff note
Before the travel window, the confirmed brief should make the next action obvious: where the passenger meets the chauffeur, how the vehicle is identified, who is traveling, what destination follows and whether the vehicle remains available. That level of clarity is especially useful when a principal, assistant, crew coordinator and transportation team are all working from the same movement.
A well-formed handoff note is not excessive detail. It is a short way to keep the passenger experience private, predictable and easy to execute when the aircraft schedule is moving.