Your flight is at 00:35 on Thursday. You leave the hotel on Wednesday night, reach the airport before midnight and check in while the departures board still says Wednesday. So what date belongs on the flight itinerary?
Thursday. The departure date is the calendar date at the airport where the flight takes off. For a 00:35 departure, that is already the new day, even if most of your airport journey happened the night before.
This small detail causes an impressive amount of travel confusion. It is especially easy to get wrong when you are choosing an onward flight, checking a reservation PDF or arranging a late-night connection.
The airport clock wins, not your bedtime
Take an entirely illustrative flight leaving Bangkok at 00:35 on 21 October. You might leave your accommodation at 21:00 on 20 October and stand in the check-in queue at 22:30. The flight is still a 21 October departure.
If you search for 20 October because that is the evening you travel to the airport, you could end up looking at a completely different service. A flight at 00:35 on 20 October left nearly a full day earlier.
The easiest way to think about it is to separate the airport night from the flight date. Your night at the airport may straddle two calendar days. The scheduled departure has one date, printed in the departure airport's local time.
A quick note on midnight itself: 00:00 is the beginning of a day, not the end. A flight at 23:55 on Tuesday and one at 00:05 on Wednesday may be only ten minutes apart, but their tickets carry different departure dates.
Why an itinerary can show two different dates
Airline schedules use local time at each airport. A flight can leave late on one day and land the next morning; a long flight across several time zones can arrive on a surprisingly different calendar date.
Emirates displays arrival times with a “+1” marker when the arrival is the following day. KLM's published schedules likewise identify next-day arrivals and state that the listed times are local. The marker belongs to the arrival, not to a second departure date.
Picture a journey with these made-up times:
| Event | Local date and time |
|---|---|
| Depart your first airport | Wednesday, 21 October, 22:45 |
| Arrive at the next airport | Thursday, 22 October, 06:15 (+1) |
The date that describes when you left the first country is Wednesday. Thursday describes when you arrived. You don't move the departure to Thursday just because the aircraft landed after midnight.
There is no need to calculate the flight duration by subtracting the two clock readings. They belong to different time zones. The airline's elapsed travel time already accounts for that difference.
What if the onward flight itself has a connection?
Look at the first leg that actually leaves the country you're visiting. If it departs at 23:40 on Wednesday and the next flight leaves the connecting airport at 02:10 on Thursday, your departure from the first country is on Wednesday.
If the first flight leaves at 00:40 on Thursday, then Thursday is the departure date. The date of the second leg doesn't rewrite the first.
A connecting itinerary can display several dates on one page. Read each row as its own event: departure airport, local departure date and time, arrival airport, local arrival date and time. Airport codes are especially helpful when the journey crosses a time zone or changes terminals.
If your connection is on a separate booking, keep both itineraries handy. The guide to airline document checks at check-in explains why an independently booked next flight may need to be shown separately.
The date you enter when searching for an onward flight
Start with the city you will physically depart from, not the city where your phone happens to be set. Choose the calendar day on which the aircraft is scheduled to leave that airport.
This matters when you search from home across a time-zone difference. A flight that appears late at night in your home time zone may already be the next morning at its departure airport. Airline booking screens normally show the relevant local airport times; use those displayed dates rather than converting them in your head.
If your planned departure is near the end of your stay, the midnight boundary deserves extra attention. A flight at 00:20 on the following calendar day is not a 23:40 flight on the previous one. Use the date on the actual schedule and keep the intended stay aligned with it.
The guide to choosing an onward destination helps with the other half of the decision: making sure the airport and next stop fit your route.
The flight date and the reservation's life are separate
There is another clock on some flight documents: how long a reservation remains active. A temporary booking can be created today for a flight weeks from now and still expire well before that flight takes place.
That expiry window has nothing to do with whether a 00:35 flight belongs to Wednesday or Thursday. One is about the record's availability; the other is the scheduled departure on the itinerary. The reservation timing guide deals with the first question.
Before you save the PDF, compare the flight date against the airline's current schedule, especially after any change notification. A small retiming from 23:55 to 00:15 can shift the departure to the next day without changing the journey very much.
The rule is uncomplicated once you stop thinking of the evening as one long day: the flight leaves on the date shown by the clock at its departure airport. Your hotel checkout, taxi ride and arrival date are separate entries in the travel diary.