College Park & Potomac Airfield Transportation

Planning College Park & Potomac Airfield Transportation

Arrange a confirmed private-car connection to College Park Airport or Potomac Airfield in Maryland. These are distinct facilities with different operating contacts and access procedures, so identify the actual airport and current handler before dispatch.

The traveler or aviation coordinator must confirm the airport currently authorized for the flight, applicable security procedures, operator contact, arrival estimate, and approved meeting point. DC Black Cars does not grant airport access or determine flight eligibility.

The Two Operating Maryland Airports in This Guide

College Park Airport (CGS) is in College Park, Maryland. Potomac Airfield (VKX) is in Friendly, Maryland, within Prince George’s County. Confirm the airport identifier, the operating flight, the airport or handler contact, and the approved passenger meeting point in the current reservation record. Airport city and name alone do not establish airside access or a pickup location.

Older aviation references may group these facilities with Washington Executive Airpark, also known as Hyde Field (W32), as the “Maryland Three.” Hyde Field in Clinton, Maryland, permanently ceased flight operations on November 30, 2022. It is not an active airport destination or pickup location. This guide covers College Park and Potomac Airfield only. Hyde Field’s closure notice confirms the closure.

Who This Guide Is For

This guide is designed for private-aviation passengers, pilots, aircraft owners, charter teams, family offices, executive assistants, and aviation coordinators. The booker, passenger, payer, travel-day contact, and person authorized to approve changes may be different people, so those roles should be named before service.

The plan should specifically account for confirmed airport, operator or FBO contact, aircraft reference, authorized travelers, security procedures, luggage, final address, and schedule changes. Those details determine whether the request is a simple transfer, a waiting assignment, a multi-vehicle movement, or a retained program.

Build the Operating Record

Airport and federal requirements can change. Transportation is confirmed only after the ground itinerary is accepted, and passengers remain responsible for aviation credentials, security-program compliance, and instructions from the airport, operator, TSA, FAA, or other controlling authority.

Keep the aircraft operator, FBO and passenger coordinator aligned on the current arrival and pickup point. FBO waiting terms are confirmed separately, and no grace period applies to FBO pickups.

Select a Transfer, FBO Pickup or Retained Vehicle

A fixed commercial-airport transfer suits a known airline arrival and destination. A private-aviation pickup requires the actual airport, current FBO or handler and approved meeting point. Retained service is a separate request for a defined window when a passenger may leave the airport for meetings or return at an uncertain time.

Do not treat the aircraft schedule as a confirmed chauffeur release time. Provide the expected arrival, passenger contact and change authority, then confirm any waiting, return or extended availability in writing.

Match the Vehicle to the Flight Party

Identify whether the travelers are arriving together and count every passenger, checked case, carry-on, garment bag and oversized item. An executive transfer with two travelers and minimal luggage differs from a family or aircraft party carrying several cases. Seat capacity alone does not confirm that the complete load will fit.

For a group with separate arrival times or destinations, assign a mission to each vehicle. State whether the driver meets a single traveler, several passengers or a party representative, and confirm exact equipment and luggage capacity before booking.

Confirm Commercial Terminal or FBO Before Dispatch

For a commercial airport arrival at IAD, DCA or BWI, provide the operating airline and flight number, passenger mobile, baggage, meeting method and destination. Airport arrivals include a 30-minute grace period, except at FBOs; changed flights, cancellations, diversions and rebookings must be reported directly.

For private aviation, confirm which airport and current FBO or handler is operating the flight, who will release the passenger and where the vehicle may meet them. FBO waiting terms are confirmed separately; no grace period applies to FBO pickups. An airport name alone is not sufficient for an FBO pickup.

Use the Confirmed Passenger Meeting Point

The passenger or aviation coordinator should provide the approved meeting point and any handler instructions. Do not assume that an aircraft, terminal, private lounge or restricted area is accessible to the chauffeur or vehicle. The responsible airport, FBO or operator controls its own access rules.

Dispatch needs the passenger contact, flight or aircraft reference, luggage, final address and authorized change contact. Aviation credentials, security-program compliance, handling, flight operations and passenger screening remain with the relevant traveler and provider.

Plan for Flight Changes and Passenger Release

If the operating flight, aircraft, airport or FBO changes, notify dispatch before the original meeting plan becomes unusable. The coordinator should be reachable while passengers deplane, collect luggage or complete the handoff. Flight monitoring supports planning but does not replace direct notice of a rebooking or changed meeting point.

For a tight onward appointment, share the required arrival and final address before confirming the pickup. A chauffeur cannot guarantee a flight connection or control aircraft release, airport processing, traffic or the passenger’s readiness.

Maryland Airport or FBO Booking Details

Provide the date and local time zone, operating airline and flight or aircraft reference, airport and terminal or FBO, lead passenger mobile, handler or release contact, meeting point, passenger and luggage count, final address, required arrival, return or waiting request and authorized change contact.

For multiple travelers or aircraft, identify who travels together and assign each vehicle a specific pickup. Airport arrivals include a 30-minute grace period, except at FBOs. FBO waiting terms are confirmed separately; no grace period applies to FBO pickups.

Choose the Gateway and Handoff That Fit the Flight

Choosing among IAD, DCA and BWI starts with the operating flight, aircraft or airline, and the passenger’s final destination. A commercial arrival at one airport is not interchangeable with an FBO movement at another. The booking party should confirm the actual facility, handler, terminal or FBO, passenger release contact, baggage and legal meeting point. Each airport controls its own curb, staging and access instructions, which may change with operations or security conditions.

For an itinerary that uses more than one airport, list the arrival and departure flight numbers separately and identify who will remain reachable during the transfer. If a traveler moves between an FBO and a commercial terminal, build time for passenger release, luggage and the second airport’s check-in requirement. A vehicle should not be dispatched against an aircraft estimate without a confirmed handler reference and current pickup instructions.

Coordination After Confirmation

After confirmation, send aircraft, FBO, arrival time, passenger, luggage or destination changes through the authorized aviation contact. The handler’s release information and the written transportation confirmation must agree; an informal message to a chauffeur does not approve a changed pickup.

For a private-aviation arrival, identify the aircraft handler, lead passenger, authorized booker and approved FBO meeting point on one movement record. Commercial airport pickups and FBO handoffs follow different arrival procedures, so keep each leg and its passenger contact distinct.

Frequently Asked Questions