Record the aircraft configuration
Before flight, identify the X-Plane build, aircraft base and update, livery, navigation-data cycle, applicable plugins, checklist revision and initial aircraft state. Record the active configuration. Do not change the aircraft installation or navigation database during an active flight. Use a compatible base aircraft package and updates. The installation reference prohibits combining incompatible bases or using the default Laminar aircraft as the installation base. Initial installation includes a launch to build supporting navigation databases. Saved situations from another aircraft version require separate compatibility assessment. Apply the installation reference’s simulator configuration: downwind ILS disabling unchecked, controllers calibrated, X-Plane failures off, and this aircraft excluded from the AI-aircraft list. Any intended fault condition must be part of the assigned scenario.Aircraft options
The following options affect procedure applicability or control behavior. Obtain the selected values before beginning an affected procedure.
Use a configuration compatible with the required checklist settings. Permanently open guards cannot satisfy Guard closed. An AUTO-labelled engine-start installation must have an explicit applicable interpretation before using an OFF requirement; do not substitute AUTO without that interpretation.
Fuel, payload and balance
Use the aircraft EFB or a specifically supported loading integration. Do not use the Laminar Weight, Balance & Fuel window for this aircraft. For the documented fuel-truck process, engines must not be running, the aircraft must be stationary with parking brake or chocks applied, the fuel request must be entered, and refuel time must be REAL or LONG. Enter the request in the Fuel, Payload and CG window and initiate the truck process from the associated service window. Verify actual fuel after loading; the requested quantity is not evidence of fuel on board. The EFB example accepts10.0 or 10000 for the same 10,000 kg request. This is EFB keypad syntax only. It does not define an MCP request body or establish an additive-fuel API.
Account for baggage when loading passengers. Passenger-only manual, autofill and random methods do not include passenger bags automatically. Absolute-payload autofill distributes both passengers and cargo. Verify the resulting weights and CG against the selected aircraft’s limits and envelope. Do not use reference-screen example weights as flight targets.
Performance data
Use the FMC entry and verification workflow to check displayed approach-reference values. A VREF entry alone does not establish that the available runway is long enough. Obtain takeoff and landing performance for the actual runway, conditions, weight and configuration. Maintain the source and applicability of each value. The EFB reference marks its takeoff-performance window “not yet functional”. The later installation reference specifies the separate 737simpleOPT plugin to enable the performance calculator. Establish the installed calculator capability before relying on an output. The documented landing-performance calculation requires completion of its input page before the result page becomes available. Inputs include runway, conditions, wind, temperature, pressure, landing weight, flap, air-conditioning, anti-ice, braking and VREF addition. Runway condition and reverse-credit selections are linked in the referenced edition. Review the required landing length and any result outside the landing parameters. When PLAN/FUEL is installed, pre-start gross weight can use planned fuel and then change to final fuel at engine start without a takeoff-speed-change warning. Reconcile the actual fuel, weight and affected takeoff data after engine start.Ground services
Airside Services accepts imported OFP data or manual passenger, cargo and fuel entries. Activation can connect jetways or stairs, operate doors, call the fuel truck, load cargo and board passengers. Confirm the state of each relevant service before aircraft movement. The referenced OFP export isb738x.xml in X-Plane 12/Output/FMS Plans. Boarding depends on the configured NO SMOKING/CHIME option and the required switch change after service activation. At arrival, anti-collision OFF can initiate deboarding and cargo unloading. Account for these side effects when operating the associated switches.
Ground Services includes physical GPU, chocks, Better Pushback, ASU, de-icing, stairs and external doors. The physical GPU connection is separate from the electrical-panel GPU switch. At supported gates, ground power can connect automatically and disconnect approximately 15 seconds after the APU generators are connected to the bus.
Door indications distinguish closed, moving, open and locked states. Starting either engine locks the ordinary external doors; unlocking at arrival requires both engines shut down. Do not use an earlier door indication as current clearance.