Skip to content
Marquee Chauffeur — Portland's white-glove chauffeur and luxury black car service
PDX airport pickup with FlightAware live wheels-down tracking on Marquee Volvo S90

How It Works

FlightAware Tracking for PDX Pickups.

Every Marquee PDX pickup carries a tail number into the dispatch board at booking. The FlightAware feed polls that record continuously and pushes wheels-down data into dispatch the moment the aircraft touches the runway. A weather-delayed flight holds the chauffeur at the Cell Phone Lot without any meter on the wait. An early arrival pulls the chauffeur to the assigned door before baggage claim opens. The 60-minute grace window after touchdown comes included on every PDX pickup at no extra charge. The integration only works on commercial PDX arrivals where FlightAware has a live feed. Private aviation runs on a separate protocol through the FBO desk.

Last updated: April 21, 2026

Bottom line: FlightAware integration is included on every Marquee PDX pickup. The tail number enters dispatch at booking, the live feed reroutes the chauffeur on delays or early landings, and the 60-minute grace window after wheels-down carries no extra charge. Rideshare scheduled-arrival tracking runs on planned ETA only and meters wait time once the contractor arrives. The two products handle the same flight differently.

01The Booking Flow

Tail Number Enters Dispatch
At The Moment Of Reservation.

The FlightAware integration starts at booking. The flight number goes into the assignment along with the airline code, arrival date, and origin city. The dispatch board attaches the record to the rider's pickup window and the live FlightAware feed starts polling. Bookings come through the form on PDX airport car service, by email, or by phone with the live dispatcher at (503) 706-8662. The full booking sequence including required fields and timing windows lives on how to book a PDX airport chauffeur.

What dispatch captures

The booking form pulls the airline code, the flight number, the arrival date, the origin city, and the scheduled arrival time. Those five fields populate the FlightAware record on the assignment. Dispatch also captures the rider name, the destination address, the requested vehicle, and any preferences like a child seat or a specific bottle of water. The flight identifier is the single field that distinguishes a tracked PDX pickup from a generic point-to-point ride.

Confirmation timing

Marquee sends the booking confirmation by email within 10 minutes of the reservation with the named chauffeur, the assigned vehicle, the direct cell number, and the flight identifier on file. The morning ride sheet for the chauffeur lists the same flight record, so the named driver knows the tail number on shift before leaving the garage. The rider does not need to resend the flight number or check in on the day of travel for the tracking to activate.

Updates and changes

A flight number change after booking goes through the dispatcher at (503) 706-8662 or as a reply to the confirmation email. Dispatch swaps the FlightAware record on the assignment within minutes. Travelers who book an earlier connecting flight on the day of travel use the same channel. The swap does not affect the locked hourly rate or the grace window. Dispatch carries the change through to the chauffeur ride sheet before the start of shift.

Commercial PDX only

The FlightAware feed runs on commercial arrivals at PDX where the airline files the flight plan publicly. Private aviation tail numbers route through the FBO desk on a separate protocol. The Atlantic Aviation arrival workflow including ramp clearance, baggage handling, and the sequence from wheels-down to vehicle stage is on the Atlantic Aviation chauffeur guide. The two protocols sit on separate dispatch tracks rather than running through the same logic.

Volvo S90 cabin staged at PDX Cell Phone Lot during weather-delayed Alaska arrival
The Volvo S90 holds at the Cell Phone Lot through weather delays. The 60-minute grace window starts at FlightAware-confirmed wheels-down rather than the original schedule.

02Live Wheels-Down Feed

Touchdown Triggers The Reroute,
Not The Scheduled ETA.

The FlightAware feed pushes the wheels-down event into dispatch the moment the aircraft touches the runway at PDX. The dispatch board flips the assignment status from monitoring to active at that timestamp. The chauffeur receives a notification with the gate, the baggage claim carousel, and the staging instruction for the lower roadway. Scheduled ETA is a forecast. Wheels-down is a recorded fact. The reroute logic runs on the recorded fact rather than the forecast, which is the structural difference from rideshare scheduled-arrival dispatch covered on chauffeur vs Uber Black.

