INDUSTRY REFERENCE
Military Time in
Logistics & Transportation
Every major mode of freight — air, rail, sea, road — operates on 24-hour time. This is not a convention; it is a technical and regulatory requirement driven by the need to coordinate across time zones, satisfy federal record-keeping rules, and eliminate the scheduling errors that cost the industry billions of dollars annually.
The Operational Case
Why Global Logistics Requires 24-Hour Time
A shipment leaving a factory in Shenzhen at 2:00 PM local time will pass through a port in Hong Kong, load onto a vessel that crosses the international date line, arrive in Los Angeles, clear customs, transfer to a rail yard, and be delivered by a truck driver subject to federal hours-of-service regulations. Every handoff requires a timestamp that is unambiguous across all parties and jurisdictions.
The 12-hour clock makes this impossible at scale. When a vessel ETAs at "4:00" and the terminal gate closes at "4:00," the operations team cannot afford ambiguity about whether those are the same time. A missed vessel costs a shipper tens of thousands of dollars in detention, re-booking, and supply chain delays.
Twenty-four-hour time solves this by making all time expressions visually and numerically unambiguous. 0400 and 1600 look completely different. A scheduling system, a human dispatcher, and a customs document all read the same number and arrive at the same conclusion.
International coordination
Supply chains routinely span 10+ time zones. A single 24-hour format with UTC reference eliminates conversion errors at every handoff point.
Regulatory compliance
DOT Hours of Service, FRA railroad regulations, and IMO maritime rules all require 24-hour timestamp records. Non-compliance can result in operating authority revocation.
Just-in-time manufacturing
Automotive and electronics assembly lines operate on inbound delivery windows measured in 30-minute increments. An AM/PM error on a delivery appointment shuts down a production line.
Automated systems
EDI (Electronic Data Interchange) transaction sets, TMS and WMS platforms, and port community systems all store and transmit timestamps in 24-hour format.
Industry Reference
How Each Transport Sector Uses 24-Hour Time
| Industry | Example Format | Equivalent | System / Standard | Notes |
|---|---|---|---|---|
| Commercial Aviation | 1435 | 2:35 PM | IATA / ICAO 24-hour | All timetables, ATC, and flight ops use 24-hr time globally |
| Railroad (Class I) | 1435 | 2:35 PM | AAR standard 24-hr | Train orders, dispatcher logs, and crew scheduling all 24-hr |
| Maritime / Shipping | 1435Z | 2:35 PM UTC | Zulu / UTC | SOLAS and MARPOL require UTC logging; port times are local 24-hr |
| Trucking / HOS | 14:35 | 2:35 PM | DOT 24-hr | ELD devices record duty status changes in 24-hr local time |
| Air Cargo (IATA) | 1435 | 2:35 PM | IATA CASS/CARGO IMP | Airway bills and cargo manifests use 24-hr time |
| Port Operations | 1435 LT | 2:35 PM local | Local 24-hr | Vessel ETAs, berth schedules, and gate times are local 24-hr |
| Postal / Courier | 14:35 | 2:35 PM | Internal 24-hr | FedEx, UPS, DHL operations centers use 24-hr for sort schedules |
| Warehousing | 1435 | 2:35 PM | WMS 24-hr | Warehouse Management Systems timestamp picks and shipments in 24-hr |
Aviation
Airline Timetables & IATA Standards
Commercial aviation was one of the first industries to standardize on 24-hour time universally. The International Air Transport Association (IATA) and the International Civil Aviation Organization (ICAO) both mandate 24-hour time for all official documents, flight plans, and air traffic control communications worldwide.
Airline schedule databases — maintained in SSIM (Standard Schedules Information Manual) format — express all departure and arrival times in local 24-hour time. Every system that ingests airline schedules, from travel agency GDS platforms (Amadeus, Sabre, Travelport) to airport FIDS (Flight Information Display Systems), processes and displays times in 24-hour format natively, even when the consumer-facing display converts to 12-hour for US domestic audiences.
| Flight | From | To | Departs (24-hr) | Arrives (24-hr) | Departs (12-hr) | Arrives (12-hr) |
|---|---|---|---|---|---|---|
| AA 11 | JFK | LAX | 0830 | 1205 | 8:30 AM ET | 12:05 PM PT |
| DL 401 | ATL | LHR | 1730 | 0715+1 | 5:30 PM ET | 7:15 AM GMT (+1 day) |
| UA 857 | SFO | NRT | 1135 | 1500+1 | 11:35 AM PT | 3:00 PM JST (+1 day) |
The "+1" notation (e.g., 0715+1) indicates the arrival is the next calendar day. This is a standard SSIM convention and is only necessary because times are expressed in local time — if all times were UTC, the date arithmetic would be handled differently.
ATC uses Zulu time
While airline timetables use local 24-hour time, air traffic control communications are conducted in Zulu (UTC) time worldwide. When a pilot contacts approach control, all altitude clearances, expected approach times, and coordination with adjacent centers reference Zulu time — regardless of what the local clock reads.
Railroad Operations
Class I Railroad Dispatch & Scheduling
The seven Class I railroads in North America — BNSF, Union Pacific, CSX, Norfolk Southern, Canadian National, Canadian Pacific Kansas City, and Amtrak — all operate on 24-hour time. This has been standard practice since the early 20th century, when railroad companies needed to coordinate schedules across multiple time zones without telephone communication being available at every point.
Train dispatchers — who manage train movements across hundreds of miles of track from centralized dispatch centers — use 24-hour time for all train orders, track warrants, and movement authorities. The Federal Railroad Administration (FRA) requires that train handling records and accident/incident reports use 24-hour timestamps. FRA Form 6180.78 (Railroad Injury and Illness Summary) and related forms all specify 24-hour time fields.
| Train | Origin | Destination | Departure | ETA | Transit | Type |
|---|---|---|---|---|---|---|
| BNSF #KCLA | KC | LA | 0200 | 2300 | ~45 hrs | Intermodal |
| UP #LATHO | LA | Chicago | 1800 | 0600+2 | ~60 hrs | Auto rack |
| CSX #Q028 | Jacksonville | Cleveland | 2300 | 1400+1 | ~39 hrs | Mixed freight |
Railroad timetables use the "+1" and "+2" day convention for multi-day transits, identical to airline scheduling. A train departing at 2300 that arrives at 0600+2 takes approximately 31 hours.
Maritime Shipping
Port Operations & Vessel Scheduling
Maritime operations present a unique timekeeping challenge: a vessel at sea is in international waters where no local time zone applies. The International Maritime Organization (IMO) requires that ship logs — the Official Log Book maintained under SOLAS regulations — use UTC for all entries while at sea. When in port, local time is used for shore-side coordination, always in 24-hour format.
The Notice of Readiness (NOR) — the document a vessel tenders to signal it has arrived and is ready to load or discharge cargo — must include a 24-hour timestamp that triggers the commencement of laytime. Laytime is the contractually agreed period for loading/unloading, and demurrage (the penalty for exceeding it) accrues by the hour. Ambiguous timestamps in NOR documents are regularly litigated in maritime courts.
Vessel ETAs
Shipping lines publish vessel ETAs to port terminals and agents in 24-hour local time. A container terminal allocates berth slots in 2–4 hour windows based on these ETAs — a misread time means a missed berth and a costly anchorage delay.
AIS (Automatic Identification System)
All commercial vessels broadcast their position, speed, and heading via AIS. The AIS timestamp is UTC to the second, enabling coast guards, port authorities, and vessel traffic services to reconstruct vessel movements to the minute.
MARPOL fuel records
The Oil Record Book, Garbage Record Book, and Cargo Record Book required under MARPOL Annex I and V all use 24-hour UTC timestamps. These are inspected by port state control officers during port calls worldwide.
Charter party agreements
Standard charter party forms (GENCON, NYPE, Baltime) reference time in 24-hour format for all laytime, cancellation, and delivery clauses. Maritime arbitration panels expect all time evidence to be in 24-hour format.
Trucking & Road Freight
Hours of Service, ELD Devices & DOT Regulations
The Federal Motor Carrier Safety Administration (FMCSA) Hours of Service (HOS) regulations govern how many hours a commercial truck driver can operate. Under 49 CFR Part 395, property-carrying drivers are limited to 11 hours of driving in a 14-hour window, followed by a mandatory 10-hour off-duty period.
Since December 2019, the Electronic Logging Device (ELD) mandate requires most commercial motor vehicles to use certified ELDs that automatically record duty status changes. ELD data is stored in 24-hour format. When a roadside inspector from DOT or a state trooper requests the ELD log, it displays a 24-hour duty status grid — the same format used in paper logs for decades before the ELD mandate.
DOT Hours of Service — Key Times in 24-Hour Format
A driver who starts their driving window at 0600 must complete all driving by 2000 (the 14-hour limit) and may only drive until 1700 if they reach the 11-hour driving limit first. The 30-minute break must be taken before the 8th hour of driving time — in this example, by 1400 at the latest.
Carriers and drivers use 24-hour time in all trip planning and dispatch communication to avoid the catastrophic legal and safety consequences of an HOS violation.
Freight brokers, 3PLs (third-party logistics providers), and shippers all coordinate pickup and delivery appointments in 24-hour time. A load tender from a major shipper like Amazon, Walmart, or Procter & Gamble will specify a delivery appointment window such as 0600–0800 — never "6–8 AM" — because the TMS (Transportation Management System) transmits these appointments via EDI 204 (Motor Carrier Load Tender) in 24-hour format.
Warehousing & Supply Chain
Distribution Centers & Warehouse Operations
Modern distribution centers — whether operated by Amazon Fulfillment, FedEx Ground, UPS Supply Chain Solutions, or a 3PL — run multiple shifts around the clock. Shift schedules, inbound receiving appointments, outbound load departures, and pick-and-pack productivity metrics are all tracked in 24-hour time.
Warehouse Management Systems (WMS) from vendors including Manhattan Associates, Blue Yonder (JDA), SAP EWM, and Oracle WMS Cloud all store timestamps internally in 24-hour format (or UTC, then display local time). Cycle count schedules, labor management records, and carrier appointment scheduling systems all use 24-hour notation to prevent the double-booking and missed appointment problems that arise from AM/PM ambiguity.
Inbound receiving
Dock appointment slots are booked in 30–60 minute windows: 0600, 0630, 0700…
Outbound cutoffs
Carrier pickups have hard departure times: 1800 FedEx / 2000 UPS
Shift handoffs
Typical 3-shift warehouse: 0600 / 1400 / 2200
Express Parcel
FedEx, UPS & DHL Operations Centers
The express parcel networks — FedEx, UPS, and DHL — are among the most precisely timed logistics operations in the world. A FedEx Priority Overnight package picked up at 1700 must clear the hub sort facility, be loaded onto a feeder aircraft, flown to a regional hub, re-sorted, loaded on a delivery van, and arrive at the destination by 1030 the next business day.
FedEx operates the world's largest cargo airline by freight ton miles, with its Memphis "SuperHub" processing over 1.5 million packages per night. Hub sort operations run on precise 24-hour schedules: the "primary sort" runs from approximately 2300 to 0300, with feeder aircraft departing between 0300 and 0500 to reach destination cities before morning delivery routes begin.
Package tracking timestamps
Every scan event in a parcel carrier's tracking system is stored with a 24-hour timestamp in UTC, then displayed in the recipient's local time zone. When you see "Departed FedEx facility at 2:35 AM," the underlying data record reads 0235 UTC (or local, depending on the facility's time zone setting). International shipments crossing the date line or multiple time zones require UTC as the canonical time reference for all internal processing.