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.

Slippery bird. 250 - 10000

Featured Replies

How do you usually deal with 250 - 10000 restriction on decends? I usually change the restriction to 240 - 13000 on the VNAV decend page so the engines will go idle around FL145 and this usually gives me 240-260 at FL100, but sometime it doesn't if the wind won't co-operated!What's your technique?

insert a fix about 8nm prior to passing FL100 with speed restr 250if on open descent: start speed reduction from FL CH also around 8-10nm inbound the planned SLPthat's what i do... but then again i get too many 'high speed approved's;-)cheers

Speed Brake.

ahh yes... of course ;)i only use them if i 'misplanned' or if ATC has no other option than to 'expedite'

Hello Preston,The easiest way by far is this.Just engage FLCH at ~ F120-110 and dial back to 240. This should get you slowed down nicely. If winds etc. are fighting the decceleration, throw some speedbrake into play, and I'm sure it'll get it sorted. Only, you have to watch out the FL CH with boards out, because PIC FL CH sometimes does not pitch down to commanded speed with them out, and instead slows down below commanded speed. If this occurs, immediately engage V/S with -1800 and watch the speed build back, and re-engage FL CH after restabilized. :(After FL100 many airlines prefer to explicitly use the FLCH anyway (except for <1000ft alt changes), so in my opinion there's no "breach" in realism this way either (as opposed to adding fixes or editing DES page restrictions with trial-error method, imo.)regardsTeroedit: note also that the VNAV speed intervention will NOT work in VNAV DES, because of the same reason that the restrictions don't work properly when entered in LEGS. In my experience, the SPD/ALT restrictions in current PIC work this way: it will start to capture the desired SPD/ALT restriction AFTER the WPT where you have set it, not to BE at that WPT in correct SPD/ALT like in the real aircraft.

PPL(A)

Just to add to Teros comments about "no breach of realism". When I was invited to the SAS full motion 767-sim at Stockholm, Arlanda I asked the pilots about the slipperiness of the 767. They basically said that it is very slippery and that they usually needed to perform what has been mentioned above (waypoint prior to FL100, FL CH etc. depending on the situation) but often ATC had something else to say, i.e. early or late descent clearances. When that happens they definitely use the speed brakes when needed, after all it

/Tord Hoppe, Sweden

Tero,I agree completely with your suggestions, except the "edit" section. It has been my experience that speed intervention (MCP speed window)works very well in VNAV DES. I almost always set 290 knots after descending through FL300 and adjust it as necessary to maintain separation. But then I follow your method of engaging FLCH at 12,000 and the rest of the procedure you outlined so well in that paragraph.Respectively,Mike

Mike,Aah... very interesting.The rare times I have tried it, it has misbehaved on me, but if you say it has worked for you, I believe it. And I might also have an explanation to why it hasn't worked for me.I guess the situations where I've tried to speed intervene the Vnav descent have been such that the engines have already been running idle (as IRL they should all the time), and to effectively follow VNAV path in that situation there is no way of slowing down except throwing out speedbrakes. If there is excess speed, then the SPD intervention will probably work.I'll try this later, and thanks for the tip!Tero

PPL(A)

Tero,This is of course PIC specific in that PIC has some built in "slop" relating to non-idle descent. If the "RESET MCP ALT" message is not observed or followed and the aircraft continues at altitude too long, the resulting descent path is steep enough so that idle descent is indeed required, thus speed restraint is not possible. A favorite practice (of mine) in that event is to go the other way and set MCP speed to 330 knots below FL300 to help recapture the original calculated VNAV path. From that point, a reduced MCP speed "intervention" works well since you are no longer following an idle descent. Of course, the pax are tossing their lunch all over the cabin but PIC does not model smell so what the heck.

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.