Now, I'm just confused.
The Aeronautical Charting Forum has an open Recommendation Document (13-01-262) titled "Airport Facility Directory (AFD) Depiction of Traffic Pattern Altitudes" which I have posted before in this thread. But it's the last entry that is relevant:
Acronym decipher: NFDC is National Flight Data Center and NASR is National Airspace System Resources. NASR is supposed to be a repository of information kept by the FAA so I wanted to test a theory after reading the two entries above. I found an airport in Alabama that had a 'non-standard' pattern altitude and looked it up a few different places to see what information was available. For comparison I threw KDCU in there too:
KEDN - NASR, AirNav, SkyVector
KDCU - NASR, AirNav, SkyVector
Pattern Altitude for EDN is 800' AGL (1161' MSL). AirNav, SkyVector and the A/FD all list TPA at 1161' MSL for EDN, but NASR lists nothing regarding pattern altitudes. I assume all three flight software's (AOPA FlyQ Pocket, Garmin Pilot, ForeFlight) have the same information for EDN. KDCU has no published TPA in NASR, AirNav, SkyVector, or the A/FD. It does however have the 'unofficial' TPA at 800' AGL in the three flight software's.
So if the NASR does have TPA information in it, but you can't see it in the web interface then why isn't DCU's TPA in the A/FD? But if NASR doesn't have TPA information in it or not every airport is updated, where are the flight softwares pulling their information? What information source is FAA Form 7480-1 updating?
Yes, I'm trying to make sense of a government entity.
The Aeronautical Charting Forum has an open Recommendation Document (13-01-262) titled "Airport Facility Directory (AFD) Depiction of Traffic Pattern Altitudes" which I have posted before in this thread. But it's the last entry that is relevant:
They're supposed to meet twice per year, that meant meeting 15-01 should have happened. So I hunted up the meeting notes:Aeronautical Charting Forum Meeting 14-02 said:Valerie Watson, AJV-344, briefed the previous ACF consensus that ALL traffic pattern altitudes, whether considered “standard” or “recommended”, should be both captured in the NASR database and published in the AFDs. Steve risbon, AJV-211, briefed that NFDC has not yet begun the process of populating all traffic pattern altitudes in NASR. Steve will follow up and attempt to expedite the project.
Aeronautical Charting Forum Meeting 15-01 said:Valerie Watson, AJV-553, reviewed the issue. Mike Wallin, AJV-5331, stated that NFDC is still working this issue. Valerie asked Mike if there is a new policy to collect all Traffic Pattern Altitude (TPA) data, whether standard or not, and populate the information in NASR. Mike was not sure if that policy was in place and committed to looking into the issue further and reporting at the next ACF.
Acronym decipher: NFDC is National Flight Data Center and NASR is National Airspace System Resources. NASR is supposed to be a repository of information kept by the FAA so I wanted to test a theory after reading the two entries above. I found an airport in Alabama that had a 'non-standard' pattern altitude and looked it up a few different places to see what information was available. For comparison I threw KDCU in there too:
KEDN - NASR, AirNav, SkyVector
KDCU - NASR, AirNav, SkyVector
Pattern Altitude for EDN is 800' AGL (1161' MSL). AirNav, SkyVector and the A/FD all list TPA at 1161' MSL for EDN, but NASR lists nothing regarding pattern altitudes. I assume all three flight software's (AOPA FlyQ Pocket, Garmin Pilot, ForeFlight) have the same information for EDN. KDCU has no published TPA in NASR, AirNav, SkyVector, or the A/FD. It does however have the 'unofficial' TPA at 800' AGL in the three flight software's.
So if the NASR does have TPA information in it, but you can't see it in the web interface then why isn't DCU's TPA in the A/FD? But if NASR doesn't have TPA information in it or not every airport is updated, where are the flight softwares pulling their information? What information source is FAA Form 7480-1 updating?
Yes, I'm trying to make sense of a government entity.
Last edited: