{"id":3709,"date":"2018-02-22T19:46:24","date_gmt":"2018-02-23T00:46:24","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=3709"},"modified":"2019-11-02T13:39:47","modified_gmt":"2019-11-02T17:39:47","slug":"heres-what-pilots-and-controllers-really-think-about-notams","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/heres-what-pilots-and-controllers-really-think-about-notams\/","title":{"rendered":"Here’s what pilots and controllers REALLY think about Notams"},"content":{"rendered":"

Update: November 1st, 2019<\/em>:<\/span> The Notam Team is up and running<\/strong> – we’re fixing Notams. Follow our progress at fixingnotams.org<\/a>.<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

We think Notams suck<\/strong>. No other way to say it. After a few articles we wrote (BS Notams<\/a>, The Notam Goat Show<\/a>, and more worryingly, the MH17 Notam problem<\/a>), we got some feedback in the comments section. And thought we should share, because they really show the problem. So, here they are.<\/p>\n

Caution, some strong language!<\/strong><\/p>\n

We’re working on a solution, so you can help and add your thoughts as a comment below<\/strong>. Also, send us the really bad ones and enter the 2018 Notam Goat Show<\/a> contest.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

\n

\"\"<\/a><\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

\n

Personally I think taxiway and apron closure NOTAMs are too readable<\/strong>, I think they should be distributed in RADIAL\/DME format, or perhaps raw Lat-Lon. Additionally, time should be specified in seconds since the founding of the FAA.<\/span><\/p>\n

\n

TAXIWAY CLOSED BETWEEN ORL180\/08.5DME ORL181\/08.6DME ORL181\/08.65DME ORL180\/08.65DME FROM 1829088020S to 1829190200S<\/p>\n

What could be more clear than that?<\/p>\n

\n

I wonder if a buried Notam ever did contribute to bent metal, injury, or death? I agree that the volume of nuisance notams is a real task to read through wether it be a long or short turn. However, nothing will be done till there is blood. That’s how the FAA works. Till then, its on us to be like aviation lawyers before every flight regardless of schedule.<\/p>\n

\n

Maybe we can get them in binary?<\/strong><\/p>\n

You have to go to binary first, then convert to Morse.<\/p>\n

01010100 01000001 01011000 01001001 01010111 01000001 01011001 00100000 01000011 01001100 01001111 01010011 01000101 01000100 00100000 01000010<\/p>\n

—– .—- —– .—- —– .—- —– —– —– .—- —– —– —– —– —– .—- —– .—- —– .—- .—- —– —– —– —– .—- —– —– .—- —– —– .—- —– .—- —– .—- —– .—- .—- .—- —–<\/p>\n

For good measure they should be put through an Enigma machine, too. And the output formatted to wingdings<\/p>\n

\n

Yes. The NOTAM system is fucked. We have Notams about those solar arrays near Vegas in every flight plan. Yes, I see them. I want to know if the damn runway is closed. Why the weird coding? Is it to make pilots feel multi-lingual?<\/p>\n

\n

It’s funny, they seem to have every little f*ing detail about towers that are under 400 agl 20 miles either side of my route with one light bulb missing but I can’t get a god damn reliable source for f*ing TFRs. Even the piece of shit FAA website for TFRs is not a “complete and accurate source” but some guy in a FSS station is?????? Such complete and utter bullshit.<\/p>\n

\n

The reason nobody reads NOTAMs is because they are mostly garbage.
\nWhy do I care that a crane that is 200 feet AGL ten miles from any airport is unlit? We can’t fly below 500AGL anyway.
\nWhy do I have to decipher code that can easily be written as: From 20170608 1900Z to 20170610 0000Z CYYZ Taxiway L Closed
\nThe system is broken and nobody cares to fix it.<\/p>\n

\n

I f*in’ love doing a flight from Newark to DC and getting notams about the North Atlantic Tracks. Motherf***r, if I end up on the tracks during that leg in a 145, the Notams are the least of my damn problems.<\/p>\n

\n

The biggest frustration for me is the NOTAMs don’t match reality<\/strong>. KAUS often NOTAMs a runway closed for several hours a couple days each week. Yet we get there and it’s open.
\nOr an airport will NOTAM an ILS out of service for the day. Show up at the airport and they’re using that ILS.
\nMy home airport is KDAL. One of the PAPIs was out for three days before they NOTAM’d it out of service. Delta landing in front of me asked about it. Tower said they showed it on and asked me. I said, “Uh… It’s been out for several days. I thought y’all knew?”
\nFinally, my favorite: Surprise runway closures for routine runway inspections. NOTAM? Nah. BTW there’s a 150′ tower 15 miles away with a light out and there’s birds around the airport. Awesome.<\/p>\n

\n

I can honestly say that if it isn’t a runway closure or terminal closure then I don’t really care. The amount of closed taxiways at every airport is absurd. Not to mention many of them are closed year round with no intention of opening them again, just a permanent NOTAM.<\/p>\n

\n

Can only agree. It has been raised at the RAPACs, but no progress to date.<\/p>\n

\n

If I’m 5nm from the ARP at 150′ AGL, then I have more things to worry about than a crane without a red light…<\/p>\n

Ass-covering gone mad.\u00a0Really… a tree<\/p>\n

OBST TREE 58FT AMSL
\nPSN 386M FM THR RWY 25 AND 183M LEFT OF RWY 25 CL
\nBRG 047 MAG 0.91NM FM ARP
\nFROM 01 310536 TO 03 300500 EST<\/p>\n

\n

My personal favourite is the “trigger notam” cross-referencing to yet another unfindable \/ unreadable pile of nonsense.
\nJust tell us what matters to an “Airman”; today and leave the grand plan, 12 month projection crap out of NOTAMS.<\/p>\n

\n

All of this so true, I imagine a world of technology and wonder (ozrunways\/avplan\/anything but airservices\/casa))where we can quickly read a Notam and weather briefing without having to nut it out and do a slow-ass flight plan every time. 2017 and we still cant embrace all the tech.<\/p>\n

