Why does the FS2004 Boeing 737 autopilot miss approaches?

The FS2004 Boeing 737 autopilot usually misses an approach because it is following GPS instead of NAV1, the ILS frequency or front course is wrong, or the aircraft reaches the localiser too high, too fast or at a poor angle. The default 737-400 cannot automatically fly and descend on every GPS approach.

This applies directly to the stock FS2004 Boeing 737-400. Add-on 737 panels may replace the default autopilot, navigation source selector or GPS with their own FMC logic, although the same tuning and interception checks still apply.

What usually causes the autopilot to miss the approach?

The cockpit indications normally reveal whether the fault is incorrect tuning, poor capture geometry or an expectation the default autopilot cannot meet.

If the MCP modes themselves are unclear, our practical explanation of Boeing 737 autopilot controls covers heading, altitude, speed and approach-mode behaviour.

How do I make the FS2004 737 capture an ILS?

A successful FS2004 ILS capture requires a valid NAV1 signal, NAV selected as the guidance source and a stable interception from below the glideslope.

1. Confirm that the runway has an ILS. Use FS2004's own airport or map information rather than relying only on a modern real-world chart. The simulator's navigation database reflects an older period, and some runways have no ILS or only a localiser.
2. Tune the active NAV1 radio. Enter the correct ILS frequency, transfer it from standby if necessary and set the published inbound front course. Tuning NAV2 will not provide the expected approach guidance to the stock autopilot.
3. Select NAV rather than GPS. Use HDG mode to turn towards the final approach course. Do not expect APP to make a large turn from an arbitrary GPS waypoint.
4. Intercept from below. Approach the localiser level at the cleared or planned intercept altitude, with the glideslope indication above the centre. Capturing a glideslope from above is unreliable and may leave the aircraft in altitude hold.
5. Reduce speed and configure early. A fast, clean 737 can cross the localiser before the autopilot establishes the turn. Set a sensible approach speed and begin flap and landing-gear configuration before the final segment.
6. Arm approach mode. Press APP when the localiser signal is alive and the aircraft is on a reasonable intercept. Altitude hold should remain active until glideslope capture, at which point the approach mode should command the descent.
7. Monitor the needles and mode state. An armed mode is not the same as a captured mode. Disconnect the autopilot and correct manually if the aircraft crosses the localiser, remains above the glideslope or commands an unsafe turn.

Our complete Boeing 737 ILS sequence covers the flight from localiser interception through final approach. The stock FS2004 737-400 does not model a complete certified autoland and rollout system, so plan to disconnect and hand-fly the flare and landing.

Why does the GPS approach not make the 737 descend?

GPS mode in the default FS2004 737-400 provides lateral route guidance but does not supply the modelled VNAV capability needed to fly an automatic vertical approach profile.

Loading an approach into the GPS adds approach fixes, but it does not make every procedure equivalent to an ILS. A vectors transition may also expect you or ATC to position the aircraft rather than directing the autopilot automatically onto final.

• For an ILS approach, descend and position the aircraft using altitude and heading modes, then change from GPS to NAV for localiser and glideslope capture.
• For a localiser-only approach, the autopilot can provide lateral guidance, but you must manage the published descent and minimum altitude.
• For a GPS, VOR or NDB approach, expect to control the vertical profile yourself unless a particular add-on aircraft explicitly models that capability.

If the aircraft reaches final too high or too fast, use our 737 descent and approach setup workflow to plan the energy reduction before localiser interception.

What if the setup is correct at an add-on airport?

An add-on airport can cause a missed or offset approach when its runway layout, AFCAD data and ILS beam do not match.

Compare the tuned frequency with the information available inside FS2004 and any documentation supplied with the airport. A present-day frequency may differ from the one represented by FS2004, while duplicate airport files can place runways, thresholds and navigation aids in conflicting positions.

If the localiser needle centres and the autopilot follows it accurately but the aircraft tracks beside the runway, the autopilot is probably working. The likely problem is an offset localiser, changed runway geometry or conflicting scenery data. Temporarily disable the add-on airport or duplicate AFCAD entries and repeat the approach at the stock airport.

How can I isolate the exact failure?

A controlled test with the default aircraft separates autopilot faults from route, aircraft and scenery problems.

1. Use the stock FS2004 Boeing 737-400 at a default airport with a known ILS.
2. Select clear, calm conditions and intercept using heading mode rather than a GPS flight plan.
3. Tune NAV1, set the front course, select NAV and approach the localiser from below at a shallow angle.
4. Watch the localiser and glideslope indications before arming APP.

No moving needles indicate a frequency, coverage or scenery problem. Moving needles without capture point to the navigation source, autopilot mode or intercept geometry. If the stock aircraft captures normally but an add-on 737 does not, inspect that aircraft's panel, gauges and documented mode logic rather than changing the airport.