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.

Reporting KSJU instead of TJSJ / KSTT instead of TIST

Featured Replies

While flying from San Juan to Nevis, I loaded my FP into the route planner for AS and processed. All of the stations that were reported in the briefing were correct, but when it came time to fly, the stations that actually displayed weather were incorrect. Two examples:TJSJ was reported as KSJU (there is a SJU VOR)TIST was reported as KSTT (there is a STT VOR)Perhaps the VOR identifers conflicted with something inside AS? Something to look into anyway. ;)Secondly, what's the trick to get destination weather to click in before your on the ground. AS will not update my weather to match the destination until AFTER I'm on the ground. Not good if your trying to pick the right runway online. I can hit refresh on a 2 mile final and AS will still plug in the next to last wx station, not the destination. I've tried to mess with the supression settings but haven't had any luck.Chris

Here's a screenie by the way...

  • Commercial Member

Hi Chris,KSJU is actually the same airport ID, San Juan Puerto Rico, an actual US location thus the KSJU ID. In FS9 occasionally there are multiple reporting stations for the same airport like this. Our routines in AS2004 to handle this are problematic at the moment... something I am working on right now. The conditions at the linked ID should be the same, but they are interpolating incorrectly. Same goes for KSTT/TIST.Destination weather will not activate? Well this is probably due to your suppression and update rates. When you get close to the destination (within 200nm) the wx will be set at the first occuring update. If your update rate is long, you might never see the correct wx. To fix this, turn your update rate down (suggest 10 minutes). Also check your suppression ceiling.. if you're flying below this ceiling, updates will not occur (until you are on the ground or climb above). If you have continued trouble with suppression you can disable all suppression options and this will always update at the specified interval.Hope that helps!-Damian

Damian Clark
HiFi  Simulation Technologies

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.