How to Write and Read a Military Date-Time Group (DTG)
A misunderstood time can end a career. It can start a war. The DTG exists to make that impossible. It is not a convention. It is a precision instrument designed to make the instant of an event unmistakable across continents, languages, and radio static. A correctly written DTG removes every scrap of ambiguity from the question "when?"
The format looks like this: 291800ZSEP26. That string tells you the 29th day of the month, 1800 hours (6:00 PM), Zulu time, in September, in the year 2026. Learn to parse the components and you can read any DTG on sight.
Day, Time, Zone, Month, Year: The Unbreakable Order
The DTG follows a strict sequence. Memorize it: Day, Time, Zone, Month, Year.
- Day (Two Digits): The day of the month, from 01 to 31. Always two digits. The 5th is "05," never "5."
- Time (Four Digits): The time in 24-hour format, from 0000 to 2359. No colon, no AM, no PM. 3:45 PM is "1545."
- Zone Letter (One Character): A single letter from A to Z (skipping J) that indicates the UTC offset. Z is Zulu (UTC+0), the default for most operations. J is Juliett, the observer's local time. The letter makes the time unambiguous.
- Month (Three Letters): The first three letters of the month, capitalized. JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC.
- Year (Two Digits): The last two digits of the year. 2026 is "26." Optional in some contexts, mandatory in formal logs and any document read after the new year.
Dissect 291800ZSEP26
Take the example apart.
- 29: The day. The 29th.
- 1800: The time. 1800 hours, which is 6:00 PM.
- Z: The zone letter. Zulu, meaning UTC+0.
- SEP: The month. September.
- 26: The year. 2026.
Read it left to right, component by component: 1800 Zulu on 29 September 2026. The order is fixed. The first two digits are always the day, the next four always the time. There is no other way.
When to Omit the Year
In a log that spans a single day, the year is clutter. In a five-year plan, the year is survival.
Omit the year in a short, time-sensitive message within a current operation. Coordinating a convoy that leaves in two hours? "291800ZSEP" is enough. Everyone knows the year.
Include the year in a formal report, a long-range plan, a maintenance schedule lasting more than a year, or any archived document. A document dated "15JAN" is useless on 1 February. It is a liability on 1 January next year. When in doubt, add the year. One extra character costs nothing. A misplaced date costs everything.
Where the DTG Appears
The DTG is the common language of the entire defense apparatus.
- Military Logs: Stamp every entry in a unit's journal or a ship's log with a DTG. This creates a legal record. If there is a dispute, the DTG is the first piece of evidence.
- Radio Communications: Spell out the DTG over a noisy radio. Do not say "two nine one eight zero zero zulu." Say "Two Niner, One Eight, Zero Zero, Zulu, Sierra Echo Papa Tango." The letters and numbers are chosen to be distinct over static.
- Operational Reports: Begin every SITREP and OPREP with the DTG of the report's creation. This tells the chain of command exactly how current the information is.
Errors That Break a DTG
The DTG is simple. It is not immune to error.
The wrong zone letter. The most dangerous mistake. Forgetting the Z or using a local zone letter when you mean Zulu shifts an operation by hours. Double-check the zone letter. If unsure, use Z.
The month mix-up. Writing "09" for September is wrong. The DTG uses letters. "SEP" is September. "09" is the ninth day of an unspecified month. This mistake can cause a 21-day error.
The day/time transposition. Putting the time before the day is incorrect. Day comes first. Always.
Midnight confusion. Use 0000 for the start of a day. Use 2400 only to indicate the exact end of a period, like closing out a log at midnight. For midnight on 1 January, write "010000ZJAN26," not "012400ZJAN26."
DTG vs ISO 8601
The military is not the only organization that needs unambiguous timestamps. The international civilian standard, ISO 8601, solves the same problem differently.
- Military DTG:
291800ZSEP26 - ISO 8601:
2026-09-29T18:00:00Z
ISO 8601 is built for computers and international trade. It sorts by year, then month, then day. It uses a "T" to separate date from time. The military format is built for human voice and paper forms. It puts the day first because that is how military personnel think about immediate time: "What day? The 29th. What time? 1800."
Writing software? Use ISO 8601. Writing an operations order? Use the DTG. The DTG is optimized for voice transmission and speed. ISO 8601 is optimized for lexical sorting and parsing. Both are correct. They are built for different environments.