\n

I totally agree. The last thing any crew is going to be able to do when checking NOTAMs before departure is to magic up a way to access cross-referenced documents in various other publications. Especially when the departure point is not anywhere near base ops, or even any other operations centre.<\/p>\n

\n

B.S. NOTAMS….100% concur. Our whole world of aviation is being swamped by similar legal ass-covering paperwork. How can ANY pilot be expected to remember all the additional codicils that do NOTHING to improve safety of flight, but rather give an army of lawyers and providers more chances to fleece an already cash-strapped industry?…..Rant over!<\/p>\n

\n

Congratulations, its our industry, the users should be heard.
\nStart with a blank sheet of paper, what do we want to know in a \u201cNOTAM\u201d and how best to communicate it in a cockpit \/ in a flight briefing package. If the current format was frozen in 1924, the next system needs to be good for a couple of years.<\/p>\n

\n

This information ceased to be \u201cNOTAMs\u201d long ago. Today they are \u201cNOTOLs\u201d, Notice To Litigants. Thanks for making an effort to change this ancient system.<\/p>\n

\n

How many pilots out there actually read ever Head Office Notams or even daily Notams in meticulous detail? Few (if any). You sign on an hour before departure, there is simply not enough time to divulge all the ass covering crap that\u2019s generated daily. Airline companies only want one thing, OTP; how a pilot goes about that they couldn\u2019t care less as long as you don\u2019t break any rules! NOTAMS = \u201cNone Other Than Aircraft Missing Slots\u201d<\/p>\n

\n

You can bet your life, the one you needed to see at 3 in the morning was the one you missed! Any wonder…<\/p>\n

\n

Well said. Have you ever read \u201cMEN AND EQUIPMENT NEAR THE RUNWAY: LANDING WITH CAUTION\u201d?
\nSo, If you don\u2019t tell me that, I will land recklessly..<\/p>\n

\n

You are a mind reader.
\nYou captured the issue perfectly and the historical context was excellent. While airspace and aircraft have all continued to develop our most basic system of communicating the status of an airport\/airspace has not. I could take that further and say communication with ATC is still by AFTN for the most part.So now put yourself in the position of dispatcher\/FOO working a series of long haul ETOPS Flight. You might have 20 or more departure \/Take off alternate station notams, a whole galaxy of FIR\/UIR Notams, not to mention all of the ETOP alternates and if you re-dispatch\/re-analysis, you will get to do it inflight once again. Now do that 15-20 times depending on workload. Can you say human data saturation?
\nThis article certainly illustrates the infrastructure issues we face, but it doesn\u2019t come close explaining some of the processes and procedures we have had to put in place to ensure:
\n1. That we actually get NOTAMS.
\n2. That we get airport conditions as some countries don\u2019t put them out as Series-S ICAO NOTAM versus Series-A (Yes, theses are the countries that haven\u2019t fully adopted ICAO standards which were adopted in 1944 and ratified in 1947 by the Chicago convention).
\nQuestion: What is the current year?<\/p>\n

