Why won't the rudder steer my aircraft in FlightGear?
In FlightGear, the rudder controls yaw; it does not steer an aircraft through an airborne turn by itself. Bank with the ailerons and coordinate with rudder. If the problem occurs while taxiing, verify the rudder-axis assignment, remove duplicate bindings, and check whether that aircraft uses nosewheel steering, a free-castoring wheel or differential brakes.
Does the rudder turn a FlightGear aircraft in the air?
In normal flight, the rudder points the nose left or right around the yaw axis, while the ailerons bank the aircraft and produce the turn. Rudder alone usually creates a sideslip rather than a properly coordinated change of direction.
Use aileron to establish the bank, then apply enough rudder to keep the turn coordinated. Rudder becomes especially noticeable during crosswind correction, engine-out flight and spin recovery, but it is not a substitute for banking.
At very low speed, an aerodynamic rudder also has little authority because there is little airflow over it. Propeller slipstream may help on some aircraft, but FlightGear models this according to the individual aircraft and flight-dynamics model.
How can I tell whether FlightGear is receiving rudder input?
The quickest diagnosis is to check the controller, FlightGear assignment and visible rudder movement in that order.
- Test the hardware outside FlightGear. Confirm that the rudder or twist axis moves smoothly from one end to the other and returns to centre. Windows users can test the joystick or pedal axes before opening the simulator. If the axis is missing, jumping or off-centre there, FlightGear cannot correct it.
- Open FlightGear's controller configuration. The screen and wording vary between releases and operating systems, but the physical pedal or twist axis must be assigned to rudder. Bind only one axis to that function.
- Check direction and centring. Pressing the left pedal should move the rudder's trailing edge left and yaw the nose left once there is airflow. Reverse the axis only if it moves in the wrong direction; recalibrate if it does not settle near centre.
- Remove competing inputs. A gamepad, joystick twist grip and rudder pedals can all send rudder commands at once. Unplug unused controllers or clear their duplicate rudder bindings. Also check that the same axis has not accidentally been assigned to a brake or another flight control.
- Test without assistance. Disconnect the autopilot and yaw damper, and temporarily disable auto-coordination. These systems can move or mask the rudder while you are trying to identify the raw input.
- Compare with keyboard input. Use the standard bindings to deflect and centre the rudder; our guide lets you check FlightGear's keyboard rudder commands. If the keyboard works but the pedals do not, the fault is in the hardware assignment rather than the aircraft model.
If the pedals remain dead, reversed or erratic after these checks, work through the wider rudder-pedal fault checklist for calibration, duplicate axes and controller conflicts.
Why does the rudder move but not steer while taxiing?
A moving rudder surface does not guarantee ground steering because FlightGear aircraft can model the nosewheel, tailwheel and brakes separately.
| What you see | Likely explanation | What to do |
|---|---|---|
| Rudder moves, but the wheel does not | The aircraft uses a separate tiller, a free-castoring wheel or differential braking | Use the aircraft's steering control or left and right brakes rather than expecting the rudder surface to turn the wheel |
| Wheel turns, but the aircraft stays straight | The aircraft is stationary, a brake remains applied or the wheel-steering model is not engaging | Release the parking and toe brakes, begin rolling slowly, then retest with modest steering input |
| Aircraft pulls strongly to one side | A toe-brake axis may be reversed or failing to return to its released position | Check both brake-axis indicators and reverse or recalibrate the affected side |
| Pedals produce only a small steering angle | The model may limit pedal-controlled nosewheel movement | Use the tiller for tight turns if the aircraft implements one; pedal steering may be intended only for small corrections |
Taildraggers may have a lockable or partially free-castoring tailwheel and often need differential braking for tight turns. Larger aircraft commonly use a tiller for substantial nosewheel movement. These details depend on how faithfully the FlightGear aircraft package implements its ground-handling system.
Why is only one FlightGear aircraft affected?
If rudder and ground steering work in a simple bundled aircraft, the global controller assignment is sound and the affected aircraft's systems or modelling are the likely cause.
- Flight-control or gust lock: release it before testing control movement.
- Hydraulic power: a complex aircraft may not move powered controls until the appropriate systems are operating.
- Steering or tailwheel lock: check whether the model provides a separate lock or tiller control.
- Autopilot, yaw damper or auto-coordination: disconnect them for a clean manual-control test.
- Aircraft-specific configuration: an add-on may define steering differently or contain an incomplete flight-dynamics model.
Test the affected aircraft with its systems powered, flight controls unlocked and assistance disabled. If FlightGear shows valid rudder input but neither the control surface nor wheel responds, while another aircraft works correctly, the problem lies with that aircraft package rather than the pedals.