Welcome to the AOPA Airports and Destinations User Forum!
Please search for similar topics before creating new ones. You can vote or contribute additional information to topics that are similar to issues or questions you have.
Hello. My name is Carl and I am a big fan of these AOPA kneeboards and just the airport directory website in general. Thank you for your service. A slight update needed on https://www.aopa.org/Kneeboard/Kneeboard/GeneratePdf?airportId=KLCI
RWY26 is now left traffic.
Hello and thank you for contacting us.
The traffic pattern data we present in our airport directory and on the kneeboard format comes directly from the FAA every 28 days. We are not permitted to change FAA data so once the FAA updates their official database and indicates Rwy 26 as Left traffic pattern, it will be correct in the AOPA presentations of the data. I checked several other common airport directories and EFB apps and they are also still showing Rwy 26 as Right traffic.
There is a Note added by the Airport Manager on the kneeboard format and in our online directory that indicates Rwy 26 is now Left traffic pattern as well as a NOTAM from the FAA indicating Left traffic pattern. Pilots should always consult NOTAMS for changes that occur in-between cycle updates since this is the method the FAA uses to communicate changes since the last 28-day update. It can sometimes take longer than 28 days for the FAA to update their official dataset depending on when the change occurred as well as other factors.
Had the distinct misfortune of having my annual done by Treasure Coast Aircraft Solutions. Trev removed one of my comm antennas thinking it was an ELT antenna. Had to sue him to get my antenna back. He quotes one price for work he is doing but charges significantly more. Avoid this A&P at all costs!!
KCRE Kneeboard drawing is not up to date. Major taxiway change which is shown on the airport diagram
Thank you for drawing our attention to the taxiway changes at KCRE. The FAA does not indicate when taxiway changes are made in their dataset, only when change are made to runways. We have gone in and updated the diagram that is used on the AOPA Kneeboard format though.
On the kneeboard format for KPDC, the pattern altitude is listed at 1460, while the elevation is 660, or an unusual 800 ft AGL. On the chart supplement, no such note of an unusual pattern altitude is indicated.
https://aeronav.faa.gov/Upload_313-d/supplements/CS_EC_20200716.pdf (page 369 in the Chart Supplement, and the actual page in the digital document is 371).
I'm a student pilot and trying to reconcile these two sources. On my home airport (Platteville, WI; KPVB) it notes that there is no indication of pattern altitude, but to assume 1000 ft AGL. https://www.aopa.org/Kneeboard/Kneeboard/GeneratePdf?airportId=KPVB
It looks like the PDC kneeboard is just a typo, but it notes the pattern altitude whereas the PVB kneeboard does not.
As a student pilot (or any other type) I presume the smart move with the kneeboard formats supplied by AOPA is to validate any data on them with both the Sectional Chart and the Chart Supplement? Or is the information on the kneeboard format as verified by the Airport Manager. And if it is that, why doesn't that info appear in either the chart supplement or on the sectional?
As I've checked area airports, I found the kneeboard shows a traffic pattern KOVS (Boscobel Wi) is 1502 feet, while the elevation is 673, or a rather odd 829 ft AGL) .
You have KFNL listed an non-towered, but it is in fact controlled and towered.
The datapoint regarding a control tower is official FAA data and cannot be updated by AOPA. The official FAA data shows that FNL is not a towered airport however there is a temporary tower operating which is referenced in the NOTAMs. If the FAA updates their official data, then our directory (and others) will show the tower as being present. Until the data is updated, NOTAMs should be consulted since this is the mechanism that the FAA uses to reflect mid-cycle operational changes or temporary changes to their official data.
Customer support service by UserEcho