Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Station Proximity Confusion

Featured Replies

Ran into a situation tonight on a flight from Vancouver (CYVR) to Yakutat, Alaska (PAYA). All the way up I was getting forecasts and reports of 1/2 mile vis at PAYA. On final approach, I was still getting ATIS for KYAK, and a destination report for PAYA, both of which were quite different to each other. I could see the runway from the OM so I knew I had at least 4 mile vis (hard to tell how much more - it was night). On the ground I tuned in 122.00 again and got the same reports for KYAK and PAYA, with the 1/2 mile vis reported at PAYA (where I was) and much more than that for KYAK.I brought up the AS2004 window and it showed KYAK as the nearest station at 0nm away, and PAYA the destination at 0nm away. The report in the window was for KYAK and was as follows:240519Z 00000Kt P6SM SCT025 BKN050 05/04 A2919 DYNAMIC TAFIt looks like there are 2 reporting stations located at the same airport, each with a different identifier. The weather picture looked correct for the KYAK and not for the PAYA reports, so in that respect, AS2004 was doing its job. It's hard for the pilot to tell though, just what he's going to have under those conditions, and I thought I noticed quite a cloud 'bump' as I was on descent, so maybe one station was "fighting" with the other. Not sure on that one. Anyway, it might be something that will need clarifying or adjusting at some point.Thanks guys!

Jim, Damian,Let me poke around here a bit with this. This could be an isolated case that sometimes occurs around the Alaskan coast. They have 2 sets of identifiers up there, and that can cause a lot of confusion. It could be that this might only occur at that point (PAYA). On my subsequent flight out of there, I got a lot of popping in and out of clouds as I went down the runway, so I'm sure there's a conflict going on there. However, my approach into Northway a half hour later was normal (except that "you guys" gave me lousy weather and I had a miss! :-fume ;-) ), and the subsequent approach into Cordova (my alternate) went without a hitch. So as I say, this may be isolated, and I can do some poking around to see what happens at various places and report my findings to you. It may not be worth expending any real energy on this at all, and certainly not at this point. Back at you in a day or two on this. In the mean time, have a VERY happy holiday, and Jim - GET SOME DAMN SLEEP!!! :-hah.All the best guys!http://home.cogeco.ca/~gdfs01/NWA/NWA002.jpgOffloading several thousand pounds of booze at Cordova :-eek

Bump for relevancy

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.