I have a little bit of an automation problem, read the monkey doesn't push the right buttons. I use Vox ATC and rarely get a decent instruction at the TOD marker. In many cases I get it slightly after the TOD mark, prob around 600 - 1000' late according to the VNAV path marker. What will be the correct way to decent from here? What I did thus far was pressing LVL CHG and then as the VNAV deviation is around 100' I enable VNAV again. I always end up high on the approach. What will the procedure be if you get the decent instruction before the TOD mark?FRED

try upgrading to vatsim, highly recommended.

You could use vspeed to catch up to the vnav profile. I believe the vertical situation indicator will indicate nicely the exact point you will intercept it at.And I would of course very highly recommend vatsim/ivao as well :)

Edited March 5, 201214 yr by Sekstifire

Use SPD INTV and roll the speed higher than the FMC is commanding. For example: the FMC wants 260, roll it up to 300 (of course, paying attention to the limits, shown by the red hatched lines). Keep it at this speed until you're below the FMC's path, and then hit SPD INTV again. The reason you want to undershoot, is that when you "close" the speed window (by hitting SPD INTV the second time), the plane will level out some to bleed off speed. It will begin descending again when you've hit the proper speed. Had you closed the speed window when you got on path, you'd have to play catch up again.As mentioned by others, I'd upgrade to better ATC on VATSIM/IVAO. VOX ATC tends to be very gamey. It's better in some cases than FS's default, but it's still very inaccurate.

I think you can also use the DES NOW option in the FMC. It'll put the plane in a 1000ft/min descent untill it picks up the actual descent path that's in the FMC.

I think you can also use the DES NOW option in the FMC. It'll put the plane in a 1000ft/min descent untill it picks up the actual descent path that's in the FMC.

That won't work if you're above the path.

You might find these helpful. :(http://forum.avsim.n...page__hl__videohttp://forum.avsim.n...page__hl__video

Edited March 5, 201214 yr by falcon999

I think you can also use the DES NOW option in the FMC. It'll put the plane in a 1000ft/min descent untill it picks up the actual descent path that's in the FMC.

Yeah, best to use this if you get the ATC call to descend before T/D. Nowt wrong with VOX ATC! I often get the call to decend before T/D, so no issues there. v6 is much better, and make sure you have the latest patch from the avsim forum (not the website)

Edited March 5, 201214 yr by CrashEd

Use SPD INTV and roll the speed higher than the FMC is commanding. For example: the FMC wants 260, roll it up to 300 (of course, paying attention to the limits, shown by the red hatched lines). Keep it at this speed until you're below the FMC's path, and then hit SPD INTV again. The reason you want to undershoot, is that when you "close" the speed window (by hitting SPD INTV the second time), the plane will level out some to bleed off speed. It will begin descending again when you've hit the proper speed. Had you closed the speed window when you got on path, you'd have to play catch up again.

That's the Jack Cowill approach of doing things, which is awesome. Other than that however, if you just continue to fly straight ahead after having passed the T/D, I believe there's still energy compensation which will automatically slow down the aircraft so you lose some energy that you can regain during your first, steeper part of the following descent. Obviously all these methods will have limitations and won't help much if you delay your descent too much.The DES NOW hint doesn't work, as Matt already suggested, as it's a common method for descending before having reached the T/D. In this case you'll descend at 1000 fpm until intercepting the original VNAV path, to put it in simple terms.

Use SPD INTV and roll the speed higher than the FMC is commanding. For example: the FMC wants 260, roll it up to 300 (of course, paying attention to the limits, shown by the red hatched lines). Keep it at this speed until you're below the FMC's path, and then hit SPD INTV again. The reason you want to undershoot, is that when you "close" the speed window (by hitting SPD INTV the second time), the plane will level out some to bleed off speed. It will begin descending again when you've hit the proper speed. Had you closed the speed window when you got on path, you'd have to play catch up again.

This sounds like a great technique - thanks for sharing.

Yep, use Jack's technique from his videos when the plane was first released - SPD INTV to a higher speed to regain the path.

Use SPD INTV and roll the speed higher than the FMC is commanding. For example: the FMC wants 260, roll it up to 300 (of course, paying attention to the limits, shown by the red hatched lines). Keep it at this speed until you're below the FMC's path, and then hit SPD INTV again. The reason you want to undershoot, is that when you "close" the speed window (by hitting SPD INTV the second time), the plane will level out some to bleed off speed. It will begin descending again when you've hit the proper speed. Had you closed the speed window when you got on path, you'd have to play catch up again.As mentioned by others, I'd upgrade to better ATC on VATSIM/IVAO. VOX ATC tends to be very gamey. It's better in some cases than FS's default, but it's still very inaccurate.

I like the sound of this will try this technique when i next need.

Why can't anyone spell "descent" anymore?Gerry

@badderjet: the DES NOW will work in regard to what the TS also asked in his last sentence...what to do if he gets a descent BEFORE the TOD?<br />It won't work ofcourse after he's crossed the TOD.

Edited March 6, 201214 yr by Tallguy

@badderjet: the DES NOW will work in regard to what the TS also asked in his last sentence...what to do if he gets a descent BEFORE the TOD?

Ah yeah, kinda missed that one. Of course DES NOW is your choice if you are to descent in advance of the T/D, correct. Or V/S maybe, if 1000 is still too much. In fact I've seen RW situations where they dialed in 200 or 300 fpm initially. Certainly gave a smooth ride.

Edited March 6, 201214 yr by badderjet