Fix incorrect local time in FSX by checking UTC, the date and Windows settings, then correcting daylight-saving or time-zone boundary errors.
FSX and FSX: Steam Edition calculate local time from the simulator’s internal UTC clock and built-in time-zone data. If UTC, the date or Windows clock is wrong—or FSX’s old zone boundaries do not match modern daylight-saving practice—the local display will be wrong. Correct UTC first, then the zone offset.
What makes FSX local time incorrect?
Most FSX time errors can be identified by where and when the discrepancy appears. FSX may label UTC as GMT; for this troubleshooting, treat the two as equivalent.
| Symptom | Likely cause | Best fix |
|---|---|---|
| Every airport is wrong by the same amount | Incorrect simulator UTC, date or Windows clock | Correct Windows first, then reset FSX time |
| Local time is exactly one hour out | Daylight-saving mismatch | Keep UTC correct and apply a regional time-zone correction |
| Only certain airports are wrong | Old or coarse FSX time-zone boundaries | Use corrected world time-zone data |
| The error returns after loading a flight | The saved flight contains its own date and time | Correct and resave the flight |
| Time drifts or jumps during a flight | Pause, time acceleration or competing add-ons | Return to normal simulation rate and test without time-management tools |
How do I correct the time in FSX?
Correct the simulator’s UTC and date before trying to repair its local-time offset. Entering local clock time as GMT is a common mistake and shifts every location by the time-zone difference.
- Verify the Windows clock. Check the date, local time, time zone and automatic clock synchronisation before launching FSX. Windows does not replace FSX’s global time-zone map, but an incorrect system clock can give a current-time flight the wrong starting value. Our Windows date, clock and time-zone checklist covers these settings in more detail.
- Load the intended airport first. FSX needs the aircraft’s location before it can calculate the appropriate local offset.
- Open Time and Season. With the menu bar visible, use the World menu and open the time-and-season controls. Adjust the date and time until the displayed GMT or UTC matches the value you intend to simulate.
- Compare the local offset. Check what civil time should be at that airport on the selected date. Include daylight saving where applicable, and remember that some regions use half-hour or quarter-hour offsets.
- Classify the remaining error. If UTC is correct but one region remains wrong, changing Windows or global simulator time is not the answer. The fault lies in FSX’s regional conversion data.
- Check add-ons if time changes again. Disable utilities that alter simulator time, test a stock flight, then restore only one time-synchronisation tool. Two tools trying to control the clock can produce repeated jumps.
Why is FSX exactly one hour out?
A one-hour discrepancy usually means FSX and the real location disagree about daylight saving. FSX does not have a continuously maintained global civil-time database, and many countries have changed their rules since the simulator’s time-zone data was produced.
Do not change the Windows time zone merely to compensate for one airport. If accurate UTC, AI schedules and solar position matter, preserve UTC and correct the regional offset instead. If you only need a quick visual workaround, you can move the simulator clock by an hour, but that also changes the simulated UTC and everything tied to it.
For flights intended to follow real-world time, the downloadable FS Real Time synchronisation utility and World Time Zones data can synchronise FSX with real UTC and correct regional boundary errors. Do not run it during historical scenarios or intentional time acceleration, and avoid stacking it with another world time-zone replacement.
Why does the wrong time return after loading a flight?
Saved FSX flights can restore their recorded date, time and location instead of using the clock you just configured. Load the flight, correct its time, then save it under a new name; if an old flight loads automatically, replace it as the default only after confirming the new settings.
An add-on may also rewrite the clock after loading. If the corrected value immediately changes, test the same aircraft and airport without any utility that manages time or restores a saved scenario.
Does incorrect local time affect AI traffic and daylight?
Incorrect UTC can shift AI traffic and the simulated position of the sun, while a wrong local-time label caused only by bad zone data may leave the underlying UTC correct. FSX flight plans schedule AI movements in UTC, not airport local time; our guide to UTC in FSX AI schedules explains the conversion and daylight-saving trap.
What if only the cockpit clock is wrong?
A wrong panel clock does not necessarily mean FSX’s global time is wrong. Some aircraft clocks display UTC, some have a local/UTC selector, and custom gauges may keep their own offset. Compare the gauge with the Time and Season window; if the simulator values are correct, troubleshoot the aircraft clock rather than changing global time.
Is the fix different in FSX: Steam Edition?
The time calculation and diagnosis are essentially the same in boxed FSX and FSX: Steam Edition. Add-on installation paths can differ, however, so use instructions written for the active edition and keep a backup before installing replacement time-zone data.