Learn how to take off in FlightGear: set power, steer with rudder, rotate at the right speed, establish a climb and fix common problems.
To take off in FlightGear, start on a runway with a simple trainer, release the parking brake, apply full power smoothly and keep straight with rudder. In the Cessna 172, gently raise the nose at about 55 KIAS, then climb at roughly 70–80 KIAS. Other aircraft require their own speeds.
FlightGear take-off procedure
The easiest reliable first take-off is from a long runway in calm weather using a Cessna 172 or another basic trainer.
- Choose simple conditions. Start on a runway rather than at a parking position, with daylight, good visibility and little or no crosswind. If basic handling is unfamiliar, our advice on setting up and practising a first simulator flight will help.
- Check the controls. Confirm that pitch, roll, rudder, throttle and brakes respond in the correct direction. Centre the controls and make sure no second device is sending unwanted inputs. A joystick or gamepad is much easier to control precisely; our comparison of simulator control options explains the practical differences.
- Set the aircraft for take-off. Use take-off or near-neutral trim, retract spoilers, and set the flaps prescribed by the aircraft checklist. A normal Cessna 172 take-off generally uses flaps up. Use full-rich mixture near sea level; at a high-elevation airport, lean as required for maximum engine power.
- Line up on the centreline. Point the nose straight down the runway, release the parking brake and hold position with normal wheel brakes only if necessary. Avoid starting with the rudder already displaced.
- Apply take-off power. Advance the Cessna's throttle smoothly to full power, then release the brakes. Other aircraft may have a specified take-off power limit. Check that the engine develops normal power and that the airspeed indicator begins increasing.
- Steer with rudder. Make small rudder corrections to remain on the centreline. Aileron controls bank, not ground direction; trying to steer with it is a mistake we see constantly. Nosewheel steering arrangements vary between FlightGear aircraft, but the rudder becomes increasingly effective as speed builds.
- Rotate gently. At about 55 KIAS in a normally loaded Cessna 172, apply light back pressure and raise the nose gradually. Do not pull the control fully back or force the aircraft into the air.
- Establish the climb. Hold roughly 70–80 KIAS in the Cessna by adjusting pitch, keep the wings level and follow the runway heading. Once the climb is stable, trim away sustained control pressure.
Which FlightGear controls are needed for take-off?
The essential controls are throttle, elevator, aileron, rudder and wheel brakes. On the common default desktop mapping, Page Up increases throttle and b applies the wheel brakes, but customised profiles, compact keyboards and Num Lock can affect key behaviour.
If using the mouse, put it into FlightGear's flight-control mode rather than leaving it in pointer or view mode. Check our reference for FlightGear throttle, steering, brake and flight-control keys if an input does nothing.
Keyboard-only flying is possible, but each key press can produce a coarse control change. Tap rather than hold directional keys, and avoid rapid corrections in opposite directions.
How fast should you take off in FlightGear?
There is no universal FlightGear take-off speed because rotation speed depends on the aircraft model, weight, flap setting and operating procedure.
For a typical Cessna 172 simulation, about 55 KIAS is a sensible rotation target, followed by a climb near 70–80 KIAS. Treat these as practical training figures rather than speeds for every Cessna variant or loading condition. Jets, warbirds and heavy aircraft require their own checklist speeds.
Read the indicated airspeed, not groundspeed. A headwind reduces the groundspeed and runway distance needed to reach a given indicated speed, while a high-altitude or hot-weather departure usually requires a longer ground roll.
Why will the aircraft not take off?
Most failed FlightGear take-offs come from an active brake, insufficient airspeed, a reversed elevator axis or an aggressive rotation.
| Symptom | Likely cause | What to check |
|---|---|---|
| The aircraft barely moves | Parking brake applied, a brake axis stuck on, low power or the simulation paused | Release the parking brake, inspect brake inputs and confirm that the throttle reaches its full range. |
| It veers off the runway | Too much rudder, crosswind, propeller effects or a noisy brake/rudder axis | Use small rudder inputs, begin in calm weather and add a control dead zone if the input flickers. |
| The nose will not rise | Insufficient indicated airspeed, nose-down trim, reversed elevator or deployed spoilers | Accelerate to the model's rotation speed and verify elevator movement. See our detailed checks for diagnosing an aircraft that will not rotate. |
| It lifts off and immediately stalls | Rotation was too early or the nose was raised too far | Lower the nose enough to regain the recommended climb speed, then use smaller pitch corrections. |
What should you do after liftoff?
After liftoff, use pitch to maintain the aircraft's climb speed, keep the runway heading and make only small corrections. Confirm a positive climb before retracting the landing gear on a retractable aircraft; the Cessna 172 has fixed gear.
Retract take-off flap in stages and only at the speed and height specified for that model. Do not immediately pull the power back simply because the aircraft is airborne—maintain the prescribed take-off or climb power until the aircraft checklist calls for a reduction.