Weather-delayed Alaska from SEA

A scheduled 9:30 PM Alaska arrival from SEA running 90 minutes late on a Tuesday in February sits in dispatch through the delay. The chauffeur stages at the Cell Phone Lot rather than circling the lower roadway or paying short-term parking. FlightAware pushes the actual wheels-down at 11:00 PM and the chauffeur pulls to the curb with the rider's bottle of water already chilled in the cabin. The grace window runs to 12:00 AM at no extra charge against the booked rate.

Early Delta arrival from ATL

A scheduled 6:45 PM Delta arrival from ATL running 25 minutes early lands at 6:20 PM with FlightAware pushing the timestamp to dispatch. The chauffeur pulls to Door 5 before baggage claim opens, which means the rider walks down the jet bridge and meets the named chauffeur in the lower roadway without standing at the carousel. The early-arrival case is a smaller share of pickups than weather delays, but it shows the symmetry of the integration. Live data reroutes the chauffeur in either direction.

Cell Phone Lot staging

PDX runs a free Cell Phone Lot near the airport entrance where vehicles can stage indefinitely without any time limit. Marquee chauffeurs use the lot as the default holding pattern for inbound arrivals. The chauffeur watches the FlightAware feed and the baggage claim status from the lot, then pulls to the assigned lower-roadway door at the right minute. The full lower-roadway pickup logic with door numbers, taxi-vs-livery lane assignments, and meet-up protocol is on the PDX pickup location guide.

No meter on the wait

The 60-minute grace window after FlightAware-confirmed touchdown carries no meter and no surcharge. The locked hourly rate or flat airport quote holds regardless of how long the chauffeur sits at the Cell Phone Lot during a delay. A flight that runs two hours late and lands at 11:47 PM after a scheduled 9:30 PM arrival starts the 60-minute window at 11:47 PM. Beyond the grace window, the chauffeur stays at the curb on the booked vehicle's hourly rate. The structure is published rather than negotiated at pickup.

Cadillac Escalade ESV staging at lower-roadway pickup curb on early Delta arrival from ATL
Early arrivals trigger a chauffeur reroute to the assigned door before baggage claim opens. Live wheels-down data drives the timing rather than the original schedule.

03Why It Matters

Live Data Versus
Scheduled-Arrival Dispatch.

Rideshare scheduled-arrival tracking and FlightAware-integrated chauffeur dispatch handle the same delayed flight differently. Rideshare apps run on the rider-submitted ETA at booking and assign a 1099 contractor 15 minutes before that planned time. The contractor does not see the live wheels-down feed, the gate change, or the diversion. A weather delay triggers a fresh request after the meter started running on the original ETA. The chauffeur side reads the live data and reroutes the named driver without a new booking and without metered wait time. The full operating-model breakdown is on chauffeur vs black car service.

Two different inputs

Scheduled arrival is what the rider typed into the rideshare app at booking. Wheels-down is what the FlightAware feed pulls from the air-traffic record once the aircraft touches the runway. The two inputs match within a few minutes when a flight runs on time, but they diverge widely on weather days or at hub-routing complications. Marquee dispatch runs on the wheels-down input. The rideshare contractor app runs on the scheduled-arrival input. The same flight produces different chauffeur behavior depending on which input drives dispatch.

Cost predictability

A rideshare contractor running the meter from the original ETA bills the rider for wait time after a short grace window. The final fare expands beyond the original quote when the flight runs late. Marquee bills the locked hourly rate or the flat airport quote regardless of delay length within the included 60 minutes after touchdown. The corporate AP team reconciles a predictable invoice rather than a variable surge fare. For travel managers reviewing monthly totals on Concur or QuickBooks, the cost-predictability difference shows up directly in the line items.

Driver continuity

