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.

KSAN Zero Wind Runway

Featured Replies

I found a file sandiegointernationalfsx.zip which I assume is what was intended.In the AFX Rwy 9 is set closed for landing and take off. What I observe is that all traffic will be sent to Rwy 27 regardless of winds. In VMC arriving IFR traffic get the visual 27 and in IMC they get GPS 27. I watched some defaults, and even with 35 kts of tail wind they were able to take off, though they used most of the runway to do it.scott s..
Sorry Scott that is not how that airport is working using the sandiegointernationalfsx.zip Since the Start Location has been removed and runway 09 is closed for takeoff and landing the winds carry the highest score for runway selection plus the Base end which is RWY09.On startup of FSX at KSAN when winds are set to light and varible runway 27 will always be the active using the visual approach (VMC). If winds pickup to 40, 50, 60 kts then runway 09 becomes the active while inbounds are still trying to use runway 27 (based on the AI slot). When the AI slot card clears out then all departures and approach become runway 09.Since the Start Location is missing the holdshort will not stop the departures from stacking on the runway. Also 2 planes were slotted in the AI card for approach to runway 27. One of the Boeing's is on short final for 27 but will go missed since a Delta is cleard for takeoff (owns the runway) on RWY 09fsscr001.jpgOnce the approach AI slotted card is cleared out all planes will now use runway 09.fsscr003w.jpgWhen Runway 27 is the active and the airport is IMC ATC is assigning the Localizer approach and not the GPS. Many AI Planes with poor FD's are falling through the FAF altitude since FSX is using the canned .dll approach and not the XML approach. As long as the winds using this airport (sandiegointernationalfsx.zip) stay light and varible I agree runway 27 is the favored runway with a visual approach (VMC). On startup of FSX the default weather engine is always slow to respond (reading proper wind speed and direction). I always check the wind sock movement and the Shift Z readings to be sure the weather engine has loaded properly.Open the AFX_KSAN.bgl with SDE. The XML cannot be validated due to unknown ID's in the airport record.jim

Did some more testing, and with winds from the east at 45 kts still used Rwy 27. finally when winds were 50 kts it switched to Rwy 9. Here is a 40 kts example:ksan40kt2nmtest.jpgAI never got a LOC approach (did get ILS on 9 of course).scott s..

ScottI also see runway 09 open at 50 kts after a retest (my original test was 60). I still get the Localizer 27 for AI/User but my IMC is set at 2 mile visibility with an overcast 8/8 clould layer of 200 ft AGL. The AFX bgl does have the approach code embedded with deleteapproach set to true but no T_Waypoints which are coming from the stock APX bgl (this is not a true AFX bgl which is using split approach/T_waypoints).The weighted approaches may not be the same for everyone based on weather settings since the T_Waypoints are read at the root level.jim

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.