Learn why FSX ATC assigns the wrong runway, how wind and AFCAD data affect it, and how to request or make a permanent change.
FSX ATC chooses a runway from the airport's facility data and the weather it sees, not from real-world operating procedures. A light or conflicting wind, stale weather, incorrect runway closure flags or duplicate AFCAD scenery can produce an odd assignment. You can influence it with weather or change the airport data.
How does FSX choose the active runway?
FSX and FSX: Steam Edition use the same stock ATC logic: local surface wind normally determines the preferred runway direction, while the active airport definition determines which runway ends are available.
- Surface wind: ATC generally favours a runway offering a headwind rather than a tailwind.
- Calm or variable conditions: With no clear wind preference, FSX falls back on its own airport and traffic logic. This may not match the runway a real airport normally uses.
- Airport facility data: Runway closure flags, available starts, taxi links and coded approaches limit what ATC can assign.
- Traffic flow: Parallel runways, crossing runways and AI traffic can affect which of several active runways you receive.
Stock FSX does not model every airline preference, noise-abatement procedure, time-based runway restriction or real-world runway configuration. An assignment can therefore be internally valid even when it looks wrong to someone familiar with the airport.
Can I request a different runway from FSX ATC?
On arrival, FSX may let you select a different approach and runway, but the option depends on the flight rules, phase of flight and approaches coded into that airport. Departure ATC has no dependable command that lets you choose any runway at every airport.
- Set the weather before contacting ATC. To favour a runway, use a steady surface wind coming broadly from the direction that runway faces. For example, runway 27 should be favoured by a broadly westerly wind.
- Wait for the weather to finish loading. Injected weather can change after the flight opens. Our explanation of weather injection and real-world conditions in FSX covers the available methods.
- Listen to ATIS. Its reported wind and runways in use reveal what the stock ATC system believes the conditions are.
- Contact ground or approach after the weather settles. Changing wind after ATC has committed to a runway may not produce an immediate reassignment.
- Use the different-approach option if offered. During an IFR arrival, the ATC window may provide a list of alternative approaches. Airports without suitable coded approaches may offer little or no choice.
Selecting a runway as the aircraft's starting position only moves the aircraft; it does not force that runway to become active. Taxiing to another runway without a revised clearance can also trigger ATC warnings rather than change the assignment.
Why does ATC keep selecting an unexpected runway?
The pattern of the problem usually identifies whether weather, scenery or an FSX limitation is responsible.
| What happens | Likely cause | What to check |
|---|---|---|
| ATIS wind favours the assigned runway, but the real airport uses another | FSX does not know the real operating procedure | Request another approach or use a custom airport configuration |
| ATIS reports wind favouring the opposite runway | Weather has not settled, the wind is too light, or airport data is conflicting | Reload fixed weather and test again |
| The problem affects only one airport | Incorrect or duplicate AFCAD scenery | Check enabled scenery layers for multiple airport definitions |
| No alternative runway or approach appears | Missing approach records or runway-end closure flags | Inspect the airport facility data |
| Crossing runways behave strangely | A custom AFCAD may use a crosswind-runway technique for AI traffic | Test without that airport add-on |
A mistake we see constantly is changing the weather repeatedly when one add-on airport is the real culprit. If every other airport responds correctly to wind, inspect that airport's scenery before changing global weather or ATC settings.
How can I permanently change the runway FSX ATC uses?
You can correct persistent airport-specific assignments with Airport Design Editor or a comparable AFCAD editor. Our walkthrough for inspecting and compiling FSX airport data explains the workflow, and the airport editing utility is available in our FSX library.
- Identify the active airport definition. Look for more than one add-on BGL covering the same ICAO airport. Scenery-layer priority can cause an old AFCAD to override a newer one.
- Inspect each runway end. Check whether it is open for take-off and landing, whether appropriate approaches exist and whether taxi links reach it correctly.
- Make the smallest necessary correction. Closing a runway end can stop ATC and AI from using it, but that restriction is static. Stock ATC cannot apply a sophisticated schedule of wind, time and noise rules.
- Compile the correction as separate add-on scenery. Keep a backup and do not overwrite FSX's stock scenery files.
- Test with fixed weather. Try known winds from both runway directions, then add AI traffic. If the old behaviour returns, another airport BGL is probably still active.
Do not change a runway's heading or number merely to force an assignment. That can break approach alignment, navigation data and AI behaviour. Use weather when you need a temporary runway preference; edit airport data only when the scenery is consistently wrong or you deliberately want a fixed custom configuration.