FAA Airport Conditions: NOTAMs, Runway Reports, and Status Tools

Every flight you plan starts with one stubborn question — what's actually happening at the airport right now? Weather looks fine on the surface. The TAF reads clean. But you still don't know if the runway is half-closed for maintenance, whether braking action just dropped to medium-poor, or if a ground stop is brewing because the tower lost its primary radar feed. That's where FAA airport conditions come in. They're the layered set of reports, advisories, and live data feeds that tell you the real story behind a destination — not the marketing version, the operational one.

This guide walks through how the FAA reports airport conditions, what NOTAMs actually mean (and how to read them without losing your mind), how runway and taxiway surface assessments work using the RwyCC 0-6 scale, and which tools — ASOS, AWOS, ATIS, the FAA NOTAM Search, and the Operational Information System — give you the picture you need. If you fly, dispatch, study for the FAA written, or just want to stop pretending you understand that wall of capital letters at the bottom of a briefing, you're in the right place.

A quick note on scope before we dig in. The FAA system covers civilian operations in the United States and US territories. International airports use ICAO conventions that overlap heavily but aren't identical — different NOTAM keywords, different runway condition reporting standards, different timing conventions. If you fly internationally, learn both. If you fly domestically, the FAA framework is what you live in day to day.

Let's start with the framework. The FAA doesn't lump everything into one neat report — it splits airport conditions across several official channels, each with its own purpose. NOTAMs (Notices to Air Missions) cover anything temporary or unusual: closed taxiways, unlit obstacles, lights out, runway shortening, GPS interference, and a hundred other things.

ATIS, the Automatic Terminal Information Service, broadcasts the steady-state stuff — active runway, current weather, approach in use. ASOS and AWOS handle automated weather observations, updating every minute or so. And then you've got SNOWTAMs, field condition reports (FICONs), and the Operational Information System (OIS) for ground delay programs and airspace flow restrictions.

Here's the part people miss. These aren't redundant. Each one fills a gap the others can't. ATIS won't tell you a taxiway is closed. NOTAMs won't tell you the wind. ASOS won't tell you the runway is contaminated with slush. You need to pull from all of them — and the FAA expects you to. Skipping a NOTAM check isn't just sloppy, it's a regulatory issue under FAR 91.103, which requires pilots to become familiar with all available information concerning a flight before departure. That's not a suggestion. That's the rule.

There's also a historical reason for the fragmentation. Each of these systems grew up at different times to solve different problems. ATIS came along to reduce frequency congestion when controllers were tired of repeating the same wind and altimeter twenty times an hour. ASOS replaced human observers at airports that couldn't justify staffed weather stations.

NOTAMs evolved from teletype messages exchanged between airports in the 1940s. The FAA has tried over the years to consolidate them, but every attempt runs into operational reality — the people using each system would rather have it dedicated than blended into a one-size-fits-all firehose. So the layered approach stays.

So how do you actually read a NOTAM? They look terrible. All caps, abbreviated to within an inch of comprehension, and full of codes that haven't changed since the 1970s. But once you know the structure, they crack open quickly. A typical NOTAM starts with the airport identifier, then a series of keywords — RWY for runway, TWY for taxiway, OBST for obstacle, NAV for navigation aid, COM for communications, AD for aerodrome general. After that comes the actual content and the effective time window in UTC.

Example: "!ORD 12/345 ORD RWY 10L/28R CLSD 2401151200-2401151800." Translation — at Chicago O'Hare, runway 10L/28R is closed from 1200 UTC to 1800 UTC on January 15, 2024. That's it. The cryptic part is just shorthand. The FAA NOTAM Search at notams.aim.faa.gov lets you pull these by airport, by area, or by route. You can filter by type, time, and even draw a graphical box on a map. It's free, it's official, and it's the source of truth — third-party apps pull from this same database, just with prettier formatting.

Common abbreviations worth memorizing — CLSD for closed, U/S for unserviceable, WIP for work in progress, AUTH for authorized, EXC for except, BTN for between, FT for feet, AGL for above ground level. You'll also see latitude/longitude in unusual formats and frequencies given without decimal points. Once your brain learns to scan rather than read every NOTAM word by word, you'll get through a thick briefing in a fraction of the time. The trick is volume — read enough of them and the patterns become automatic.

The runway condition piece deserves its own section because the FAA overhauled how it's reported back in October 2016, and a lot of older training material still teaches the obsolete system. Forget the old Mu values and the descriptive-only reports. The current standard is the Runway Condition Assessment Matrix, or RCAM, and it produces a single number called the Runway Condition Code — RwyCC — on a scale from 0 to 6.

Six means dry. Five means wet, frost, or slush less than 1/8 inch deep. Four means slippery when wet, or compacted snow at outside temperatures below -15°C. Three means wet snow or slush 1/8 inch or deeper, or dry snow more than 1/8 inch. Two means standing water or slush in measurable amounts, or compacted snow at warmer temperatures.

One means ice, and zero means wet ice — which, if you've ever driven on it, you know is about the most slippery surface humans have invented words for. Airports report a RwyCC for each third of the runway: touchdown, midpoint, and rollout. So a single runway might be reported as 5/4/3 — better at the touchdown end, deteriorating toward the rollout.

Why split the runway into thirds? Because contamination rarely covers a runway evenly. Plowed strips, drainage patterns, and sun angle all create uneven surfaces. The touchdown zone might be relatively clean while the far end still has slush. Aircraft performance charts let you account for each segment separately, which can mean the difference between a legal landing and a diversion. Once you start reading FICONs this way, the asymmetric numbers actually make sense — they're telling you exactly where on the runway your braking is going to matter most.

