A Field Guide to NOTAMs
Moderators: sky's the limit, sepia, Sulako, lilfssister, North Shore, I WAS Birddog
- Beefitarian
- Top Poster
- Posts: 6605
- Joined: Wed Dec 01, 2010 10:53 am
- Location: A couple of meters away from others.
Re: A Field Guide to NOTAMs
Nice.
I particularly enjoyed that example where they corrected a height from 1732' to 1733'. I was going to fly over it but in light of the notam, maybe we better go around it.
I particularly enjoyed that example where they corrected a height from 1732' to 1733'. I was going to fly over it but in light of the notam, maybe we better go around it.
-
- Rank 11
- Posts: 4576
- Joined: Mon Feb 16, 2004 2:33 am
- Location: YYC 230 degree radial at about 10 DME
Re: A Field Guide to NOTAMs
The notam system IS fucked. Period. And Navcanada just made it worse.
Re: A Field Guide to NOTAMs
The text sounds logical, but then you start wondering: what are you going to leave out? The NOTAM system is not only built for airlines, but also for low level helicopter traffic. They might care about power lines that are unmarked or cranes right next to the grass field where they will be working.
The biggest issue I think, is that the data is not represented properly. Every notam is somehow linked to a location and an altitude. Smart software should be able to filter out which of those would be pertinent to the flight. The problem there is, once again, liability. If a notam gets missed, whose fault is it? The person issuing the notam for not specifying the paramter appropriately? The software interpreting the notam wrongly? The pilots tursting the software?
Compare it a bit to the internet if you wish. If we were still using the same systems as when it was first conceived, it would have become unusable by now. But technology evolved, and while we are still using HTML to pass information along, we also have search engines to search through the always growing hump of information.
That is what is missing. You'll never be able to prevent pollution at the source -nobody will want to take the responsibility-, but the data needs to be tagged better so it can be automaticaly processed reliably.
The biggest issue I think, is that the data is not represented properly. Every notam is somehow linked to a location and an altitude. Smart software should be able to filter out which of those would be pertinent to the flight. The problem there is, once again, liability. If a notam gets missed, whose fault is it? The person issuing the notam for not specifying the paramter appropriately? The software interpreting the notam wrongly? The pilots tursting the software?
Compare it a bit to the internet if you wish. If we were still using the same systems as when it was first conceived, it would have become unusable by now. But technology evolved, and while we are still using HTML to pass information along, we also have search engines to search through the always growing hump of information.
That is what is missing. You'll never be able to prevent pollution at the source -nobody will want to take the responsibility-, but the data needs to be tagged better so it can be automaticaly processed reliably.
As an AvCanada discussion grows longer:
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
Re: A Field Guide to NOTAMs
I am very open to hear from a low level helicopter pilot who searches for (or cares about) NOTAMs for a crane or power line next to the grass field where they will be working.digits_ wrote: ↑Wed Nov 06, 2019 7:49 pm The text sounds logical, but then you start wondering: what are you going to leave out? The NOTAM system is not only built for airlines, but also for low level helicopter traffic. They might care about power lines that are unmarked or cranes right next to the grass field where they will be working.
DId you hear the one about the jurisprudence fetishist? He got off on a technicality.
Re: A Field Guide to NOTAMs
Would you care to give an exhaustive list of what kind of notams are essential?
Or, alternatively, an exhaustive list of "garbage" notams?
I'm pretty confident there will be exceptions to both lists. It would be nice if you could prove me wrong!
Or, alternatively, an exhaustive list of "garbage" notams?
I'm pretty confident there will be exceptions to both lists. It would be nice if you could prove me wrong!
As an AvCanada discussion grows longer:
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
-
- Rank 5
- Posts: 344
- Joined: Fri Apr 23, 2004 5:38 pm
Re: A Field Guide to NOTAMs
I don't think we need an exhaustive list. I think it's actually very simple. We don't need 300 notams about closed taxiways and burnt out taxi lights, which I can't and don't care to memorize. The controllers will know which taxiways not to clear us onto and so it isn't an issue at controlled airports. We also don't need to know about altitudes that change by 3 ft and other ridiculous things. Save it for the next chart update. Save everything for the next chart update unless it's an actual hazard to aircraft.
I want to look at an airport notam for 30 seconds and know if there is an actual hazard to my aircraft. The only thing that should be on there is runway closures, runway exit closures, unservicable approaches and anything within protected airspace. Everything else is a CYA exercise by administration.
Re: A Field Guide to NOTAMs
What is clear is that there is a need for a system to communicate essential flight safety information that cannot wait for the next update cycle. This system used to be NOTAMs, but now NOTAMs are so full of garbage that there is effectively no system. Perhaps we need a new system that sends out essential flight safety information in plain text, and leave the old NOTAM system in place for all the old garbage. Eventually airports would tire of publishing useless garbage in archaic format and we could retire the NOTAM system, leaving only the new system.
- Beefitarian
- Top Poster
- Posts: 6605
- Joined: Wed Dec 01, 2010 10:53 am
- Location: A couple of meters away from others.
Re: A Field Guide to NOTAMs
Well it's flawed but that's modern life isn't it? If a thing is a CYA item they need to mix it in to force us to read everything.
If it was seperated out almost no one would read it and they would not be doing their due diligence. Regardless of how seemingly trivial.
True enough if a heavy airliner is close enough to a small tower there might be a problem that can't be prevented by a notam. And I agree if a guy flying a helicopter is going to hit a 35 foot tall crane, writing a notam probably won't prevent that.
Still they are there to alert everyone there is a crane/tower/snail track/whatever and maybe it will help us think about the thing and look out for it.
The unreasonable amount of extras will probably get worse instead of going away.
If it was seperated out almost no one would read it and they would not be doing their due diligence. Regardless of how seemingly trivial.
True enough if a heavy airliner is close enough to a small tower there might be a problem that can't be prevented by a notam. And I agree if a guy flying a helicopter is going to hit a 35 foot tall crane, writing a notam probably won't prevent that.
Still they are there to alert everyone there is a crane/tower/snail track/whatever and maybe it will help us think about the thing and look out for it.
The unreasonable amount of extras will probably get worse instead of going away.
Re: A Field Guide to NOTAMs
If you are unable to make an exhaustive list as a pilot, then how do you expect non-pilots to determine what is and is not important?tired of the ground wrote: ↑Thu Nov 07, 2019 7:32 amI don't think we need an exhaustive list. I think it's actually very simple. We don't need 300 notams about closed taxiways and burnt out taxi lights, which I can't and don't care to memorize. The controllers will know which taxiways not to clear us onto and so it isn't an issue at controlled airports. We also don't need to know about altitudes that change by 3 ft and other ridiculous things. Save it for the next chart update. Save everything for the next chart update unless it's an actual hazard to aircraft.
I want to look at an airport notam for 30 seconds and know if there is an actual hazard to my aircraft. The only thing that should be on there is runway closures, runway exit closures, unservicable approaches and anything within protected airspace. Everything else is a CYA exercise by administration.
Taxiway closures are nice to know in some circumstances. It can help you to request a different runway depending on where you are going on the field.
As an AvCanada discussion grows longer:
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
Re: A Field Guide to NOTAMs
"Nice to know in some circumstances" doesn't meet the "essential" bar, even slightly.
DId you hear the one about the jurisprudence fetishist? He got off on a technicality.
-
- Rank (9)
- Posts: 1982
- Joined: Wed Mar 13, 2013 9:24 am
Re: A Field Guide to NOTAMs
The vast majority of NOTAMs are ignored by a vast majority of pilots. Yet, nobody seems to care.
-
- Rank 5
- Posts: 391
- Joined: Tue Feb 12, 2019 7:27 pm
Re: A Field Guide to NOTAMs
Th PC and especially the CYA Lawyers are running the show just like the pedo check for flying young kids around at a COPA event. AND when the shit hits the fan , money and power will fix anything ( think Boeing and the max )
Re: A Field Guide to NOTAMs
Ok. What is truly essential then?
If a taxiway closure makes an fbo unreachable, that is essential for my trip.
A temoorary weight limitation on certain taxiways might be useless information for general aviation, but a 737 pilot might think otherwise.
As an AvCanada discussion grows longer:
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
-the probability of 'entitlement' being mentioned, approaches 1
-one will be accused of using bad airmanship
Re: A Field Guide to NOTAMs
Essential for flight safety. I'm sure your FBO would inform you if the airport had blocked all access. If a taxiway cannot handle a 737, ATC will not clear it onto that taxiway. There are many ways of dealing with trip planning details, the point of NOTAMs is supposed to be safety items important enough that they need to be highlighted rather than buried.
Re: A Field Guide to NOTAMs
There needs to be a means of filtering notams so only relevant ones for a particular flight are displayed.
We will never convince the lawyers and bureaucrats to stop publishing BS on a whim. For them it's pure CYA and pass along the responsibility and liability to pilots. That way during an investigation they can always point to the vital info, buried on page 14 of the notams, camouflaged in a sea of horseshit and blame the pilot. It's like having to watch a 2 hour movie because you need to hear one line that one actor says at some random point.
The irony is, the "more is better" mentality only makes it less safe. With the number of notams exponentially growing, there's greater chances I'll miss the important notam about the runway being shortened because there's notams about things like grass cutting creating so much visual noise. Despite reducing safety, the airport authority will continue to publish grass cutting notams, they don't want to be sued because of a lawnmower. So in it goes.
ICAO needs to show some leadership and change the circa 1924 (literally) notam format so it's less cryptic, more standardized, and allows for searchable quiries that reliably and consistently can filter out irrelevant notams. This isn't a complex task. A first year computer science student could probably set it up in their spare time.
With a proper filter system, if you're flying a 737 from a major Int'l airport, IFR to another major Int'l airport, you can filter out all the notams on cranes, grass cutting, that parking position D29 on the cargo ramp cannot take An-124, that the tower controller's birthday is on Saturday, etc. I just don't care.
Simmilarly, the low level VFR helo pilot can filter out that Rwy 24R is 4000' shorter with a displaced threshold. I'm sure he doesn't care. Maybe he does care that there's a crane 5nm away from the runway that's 136' high. If it doesn't penetrate an IFR obstacle surface (which would trigger a corresponding notam raising minimums or departure climb gradients etc.) then the crane couldn't be less important to me.
The growth in the number of notams is getting out of hand and soon you'll need an hour briefing with a lawyer before going flying.
Less is more. But for CYA reasons, the people publishing notams will always go with "if in doubt, publish". The information overload is creating a safety issue, not improving safety. Pilots need a reliable and consistent way to filter what is essential to them.
We will never convince the lawyers and bureaucrats to stop publishing BS on a whim. For them it's pure CYA and pass along the responsibility and liability to pilots. That way during an investigation they can always point to the vital info, buried on page 14 of the notams, camouflaged in a sea of horseshit and blame the pilot. It's like having to watch a 2 hour movie because you need to hear one line that one actor says at some random point.
The irony is, the "more is better" mentality only makes it less safe. With the number of notams exponentially growing, there's greater chances I'll miss the important notam about the runway being shortened because there's notams about things like grass cutting creating so much visual noise. Despite reducing safety, the airport authority will continue to publish grass cutting notams, they don't want to be sued because of a lawnmower. So in it goes.
ICAO needs to show some leadership and change the circa 1924 (literally) notam format so it's less cryptic, more standardized, and allows for searchable quiries that reliably and consistently can filter out irrelevant notams. This isn't a complex task. A first year computer science student could probably set it up in their spare time.
With a proper filter system, if you're flying a 737 from a major Int'l airport, IFR to another major Int'l airport, you can filter out all the notams on cranes, grass cutting, that parking position D29 on the cargo ramp cannot take An-124, that the tower controller's birthday is on Saturday, etc. I just don't care.
Simmilarly, the low level VFR helo pilot can filter out that Rwy 24R is 4000' shorter with a displaced threshold. I'm sure he doesn't care. Maybe he does care that there's a crane 5nm away from the runway that's 136' high. If it doesn't penetrate an IFR obstacle surface (which would trigger a corresponding notam raising minimums or departure climb gradients etc.) then the crane couldn't be less important to me.
The growth in the number of notams is getting out of hand and soon you'll need an hour briefing with a lawyer before going flying.
Less is more. But for CYA reasons, the people publishing notams will always go with "if in doubt, publish". The information overload is creating a safety issue, not improving safety. Pilots need a reliable and consistent way to filter what is essential to them.
Re: A Field Guide to NOTAMs
Perfect example is why when a runway is closed and they disable all the approaches do they have to publish a separate Notam for every damn approach to that runway, just say all approaches for runway 30 are U/S Until x time.
Or my personal pet peeve is something that should be on the chart since it’s been a notam for 10 years like the threshold of 23 in YYZ
Or my personal pet peeve is something that should be on the chart since it’s been a notam for 10 years like the threshold of 23 in YYZ
-
- Rank (9)
- Posts: 1982
- Joined: Wed Mar 13, 2013 9:24 am
Re: A Field Guide to NOTAMs
Has anybody submitted an SMS report with their company about this NOTAM crap?