The 12-hour clock falls apart at the date line
Here is a real scenario. You are on a flight from Narita to LAX. Departure is 2300 Monday. You are in the air for about nine hours. You land at 0100 Wednesday. Not Tuesday. Wednesday.
If you think in 12-hour time, you just watched Monday's 11:00 PM become Wednesday's 1:00 AM. Tuesday never happened for you. The clock said 11:00 PM, then it said 1:00 AM, and the calendar jumped a day. That is not a quirk. That is the International Date Line doing its job.
The 24-hour clock makes this legible. 2300 Monday becomes 0100 Wednesday. No AM or PM to fumble. No "wait, was that 1 in the afternoon?" The hour numbers run 00 to 23, and when you cross the date line, the date changes even though the minute hand never stops.
What the date line actually does to time
The International Date Line runs roughly along the 180th meridian, through the Pacific Ocean. It is not a straight line. It kinks around island nations so that no country is split into two different dates. But for the purpose of reading military time, the rule is simple: cross it going west, add a day. Cross it going east, subtract a day.
Here is the part that confuses people: the time of day does not have to change. You can fly from Fiji to Honolulu and your watch might read 2300 on a given evening when you take off and 2300 on the previous evening when you land. Same hour. Different date. The 24-hour clock just tells you which hour it is. The date line tells you which day it is. You need both.
That is why the military and aviation never say "Monday 11 PM." They say "2300 Zulu" or "2300 local" and they attach a date. The date is not optional. It is half the information.
Why 0000 and 2400 matter more than you think
Here is where the date line collides with the most common military time question: is midnight 0000 or 2400?
Both are real. They are the same instant, but they are not the same date.
0000 is the start of a day. 2400 is the end of a day. So 0000 on a given day is the first minute. 2400 on that same day is the last minute. They are the same point on the timeline, but one opens a date and one closes it.
Now cross the date line. If you are at 2400 Monday and you move west, you are now at 0000 Wednesday. You skipped a whole day. If you are at 0000 Wednesday and you move east, you are at 2400 Tuesday. You went back into the previous day. Same instant, two different dates, and the military time notation tells you which one you are in.
This is not academic. Ships and aircraft submit reports in Date-Time Groups (DTGs). A DTG written as 2400Z Monday and one written as 0000Z Tuesday refer to the same second. But if a report is due at 0000Z Tuesday and you file at 2400Z Monday, you are on time. If you file at 0000Z Wednesday, you are 24 hours late. The notation is the difference between a deadline met and a deadline missed.
The lettered zones: Zulu is the anchor
You have probably seen the letters: A through Z, skipping J. Each one is a fixed UTC offset. Zulu (Z) is UTC+0. Alpha (A) is UTC+1. Bravo (B) is UTC+2. Charlie (C) is UTC+3. And so on up to Mike (M) at UTC+12, then November (N) at UTC-1, down to Yankee (Y) at UTC-12.
These zones are not time zones in the civilian sense. They have no daylight saving. They are just offsets. When you say "1500 Zulu," you are saying "1500 UTC" and letting everyone else do the arithmetic to their own offset.
Here is what trips people up when the date line is involved. The lettered zones stop at M (UTC+12) and Y (UTC-12). There is no zone for UTC+13 or UTC+14. But the real world has places at those offsets. Some Pacific islands run at UTC+14. The military letter system cannot represent that. So a flight from Kiribati to Hawaii might be at UTC+14 local time, which is a date ahead of Hawaii even though the hours look similar.
The workaround is to use Zulu time for everything and convert to local only when you land. That is what aviation does. A pilot flying from the Pacific to North America does not think in "local military time." They think in Zulu. They check the local time for weather briefings and airport operations, but the coordination happens in Zulu.
What happens when you cross the date line on a flight
Let us run the example from the opening. Tokyo is at UTC+9, which is military zone I (India). Los Angeles is at UTC-7 in July, which is military zone T (Tango) during daylight saving, or UTC-8 in January, which is zone U (Uniform). The flight leaves Tokyo at 2300 Monday local.
2300 Monday in Tokyo is 1400 Monday Zulu. Same instant. The flight is nine hours, so it lands at 2300 Monday Zulu. That is 1600 Monday in Los Angeles. But the flight is actually about ten hours. So it lands around 0000 Tuesday Zulu, which is 1700 Monday in Los Angeles. Wait. That is wrong.
Let us be careful. Tokyo to LAX is roughly ten hours. Depart 2300 Monday Tokyo time. Tokyo is UTC+9, so 2300 Monday Tokyo is 1400 Monday Zulu. Add ten hours of flight time. That is 0000 Tuesday Zulu. Los Angeles in July is UTC-7, so 0000 Tuesday Zulu is 1700 Monday in Los Angeles.
You landed on Monday. You took off on Monday. You were in the air for ten hours and you landed on the same day you left. That is the date line working in your favor. You gained a day. But if you look at your watch and it says 2300 and then it says 1700, you have to trust the date. The hours alone will lie to you.
Now fly back. Depart LAX at 2300 Monday local. 2300 Monday in July is 0600 Tuesday Zulu. Add ten hours. That is 1600 Tuesday Zulu. Tokyo is UTC+9, so 1600 Tuesday Zulu is 0100 Wednesday in Tokyo.
You left Monday night. You landed Wednesday morning. You lost a day. Your watch said 2300 Monday, then 0100 Wednesday. The 24-hour clock kept counting. The date jumped. That is the International Date Line.
Who should change how they do this
The default advice for travelers is to change your watch to local time on arrival and move on. That works for civilians. It is the wrong move for anyone who has to file a report, catch a connecting flight, or log a shift across the date line.
If you are a shift worker, a dispatcher, a nurse, or a pilot, do not convert to local time in your head. Write the Zulu time and the date. Write the local time and the date. Both. Every time. The person who reads your log in 12 hours will not know what you meant if you only wrote "0100." They need the date, the offset, and the time. That is why the military uses the DTG format: a six-digit date, a four-digit time, a letter for the zone, and a year. It is clunky. It is unambiguous. It is correct.
The one group that should ignore this entirely is the amateur radio operator. If you are logging contacts, you use Zulu time and you do not care about the date line at all. You are already on UTC. Keep it that way. The date line does not exist for you.
For everyone else: when you cross the date line, stop thinking about what time it is and start thinking about what date it is. The hours will take care of themselves.