Beyond the standard reports, you'll occasionally run into something that grounds an entire region — a Ground Delay Program, or GDP. These are issued by the FAA's Air Traffic Control System Command Center when arrival demand at an airport is projected to exceed acceptance rate. Instead of sending everyone airborne to hold, the FAA holds aircraft on the ground at their departure airports and meters them into the destination on a controlled schedule. You'll see this most often at slot-constrained airports like Newark, San Francisco, and LaGuardia, especially during low ceilings or strong crosswinds.

The Operational Information System — fly.faa.gov — is the public window into all this. You can pull current ground stops, ground delays, airspace flow programs, and general airport status updates. It refreshes constantly throughout the day. If you've ever wondered why a flight from Phoenix to Boston is delayed two hours when the weather looks fine at both ends, the answer is usually buried somewhere in the OIS — maybe a ground stop in Atlanta cascading northeast, or a flow program through the Northeast Corridor metering everyone heading to BOS.

Ground stops are different from ground delays — worth knowing the distinction. A ground stop is a hard halt. No departures to the affected airport, period, until it lifts. A ground delay program assigns each flight a controlled time of departure to smooth traffic. Both are managed by traffic management coordinators, both publish to the OIS, and both can change with little notice. Smart dispatchers refresh the page every fifteen to thirty minutes during active weather days because a ground stop announced mid-taxi can save fuel and crew duty time if you catch it before pushback.

If you're studying for an FAA written exam — Private, Instrument, Commercial, ATP — questions on airport conditions show up constantly. They're easy points if you know the framework, and easy losses if you don't. The exam writers love testing the difference between NOTAM types, the meaning of specific RwyCC values, what ASOS reports versus AWOS, and which agency issues what. They also love pulling small details out of long NOTAMs and asking you to interpret them under time pressure.

Here's a practical checklist for any preflight, whether you're taking off in a Cessna 152 or dispatching a 777. Run through these every time and you'll catch the things that matter.

Now, a word about technology and the gap between what's official and what's convenient. ForeFlight, Garmin Pilot, SkyVector, and most EFB apps pull NOTAMs and weather from the FAA's data streams. They're great for usability, but they're not always immediate. The FAA's own systems are sometimes seconds behind the actual issuance, and third-party apps can lag a few minutes more. For most operations that's fine. For commercial dispatch, military, or any flight where the difference between an open and closed runway matters in the next hour, go to the source.

There's also a real tension between the legacy NOTAM format and modern usability. The FAA has been working on the ICAO-compliant NOTAM format and a system called FNS-NEM (Federal NOTAM System NOTAM Entry Module) that produces machine-readable output. You'll see this transition referenced in some study materials and not in others — which is fine, because both formats coexist for now. Read the words, ignore the formatting, and you'll be ahead of pilots who only know one style.

The January 2023 nationwide ground stop — caused by a corrupted file in the NOTAM system — was a reminder that even the official source can fail. The FAA halted all departures across the country for about ninety minutes that morning while the system was rebuilt from backups. That event accelerated modernization work and pushed redundancy improvements that should make a repeat far less likely. But it also highlighted just how central the NOTAM system is to US aviation — when it goes down, nothing flies.

One last point worth driving home — weather is connected to conditions, but the two aren't the same thing. Weather is what the atmosphere is doing. Conditions are how the airport is responding. A 200-foot ceiling at JFK doesn't automatically mean delays. JFK has CAT III ILS on multiple runways and operates routinely in those conditions.

But a 200-foot ceiling combined with a NOTAM that the CAT III equipment is out of service? Now you've got a real problem. That kind of compound assessment — weather plus equipment plus runway plus traffic — is what separates a competent briefing from a checkbox briefing.

This is also where the FAA written exam gets interesting. It rarely asks you to memorize raw weather. It asks you to reason through a scenario. Given this METAR, this NOTAM, and this approach plate, can you legally accept the approach? Can you legally land? What's your minimum runway requirement based on the FICON report? These questions reward people who actually understand how the pieces fit together, not just people who memorized definitions. If your study plan is heavy on flashcards and light on scenarios, fix that before test day.

Another piece often overlooked — pilot reports, or PIREPs. They're not technically airport conditions, but they're invaluable context. A PIREP from the previous arrival saying braking action was poor on the rollout is sometimes more useful than the official FICON, because it's a real aircraft, real weight, real touchdown. Controllers solicit them constantly during marginal weather. If you receive an unsolicited braking action report or icing report after your own landing, file one. The next crew might literally avoid an excursion because you took thirty seconds to share what you saw.

The bottom line — FAA airport conditions aren't a single product. They're a system, and the system rewards pilots and dispatchers who treat it as such. Don't just read NOTAMs. Read them against the weather, against the equipment list, against your aircraft's performance numbers, and against the route structure. Don't just listen to ATIS. Listen for what's missing — sometimes the absence of a remark is the most important information available. And don't trust a single source when three are available for free at your fingertips.

If you build that habit early, the FAA written becomes mostly common sense, and the operational stuff — the real flying — becomes far less stressful. You'll spot the bad situations before they trap you. You'll catch the runway closure your buddy missed. And eventually, you'll be the pilot or dispatcher other people lean on when the picture gets ugly. That's worth a few extra minutes during preflight, every single time.

One closing thought. Aviation is full of acronyms and procedures that look like bureaucratic overhead until the day they save you. NOTAMs, FICONs, ATIS, OIS — they exist because someone, somewhere, learned the hard way that the information needed to be standardized. Respect the system, use it fully, and contribute back when you can with quality PIREPs.

That's how the network stays sharp for everyone who comes through the same airport tomorrow, next week, and twenty years from now. The pilots and dispatchers who get this — really get it — aren't the ones with the most hours or the fanciest ratings. They're the ones who treat every preflight like the conditions might actually matter. Because one day, they will.