A rideshare contractor who waited through the short grace window and then canceled triggers a fresh dispatch request at the moment the rider walks out of baggage claim. The new contractor is whoever is closest, which means a different driver and a different vehicle than the rider expected at booking. Marquee holds the named chauffeur on the assignment through the delay, which means the same Volvo S90 with the same trained driver pulls to the curb regardless of how long the flight ran late. The continuity matters for first-time international arrivals and for executive travel where the rider expects the named driver from confirmation.

Diversions and gate changes

FlightAware tracks diversions to alternate fields like SEA, EUG, or RDM in real time. The dispatch board flips the assignment status to manual oversight and the dispatcher reaches out to the rider by text and phone with the recovery plan. Gate changes after landing also reflect on the dispatch board, which adjusts the chauffeur staging from one door to another at the lower roadway. Rideshare scheduled-arrival logic does not handle diversions or post-landing gate changes natively. The chauffeur-side workflow handles both as standard dispatch behavior.

04Limits Of The Integration

Commercial Arrivals Only,
Private Aviation On A Separate Track.

FlightAware works on commercial PDX arrivals where the airline files the flight plan publicly through the FAA system. Private aviation operates on a different framework. Tail numbers register with FlightAware, but the arrival logic at the FBO uses the FBO concierge desk for clearance rather than commercial dispatch logic. Atlantic Aviation runs the dominant FBO at PDX with ramp clearance, baggage handling, and the sequence from wheels-down to vehicle stage all coordinated through the concierge. The full FBO arrival workflow with ramp protocol, vehicle staging rules, and the chauffeur-side coordination is on the Atlantic Aviation PDX chauffeur guide.

Why FBO is different

Commercial flights operate under FAA-filed flight plans that FlightAware reads in real time. Private aviation flight plans get filed but the wheels-down event at the FBO does not run through the same public-feed pipeline. The FBO concierge holds the inbound timing on a desk-level system and coordinates ramp access for the chauffeur directly. The protocol is operationally different rather than a worse version of commercial dispatch. The chauffeur stages at a separate location, holds different ramp credentials, and follows a separate baggage-handling sequence.

Coordination through the concierge

Marquee coordinates Atlantic Aviation arrivals through the FBO concierge desk on the morning of the trip. The chauffeur receives the ramp instructions and the staging assignment from the concierge rather than from the FlightAware feed. The Volvo S90, Escalade ESV, or Sprinter holds at the FBO parking area with engine ready until the aircraft arrives at the ramp and the concierge releases the vehicle to the gate. The handoff sequence runs the same way whether the inbound aircraft is a Cessna Citation, a Gulfstream G-650, or a Bombardier Challenger.

Booking through both channels

Riders mixing commercial and private aviation across a multi-day Portland visit use both protocols on the same booking. A commercial arrival from JFK on Monday runs on the FlightAware feed at the lower-roadway pickup. A private departure to Sun Valley on Wednesday runs through the FBO concierge at the Atlantic Aviation ramp. The dispatcher coordinates both arrivals on the same corporate account with one consolidated invoice. The two-protocol structure carries no extra cost beyond the standard hourly rates on the booked vehicles.

No upcharge on either side

The FlightAware integration on commercial arrivals carries no extra charge against the booked rate. The FBO concierge coordination on private arrivals also carries no extra charge. The 60-minute grace window after touchdown applies on the commercial side. The FBO coordination on private aviation handles staging through the concierge release rather than against a fixed grace window because the FBO timing model is different. Both protocols run as standard dispatch behavior rather than as premium upgrades.

Frequently Asked

Questions, Answered.

Reserve Your Chauffeur

Reserve a Portland
Chauffeur Now.

Book your PDX pickup with FlightAware tracking included. Call Marquee Chauffeur at (503) 706-8662, available 24/7. The tail number enters dispatch at booking, the live wheels-down feed reroutes the chauffeur on delays or early arrivals, and the 60-minute grace window after touchdown carries no extra charge. Volvo S90 at $110 per hour, Escalade ESV at $135 per hour, Sprinter at $165 per hour, all under Oregon PUC certification with W-2 chauffeurs and $1 million commercial liability.