World airport problem reports

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Name: Fogo Aerodrome

Remove [Duplicate] from name information.

Currently the Airline field says "no". That is not correct. It should show "Yes". MWCL/LYB is served by Cayman Airways Express, typically with several flights daily to/from MWCR/GCM and MWCB/CYB.

Good day. Every single airport in Canada, uses MAGNETIC not TRUE headings, you are incorrectly reporting every single runway at every single airport in Canada. I have copies of NAV Canada's publications of the runway at CYYT, I can forward them when I receive the response email.

Runway 10/28 for example at my airport CYYT (102°/282° MAG as per the legal published areodrome charts) is being shown as 086°/266° TRUE. I use to use the METAR/TAF decoder website/app that is using your information to help me see what way the winds were blowing across the runway at the start of my shift so I could get a heads up to plan how I was plowing the runway with the winds. But due to the incorrect reporting of the runway, the winds will show it straight down the runway, when we have a cross wind for example.

Two thoughts:

1. Your aggressive opening statement is factually incorrect. Airports in northern domestic airspace have runways numbered and weather reported in degrees true.

2. As @Bill35 noted, the true headings of runways are much more reasonable to record as permanent information in a database, as magnetic headings will change and can be calculated with a current map of magnetic variation (but the runways themselves rarely move). If the developer of a weather app chose to use an open database and not read the documentation on the database (or apply the data correctly), that's their problem and not a reason to expect an open data project to maintain accurate and current magnetic data as the pole moves. A quick google search suggests there is an MIT-licensed Python library that implements the World Magnetic Model that could be used to calculate up to date magnetic headings from the true headings in the OurAirports database. Maybe you should direct this complaint to the developer of your decoder website and suggest they implement something like that.

It is correctly marked as closed. The edit history suggests it did exist in the recent past.

Correct Frequencies for u14: CTAF/UNICOM: 123.075

WX AWOS-3PT: 118.275 (435-623-1397)

Please add runway designators: 08/26

Source: german AIP https://aip.dfs.de/BasicVFR/pages/P001BB.html

Name: Château de Lastours circuit DZ

Municipality: Portel-des-Corbières

Name: Fontjoncouse circuit DZ

Municipality: Fontjoncouse

Name: Vaux Andigny DZ

09L-27R no longer exists

Frequency 119.655 Mhz

Name: Elisusperficie lago Serru

Keywords or comments: Autorizzata giorno notte (night and day)

EU iso AS

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe

Continent: Asia instead of Europe