How do I fly the Zibo 737-800 in X-Plane 12?
To fly the Zibo 737-800 in X-Plane 12, configure its tablet and controls, power the aircraft, align the IRS, programme the FMC, start the engines, then use the MCP for take-off, climb, cruise, descent and approach. Learn it in stages: this model expects realistic Boeing procedures and punishes skipped configuration steps.
What should I set up before my first Zibo flight?
Before your first Zibo flight, verify the installation, calibrate every control axis and assign the essential Boeing commands.
The Zibo must be installed as its own aircraft rather than overwriting X-Plane's default 737. If the cockpit contains missing displays, dead switches or error messages, check the correct X-Plane 12 package and update layout before troubleshooting the aircraft itself.
Calibrate the joystick or yoke, rudder pedals and throttles in X-Plane, then check for duplicate assignments. At minimum, bind:
- Pitch, roll, rudder and toe brakes
- Both throttle levers
- Pitch trim
- Flaps, landing gear and speedbrake
- TO/GA and autopilot disconnect
- Reverse thrust or individual reverser commands
Use the Zibo tablet to review hardware, realism and aircraft-state options available in your installed build. Throttle noise, an uncentred trim axis or two devices controlling the same function can disconnect the autopilot or make the autothrottle fight your hardware.
How do I fly the Zibo 737 from cold and dark?
A complete Zibo flight follows the same broad sequence as the real 737: establish power, align navigation systems, programme the FMC, start the engines, configure the MCP, then fly and monitor each phase.
Establish electrical power. Switch on the battery and place standby power in its normal automatic position. Connect external power through the tablet when available, or start the APU and place its generators on the electrical buses.
Align the IRS. Move both IRS selectors to NAV, open the FMC position-initialisation page and copy a valid GPS position into the IRS position field. Keep the aircraft stationary while alignment completes; LNAV, the map display and reliable heading information depend on it.
Programme the FMC. Enter the origin, destination and runway, build the route, select the departure and arrival, then activate and execute it. Our route-building and flight-plan workflow explains the planning stage, while the full Boeing 737 FMC entry sequence covers POS INIT, RTE, LEGS, PERF INIT, N1 LIMIT and TAKEOFF pages.
Inspect every waypoint and altitude constraint on the LEGS page. Delete a discontinuity only when the route should genuinely be continuous; one left for radar vectors may be intentional. Enter the take-off flap setting, centre of gravity and V-speeds, then set the stabiliser trim to the value calculated by the FMC.
Configure the MCP. Set the cleared altitude, initial heading and take-off speed, turn on both flight directors and arm the autothrottle. LNAV and VNAV may be armed before departure when the route and clearance support them; otherwise use HDG SEL and a suitable vertical mode after take-off.
Start the engines. Run the APU with its bleed-air supply available, switch the packs off for starting and open the pneumatic isolation path. Turn on only the fuel pumps appropriate to the fuel actually loaded; do not run centre-tank pumps with empty centre tanks.
Place an engine start selector at GRD. When N2 has reached a healthy, stable motoring value, move that engine's fuel control lever to IDLE and monitor N2, oil pressure, fuel flow and EGT. Repeat for the second engine, then restore the packs and normal isolation-valve position, place the engine generators online and shut down the APU when it is no longer needed.
Prepare for taxi. Set the take-off flaps and trim, check the flight controls, select appropriate hydraulic pumps and lights, and test the brakes as the aircraft begins moving. Taxi slowly; the 737 builds momentum quickly and requires advance planning for turns.
Take off. Line up, stabilise the engines at an intermediate thrust setting, then press TO/GA. Keep the aircraft on the centreline, call V1 and rotate smoothly at VR towards the flight-director command bars. Select gear up after a positive climb and follow the planned lateral mode.
Climb and cruise. Engage CMD only after the aircraft is stable and above the applicable minimum engagement height. Retract the flaps on schedule as speed increases, confirm VNAV or another vertical mode is controlling the climb, and keep the MCP altitude set to the altitude you are cleared to reach.
At cruise, monitor fuel, pressurisation, route progress and the active mode annunciations. The autopilot flies the instructions it has been given; it does not verify that the route, altitude or speed is sensible.
Set up the descent and approach. Enter the arrival and approach, check the resulting LEGS page, set landing performance and lower the MCP altitude before the top of descent. VNAV will not descend through an MCP altitude that remains above the aircraft.
For an ILS, tune and identify the correct frequency, set the inbound course and intercept the localiser from a suitable angle while below the glideslope. Arm APP only for a valid localiser-and-glideslope approach, not for an ordinary RNAV procedure. Our 737 descent and approach procedure covers path control, speed reduction and configuration in more depth.
Land and stop. Establish a stabilised approach with the landing gear down, landing flaps selected, speedbrake armed and autobrake set as required. Fly the FMC's VREF with an appropriate wind additive, flare gently near the runway and bring the thrust levers to idle. After touchdown, verify speedbrake deployment, apply reverse thrust and use braking to slow before leaving the runway.
How should I use LNAV, VNAV and the MCP?
Use LNAV and VNAV only when the FMC route and performance data are valid; use the MCP's basic modes when ATC vectors you or when the automated path is unsuitable.
- LNAV follows the active FMC lateral route. If the aircraft is not positioned to intercept it, use HDG SEL first.
- VNAV follows the FMC speed and altitude profile, subject to MCP altitude limits and programmed restrictions.
- HDG SEL flies the heading selected on the MCP and is the practical choice for vectors or route interception.
- LVL CHG changes altitude while controlling speed with pitch; thrust normally supplies or removes the required energy.
- V/S commands a selected vertical speed. Watch airspeed closely because an excessive climb or descent rate can leave too little energy.
- APP arms the localiser and glideslope modes for a correctly tuned ILS approach.
After every mode selection, read the flight mode annunciator at the top of the primary flight display. Green modes are active and white modes are armed. The FMA—not the button you pressed—is the authoritative indication of what the aircraft will do next.
Why won't LNAV, VNAV or the autopilot work?
When Zibo automation refuses to engage or behaves unexpectedly, the cause is usually incomplete FMC data, an MCP restriction, poor route geometry or conflicting hardware input.
| Symptom | Likely cause | What to check |
|---|---|---|
| LNAV will not arm or capture | The route is not activated, an EXEC change remains pending, or the active leg is behind the aircraft | Activate and execute the route, select the correct active leg and use HDG SEL to establish an intercept |
| VNAV is unavailable | Required performance information is missing | Check cruise altitude, weight, reserves, cost index, thrust limit and take-off entries |
| VNAV will not descend | The MCP altitude remains above the planned descent or the aircraft has not reached the descent point | Set the cleared lower altitude and confirm the top-of-descent marker and active FMA mode |
| CMD disconnects immediately | The aircraft is badly out of trim or a noisy control axis is overriding the autopilot | Trim the aircraft, centre the controls and remove duplicate or unstable axis assignments |
| Autothrottle hunts or throttles move unexpectedly | Hardware throttle input is continually overriding commanded movement | Recalibrate the levers and review the Zibo tablet's hardware-throttle options |
| Glideslope does not capture | The aircraft is above the glideslope, the ILS is mistuned or APP is not armed | Verify frequency and course, intercept from below and confirm LOC and G/S are armed on the FMA |
Should I start cold and dark or with the engines running?
Start with the engines running while learning to hand-fly, then add FMC and system procedures once basic aircraft control is comfortable.
| Starting state | Best used for |
|---|---|
| Runway, engines running | Take-off, landing, circuits, trim and basic handling |
| Gate, engines running | FMC practice, taxiing and autopilot mode training without a full start |
| Turnaround state | Learning route setup, passenger-to-cargo configuration and normal departure preparation |
| Cold and dark | Full electrical, pneumatic, hydraulic, IRS and engine-start procedures |
A productive learning order is manual circuits first, then MCP heading and altitude modes, followed by LNAV, VNAV, ILS approaches and finally complete cold-and-dark flights. Trying to learn the overhead panel, FMC, autopilot and landing technique on the same first flight makes it much harder to identify what went wrong.