Learn every PMDG 737 EFIS control in MSFS, with practical settings for departure, cruise and ILS approaches plus missing-display fixes.
The PMDG 737 EFIS control panel configures the PFD and navigation display in Microsoft Flight Simulator. Select an ND mode and range, add only the overlays you need, set barometric pressure and approach minimums, then verify the result on your side’s displays. It changes presentation; it does not steer the aircraft.
What does each PMDG 737 EFIS control do?
The panel divides into PFD settings, navigation-display formats and optional map overlays. The captain’s and first officer’s panels normally control their respective displays, so their modes, ranges, pressure settings and minimums can differ.
| Control | Function | Practical use |
|---|---|---|
| MINS RADIO/BARO | Selects radio-altimeter or barometric minimums. Turn the adjacent knob to set the value. | Use the reference specified by the approach procedure and operating practice. RADIO is based on height above terrain; BARO uses barometric altitude. Pressing RST resets the minimums alert after it has triggered rather than simply erasing the selected value. |
| BARO IN/HPA | Selects inches of mercury or hectopascals and sets the altimeter pressure. | Set the reported local pressure below the applicable transition level. Push STD when standard pressure is required, then confirm the PFD shows STD. |
| FPV | Adds the flight-path vector to the PFD. | Useful for seeing where the aircraft is actually travelling. It is not the flight director and does not command pitch or roll. |
| MTRS | Adds metric altitude information to the PFD. | Use when an ATC clearance or procedure provides altitudes in metres; otherwise it can remain off. |
| VOR/ADF selectors | Displays bearing pointers from the selected VOR or ADF receivers. | The associated receiver must be tuned and receiving a valid signal. Selecting a pointer does not tune the station. |
| APP | Shows an expanded approach presentation on the ND. | Useful for localiser and ILS tracking. This EFIS selection is separate from the MCP APP button. |
| VOR | Shows an expanded VOR course presentation. | Choose it when tracking or cross-checking a VOR course. |
| MAP | Shows the normal moving-map route display. | This is the usual mode for departure, en-route flight and most arrivals. |
| PLN | Shows the FMC route in a north-up plan format. | Use it on the ground to inspect every leg. The CDU LEGS page STEP prompt moves the display through the route. |
| CTR | Toggles between expanded and centred formats where available. | Centred MAP gives more context behind the aircraft; the expanded format gives more space ahead. PLN has its own centred presentation. |
| RANGE | Changes the ND scale, commonly from 5 to 640 NM depending on the fitted panel. | A smaller range gives local detail; a larger range gives strategic route context. Some symbols are intentionally removed at larger scales. |
| TFC | Requests the TCAS traffic overlay. | Traffic also depends on the transponder/TCAS mode and the simulator’s available traffic data. |
| STA, WPT and ARPT | Add navigation stations, waypoints and airports. | Use them selectively. Enabling every overlay can obscure the route and traffic symbols. |
| DATA and POS | DATA adds FMC route information such as waypoint constraints; POS adds position-reference information. | DATA helps when checking restrictions. POS is primarily a navigation-source cross-check. |
| WXR and TERR | Request weather-radar or terrain shading. | The underlying aircraft systems must be operating and supported. Weather and terrain overlays are normally mutually exclusive. |
For help interpreting the resulting colours, pointers, deviation scales and annunciations, use our 737 PFD and navigation-display symbol reference.
How should I set the EFIS panel for each flight phase?
Use MAP for most of the flight, adjusting range to match the amount of detail needed and selecting APP, VOR or PLN only for a specific task.
- Power and align the aircraft. The displays need electrical power, while a usable moving map requires valid navigation position data. Follow our PMDG power-up and IRS-alignment sequence when starting from cold and dark.
- Set barometric pressure. Select IN or HPA, enter the local setting and compare both pilots’ altimeters. Change to STD at the transition altitude specified for the flight, not at one assumed universal altitude.
- Select MAP and a useful range. Around 10–20 NM gives departure detail; 40–160 NM is often more useful in cruise; 10–40 NM restores detail for an arrival. These are practical starting points rather than mandatory settings.
- Add only necessary overlays. ARPT can help around the terminal area, DATA exposes route restrictions, and TERR provides terrain awareness. Reduce the range if a selected symbol category appears to be missing.
- Check the FMC route. EFIS displays the route supplied by the FMC but does not create one. Activate and execute the route, clear unintended discontinuities and inspect it in PLN mode using the LEGS page STEP prompt. Our 737 FMC route-programming walkthrough covers that process.
- Set approach minimums before the approach. Select BARO or RADIO exactly as required, dial the published value and verify it on the PFD rather than trusting the knob position alone.
A mistake we see constantly is treating range as ordinary graphical zoom. It also affects decluttering, so airports, stations and waypoints can disappear at wider scales even though their overlay buttons remain illuminated.
How do I use EFIS for an ILS approach?
For an ILS, set local pressure and the correct minimums, confirm the ILS is tuned, then choose APP for an expanded localiser presentation or retain MAP when route and missed-approach context is more useful.
- Set QNH and minimums. Use BARO or RADIO according to the charted minima and operating procedure.
- Tune and identify the ILS. Confirm the frequency, front course and received identification where applicable. Selecting EFIS APP neither tunes the ILS nor captures it.
- Select the display. APP with a short range gives a clear localiser picture. MAP can be preferable when monitoring turns onto final or the missed-approach routing.
- Arm the aircraft’s approach modes separately. The APP button on the MCP arms the autopilot/flight-director localiser and glideslope modes; the APP position on EFIS only changes the ND format. Our PMDG 737 autopilot operating guide explains the MCP and flight-mode annunciator logic.
- Verify the indications. Check the PFD flight-mode annunciator, localiser and glideslope pointers, selected minimums and barometric setting. Do not use the illuminated EFIS button as evidence that the approach is armed or captured.
Why is the EFIS display blank or missing data?
Most PMDG 737 EFIS faults come from missing power, incomplete IRS alignment, an unexecuted FMC route, display decluttering or an aircraft system that has not been switched on.
- Entire PFD or ND blank: check aircraft electrical power and the relevant display brightness control. EFIS mode selections cannot illuminate an unpowered or fully dimmed display.
- MAP or position warning: complete IRS alignment and ensure the FMC has valid position data. The alignment time and required inputs depend on the aircraft state and PMDG configuration.
- No magenta route: activate and execute the FMC route. Check for discontinuities, an empty active leg or a route entered only in the MSFS planner rather than the aircraft FMC.
- Missing airports, stations or waypoints: press the appropriate overlay button and select a smaller range. ND decluttering deliberately suppresses detail at wider scales.
- No VOR or ADF pointer: confirm the EFIS pointer source, receiver frequency and station reception. The source may be out of range even when correctly tuned.
- No ILS guidance: verify tuning, course, aircraft position and signal reception. EFIS APP changes the display but does not tune the receiver or arm LOC and G/S.
- No WXR or TERR image: confirm the corresponding aircraft system is available and operating. Simulator and add-on limitations can prevent weather returns even when WXR is selected; choosing TERR may also remove WXR.
- No traffic symbols: set the transponder/TCAS to an operating mode, press TFC and confirm that MSFS is supplying traffic. EFIS cannot display traffic that the simulation has not injected.
- Only one pilot’s side looks wrong: inspect that side’s EFIS panel, pressure setting, minimums and brightness controls. The two sides are designed to be configured independently.
Exact controls and available overlays can vary slightly between PMDG 737 variants and fitted aircraft options, but the operating logic remains the same: establish valid aircraft systems first, select the required display format, and verify the indication on the PFD or ND.