Time zones in private jet itineraries: a planner’s guide

Attach the time to the location and date

Write the departure time with the departure location and the arrival time with the arrival location. Keep the calendar date visible at both ends, particularly when a flight crosses midnight or the itinerary spans several days. Avoid assuming that the reader knows which city’s clock you mean.

When requesting a quote, distinguish a preferred departure from a required arrival. ‘At the office by 10:00 local time’ and ‘land at 10:00’ are different instructions. Give your broker the actual constraint and ask them to confirm the proposed flight schedule and relevant ground arrangements.

Be careful with copied calendar events

A calendar application may display an event in the viewer’s current time zone. That behavior is useful, but it can make a screenshot or copied line ambiguous. Check the event’s location, date and zone before using it as an instruction to a broker or driver.

Use a reliable date-aware calendar or time-zone tool when converting times. A fixed offset remembered from a previous trip may not apply on another date. If a conversion affects a booking or handoff, ask the relevant contact to confirm their interpretation rather than relying only on your calculation.

• Does the event show the intended location and travel date?
• Is the displayed time local to departure, local to arrival or another agreed basis?
• Does the arrival fall on the same date or a different date?
• Will the recipient’s calendar display the time differently?

Use an unambiguous confirmation format

Put the time basis in the same line as the time. Keep both the requested and confirmed arrangements where they can be distinguished. If you send a revision, name the old arrangement being replaced so recipients do not have to infer which message is current.

Timing confirmation
Trip / leg:
Departure: [date], [time], local time at [airport / city]
Arrival: [date], [time], local time at [airport / city]
Required event arrival: [date, time and location]
Ground transfer owner:
Confirmed by broker on:
This replaces:
Open timing questions:

Test the full itinerary, not one timestamp

Read consecutive legs in order and make sure the sequence makes sense as a journey. Check overnight stays, pickup instructions and meeting invitations against the confirmed itinerary. A return leg copied from an earlier quote may be correct in isolation and still conflict with the rest of the trip.

In WingStack, ask your broker to demonstrate how time information appears in the planner and passenger views for a trip across time zones. Use the same example on desktop and mobile. If a label is unclear, resolve it before travel and keep the agreed meaning in the trip discussion.