Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Autobrake Disengage on Touchdown

Featured Replies

I have had a repeated problem with the autobrakes on my MD11. As soon as the aircaft touches down, the autobrakes disenagage. I have CH pedals with tow brakes - could the sensitivities be too high ? Any ideas would be appreciated.ThanksRichard Foreman

the autobrakes disengage when you press the pedals for manual braking action.With CH pedals it must be an interference...there was some posts about it in the past.Try to search them with "search" function...Cheers,

Paolo Fumagalli

 

"Everyday is a new flight, with new system to learn, new failures to prevent and new database to update..."

 

100199m.jpg

I am experiencing the same problem, but I can not find a post with the relevant solution. With the PMDG 747 autobrakes appear to working OK.Jan Peter

i9-10900, RTX3080/10GB, FSX/P3Dv4.5

I am experiencing the same problem, but I can not find a post with the relevant solution. With the PMDG 747 autobrakes appear to working OK.Jan Peter
The signal from any analogue source is never truly constant. It's possible you just need a larger dead-zone to eliminate spurious signals.

Kenneth Weir

My Saitek yoke mod

 

i7 2600k @ 4.7

8GB Gskill CAS7

2x GTX580 SLI Surround + GT520 Accessory

Win7x64

Ken,I already tried that without success. Fiddling around with FSUIPC was also unsuccessfull. I blamed it on my CH pedals being worn-out after many flight-hours, LOL. Nevertheless, I think it is a CH problem.Jan Peter

i9-10900, RTX3080/10GB, FSX/P3Dv4.5

I have had a repeated problem with the autobrakes on my MD11. As soon as the aircaft touches down, the autobrakes disenagage. I have CH pedals with tow brakes - could the sensitivities be too high ? Any ideas would be appreciated.ThanksRichard Foreman
If you have FSUIPC, you might want to remove the calibration of the brake pedals through FSUIPC for FS... I had similar problems with the autobrake releasing as soon as the mains touched down. I had calibrated pedals, yoke, and lever quadrant with FSUIPC (all Saitek ProFlight)... went mad trying to work out why the disconnect was happening... I removed the FSUIPC calibration for the brakes and everything has been fins with autoland, autobrak, and all ever since...Worth trying if you have FSUIPC and have calibrated with it...Hope this helpsAndrew

Andrew Entwistle

  • 2 weeks later...

I had this problem with both the Queen and the MD-11. Since I use a Reg'd copy of FSUIPC for all my controller axis, there was a simple fix - make the brakes axis "Send Direct to FSUIPC Calibration" when selecting the axis type in FSUIPC (Axis Asssignments tab). Don't do this for rudder, aileron, throttle, or elevator axis as many advanced add-on aircraft such as PMDG and Level-D, need those axis to be "Send to FS as normal axis" because of their unique way they refer to FS Axis. If you do, you'll get squirly Autopilot controls, especially on ILS approaches.Runnig the brakes axis 'direct to FSUIPC calibration' smooths-out any and all transient spikes that routinely cause Autobrakes and Spoliers not to deploy during touchdown. The MD-11 is especially sensitive to this and it is why the 'Direct' mode helps. Also in FSUIPC, when you calibrate the brake axis, make sure you have 0 (zero) axis output always, when the brakes are not actively being pushed - raise your zero calibration point if you must, to get a solid, stable, zero output.Also, make sure your zero throttle calibration points are solid - and put your throttles into the idle detents (zero oupout) well before you touchdown; or again, autobrakes won't workIf you use profiles in FSUIPC for different aircraft assignments, open up your FSUIPC.ini file and make sure you have all axis set to type 'F' except the brake axis, those should now be type 'D'.As an example, here is my profile-specific MD-11 Axis assignments from my FSUIPC.ini file. Axis Y=Seitek Yoke/Throttle, R=CH Pedals, & T= Seitek 2nd Throttle.Note my brake axis (lines 5 & 6) - they're type 'D' and the zero calibration point has been raised from my standard -16384 to -11392/-11430.

[JoystickCalibration.PMDG_MD11]...Aileron=-16384,-512,512,16383Elevator=-16384,-512,512,16383Rudder=-16384,-512,512,16383LeftBrake=-11392,16383/24RightBrake=-11430,16383/24Throttle1=-16384,-512,512,16383/32Throttle2=-16384,-512,512,16383/32Throttle3=-16384,-512,512,16383/32Spoilers=-16383,16384/16Flaps=-16383,16384/16[Axes.PMDG_MD11]0=YX,256,F,65763,0,0,01=YY,256,F,65762,0,0,02=YZ,256,F,66382,0,0,03=YU,256,F,66420,0,0,04=YV,256,F,66423,0,0,05=RX,256,D,7,0,0,06=RY,256,D,8,0,0,07=RZ,256,F,65764,0,0,08=TX,256,F,66426,0,0,09=TZ,256,F,66534,0,0,0

Regards,
Al Jordan | KCAE

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.