Need your help on this one.....
And what kind of a landing rate can actually cause physical damage to the airplane?
Pilot No: 2727
Sathya Narayanan
btw, this is my first post on GCVA!

Moderators: Staff, HR, Flight Ops
Actually, the Speed Brakes will generally only be used for times where you get slam dunked by ATC and they want an expedited descent or they want you to slow up quickly.hihello_21 wrote:Thanks guys for the replies and especially John, for your detailed explanation. Yes I tried autoland a couple times and now I can somewhat manage to do better landings.
And during descents I always have to get the speedbrakes up in order to keep the speed in control. For most part of my descent I keep the speedbrakes up. Does this happen in real life too?
Mike,Brogs wrote:Prior to descent, here's a tip I read and found very useful, on the FIX page of the CDU enter the destination Airport e.g EGCC, then on the scratchpad enter /30 and line select that to the Fix line this will give you a 30 mile circle around your destination Airport, then using the Rule of Thumb "3 miles descent = 1000ft" work out the TD distance from the Airport "e.g FL300 ToD 90 mls from Destination," then enter /90 in the S/pad and upload again to Line Select and this will put a 90 mile Circle around your Destination Airport, so now you have 2 Circles around your Dest A/port, now in addition I personally add 20 mls to the 90 and put a further circle around my Dest A/port of 110 mls . When I arrive at that point "110 mls" in the Flight I start prepping for my Descent at the 90 ml point , speed adjustment etc , works for me every time, then just let the Vnav fly the descent while you monitor.
I think the trick is John not to get bogged down with numbers, gives me a headache , loljcwaugh747 wrote:Mike,Brogs wrote:Prior to descent, here's a tip I read and found very useful, on the FIX page of the CDU enter the destination Airport e.g EGCC, then on the scratchpad enter /30 and line select that to the Fix line this will give you a 30 mile circle around your destination Airport, then using the Rule of Thumb "3 miles descent = 1000ft" work out the TD distance from the Airport "e.g FL300 ToD 90 mls from Destination," then enter /90 in the S/pad and upload again to Line Select and this will put a 90 mile Circle around your Destination Airport, so now you have 2 Circles around your Dest A/port, now in addition I personally add 20 mls to the 90 and put a further circle around my Dest A/port of 110 mls . When I arrive at that point "110 mls" in the Flight I start prepping for my Descent at the 90 ml point , speed adjustment etc , works for me every time, then just let the Vnav fly the descent while you monitor.
That is a very useful tip, good information. My response was based on the assumption that they probably were not utilizing VNAV at all.
One thing that is actually a bit funny about this topic, I have seen people come up with a LOT of different ways to compute a Let-Down or Top of Descent point and these methods would employ a LOT of technical factors, however they all nearly always come up with something of 100 to 120 miles, depending on cruise altitude.
Your 3/1 rule with a little fudge factor of about 10 miles is actually very close to all that anyone needs to do. Programming the FMS or FMC for crossing restrictions or STAR's is almost cheating.....lol
What if your FMS is inopBrogs wrote: I think the trick is John not to get bogged down with numbers, gives me a headache , lol
Don't fly that bird again !jcwaugh747 wrote:Or worse than that.
What if Auto-Land AND FMS is inop???? Oh My!!! lol