Aircraft pulls or rolls when brakes are released? Learn what idle creep is normal and how to fix brake-axis, rudder and steering faults.
In a flight simulator, a slow, straight roll after brake release is often normal: jet or turboprop idle thrust can overcome tyre friction. A sideways pull is not the same thing. It usually points to unequal toe brakes, a duplicate or reversed axis, off-centre steering, wind, asymmetric thrust, or aircraft-specific ground handling.
This diagnosis applies to flight simulators generally. Setting names vary, but the first task is always to identify whether the aircraft is moving straight ahead, yawing sideways or physically banking onto one wing.
Is it normal for an aircraft to roll after brake release?
Yes. A slow, straight creep can be normal when the engines are running and the parking brake is released. Jet and turboprop idle thrust is often sufficient to start taxiing, while surface slope, aircraft weight and the simulator’s ground-friction model affect how readily movement begins.
Confirm that the cockpit throttle levers and engine indications show true idle. A hardware lever can be against its stop while poor calibration still commands some thrust. Turboprops add another complication: flight idle may produce appreciable thrust, while ground-idle and beta ranges depend on the aircraft.
| Symptom | Most likely explanation | First check |
|---|---|---|
| Rolls slowly and straight | Normal idle thrust or surface slope | Confirm true idle and repeat on level, fixed ground |
| Pulls as soon as brakes are released | One toe brake remains applied | Compare commanded left and right brake pressure |
| Turns with both brakes released | Rudder, tiller, nosewheel-steering or wind effect | Centre steering axes and remove duplicate bindings |
| Pull becomes stronger with power | Propeller effects, unequal thrust, wind or light brake drag | Compare engine indications and verify brake release |
| Occurs with one aircraft only | Aircraft-specific controls, failures or configuration | Test a built-in aircraft with the same controller |
| Occurs only on a carrier | Deck movement, slope or moving-platform contact model | Repeat the test on a fixed paved runway |
What is the difference between pull and roll?
A pull is a sideways veer or yaw, a forward roll is simple ground movement, and a true aerodynamic roll is rotation around the aircraft’s longitudinal axis. Simmers often use “pull and roll” for all three, but they require different fixes.
If the heading changes while the wings remain level, investigate brakes and steering. If the heading stays steady while the aircraft creeps forward, check idle thrust and surface slope. If a wing drops or the aircraft tips, suspect a locked wheel, excessive taxi speed, landing-gear damage or a scenery/contact-model fault.
Why does an aircraft roll at idle on an aircraft carrier?
An aircraft can creep at idle on an aircraft carrier after its brakes, chocks and tie-downs are removed, but pronounced sliding or turning may expose limitations in the simulator’s moving-deck physics.
A carrier’s steady forward speed alone should not leave the aircraft sliding backwards; the aircraft already shares the deck’s velocity. Carrier acceleration, deck pitch and roll, slope and wind over the deck can cause relative movement. Some simulators and carrier add-ons simplify tyre friction and collision contact, making the effect much stronger than it should be.
Do not assume that lowering a launch bar or positioning over a catapult restrains the aircraft. A holdback exists only when the simulation explicitly models and engages it. When parked, use the aircraft or carrier’s modelled chocks and tie-downs; when they are removed, brakes may be needed even at idle.
Test the same aircraft on a fixed, level runway. If the pull disappears there and returns on one carrier, the carrier deck or moving-platform model is the stronger suspect. If it follows the aircraft everywhere, continue with the controller checks below.
How do I stop the aircraft pulling after brake release?
Start with a controlled ground test, then isolate brake, steering, weather and aircraft variables one at a time.
- Establish a clean baseline. Use a level paved runway, calm weather and a built-in aircraft. Select true idle, centre the controls, disable automated taxi assistance and remove any modelled chocks, tow connection or ground lock before releasing the parking brake.
- Identify the motion. Watch the heading, nosewheel and wings. A turn towards one side indicates yaw; straight-ahead movement indicates idle creep; a wing drop is a separate contact or stability problem.
- Check commanded brake pressure. Use cockpit brake indications, pedal animation or the simulator’s controller-input display where available. Both left and right brakes must be fully released. Controller menus do not all represent released axes with the same numerical value, so verify the resulting brake command rather than assuming that released must display as zero.
- Verify each toe-brake axis. Press and release the pedals independently. If pressing a pedal releases that brake, reverse the axis. If a brake flickers near its released endpoint, calibrate it before adding a small dead zone. On PC, our guide shows how to check both toe-brake axes and their released positions in Windows.
- Remove duplicate and combined assignments. Inspect every connected pedal set, joystick, yoke, throttle, gamepad and keyboard profile. Separate toe pedals should normally have independent left- and right-brake axes; remove unintended combined-brake, parking-brake and duplicate axis bindings. If moving the yoke, stick or throttle changes brake pressure, use these checks to trace brake cross-talk from another flight control.
- Centre the steering controls. Check rudder, tiller and dedicated nosewheel-steering axes for offset, reversal and duplicate assignments. Some aircraft connect the rudder pedals to the nosewheel, others require a tiller, and free-castoring nosewheels rely heavily on differential braking. Our explanation of aircraft-specific taxi steering and differential-braking methods covers those differences.
- Test what the fault follows. Restore your normal weather, aircraft, airport or carrier and controller profile separately. A fault affecting every aircraft usually points to hardware or global bindings. One affected aircraft suggests custom steering logic, failures or an aircraft-specific profile; one affected location suggests scenery or moving-platform contact physics.
A button can create the same problem as an axis. A trigger may be assigned to the left brake alone, a parking-brake toggle may remain latched, or a gamepad control may be held against another object. A dragging left brake normally yaws the aircraft left; a dragging right brake yaws it right.
Why does the aircraft pull only when power is increased?
A pull that begins only as power rises is more likely to involve propeller effects, wind or unequal engine thrust, although a light brake drag should still be ruled out first.
Single-engine propeller aircraft can yaw because of slipstream, P-factor, torque-related effects and, in taildraggers, gyroscopic effects as the tail rises. The direction and strength depend on propeller rotation, aircraft design and phase of the take-off roll; not every aircraft necessarily pulls left. Our guide to left-turning forces and corrections during take-off explains when rudder input is normal rather than a controller workaround.
In multi-engine aircraft, compare the cockpit throttle positions and engine indications instead of relying only on the hardware levers. Separate throttle axes can have mismatched endpoints, causing one engine to spool up before the other. Crosswind can also make the aircraft weathercock, especially with a free-castoring nosewheel or tailwheel.
Do not use rudder trim to hide a brake or steering fault. It may make the ground track look straighter while leaving the aircraft badly out of trim after lift-off.
What if the aircraft banks or tips when the brakes are released?
A genuine wing drop or ground tip is not normal idle rolling and should be treated as a wheel-contact, landing-gear, speed or scenery problem.
Likely causes include one locked wheel, an abrupt steering input at excessive taxi speed, damaged landing gear, a rough terrain seam or incorrect wheel contact points in an add-on aircraft. On a carrier, a wheel can also catch a deck-edge or collision boundary that is not visible from the cockpit.
Test the aircraft on a standard paved runway, then test a different built-in aircraft at the original location. If the problem follows one aircraft, inspect its failures, model and configuration. If several aircraft tip at the same location, the airport or carrier surface is the stronger suspect. If everything is affected everywhere, return to the brake and steering assignments.