Private aviation
FBO to boardroom: the chauffeur brief that prevents a missed handoff
An airport code and wheels-down time are not a private-aviation pickup plan. The ground team needs the facility, aircraft, release signal, access boundary, contact hierarchy, luggage picture, and first hard commitment in one controlled brief.
Decision in brief
The operating answer
The minimum reliable FBO handoff names the airport and handler or facility, tail number, passenger-ready trigger, permitted pickup point, primary and fallback contacts, bag count, vehicle, destination, and first hard door time. If any one of those is unknown, assign an owner and a deadline to close it before launch.
Key takeaways
What matters most
- Treat wheels down and passenger ready as two different events.
- Confirm the pickup access boundary directly with the handler or facility; never assume vehicle-side access.
- Build a contact hierarchy that still works when the principal is unreachable.
- Match the vehicle to people, luggage, working space, and continuity across the whole assignment.
Wheels down is a tracking event—not the pickup time
A private aircraft can be on the ground while the passenger is still minutes away from release. Taxi time, parking position, stairs, handler activity, bags, customs where applicable, and a conversation planeside or inside the facility can all separate touchdown from movement. Publishing one timestamp for both creates unnecessary curb pressure and misleading ETAs.
Track the aircraft event, but brief a separate passenger-ready trigger. That trigger might be a handler message, a lead traveler’s text, or confirmation from the flight department. The chauffeur should know which signal releases the final approach and who owns it.
| Event | What it tells the desk | What it does not prove |
|---|---|---|
| Wheels down | The aircraft has landed | The passenger is ready or the vehicle may approach |
| On blocks | The aircraft has reached its parking position | Bags and passengers have been released |
| Passenger ready | The traveler can move to the confirmed pickup point | The curb or ramp access instruction is unchanged |
| Loaded and rolling | The ground movement has begun | The original route ETA remains valid without a live check |
Confirm the access boundary with the handler
Published DCA and IAD transportation pages show that even public-terminal pre-arranged service uses airport-specific pickup procedures; neither page establishes FBO access. Fahad’s operating framework therefore treats private-aviation access as an unresolved field that must be confirmed directly with the current handler or authorized facility contact.
Private-aviation facilities do not share one universal vehicle-access rule. Airport controls, facility policy, security posture, aircraft position, and the operating provider can change where the handoff occurs. A vehicle may be directed to a public entrance, controlled apron position, or another assigned point.
Write the confirmed pickup point into the movement brief along with the person who provided it and the time of confirmation. If access changes, the desk updates the chauffeur and passenger-side contact together so neither side is working from an obsolete plan.
Build a contact hierarchy before the aircraft departs
The principal is often the least useful person to make the only contact. Their phone may be off, delegated, or intentionally quiet. A robust brief names a primary operational contact and one fallback: flight department, scheduler, assistant, protection lead, family office, or handler as appropriate to the assignment.
Define who can change the destination, release the vehicle, add a passenger, or approve waiting. This prevents the chauffeur from negotiating itinerary authority at the aircraft door and protects the principal from avoidable calls.
- Primary passenger-side operational contact.
- Fallback contact if the primary does not answer.
- Handler or facility desk contact.
- Altaie desk contact for one accountable change channel.
- Named authority for route, wait, and passenger changes.
Match the vehicle to the whole movement
Passenger count alone is a weak vehicle-selection rule. The brief should account for hard-shell cases, garment bags, presentation materials, security equipment, child seats, accessibility needs, and whether the passenger expects to work privately between stops. If a follow vehicle or luggage vehicle is required, establish the load plan before arrival.
Continuity matters as much as capacity. A vehicle that works for the FBO transfer may be wrong for a six-stop day, a late return with additional passengers, or a secure-item handoff. Choose once against the full itinerary whenever possible.
| Question | Why it matters |
|---|---|
| How many travelers and bags arrive together? | Determines usable passenger and cargo space, not brochure capacity |
| Will anyone work or call from the vehicle? | Changes the privacy and cabin-space requirement |
| Does equipment stay with the vehicle? | May make vehicle continuity more valuable than separate transfers |
| Will the party grow later in the day? | Prevents a mid-assignment vehicle mismatch |
The twelve-line FBO movement brief
The best brief is short enough to scan and complete enough to operate. Put live identifiers first, decision authority second, and preferences last. Keep passport data, government IDs, and other unnecessary sensitive information out of general movement messages.
Illustrative brief — not a live assignment
A fictional executive arrival continuing to two Washington meetings.
- Movement
- IAD private arrival → K Street → Capitol Hill
- Aircraft
- Tail number supplied securely to the desk; ETA tracked separately from passenger ready
- Handler
- Facility name, desk number, and current pickup boundary confirmed
- Release trigger
- Handler texts Altaie desk when the passenger is ready
- Contacts
- Assistant primary; flight department fallback; principal not called unless requested
- Party
- Two travelers, three roll-aboards, one garment bag
- Vehicle
- Executive SUV requested, subject to desk confirmation
- First hard door
- K Street lobby at 11:30 a.m.; building entry instructions attached
- Change authority
- Assistant may revise stops and waiting; desk relays one clean update
Decide the delay protocol while the plan is calm
Write down what happens when the aircraft is early, late, diverts, or changes facilities. The desk should know whether to hold the same vehicle, revise the chauffeur report time, or escalate for a new operating solution. The assistant should know when they will receive an updated plan and which parts remain provisional.
For the destination leg, use a live ETA only after the passenger is loaded and the current route is visible. Any earlier number is a planning range. A professional update names the new fact, its effect on the first hard door, and the next decision time.
- Track the aircraft, but do not treat flight data as the passenger-ready signal.
- Reconfirm the facility if the aircraft diverts or the operator changes handling.
- Preserve one change channel so the chauffeur is not receiving conflicting instructions.
- State the next update time when the final answer is not yet knowable.
Verification trail
Sources and current guidance
Public operating instructions can change. These links identify the source pages used for this note; reconfirm current instructions before travel.
Written by
Fahad Hamid
Altaie chauffeur and Field Notes author covering Washington airport arrivals, private aviation handoffs, and assistant-led executive itineraries.
Author profile