Quote:
Originally Posted by nolimitfiend
This thread has renewed my interest in MS Flight Simulator. I have a few questions regarding altitude and speeds:
What is your typical rate of climb upon takeoff? What speed do you maintain during climb in the terminal area?
We typically climb at a minimum of 2000'/minute. If we're lightly loaded, we'll often see 3500-4000 feet minute on the initial climb. Once, in an empty MD-88, we had the VSI pegged which means we were doing over 6000'/minute.
Right after takeoff, we accelerate to V2 speed which, like V1 and VR, is calculated for each takeoff. This speed gives us maximum climb (altitude is our friend!) and is a safe climb speed in the event of an engine failure right after takeoff.
At 1000' AGL, we reduce power to climb power (easier on the engines) and lower the nose slightly to accelerate and clean up the plane (raise the flaps). We'll accelerate to 250 kts and maintain that through 10,000' MSL.
Quote:
What is your typical cruising altitude?
This will be based on aircraft weight, winds and turbulence reports. The usual range I've seen is from 32,000 to 39,000. For the higher cruise altitudes, we often have to start the flight lower due to aircraft weight and then climb later as we burn off fuel.
Quote:
How far from your destination do you initiate descent and at what rate/speed?
The descents are often dictated by the STAR (Standard Terminal Arrival Route). I just flew in to JFK yesterday morning from LAS and we flew the LENDY5 Arrival. As you can see here, it has some altitudes that we can expect from ATC (HARTY at or below FL230; LENDY at FL190 and 250 kts):
When left to our own devices on a descent (no altitude restrictions), we use the old 3-to-1 rule, i.e. figure 3 nm per 1000 feet of altitude. So 30 miles out we don't want to be much more than 10,000 feet over airport elevation. If we're up at FL360, we'll probably be asking ATC for a descent if we're getting close to 100 nm from the airport. This isn't usually necessary as the controllers are aware of our descent capabilities, but every once in a while we do have to ask.
There's an old story about ATC issuing a late descent clearance to cross a certain fix at a specific altitude. The Captain responds, "We're not going to be able to make that restriction." ATC replies, "Don't you have spoilers on that plane?", to which the Captain replied, "Those are for
my mistakes, not yours." (Yes, this passed for humor when I first heard it 25 years ago.)
Quote:
When under the 10,000(?) ft level, what speed do you maintain and at what point in the landing sequence do you achieve full landing and speed configuration?
In the U.S. there is a 250 kt speed limit below 10,000 MSL. Speeds on approach are often assigned by the approach controller as determined by her current traffic flow. At JFK, we'll often be asked to maintain 180 kts to the marker (about 5 miles from the runway). At the 5 mile point, we then drop the gear and get the final flaps setting and slow to approach speed (~130 kts on my approach yesterday morning).
If no speed is assigned, we may configure a mile or two earlier, but the marker is a good point at which to be fully configured for landing. If the weather is really bad with low ceilings, we'll get it all done earlier to get the approach really stabilized for a longer straight-in final approach.
Quote:
When flying GA, the pattern altitude is approximately 1,000 AGL. What is the pattern altitude for an air transport category plane?
Here again, we kind of rely on the 3-to-1 rule. That would put us at about 1500' at the marker. We don't often fly a VFR rectangular pattern like GA planes fly at uncontrolled airports; we're usually vectored onto the final approach course. I'd be comfortable flying a VFR pattern at 1500-2000'.
Quote:
For the umpteenth time, thank you for your time and effort in this thread. Suffice it to say I'm probably not the only 2+2er disappointed when no new posts are available.
I look at this thread almost every day, but I don't always have the time to respond to the depth that I'd like so I put it off. Your post, for example, was one that I didn't want to answer with just one or two sentences.