A private aviation ground transportation checklist should start with the exact FBO, tail number, passenger-ready time, passenger roles, baggage volume, handoff type, and lead contact. The airport code alone is not enough because FBO procedures, ramp access, canopy access, lobby handoff, baggage handling, and security rules vary by airport and provider. The cleanest request tells the car-service coordinator who rides where, which bags move with the principal, whether a support vehicle is needed, and how updates should flow if the aircraft arrives early, delays, diverts, or changes FBO.
Artisan Chauffeur & Concierge arranges private aviation ground transportation through vetted licensed local operators, with FBO, tail number, vehicle class, baggage plan, handoff point, wait policy, toll treatment, and day-of contact path confirmed before pickup. The checklist is built to remove ambiguity before the aircraft arrives.
This guide should help a traveler choose the right option quickly, then move into a quote when the itinerary needs control over pickup, vehicle class, and handoff.
The important comparison is not just price. It is the tradeoff between cost, luggage friction, pickup control, and how much of the final handoff can be planned before confirmation.
Costs and timing reflect public source data and operator-network planning ranges; the quote states inclusions and pass-through variables before confirmation.
Name the FBO and tail number before vehicle class is finalized.
Assign each vehicle a job: principal, family, staff, crew, luggage, or support.
The confirmation should state the handoff point and backup if ramp access is not available.
Name one lead contact with authority to change timing or release vehicles.
Send the FBO name, tail number, scheduled arrival or passenger-ready time, passenger count, baggage count, destination, preferred vehicle class, and lead contact. If the principal, staff, crew, and luggage should not move together, say that in the first request.
Verify the FBO, handoff point, vehicle class, assigned contact path, baggage plan, and wait policy before the aircraft lands. For Teterboro, naming only the airport code is not enough because multiple FBOs operate at the field.
Do not assume planeside pickup, exact vehicle model, or unlimited luggage space. Ramp-adjacent access depends on FBO and airport rules, and the vehicle plan should account for a lobby or curb handoff when that is the correct procedure.
Send the exact FBO, tail number, scheduled arrival, passenger-ready time, passenger count, baggage count, destination, vehicle preference, handoff preference, and lead contact. Add principal, staff, family, crew, or luggage split if roles matter.
No. Tail number helps with tracking and coordination, but the quote still needs FBO, passenger-ready time, passenger count, baggage, handoff point, destination, and day-of contact. At airports with multiple FBOs, the exact FBO is essential.
Only where permitted by airport and FBO rules. The confirmation should state whether pickup is ramp-adjacent, FBO canopy, lobby, desk, or curbside, plus a fallback if access changes.
Use two vehicles when the principal needs privacy, staff or security should move separately, baggage volume is high, or family/crew movement should not crowd one cabin. The confirmation should assign each vehicle a role.