You're a pilot, meticulously planning a flight. You check the Terminal Procedures Publication (TPP) for alternate minimums, a crucial piece of information for those 'just in case' scenarios. You're looking for airports that can serve as a safe haven if your destination becomes unusable. But then you encounter 'NA'. What does it really mean, and why is it sometimes so hard to figure out?
It turns out, this little 'NA' can be a source of significant confusion, a point of contention that even aviation authorities are looking to clarify. The FAA's own U.S. Terminal Procedures Publication (TPP) has a section dedicated to IFR Alternate Minimums. The introduction explains that 'NA' signifies that alternate minimums aren't authorized. The reasons? Things like an unmonitored facility, a lack of weather reporting, or inadequate navigation coverage. Simple enough, right? Well, not always.
As a recent discussion highlighted, the reality on the ground – or rather, in the charts – can be quite different. Take Ellenville Airport (N89) for example. If you just glance at the IFR Alternate Minimums section of the TPP, you might not find it listed at all. This could lead a pilot to assume standard alternate minimums apply – typically 800 feet ceiling and 2 miles visibility. But dig a little deeper, and you'd find that on the actual approach charts for N89, a little 'triangle A' symbol appears. This symbol, when you know what to look for, indicates that the airport is indeed 'NA' as an alternate. Two different places, two different messages, and a pilot has to do some detective work.
Then there's East Hampton (HTO). Here, the TPP's Alternate Minimums section might show some information, but again, the approach charts tell a more complex story. You might find the 'triangle A' on some approaches but not others. This inconsistency forces pilots to spend extra time cross-referencing, trying to piece together whether HTO is a viable alternate and under what conditions. It’s not just about saving paper, as some might suggest; it’s about pilot workload and ensuring clear, unambiguous information when safety is paramount.
This inconsistency was brought to the forefront by Garmin, who suggested a straightforward solution: if any runway at an airport has non-standard or 'NA' alternate minimums, then all runways for that airport should be listed in the IFR Alternate Minimums section of the TPP. This way, pilots wouldn't have to hunt for information scattered across different parts of the publication.
The FAA acknowledged the issue, with Terminal Charting expressing willingness to add these procedures to the Alternate Minimums section. The idea was that if an airport had an 'A' notation on its charts, it would be listed in the front. However, this also led to discussions about removing the 'A NA' notation from individual charts, which some military and industry representatives felt was important to retain for clarity. The sheer effort involved in updating these charts, especially without an automated system, is a significant hurdle.
Ultimately, the goal is to make this information as accessible and clear as possible. Suggestions were made to even list procedures with standard alternate minimums in the same central location, so pilots have all their alternate minimum information in one place. It’s a complex puzzle, but one that aviation professionals are actively working to solve, ensuring that 'NA' becomes a clear signal, not a confusing question mark.
