Correctly display flight time when different timezones need to be considered.
complete
Jason Bragg
Total flight time showing for flights incorrect when the flight crosses the international date line.
ie pax is leaving Los Angeles on 24th Jan and arriving in Sydney on 26th Jan so the Tourwriter shows the dates correctly, and the time the flight took to reach Sydney is shown as 34 hours instead of 36.
One solution could be to enable (For flight type only) a Flight time field that is visible on the Add Item and Edit Item dialogs that:
- Automatically calculates the time ie 36 hrs 00 min based on the Departure time and Arrival time
- Allows the User to manaully override the time to be whatever they want. ie 34 hrs 00 min
Sina Zimmermann
Merged in a post:
Issue with International Date Line Flights Displaying Incorrectly in Itineraries
Hi Admin team and fellow users,
I’d like to raise an issue we regularly encounter with international flights that cross the International Date Line, and suggest an improvement that would greatly reduce client confusion.
The problem
When clients depart Australia or New Zealand on a Thursday and arrive in destinations like French Polynesia on the Wednesday (due to crossing the Date Line), Tourwriter currently displays the flight on Day 2 instead of Day 1.
This creates a confusing itinerary sequence for clients. For example:
The first service listed is a hotel or transfer in Tahiti on 4 January
The international flight from AU/NZ to Tahiti appears on 5 January, even though logically it is what gets them there
From a client’s perspective, it looks like they are already in Tahiti before they fly.
Ideal outcome
Ideally, the itinerary would allow:
The international flight (departing Thursday 5 January, arriving Wednesday 4 January) to be shown as the first service
Followed by the arrival transfer and hotel on Wednesday 4 January
Then continuing with planned services from 5 January onward in a logical, chronological order
This would reflect the real travel flow and make the itinerary much clearer and more intuitive for clients, especially those unfamiliar with International Date Line travel.
Why this matters
This issue comes up frequently with French Polynesia itineraries and often requires manual explanation to clients, which could be avoided with improved system logic or display options.
I’d love to hear suggestions from the community or admin team on the best way Tourwriter could handle these scenarios more clearly. If this is something you’ve also experienced, I’d really appreciate your vote so it can be considered for future development.
Thank you!
Kind regards,
I
Isolated Ocelot
Perhaps if there is a way of forcing the order in the itinerary so that the flow is correct for the client, but the booking dates remain correct for supplier requests.
M
Melodic Elk
This item is still outstanding
G
Glacier Giraffe
Jason Bragg We have found that this function is not complete as the overwritten duration doesn't pull through to the pricing page, or subsequent exports. An example is a flight departs AUS at 09:10 AEST and arrives into NZ at 14:30 NZST (12:30 AEST). Because TW doesn't have a time zone field or ability to calculate flight duration according to departure and arrival location, the system automatically set duration as 5hr 20 rather than 3hr 20. We have manually overwritten this in the build, however the document we're sharing with clients is exported from the pricing page, which still shows 5hr 20. Please enable overwritten duration to apply in all screens and/or the ability to calculate according to time zone/location. Thanks.
Jason Bragg
marked this post as
complete
1.66.0
Jason Bragg
marked this post as
in progress
Jason Bragg
marked this post as
under review