There is normally a speed limit below 10,000ft for aircraft, which is 250 KIAS. Most of the time we think it's a hindrance, when departing we would normally request a high speed climb, that is, go to 300KIAS then do the climb at that speed, or 280, depending on our weight. Those speeds, are our normal climb speeds above 10,000ft.
When our FMC isn't really up to scratch, mostly because we didn't plan ahead well enough to place artificial constraints on the route legs, we too would ask for a high speed below 10,000 and use our speed to descend lower and faster, before slowing down and getting into approach config (although I do not recommend doing this).
Asking for high speed below 10,000 is used mainly to catch up on schedule delays etc, but when you do this, you must be alert! I have had a few first officers breaking a sweat when I tell them to go fast below. They seem to have a hard time adjusting to the pace and the planning ahead that's required. Most are OK with it and can do it well, but some, ABUSE IT.
I used to love abusing it, it was an adrenalin rush. In one of my previous companies, we had a very short leg of only 20 minutes. On that leg, we would take off, turn around then accelerate to the red line, and then slow down and configure for the approach and landing in time. We would do this at about 8000 - 10000 ft.
One particular day, the winds were strong up above 4000, and we needed to be at 6000ft only. After take off, I sped up, I was flying the leg. At 6000ft, on the right hand as I was a first officer in those days, the ground whizzed by quicker. The Captain was busy monitoring the instruments and I was too, but also looking out from time to time.
I saw a moving speck on the windshield. With curiousity I leaned forward. The captain saw this and asked "What are you doing?"
"I think I see something."
"Where?"
"Dead ahead, our level."
He too was looking for it. There was nothing in our TCAS. Was it a small plane?
As the spec becomes bigger, and bigger, the shape became clearer but the time to avoid it becomes less and less. Suddenly, we realized what it was.
"Bird! Bird!" I shouted.
"Oh no, this is going to be a close one!" The captain shouted.
"Evade?"
Not enough time, within a moment, the large bird whizzed accross the left side of the aircraft, only a few meters off the fuselage. We were there just stunned.
"Did anyone back there see that?" He asked.
"I don't know, the question is, did it hit the stabilizer?"
We decided to slow down and check if the trim was affected (it shouldn't, but you don't want to find out only at approach do you?). As we slowed to 250 knots, the trim wheel moved and the altitude remained. We handflew the aircraft to the landing from then.
After parking we quickly went out to check if there's anything on the left wing or left stabilizer. We found nothing.
That was the last schedule I had on that leg before I moved companies. Hitting a Pelican on the windshield at 350 knots wouldn't be pleasant, luckily we didn't hit it.
When our FMC isn't really up to scratch, mostly because we didn't plan ahead well enough to place artificial constraints on the route legs, we too would ask for a high speed below 10,000 and use our speed to descend lower and faster, before slowing down and getting into approach config (although I do not recommend doing this).
Asking for high speed below 10,000 is used mainly to catch up on schedule delays etc, but when you do this, you must be alert! I have had a few first officers breaking a sweat when I tell them to go fast below. They seem to have a hard time adjusting to the pace and the planning ahead that's required. Most are OK with it and can do it well, but some, ABUSE IT.
I used to love abusing it, it was an adrenalin rush. In one of my previous companies, we had a very short leg of only 20 minutes. On that leg, we would take off, turn around then accelerate to the red line, and then slow down and configure for the approach and landing in time. We would do this at about 8000 - 10000 ft.
One particular day, the winds were strong up above 4000, and we needed to be at 6000ft only. After take off, I sped up, I was flying the leg. At 6000ft, on the right hand as I was a first officer in those days, the ground whizzed by quicker. The Captain was busy monitoring the instruments and I was too, but also looking out from time to time.
I saw a moving speck on the windshield. With curiousity I leaned forward. The captain saw this and asked "What are you doing?"
"I think I see something."
"Where?"
"Dead ahead, our level."
He too was looking for it. There was nothing in our TCAS. Was it a small plane?
As the spec becomes bigger, and bigger, the shape became clearer but the time to avoid it becomes less and less. Suddenly, we realized what it was.
"Bird! Bird!" I shouted.
"Oh no, this is going to be a close one!" The captain shouted.
"Evade?"
Not enough time, within a moment, the large bird whizzed accross the left side of the aircraft, only a few meters off the fuselage. We were there just stunned.
"Did anyone back there see that?" He asked.
"I don't know, the question is, did it hit the stabilizer?"
We decided to slow down and check if the trim was affected (it shouldn't, but you don't want to find out only at approach do you?). As we slowed to 250 knots, the trim wheel moved and the altitude remained. We handflew the aircraft to the landing from then.
After parking we quickly went out to check if there's anything on the left wing or left stabilizer. We found nothing.
That was the last schedule I had on that leg before I moved companies. Hitting a Pelican on the windshield at 350 knots wouldn't be pleasant, luckily we didn't hit it.
