Intro: The 24-hour clock we now call military time did not begin with the armed forces, nor with a single inventor. Its roots stretch back over four thousand years to ancient Egypt, and its modern form emerged from railways, world wars, and medical malpractice lawsuits.
Ancient Origins: Egyptian Decans and Italian Time
The earliest known system of 24-hour timekeeping dates to ancient Egypt. The Egyptians divided the night into 12 parts using "decans", 36 star groups that rose sequentially as the night progressed. Each decan marked roughly 20 minutes of darkness, and grouping them into sets of three produced 12 night hours. The daylight period was similarly divided into 10 daytime hours plus two twilight hours, giving 24 total divisions.
Why the Egyptian hour was not fixed
But the ancient Egyptian hour was not fixed. Summer daylight hours were longer than winter ones. The system worked for religious and agricultural purposes, but it was not a precise measure.
Italian time: 24 hours from sunset
The shift to equal, 24-hour days came much later, in medieval Europe. The "Italian time" system (ora italica) counted the full day as 24 hours beginning at sunset. This was not a niche curiosity. Italian time governed public clocks, church bells, and civic life across the Italian peninsula from the 14th century well into the 19th. Travelers in Florence in 1750 would have heard the hour announced as "the 23rd hour" near dusk, not "5 PM."
What Italian time solved
Italian time mattered because it solved a problem that AM/PM systems never could: it removed all ambiguity about which part of the day was meant. When the day resets at sunset, everyone knows where they stand. That same logic, eliminate the ambiguity, would drive every major adoption of 24-hour time that followed.
Railways Drive Adoption: Great Western Railway 1847
The modern 24-hour clock is a product of the railway age. Before trains, each town set its own clock by local solar noon. A journey from London to Bristol in 1840 required resetting your watch several times. Timetables were a nightmare of local times, and a missed connection could mean a night stranded in the rain.
The Railway Clearing House recommendation
The Great Western Railway solved this by adopting a single standard time for its entire network. In 1847, the Railway Clearing House recommended that all British railways adopt Greenwich Mean Time and use a 24-hour timetable. The GWR had already been using a 24-hour clock internally; the 1847 recommendation extended it across the industry.
Why railways, not armies, made it global
The innovation was not the 24-hour format itself. Astronomers and navigators had used it for decades. What the railways did was prove that the format could work at scale for public schedules. By 1848, most British stations had clocks with both 12-hour faces and 24-hour dials. The famous "London time" controversy, should public clocks run on local time or railway time, was settled in favor of the railway.
Canadian Pacific Railway follows
The Canadian Pacific Railway followed suit, adopting 24-hour time by 1886. The pattern repeated across Europe and Asia: wherever railways ran, 24-hour time followed. It was not military ambition but the mundane need to coordinate train movements across long distances that made the 24-hour clock a global standard.
Military Adoption: US Navy 1920, US Army 1942
The United States military came late to the 24-hour clock. Through World War I, American forces used the same 12-hour system as civilians. The Navy changed course in 1920, adopting 24-hour time for all official communications. The Army held out for another two decades.
Why the Navy moved first
Why the delay? The Army's resistance was cultural. Officers trained in the 12-hour system saw no compelling reason to change, and the peacetime Army had little reason to challenge convention. The Navy, by contrast, operated ships where a misread "2 AM" for "2 PM" could mean a missed rendezvous with a fleet. Naval officers had adopted the 24-hour system informally as early as the 1890s; the 1920 order simply formalized existing practice.
Pearl Harbor forces the Army's hand
The Army finally followed in 1942, just months after Pearl Harbor. The catalyst was not doctrine but necessity. With American forces deploying across every time zone on Earth, the cost of AM/PM errors had become unacceptable. A supply convoy ordered to depart at "8:00" might sail at 8 AM when the commanding officer meant 8 PM, or vice versa. The military could not fight a global war on a clock that left critical orders ambiguous.
WWII: When AM/PM Errors Became Operationally Dangerous
World War II is where the 24-hour clock proved its worth under fire. The military needed to coordinate airstrikes, naval bombardments, and infantry assaults across multiple time zones simultaneously. A bombing raid scheduled for "6:00" required absolute clarity about whether that meant 0600 or 1800. The difference was not academic.
The spoken convention is born
The spoken convention developed during this period. "Zero six hundred hours" replaced "six o'clock in the morning" because radio transmissions could garble "six" and "sixteen" or drop the "AM" suffix. The military also adopted the letter "Z" for Zulu time (UTC+0) to coordinate operations across all zones simultaneously. A pilot flying from Hawaii to Australia needed to know both local time and Zulu time for every phase of the mission.
Errors that got people killed
The errors that drove the 1942 Army adoption were not hypothetical. After-action reports from North Africa and the Pacific documented missed attacks, misdirected supply convoys, and misidentified rendezvous points, all traced to AM/PM confusion. The military did not adopt 24-hour time because it was elegant or traditional. It adopted it because the alternative killed people.
NATO Standardization and STANAGs in the 1950s
After WWII, the North Atlantic Treaty Organization faced a coordination problem. Its members used different time formats: the US and UK had military 24-hour time, but France and other European allies had their own conventions. A standardized system was needed for joint operations.
What the STANAGs actually codified
NATO's solution was the Standardization Agreement, or STANAG. These documents define everything from ammunition calibers to radio procedures. The 24-hour clock was codified in the STANAG series covering military timekeeping and date-time group formats.
The lettered zones: A through Z, skipping J
The STANAGs did more than mandate a format. They established the lettered military time zones (A through Z, skipping J) as a compact way to designate UTC offsets. Alpha is UTC+1, Bravo is UTC+2, and so on through Zulu at UTC+0. J (Juliett) was reserved for the observer's local time. These letters appear in radio communications, operational orders, and situation reports. They are not a formal international standard; that role belongs to ISO 8601. But they remain the operational language of allied forces.
ICAO and the Chicago Convention: Aviation Goes 24-Hour
Aviation adopted 24-hour time not by choice but by treaty. The 1944 Chicago Convention established the International Civil Aviation Organization (ICAO) to standardize international flight operations. Among its earliest mandates was the use of 24-hour time for all flight plans, air traffic control clearances, and NOTAMs (Notices to Air Missions).
Why a treaty was necessary
The reasoning was identical to the military's. A flight departing at "2:00" needs to be unambiguous when it crosses multiple time zones. The Chicago Convention made 24-hour time the default for international aviation, and ICAO Annexes have maintained that requirement ever since.
How tickets show the system at work
Today, every flight plan filed worldwide uses 24-hour time. Airline tickets show departure and arrival times in local 24-hour format. A ticket reading "Depart 2230 Arrive 0650+1" means a 10:30 PM departure arriving at 6:50 AM the next day. The "+1" eliminates the need to ask "which day?"
ISO 8601: The International Standard (1988)
The International Organization for Standardization published ISO 8601 in 1988, formalizing what railways and militaries had practiced for over a century. The standard specifies that times be written as hh:mm using a 24-hour clock, with optional seconds and fractional seconds.
Midnight: 00:00 or 24:00?
ISO 8601 also settled a long-standing ambiguity: how to represent midnight. The standard allows both 00:00 (the start of a day) and 24:00 (the end of a day), but specifies that 00:00 is preferred. This matters more than it might seem. A deadline of "24:00" on December 31 could mean the start of January 1 or the end of December 31. ISO 8601's preference for 00:00 removes the ambiguity.
Revisions that left the core untouched
The standard has been revised multiple times, but its core time representation has not changed. The 24-hour clock was already universal in computing, aviation, and the military. ISO 8601 made it the default for every context where clarity matters more than tradition.
Emergency Medicine: The 1970s-80s Shift After Malpractice Cases
The most recent major adoption of 24-hour time came in an unexpected place: hospitals. Through the 1960s, most American hospitals charted medications using 12-hour time with AM/PM suffixes. The system worked until it failed, and when it failed, patients died.
Midnight dosing and the insulin problem
The turning point was a series of malpractice cases in the 1970s and early 1980s involving midnight medication errors. A nurse charting "12:00 AM" might mean noon or midnight, depending on the day and the writer. A dose of insulin given at 12:00 AM instead of 12:00 PM could cause severe hypoglycemia. A blood thinner given at the wrong time could cause a fatal bleed.
The Joint Commission responds
The Joint Commission (then JCAHO) responded by recommending 24-hour charting for all medication administration records. The shift accelerated through the 1980s as hospitals adopted electronic health records. Today, virtually every American hospital charts medications in 24-hour time, and the practice is universal in countries that already used the 24-hour clock.
The same lesson, learned twice
The lesson from emergency medicine is that 24-hour time is not about military discipline or aviation precision. It is about reducing the human cost of ambiguity. The military learned this in combat; hospitals learned it in courtrooms. Both arrived at the same conclusion: when a mistake can kill, you eliminate the possibility of the mistake.
Why Military Time Persists
The 24-hour clock is not a perfect system. It requires adjustment from those raised on 12-hour time, and the "hundred hours" spoken convention can be confusing to newcomers. But its persistence across military, aviation, computing, and medicine is not accidental.
Every adoption of 24-hour time in history followed the same pattern: a crisis of ambiguity. Railways needed to coordinate trains across time zones. Navies needed to coordinate ships across oceans. Hospitals needed to coordinate medications across shifts. Each time, the 24-hour clock solved the problem that AM/PM could not.
The format is not going away. It is built into the operating systems of every computer, the flight plans of every aircraft, and the medication records of every hospital. The question is not whether you should learn it, but when you will need it. If you work in any field where a misread time can cost money, cause injury, or end a life, the 24-hour clock is not optional. It is the difference between "meet at 2" and "meet at 1400", and only one of those is a precise instruction.