\n

I absolutely agree. My personal bugbear is those lists of co-ordinates …. do they think anyone actually plots them on a map? They might as well not be published at all.<\/p>\n

\n

What is clear is the professional approach to the information received: too many inputs, disorderly given, contextually irrelevant, redundant and unusable. A kind of \u201ccry wolf\u201d syndrome, making the pilot complacent about such a bullshit. The very day someone of us is caught in a legal battle for a system-induced mistake leading to a incident, overlooking the NOTAMs will not appear as an excuse. How to make these information valuable?<\/p>\n

\n

Yes… and why oh why are we still using the coded TAF language. We don\u2019t have bandwidth issues anymore. We take plain English, code it, then decode it back to plain English. Surely a TAF written in plain English is not too hard a transition.<\/p>\n

\n

We train the pilots of tomorrow, they are inundated with everything the industry throws at them and the unintelligible Nonsense contained in some NOTAMS are just another accident waiting to happen. With all the technology at our disposal today, the filtering systems, electronics messages systems, integration tools and smart people to think about it, there is a solution out there. I suppose we just need to make enough noise in the right places to make a change. Oh well best we get started. hmmm, perhaps a NOTAM about change is needed.<\/p>\n

\n

And don\u2019t forget about TFR\u2019s that pop up. The one time I didn\u2019t look at TFRs I got trapped having to divert from Chicago to an outlying airport even though we were part135 and even though we got an IFR clearance and the tower gave us takeoff permission. And center control for an hour just kept passing us on.<\/p>\n

\n

How about a change in the format of NOTAMS too, so we don\u2019t have to wade through the whole lot in order to parse the relevant information. NOTAMS are removed when thy are no longer valid, so why cling to chronological order as an indexing system. How about putting them in order of critical relevance: Firstly, changes to airfield opening hours and services (fire, fuel etc). Secondly, changes to runway lengths\/closures\/etc. Thirdly, changes to approaches available. All the rest can be thrown into the mix at the end of the NOTAM.<\/p>\n

\n

Excellent analysis. My personal favorite is the NOTAM sort order which tells me that the REIL lights don\u2019t work, the glideslope is out, the runway markings are non-standard, the localizer is out… ending with: runway closed. Tell me that first, all the other BS becomes irrelevant.<\/p>\n

\n

About two days before I saw this post, I\u2019d sent a long email to my company telling them of the NOTAMs we don\u2019t need to see. Then I saw this. Brilliant! I\u2019ve just sent the link to this piece to the company to reinforce that opinion. I\u2019m hoping our briefing pack will be several pages thinner the next time I go to dispatch.<\/p>\n

\n

I have come up with a name for this problem: \u201cNOTAM Spam\u201d. It\u2019s a serious one, alright \u2014 ASRS Callback #426 brought it up in the context of the US NAS, and I\u2019m sure it\u2019s only worse for international operations. It sounds like ICAO needs to put out a recommendation or SARP about NOTAM spam control…<\/p>\n

\n

95% of Notam\u2019s we read are not applicable, or nothing can be done about them. Oh great, I\u2019ll pull out my chart and plot the 25 co-ordinates to see if this airspace will affect my flight -_- that\u2019s one Notam example from plenty of the same type, in the same Notam briefing. Now add the other irrelevant Notam types as mentioned by others in the comments.<\/p>\n

\n

Thanks for the article. I shared it with my fellow dispatchers at AAL. We read pages and pages of BS notams on a daily basis and wondered if anyone else had similar feelings about the whole process.<\/p>\n<\/div>\n

 <\/p>\n

Post your thoughts below!\u00a0<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

Update: November 1st, 2019: The Notam Team is up and running – we’re fixing Notams….<\/p>\n","protected":false},"author":24,"featured_media":3719,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,319,1437],"tags":[1052,792],"class_list":{"0":"post-3709","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-briefings","8":"category-news-item","9":"category-notams","10":"tag-goat-show","11":"tag-notams"},"_links":{"self":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/3709","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/comments?post=3709"}],"version-history":[{"count":4,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/3709\/revisions"}],"predecessor-version":[{"id":8362,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/3709\/revisions\/8362"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media\/3719"}],"wp:attachment":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media?parent=3709"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/categories?post=3709"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/tags?post=3709"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}