Aviation Relations
Six Notices on One Unit
Half the equipment that goes out at a small airport goes out again. One notice is a fact. A run of them is a pattern, and almost nobody reads the run.
Teddy Cooper
10/6/20264 min read
Quick Answer
Since mid-July, about half the airport-owned equipment that posted a NOTAM at 83 small airports posted again, and one in four posted three or more times. A single notice tells you what is out today. It does not tell you whether the unit has been down the whole time, keeps failing and recovering, or fails after weather. Those are three different problems with three different fixes. Laying one unit's notices on a calendar, with the weather beside them, shows which one you have. If a unit on your field has posted more than twice since summer, start there.
One notice says it is out. Six notices on the same unit say something else.
Every airport knows how to read one NOTAM. The PAPI on 27 is out of service. The localizer is unmonitored. The weather station is not reporting. One notice, one fact, and the field goes on.
The second notice on that same unit gets read the same way, and so does the fourth, and the sixth. Each one gets issued, gets cancelled, and the next one starts the story over. A unit can be on its sixth notice in ten weeks and still be handled as if it were on its first.
What the Summer's Notices Say
Since mid-July, I have been reading the published notices on the equipment that 83 small airports carry themselves. That means PAPIs and VASIs, runway end lights, localizers and glideslopes, DMEs, and weather stations. Procedure paperwork is left out. Only equipment conditions count, and one notice number is one notice.
Across those fields, 286 pieces of equipment posted a condition at least once. About half posted again. One in four posted three or more times. Seventeen posted six times or more. Eight of ten fields have at least one unit that posted more than once. The typical notice stayed up about five days from the day it posted to the day it cleared.
Half the units that go out go out again. That isn't a small-airport failing or anyone's fault. Equipment that lives outdoors and runs all night does this. But it means the single notice, the one everybody reads, tells you the least.
A Notice Is a Fact. A Run Is a Pattern.
Reading the pattern takes five steps and a calendar.
Count the notice numbers on one unit. Count the unit, not the field or the runway. The PAPI on one end is a different story from the PAPI on the other end, even when the same technician fixes both.
Lay the notices on a calendar, with the date each one posted and the date it cleared. Six notices in ten weeks look very different, drawn out, than they do in a list.
Look at the gaps. The days clear between notices tell you more than the outages do. Two days clear and then out again is one kind of unit. Three weeks clear is another.
Look at the spans. Five days up is typical. One notice that stays up five weeks is a different problem from five notices that each stayed up a day.
Put the weather beside it, for the same weeks, from the nearest station. Most of the time weather doesn't explain the outage, and that's the point. The calendar with the weather on it lets you rule weather in or out instead of guessing.
Three Shapes
Draw enough of these and three shapes keep coming back.
The first is one long outage re-issued under new numbers. The notice posts, hits its expiration, gets re-issued, and hits it again. Six notices, no gaps, one outage, and the unit has been down the whole time. That's a parts problem or a scheduling problem. The conversation is about a date: when the part arrives, when the technician will be in the field, and whether anyone needs to know in the meantime that this is a wait and not a mystery.
The second is short outages with clear days between them. Out for a day, clear for a week, out for two days, clear for ten. That's an intermittent fault, the kind that's fine every time somebody drives out to look. The light is on, the monitor shows green, and the technician finds nothing because there's nothing to find that afternoon. This conversation isn't about a date. It's about a log. What time did it drop? What had the weather been doing the night before? An intermittent fault gets found by the pattern, or it doesn't get found.
The third is outages that land after weather. A storm Tuesday, a notice Wednesday. A week of heat, then the regulator trips. The part looks like the problem, but the installation is. Usually it's a cabinet that takes water, a conduit that floods, or a connection that expands and contracts until it opens. Replacing the part fixes it until the next storm. That conversation is about the installation, and it's a different person at the table.
Same unit, three shapes, and a different conversation for each. The count alone, six notices, can't tell you which one you're in. Only the calendar can.
Why Nobody Draws the Calendar
Nobody's job covers the set. The technician has the unit in front of them today. The notice tells pilots what's out right now. The manager has everything else. Each notice is complete on its own, and the system that publishes them doesn't keep score. A unit's summer record exists, but in pieces, and no one is assigned to them.
So the run goes unread. The technician gets called out the sixth time the same way as the first. The board hears "the PAPI was out again," because that's all anyone wrote down. The conversation that would actually change something never quite starts, because the evidence for it was never in one place.
The Habit
The fix is a page. One unit, one calendar, every notice on it with its dates, and the weather in a line underneath. Keep it where the next person can find it. It takes about fifteen minutes a month to update.
This is for airports that carry their own lights and navaids. If the FAA maintains yours, the pattern still exists. It's just on someone else's calendar, and it's still worth knowing which shape your unit is in when you pick up the phone.
Six notices on one unit are not six facts. They are one story, told six times, to nobody in particular.
© 2026. All rights reserved.
Need to know:
All consulting activity conducted by Aviation Relations is in a personal capacity, independent of any federal employment. Content is based on publicly available information and does not represent FAA policy, positions, or endorsements.
Aviation Relations does not provide Part 171 equipment compliance consulting or services. Work is conducted using personal time and resources.