Age and Duration Labels in NOTAM Cards: Freshness at a Glance
2/12/2026
When you're triaging many NOTAMs, time context matters as much as content. We added Age and Duration attributes so you can quickly see how fresh a NOTAM is and how long it is expected to affect operations.
This improvement was built thanks to great feedback from our beta testers. Their day-to-day operational input helped us tune these labels for fast scanning in real-world workflows.
Where these labels appear
- In list cards (in NOTAM airports pages), the Age label is shown as a compact badge for rapid scanning.
- In detail view (in NOTAM details pages), Age and Duration are shown together with extra context.
New sorting rules
We also updated sorting labels and behavior to make ordering clearer.
"Most recent" is now "Latest Effective"
What used to be called Most recent is now labeled Latest Effective.
This reflects the real behavior: sorting by effective start time, newest first.
New "Latest Issued" option
We also added Latest Issued, which sorts by NOTAM issue time (issued_at), newest first.
Use this when you want to track newly published NOTAMs, regardless of when they become effective.
Sorting modes
| Sort option | Rule |
|---|---|
| Latest Effective | Sort by effective start timestamp (descending) |
| Latest Issued | Sort by issue timestamp (issued_at, descending) |
| Category | Sort by category hierarchy order, then subcategory order |
| Importance | Sort by affected-element impact priority (Pro) - read how it works |
Important behavior
- Before any selected sort is applied, list ordering first prioritizes NOTAMs active in your selected time range.
- This means active NOTAMs surface first, then each group follows the selected sorting mode.
Age label rules
Age is calculated from issued_at to "now".
| Label | Rule |
|---|---|
| FRESH | < 24 hours |
| RECENT | >= 24 hours and < 14 days |
| AGING | >= 14 days and < 90 days |
| OLD | >= 90 days and <= 12 months |
| VERY OLD | > 12 months |
Duration label rules
Duration is calculated from startdate to enddate, unless a schedule exists (see cumulative duration below).
| Label | Rule | Detail text example |
|---|---|---|
| VERY SHORT | < 24 hours | 6 hours |
| SHORT | >= 1 day and < 7 days | 3 days |
| (no label) | >= 7 days and < 90 days | 45 days / 2 months |
| LONG | >= 90 days and <= 180 days | 4 months |
| VERY LONG | > 180 days | 9 months |
| PERMANENT | PERM NOTAM | no duration detail |
If the NOTAM end time is estimated, the badge appends EST to the duration detail.
Cumulative duration (aggregated)
Some NOTAMs are not continuously active. They may have active windows from schedule interpretation. In those cases, Notamify calculates cumulative active time.
When this path is used, the duration badge adds the aggregated prefix (for example: Duration: SHORT aggregated 3 days).
This gives a more operationally accurate view for NOTAMs active in discrete windows.
Built with beta feedback
This feature started with a suggestion from one of our beta users, who asked for faster freshness and timing cues during high-volume NOTAM review. That single piece of practical feedback helped shape this release.
Want to have direct impact on our development and what we build next? Join our beta test program.
Read more...
Watcher API Is Live: Real-Time NOTAM Shipments to Webhook or Email
3/5/2026
Notamify Watcher API is now live with webhook or email delivery, a 2-3 minute delivery target, and production hardening from a 3-month beta.
Latest Product Updates: IATA Search, Smarter Briefings, Better Timelines
2/22/2026
Based on user feedback, we shipped IATA search support plus improvements in Flight Briefings and NOTAM Timeline.
Notamify Alerts: Get Notified When Critical NOTAMs Are Issued
1/31/2026
Set up smart email alerts for runway closures, fuel outages, and restricted airspace. Filter by category, affected elements, and time applicability. Built for Operations Control Centers.
QCodes are now available in API! ... and why we don't like them
1/21/2026
QCodes are now available in Notamify API responses and filtering, including Watcher API. Learn why we've added them despite their limitations, and why Atomic Elements remains our recommended approach.