Military Airfields / NOTAMs

NOTAMs

The live FAA feed scoped to your airfield, with expiring-NOTAM alerts.

The problem

A NOTAM is only useful if you see it before it matters

The FAA feed is public and current, but it isn't scoped to remind anyone of anything. A NOTAM about to expire for your airfield looks like any other line in a national feed unless someone happens to be watching for it, and nobody has time to re-read the same feed all day waiting for a countdown.

And when a NOTAM needs to go into a briefing or a record, retyping it from the feed is its own chance to get a character wrong in something that has to be exact.

How it works

The live feed, scoped and watched for you

  1. 01

    Your airfield's NOTAMs, not the whole national feed

    Glidepath pulls the live FAA feed scoped to your airfield's ICAO: the same source, filtered down to what's actually yours to track.

  2. 02

    A 24-hour window, watched for you

    Anything closing out within 24 hours shows on the list and counts on the sidebar, so an expiration surfaces well before it becomes a problem.

  3. 03

    Refreshed when it needs to be

    The feed pulls on load and refreshes on demand with a manual button, so there's no separate step to go check the source yourself.

  4. 04

    A clean register, out as a PDF

    Export the current, filtered list to a PDF (number, type, status, text, and both dates) and send it by email straight from the module.

NOTAMs feed for a demo airfield
The NOTAMs feed for a demo airfield: an FAA Feed banner for KDMO shows a live indicator and last-refresh time above four active NOTAMs (a taxiway closure, an obstruction crane near the RWY 01 approach, a fuel outage window, and a runway-adjacent mowing notice), filterable by All, FAA, LOCAL, Active, or Expired, with Export PDF and email actions above the search bar.

The benefit

What it automates

Scoped to your airfield, not a national list

Every NOTAM shown is pulled live and filtered to your ICAO, so nobody scans a national feed looking for the ones that are actually theirs.

An expiring NOTAM doesn't depend on memory

The 24-hour warning shows on the list and on the sidebar count, so a NOTAM closing out doesn't rely on somebody re-checking the feed that day.

The register is a byproduct, not a rebuild

Exporting the current list to a PDF pulls directly from the live feed. Nothing gets retyped to produce the record.

Related

Works alongside

FAQ

Straight answers

Can I create or edit a NOTAM in Glidepath?

No. Glidepath doesn't originate NOTAMs. It pulls the live FAA feed scoped to your airfield and adds alerting and export on top of it; a NOTAM itself is still issued through the normal FAA process.

How do I know a NOTAM is about to expire?

Anything closing out within 24 hours is flagged on the list and counted on the sidebar, so it surfaces without re-reading the whole feed.

How current is the feed?

It pulls fresh on page load and refreshes on demand with a manual button, so there's no separate step to go check the source.

Can I export the list for a briefing or a record?

Yes. Export the current, filtered list to a PDF register, or send it by email straight from the module.