TAF validity period: how to read DDHH/DDHH
The validity group sits right after the issue time and has the form DDHH/DDHH: start day and hour, then end day and hour, all in UTC. Subtract the start from the end to get the length. EU rules allow 9, 24 or 30 hours. The end hour 24 means midnight at the end of that day. In 0900/0924 the forecast runs for the whole 9th.
Key points
- DDHH/DDHH gives start day and hour, then end day and hour, in UTC; the end hour can be 24, never the start hour.
- EU rules allow routine TAFs of 9, 24 or 30 hours, filed not earlier than 1 hour before the validity starts.
- NWS TAFs are 24 hours, or 30 hours at airports on a designated list, issued four times a day.
- A newly issued TAF cancels the previous one for the same place, even if its validity starts later.

Where the validity group sits and what it contains
The validity group is the first time block after the airport identifier and the issue time. It has eight digits split by a slash, written DDHH/DDHH. The first four digits are the day of the month and the hour (UTC) at which the forecast starts. The last four digits are the day and hour at which it ends. Everything is in UTC, so there is no local time to convert, and no minutes: validity periods are always in whole hours.
Here is a constructed line, flagged as illustrative and not taken from any source, to show where the group sits:
TAF EDDF 111100Z 1112/1218 ...
The first group after TAF is the ICAO location indicator, 111100Z is the issue time (the 11th at 1100 UTC), and 1112/1218 is the validity: from the 11th at 1200 UTC to the 12th at 1800 UTC. If you want the full order of groups, the pillar page How to read a TAF walks through every element.
To get the length of the forecast, subtract the start from the end and remember the day change. The example above is 30 hours: 12 hours left on the 11th plus 18 hours on the 12th. The same arithmetic gives 9 hours for 3009/3018 and 24 hours for 0900/0924.
Permitted lengths: 9, 24 and 30 hours
The European rules in Commission Implementing Regulation (EU) 2017/373 (Annex V, Part-MET) state that the period of validity of a routine TAF shall be either 9, 24 or 30 hours. The same text says it shall be filed for transmission not earlier than 1 hour before the commencement of its period of validity. The regulation's own TAF template shows the validity group with the form nnnn/nnnn and uses 0812/0918 as one of its two examples, which is the 8th at 1200 UTC to the 9th at 1800 UTC, or 30 hours.
The United States does not use the 9 hour length for routine TAFs. The FAA Aeronautical Information Manual says NWS forecasts are valid for 24 or 30 hours and amended as required. NWS Instruction 10-813 adds that scheduled forecasts are 24 or 30 hours long, and that amended or delayed forecasts can be shorter. Which airports get the 30 hour length is defined in an appendix of that instruction, so you cannot tell from the airport identifier alone; you read it from the validity group itself.
Transport Canada gives a validity of up to 30 hours for its TAFs.
| Authority | Routine lengths | Source |
|---|---|---|
| EU (Part-MET) | 9, 24 or 30 hours | Regulation (EU) 2017/373 |
| United States (NWS) | 24 or 30 hours | NWS Instruction 10-813, AIM |
| Canada | up to a maximum of 30 hours | TC AIM MET 7.0 |
The hour 24 and the hour 00
The "24" in a validity group is the part that confuses most readers. NWS Instruction 10-813 gives both rules in one place. A forecast period that begins at midnight UTC is annotated as 00, and if the valid period's end time is midnight UTC, it is annotated as 24. The worked example in the instruction is a 00Z TAF issued on the 9th of the month, which has a valid period of 0900/0924.
Read that group literally. The start 0900 is the 9th at hour 00, which is the very beginning of the 9th. The end 0924 is the 9th at hour 24, which is the very end of the same 9th. The forecast therefore covers one whole calendar day, and the end date is the day that is finishing, not the next one. You will never see 0910/1000 for a forecast that ends at midnight; you would see 0910/0924.
The same instruction gives a 30 hour case: a 00Z TAF issued on the 11th for 30 hours has a valid period of 1100/1206. That is the 11th at 0000 UTC to the 12th at 0600 UTC, and the end hour is a normal hour of the next day because 0600 is not midnight.
The date-and-time convention matters again inside the TAF. A change group written FM100000 means 0000 UTC on the 10th, not 1000 UTC. The FAA Aeronautical Information Manual repeats this warning in the key to its sample TAF: users are cautioned to confirm the date and time, and FM 10 0000 is 0000Z on the 10th, not to be confused with 1000Z. The FM group page covers the six-digit format.
Issue schedule and the real moment a TAF starts
Scheduled NWS TAFs are issued four times daily, every six hours. NWS Instruction 10-813 lists the scheduled issuance times and what each one covers.
| Scheduled issuance (UTC) | 24 hour valid period (UTC) | End time for a 30 hour TAF (UTC) |
|---|---|---|
| 0000 | 0000 to 0000 | 0600 |
| 0600 | 0600 to 0600 | 1200 |
| 1200 | 1200 to 1200 | 1800 |
| 1800 | 1800 to 1800 | 0000 |
Some forecast offices also issue routine amendments three hours after the initial issuance, and the FAA Core 30 airports receive regularly scheduled amendments at three hour intervals. Their valid periods run to the end of the original forecast. For example, the instruction lists a 0300 UTC amendment valid from 0300 to 0000 UTC. The amendment logic is explained in TAF AMD, COR and CNL.
A TAF does not wait for its first validity hour. The instruction states that the issuance of a new TAF cancels any previous TAF for the same time and location, and gives this example: a forecast issued at 1720 UTC is valid immediately despite the validity period in the TAF starting at 1800 UTC. It also notes that a routine TAF may still be amended before the top of the hour, for example an 18Z TAF between 1720 and 1759 UTC.
Transport Canada takes the same view. A TAF is considered to be valid from the moment it is issued: its example is a TAF with an indicated period of validity from 1100Z to 2300Z that was issued at 1040Z, which is valid from 1040Z. According to the TC AIM, and it applies until it is amended, replaced or its validity ends.
The practical consequence is that you should never check only the validity group. Check the issue time too, and when you brief a flight, look for a newer TAF that might have replaced the one in your hand.
Reading a real 9 hour TAF
A new TAF replaces any previous one for the same place, as the NWS rule above says, so a validity group alone cannot tell you whether a TAF is still current. Always compare the issue time of what you hold with the latest one available.
Here is a real 9 hour example from the Met Office GetMet leaflet, which labels it a 9-hr TAF issued at 0800 Zulu on the 30th:
EGTE 300800Z 3009/3018 23010KT 9999 SCT010 BKN018 BECMG 3011/3014
6000 -RA BKN012 TEMPO 3014/3018 2000 DZ OVC004 =
The validity group 3009/3018 runs from 0900 to 1800 UTC on the 30th, so 9 hours. The TAF was issued at 0800, one hour before it starts, which matches the EU filing rule of not earlier than 1 hour before the validity begins. The Met Office decode of this example reads the group as valid from 0900 on the 30th to 1800 Zulu on the 30th.
Common mistakes with the validity group
- Reading
24as hour 00 of the following day. It is the end of the day that is finishing. - Assuming every TAF lasts 24 hours. Under EU rules the length can be 9, 24 or 30 hours, and amended TAFs can be shorter.
- Confusing the issue time
DDHHMMZ(six digits, with minutes) with the validity groupDDHH/DDHH(eight digits, whole hours). The first one is when the TAF was written, the second is when the forecast applies. - Treating the validity start as the moment the TAF becomes usable. In the United States and Canada, a TAF applies from issuance.
- Using a TAF whose end time has passed. When the validity ends and no new TAF is issued, there is no forecast for that airport.
To check a date and time of a group, the Zulu time converter helps. If you want a tool to split a TAF into its validity, base group and change groups, the TAF decoder does that,. The BECMG group page continues with the first change group you will find inside the validity period.
Method and limits
Every rule above comes from NWS Instruction 10-813, the consolidated text of Regulation (EU) 2017/373, the TC AIM MET section, the FAA Aeronautical Information Manual chapter 7 and the Met Office GetMet leaflet. The TAF line that begins with EDDF is constructed to show the position of the group and is not a real forecast. The NWS instruction also contains a table of issuance windows (for example for the 1800 UTC issuance) that is not reproduced here, except for the 1720 UTC case that the text quotes directly. The list of airports with 30 hour TAFs is in an appendix of NWS Instruction 10-813 that is not reproduced here either.
Training and reference only. For flight planning, always use official briefing sources (your national weather service, AIS or approved provider).
Frequently asked questions
What does 0900/0924 mean in a TAF?
It is a validity group: the forecast starts at 0000 UTC on the 9th (written 0900) and ends at midnight at the end of the 9th (written 0924). NWS Instruction 10-813 uses exactly this case, a 00Z TAF issued on the 9th, so the TAF covers 24 hours of one calendar day.
Why do some TAFs end at hour 24 instead of 00?
A period that ends at midnight UTC is written with hour 24 of the day that is ending, while a period that begins at midnight uses hour 00 of the new day. NWS Instruction 10-813 states both rules. That keeps the end date equal to the day on which the forecast actually finishes.
How long is a TAF valid?
Under the EU rules a routine TAF is valid for 9, 24 or 30 hours. NWS TAFs are valid for 24 or 30 hours, and Transport Canada states a maximum of 30 hours. Amended or delayed TAFs can be shorter, and a TAF stops applying as soon as a newer one is issued for the same airport.
Can a TAF be valid before its validity group starts?
Yes. NWS Instruction 10-813 gives the example of a forecast issued at 1720 UTC that is valid immediately although its validity group starts at 1800 UTC. Transport Canada also treats a TAF as valid from the moment it is issued. In the EU a TAF is filed not earlier than 1 hour before it starts.
Sources
- National Weather Service (2024). NWS Instruction 10-813, Terminal Aerodrome Forecasts (October 30, 2024)
- European Union (EUR-Lex) (2017). Commission Implementing Regulation (EU) 2017/373, Annex V (Part-MET), aerodrome forecasts and TAF template
- Transport Canada (2025). TC AIM, MET section 7.0 Aerodrome forecasts (TAFs)
- Federal Aviation Administration. Aeronautical Information Manual, chapter 7, section 1
- Met Office. GetMet: aerodrome forecast TAF decode