Others are potentially useful, but not essential for safe flight. Things like closed taxiways, nonavailability of services at an airport, etc.
And a very few are really critically important. Runway closures, correction to vital chart information, airspace changes, malfunctioning navigation aids.
The FAA's reaction to the NOTAM outage was probably the correct course of action. But make no mistake, the volume of spam NOTAMs combined with the lack of an easy way for a pilot to quickly sort for important NOTAMs makes us all less safe.
The system is in desperate need of some modernization, no argument there. The fact that there isn't a simple criticality filed with them that makes it easy to see what will actually impact flight planning (airspace closure / runway closure vs stupid chart updates) is insane.
I can’t say one way or the other, as I’m not a pilot, but that’s the argument I’d make to keep the system w/o priority levels.
Similarly, chart updates are very important if you're flying IFR. Going below minimums while in the soup ends... very badly. If somebody's changed the MEA/DA/MDA, you can bet I want to know.
NOTAMs do have keywords to tell you the subject (i.e. airport closure vs tower light), and most briefings will highlight the ones likely to be urgent.
(That said, I'd argue printing out all the tower notams in textual format is somewhat useless. The NEXTGEN FSS briefings are plotting them graphically now, which is an improvement.)
I noticed that when the day was long, and I was feeling tired and lazy it was a lot easier to find some excuse why not to run that day. This excuse was often the weather. But on the other hand I didn't want to say no matter the weather I must run, because that is obviously excessive. So I made up a simple "algorithm" to decide if the weather fits the minimums, and if it did I must go and run. And I choose to base it on the measurements from the METAR of the local airport.
(I also remember I was willing to skip running in case of anything “exciting” being reported. Like tornados, or sandstorms or vulcanic ash. Not that any of that was a real possibility.)
For folks who haven't seen what's in a METAR/TAF: https://www.faa.gov/air_traffic/weather/asos/ (By default, clicking a station gives you the abbreviated format; you can select the "decode" radio button and click "update" to translate it into English.)
Stopping takeoffs was absolutely the right move, since they couldn't handle the phone throughput.
You look at the closest available weather station and you look at the forecasts — human-authored (TAFs) and computer-autored (GFA/MOS). And when you arrive, you look outside at the actual conditions — the windsock, actual flight visibility, etc. If the conditions are worse than expected, you divert to your alternate.
That doesn't help a pilot plan ahead for conditions on their route or at their destination, though-- that's where METARs come in.
Per the source, 167 airport weather stations are not reporting correctly (either due to a highly unlikely concurrent fault with the stations, or more likely an issue with the system they report to).
Local weather is always used, but that's precisely what is unavailable right now.
If the tower is closed, or it's an untowered field, the system can run in automatic mode. In that case the radio broadcast gets updated every minute, much more frequently than METARs get updated (every hour).
We have mines being blasted to our north in temporarily restricted military airspace - lets just allow pilots to roll the dice?