Learn how to use a PMDG 737 checklist in MSFS: flows, phase order, EFB and PDF options, manual checks, and fixes for unticked items.
Use a PMDG 737 checklist as a verification tool, not a click-by-click start-up script. In Microsoft Flight Simulator, complete the cockpit flow for each phase, open the matching checklist in the PMDG tablet or a PDF, read each challenge, confirm the actual switch or indication, and only then mark the item complete.
Where is the PMDG 737 checklist in MSFS?
The available checklist depends on your installed PMDG package and aircraft build. Do not assume there must be a fully interactive list in the Microsoft Flight Simulator Checklist panel.
| Checklist source | Best use | Main limitation |
|---|---|---|
| PMDG tablet or EFB | Keeping the checklist inside the virtual cockpit | Checklist availability and automatic checking can vary by build |
| MSFS Checklist panel | Convenient toolbar access and basic prompts | Some custom PMDG controls may not register or tick automatically |
| PDF or printed 737NG checklist | Realistic flows, second-screen use and learning phase order | It cannot detect the aircraft state, so every response must be checked manually |
If you are choosing between these formats, our comparison of in-sim and external checklist tools explains when each approach works best.
How should you run each PMDG checklist?
Run each normal checklist after completing the associated cockpit flow, using the challenge-and-response method even when flying alone.
- Match the checklist to the aircraft. The PMDG aircraft represents the 737NG family, so use an NG checklist rather than one for the 737 MAX or Classic. Check that it suits your variant, fitted options and chosen operating procedure. An older phase-by-phase PMDG NGX checklist can help with sequence, but it was written for FSX/P3D and should be checked against the documentation supplied with the MSFS aircraft.
- Start from the correct panel state. A cold-and-dark flight begins with preflight and power-up work, while a runway-ready state has already completed most early checks. If joining midway, verify the critical earlier items rather than assuming the saved state is correct.
- Complete the flow first. Move around the overhead, main panel, pedestal and FMC in a consistent order. Our explanation of the 737 cockpit flow and verification method shows why the checklist follows the flow instead of replacing it.
- Read and verify each item. Read the challenge, locate the actual control or indication, and confirm the stated response. A switch position alone may not be enough; check the associated light, gauge or system indication where applicable.
- Correct discrepancies immediately. Set the item correctly, verify the resulting indication and repeat that checklist line. Never tick an item merely because the expected response is printed beside it.
- Finish before workload rises. Complete the relevant phase before pushback, take-off, descent or final approach. Do not leave routine checklist reading until the take-off roll or a busy point on final.
What order do PMDG 737 checklists follow?
A typical PMDG 737 flight uses the following phase order, although exact names and checklist divisions vary between operating procedures.
| Checklist phase | Usual trigger | What it broadly verifies |
|---|---|---|
| Preflight | After power-up and cockpit preparation | Power, safety equipment, instruments and initial FMC set-up |
| Before Start | Before pushback or engine start | Take-off data, MCP settings, trim, doors and start readiness |
| Before Taxi | After both engines have stabilised | Electrical supply, pneumatics, anti-ice and taxi configuration |
| Before Takeoff | At the holding point or runway entry | Flaps, trim, speedbrake, transponder and cabin readiness |
| After Takeoff | After gear and flap retraction | Clean configuration and climb systems |
| Descent | Before top of descent | Landing data, briefing and pressurisation settings |
| Approach | After configuring the approach | Altimeters, minimums and approach references |
| Landing | Once established in landing configuration | Gear, flaps, speedbrake and engine start-switch configuration |
| Shutdown and Secure | At the stand | Fuel, lights, electrical power and aircraft securing |
Some procedures split the Before Takeoff checklist at a line. Complete the first portion at the holding point and the remaining items when the required conditions are met; do not combine sections from two different checklists.
Why does the MSFS checklist not tick PMDG items?
Automated ticks often fail because the PMDG 737 uses custom systems that the default MSFS checklist evaluator may not recognise.
- Manual completion may be intentional. Many tablet and PDF checklists expect the pilot to verify and tick each item.
- The simulator may be watching the wrong variable. If the cockpit indication is correct but the MSFS item remains incomplete, verify it manually rather than moving controls to chase a green tick.
- A hardware binding may be overriding the cockpit. Duplicate assignments and permanently held toggle switches can move a PMDG control back immediately after you set it.
- Assistance can interfere. AI piloting or checklist assistance may alter lights, radios, fuel controls or other settings after your flow.
- The panel state may have loaded after the checklist. Reopen or reset the checklist after selecting the intended aircraft state. If tablet functions are missing or broken, update the PMDG aircraft through its supported installation method and reload the flight.
Can a checklist teach the PMDG 737 cold-and-dark start?
No. A normal checklist verifies completed work; it does not contain every action needed to power, programme and start the aircraft safely. Learn the detailed procedure with our switch-by-switch PMDG cold-and-dark start sequence, then use the normal checklist to catch omissions.
If a caution, warning or system failure appears, stop using the normal checklist as a troubleshooting script. Stabilise the aircraft and use the appropriate PMDG non-normal procedure; a generic normal checklist is not a substitute for failure guidance.