Closed runways appear to be open on the map when they appear to be closed on the ATC menu

I am sorry in advance if this has already been addressed before but I just could not seem to find the topic for this specific issue.
Basically when you’re looking over at an airport on the map, sometimes it shows every runway at the airport to be open for use but as soon as I start announcing that I am inbound to the airport, the runway that I thought was open from the map appears to be red/closed with a +10 knots wind blowing runway heading which is a definite indicator that the runway shouldn’t be used. Nevertheless, it appears open on the map.

That’s because the ATC menu takes into account all winds; the map only takes into account winds above 4 knots. If winds were at 1 knot, then the ATC menu would show which runways are suitable (red/orange/green, depending on wind direction), while the map would show all of the runways as open (green). Not sure why this is done, but it’s not an error. 🙂

1 Like

That clears things up a little bit more. With that said, if I am already inbound on a runway that is open on the map but is closed on the ATC menu, should I go around or just land at the runway?

1 Like

If you feel comfortable landing, you should proceed. The if you use the ATC menu in combination with checking the airport’s weather, then you should have no problems landing. For instance, let’s say I’m approaching EDDN, runway 10. Winds are displaying 90@2kts, but all of the runways appear on the map as green. In this case, as long as you feel comfortable landing in 2kt headwinds/tailwinds, either runway is avaliable to your use. If winds escalate and one of the runways appear as red on the map, then it is strongly recommended that you stay away from that end.

1 Like

That makes sense now, I’ll take that into account next time. 😄

1 Like

Awesome, glad I could help.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.