Descent Rate on Glide Slope

Consider that landing is art not science. Where I fly there are too many variables, wind, trees, birds, fences, airport surface, other aircraft, controllers.... etc, etc, etc. IOW, the gauges and numbers are baseline and you adapt and improve from there. You can’t go around every time something doesn’t fit a spread sheet, the aircraft has given us a lot of ‘tools’ to adapt.
 
IOW, the gauges and numbers are baseline and you adapt and improve from there.
I find it interesting to work out the numbers for myself from time to time, as it helps correlate with what I'm seeing. I'm not sure why everyone extrapolated the OPs posts to trying to rigidly adhere to these numbers while flying.

Nauga,
who trusts but verifies
 
I was thinking about the side debate about 1/2 mile being too close...and YES I'M OVERTHINKING IT, but only for the benefit of discussion

and the OP reports he's flying downwind about a mile out

I was taught in my early days that downwind should put the runway roughly mid point of the wing strut.
Uncontrolled field with 800AGL TPA

just eyeballing an angle from some nose on photos of a 172 and 152, and considering that the lower portion of the strut isn't visible at a normal head position...so maybe 25° eyeball down angle. Maybe I'm off a good bit on that angle and it's been a little while since I've flown a Cessna so my sight memory is blurry...
Anyway....If I'm doing the math correctly, x = distance from runway line to downwind line
x=800/Tan25°= 1,716 ft = 0.32 statute miles...(adjusting for those of you with 1,000 ft TPA it would be closer to 0.4 mile)
x=800/Tan30° = 1,386 ft = 0.26 statute miles

checking
Going to Google maps and measuring the landmarks for downwind to the runway at that same familiar airport, it was maybe 2,600 to 2,800 ft real world ... just over 1/2 mile
ATAN800/2800 = approx 16°

A mile out is maybe a 10.7° eyeball down angle at 1,000 ft TPA.... that's basically on the horizon!
If you loose an engine abeam the numbers and that far out, can you make the runway easily?...math for another day I suppose....
 
Another case for doing some glider flying. No power to work with, just a sight picture and a variable drag control (spoilers) in most craft. Very easy to land accurately but no go arounds.

Then there’s a glider with only flaps. Sort of a one way drag device; you can drop ‘em but practically speaking you can’t raise them if you screw up, you just land or crash short. Yup.


Sent from my iPad using Tapatalk Pro
 
I find it interesting to work out the numbers for myself from time to time, as it helps correlate with what I'm seeing. I'm not sure why everyone extrapolated the OPs posts to trying to rigidly adhere to these numbers while flying.

Nauga,
who trusts but verifies

Just me, but when someone goes into the detail the OP did, with tenths of feet (how you going to read a descent rate of 723.3' on a VSI) and tenths of degrees,

"0.5 mi downwind @ 85 mph takes 0.35 minutes. Descent is 723.3’ at 15.3 degrees."

it doesn't seem they're 'approaching' it in a general, high-level sense. But I'm certain I could have taken it in more detail than they meant.
 
As an engineer I have been accused, rightly so, of overthinking things. Flying a glideslope in IMC you don't want all this extra stuff going through your head. Just look for a reasonable descent rate (if it's 2000 fpm, you probably need to do something), but most importantly work on keeping the needles centered. Make small corrections as needed, when needed. Keep the airspeed under control, stay stabilized. That's really all you need to worry about, filling your head up with numbers and worrying about if the numbers are in spec is a waste, other than basic airspeed and a reasonable descent rate. Keep in mind that headwinds will change your descent rate.
 
Just me, but when someone goes into the detail the OP did, with tenths of feet (how you going to read a descent rate of 723.3' on a VSI) and tenths of degrees,

"0.5 mi downwind @ 85 mph takes 0.35 minutes. Descent is 723.3’ at 15.3 degrees."

it doesn't seem they're 'approaching' it in a general, high-level sense. But I'm certain I could have taken it in more detail than they meant.
This is your second post in the thread--do you feel sufficiently superior now?
 
That reply was to answer Nauga’s some what question, odd that you think it’s about superiority.

Enjoy your 723.3 feet per minute descent rate. ;)
 
I made a spreadsheet.

Given:

0.5 mi pattern. TPA = 1,000’ AGL

Downwind 85 mph. Base 75 mph. Final 70 mph.

Assume start of descent abeam numbers.

Assume 3 degree glide slope starting on base.

Working backwards:

0.5 mi final @ 70 mph takes 0.43 minutes. Descent is 138.4’ at 3 degrees. This gives 323 fpm descent.

0.5 mi base @ 75 mph takes 0.40 minutes. Descent is 138.4’ at 3 degrees. This gives 346 fpm descent.

0.5 mi downwind @ 85 mph takes 0.35 minutes. Descent is 723.3’ at 15.3 degrees. This gives 2,049 fpm descent.

Is this right? 2,049 fpm descent at 15.3 degrees just to get on the glide slope? What happened to 500 fpm controlled descent?
A 3° glideslope is about 200 ft for every half mile. Makes for a long downwind and a wide pattern, because you'll need to fly 2.5 nm (± winds) to lose 1,000 ft.
 
Just me, but when someone goes into the detail the OP did, with tenths of feet (how you going to read a descent rate of 723.3' on a VSI) and tenths of degrees,

"0.5 mi downwind @ 85 mph takes 0.35 minutes. Descent is 723.3’ at 15.3 degrees."

it doesn't seem they're 'approaching' it in a general, high-level sense. But I'm certain I could have taken it in more detail than they meant.
We read it differently, apparently. He showed his work and asked "is [2000fpm] right?" He said nothing about flying to the tenth of a degree or tenth of a mile per hour. As some pointed out there was a flaw in his assumptions, not in his math. Others were not so forthcoming.

Nauga,
mathematically inclined
 
Your math is correct but your first two examples you just calculated a descent rate based on a 3 degree angle. You didn’t use a 1,000 ft altitude to lose in those 2 examples. Your last example (downwind) you used a 1,000 ft AGL altitude loss in only .5 NM. That makes no sense since you’re not going to be losing 1,000 ft in .5 NM because you still have base and final to add to that distance.

Only realistic scenario for your 3rd example is a helicopter. If you're doing an autorotation at 85 MPH at 1,000 ft AGL, you’ll cover about .5 NM at around 2,000 FPM and a 15 degree glide path.
 
Your math is correct but your first two examples you just calculated a descent rate based on a 3 degree angle. You didn’t use a 1,000 ft altitude to lose in those 2 examples. Your last example (downwind) you used a 1,000 ft AGL altitude loss in only .5 NM. That makes no sense since you’re not going to be losing 1,000 ft in .5 NM because you still have base and final to add to that distance.

Only realistic scenario for your 3rd example is a helicopter. If you're doing an autorotation at 85 MPH at 1,000 ft AGL, you’ll cover about .5 NM at around 2,000 FPM and a 15 degree glide path.
The math is right. I considered all legs of the pattern. I used statute miles for distances.
 
The math is right. I considered all legs of the pattern. I used statute miles for distances.

Yeah, I know your math is right but your scenario on downwind is incorrect. You won’t be losing 1,000 ft in only 1/2 SM. Your distance covered is much greater than that, hence you won’t have nearly the descent rate / angle that you suggest.
 
Many years ago I did this mathematical analysis, just for curiosity. Of course, it is of no use in actualy flying, but it does give some satisfaction for the technically or mathematically inclined pilot.

TP.png
 
My scenario depicts losing 1,000 ft total in 1.5 miles, 0.5 miles on each leg.
 
Just me, but when someone goes into the detail the OP did, with tenths of feet (how you going to read a descent rate of 723.3' on a VSI) and tenths of degrees,
"0.5 mi downwind @ 85 mph takes 0.35 minutes. Descent is 723.3’ at 15.3 degrees."
it doesn't seem they're 'approaching' it in a general, high-level sense. But I'm certain I could have taken it in more detail than they meant.

the precision might be because it's good practice to run calculations with some precision, then do your rounding and such at the end. If you round up at every step you'll end pretty high....

A 3° glideslope is about 200 ft for every half mile. Makes for a long downwind and a wide pattern, because you'll need to fly 2.5 nm (± winds) to lose 1,000 ft.
Beautiful way of simplifying the "problem"! From that, just play with different leg lengths that add up to about 2.5 miles. Done.
 
Yeah, I know your math is right but your scenario on downwind is incorrect. You won’t be losing 1,000 ft in only 1/2 SM. Your distance covered is much greater than that, hence you won’t have nearly the descent rate / angle that you suggest.
Guessing you're commenting about this post by me: "For a 1 mile pattern: the downwind 1 mile at 85 mph becomes 633 fpm descent at 4.8 degrees."

This was assuming three 1-mile legs, with the same other assumptions from the OP. The descents are 447', 277', 277' on each leg.
 
Guessing you're commenting about this post by me: "For a 1 mile pattern: the downwind 1 mile at 85 mph becomes 633 fpm descent at 4.8 degrees."

This was assuming three 1-mile legs, with the same other assumptions from the OP. The descents are 447', 277', 277' on each leg.

Ok, we’ll you never mentioned 1 mile in the original post. What distance were you using to get 2,049 FPM and 15.3 degree glide path?
 
Ok, we’ll you never mentioned 1 mile in the original post.
The original post considered 0.5 mile legs.

What distance were you using to get 2,049 FPM and 15.3 degree glide path?
0.5 miles.

It's right here:

"0.5 mi downwind @ 85 mph takes 0.35 minutes. Descent is 723.3’ at 15.3 degrees. This gives 2,049 fpm descent."
 
The original post considered 0.5 mile legs.


0.5 miles.

It's right here:

"0.5 mi downwind @ 85 mph takes 0.35 minutes. Descent is 723.3’ at 15.3 degrees. This gives 2,049 fpm descent."

Ok, 1/2 mile and losing just over 700 ft does equate to those numbers. I thought you were using 1,000 ft TPA to go only 1/2 mile to the runway end. Since aircraft don’t fly a perfect 90 degree angle and I’d say most go out to around 3/4 mile vs 1/2 mile, the descent on downwind isn’t going to be as drastic as your initial example. Plus, how many are intercepting final at 3 degrees? I’m usually a bit of white over white when I turn final.
 
Last edited:
I over think everything. I'm thankful I learned to land in an airplane that didn't have a AI, VSI or turn coordinator. As it was, the instructor blocked out the altimeter and airspeed on downwind so I'd actually develop a feel for how to land. Thankful for that, too.

Pattern distance? I learned that if you can't land from wherever you are, past mid-field downwind, you're too far away. But that's just me. Some people like to fly out far enough that they need survival equipment packed aboard for pattern work.
 
I over think everything. I'm thankful I learned to land in an airplane that didn't have a AI, VSI or turn coordinator. As it was, the instructor blocked out the altimeter and airspeed on downwind so I'd actually develop a feel for how to land. Thankful for that, too.
I got lucky. An instructor did it to me during a checkout within a year after I got my CFI and covering the instruments has been a staple for me ever since. I won't solo a student until they can land with the airspeed indicator covered. I also do it sometimes for flight reviews if the pilot hasn't done it before, and it's a staple when working with any pilot who has problems with landings.

The technique works for other maneuvers too.
 
I find it interesting to work out the numbers for myself from time to time, as it helps correlate with what I'm seeing. I'm not sure why everyone extrapolated the OPs posts to trying to rigidly adhere to these numbers while flying.

Nauga,
who trusts but verifies
Narrow minds.
 
Is the tach exposed?
When it was done to me. Instructor covered the whole panel with a newspaper on downwind. The flight school began using the technique when a renter pilot went off the end of the runway in a Tiger.

I usually don't bother with anything except the ASI for landings. Experience has suggested to me that most landing issues are due to fixation on the ASI, so I take it out for the equation. Of course, if I see a particular pilot fixating and chasing ting RPM, I'd cover that. All I'm looking for is the "offending" instrument - the one which causes problems by being fixated on. For example, for ground reference maneuvers and steep turns, I cover the altimeter. (As I would pull the sticky off the altimeter, one student use to say, "and the mystery altitude is..." )
 
Last edited:
I do not understand why people try to make simple tasks so difficult.

A 3 degree descent angle is approx 3 miles for every 1000'. The rate of descent is 5 times your IAS or groundspeed...close enough.

So at 70 IAS, you would descend at 350 fpm to achieve a 3 degree descent angle.

With this being said, why would you need this info if vfr in the traffic pattern ?
 
A 3° glideslope is about 200 ft for every half mile. Makes for a long downwind and a wide pattern, because you'll need to fly 2.5 nm (± winds) to lose 1,000 ft.
Beautiful way of simplifying the "problem"! From that, just play with different leg lengths that add up to about 2.5 miles. Done.
Thanks! And to add to the fun, I don't think the FAA or TC apply their silly new "stabilized approach" standards until you're established on final — perhaps any American or instructors can let me know if I'm wrong — so you can do a safer and more natural (for light pistons) 6° glidepath on the base leg and lose roughly 400 ft/mile.
 
So at 70 IAS, you would descend at 350 fpm to achieve a 3 degree descent angle.

With this being said, why would you need this info if vfr in the traffic pattern ?
While seat of the pants and hunting and pecking is a time-honored tradition, having power/configuration targets for various phases of flight is a good operating practice. It's often not specifically covered as such until instrument training but is useful much earlier than that.

Funny...I learned the "x 5" rule of thumb during instrument training, but the more vivid memory was when I was taught to apply it to the VFR traffic pattern!
 
Thanks! And to add to the fun, I don't think the FAA or TC apply their silly new "stabilized approach" standards until you're established on final — perhaps any American or instructors can let me know if I'm wrong — so you can do a safer and more natural (for light pistons) 6° glidepath on the base leg and lose roughly 400 ft/mile.
Can't speak for TC, but the stabilized approach is described by the FAA in the Airplane Flying Handbook and elsewhere like this:
A pilot is flying a stabilized approach when he or she establishes and maintains a constant angle glidepath towards a predetermined point on the landing runway.​
The AFH talks stability on each leg.

True, most of the discussion centers on being stable by a certain point on final, but "be stable by xxx feet on final" does not equate to "be unstable elsewhere."
 
Just to go back to the title and original post for a second. The turns in the pattern are not part of the “glide slope”. That’s what initially confused me about the post. Again, in the context of IFR this all makes a lot more sense.
 
The OP was in mph.
It works for either..just a rule of thumb to get you close without using a slide rule. :)
My comment was tongue in cheek but for typical GA approach speeds the rule of thumb is off by ~9% if you use MPH and ~25% if you use knots. Since it's just a crosscheck for VFR you're almost as close or closer to just shoot for 250-300 fpm and adjust as you fly. *This* is just one reason why I think it's important to understand the math behind rules of thumb.

Nauga,
bounded
 
Last edited:
My airport doesn’t even have a glide path, so it’s completely eyeballed. It’s never occurred to me to get so specific and calculate my descent rate on a visual approach. This sounds more like an IFR exercise.
 
Just to go back to the title and original post for a second. The turns in the pattern are not part of the “glide slope”. That’s what initially confused me about the post. Again, in the context of IFR this all makes a lot more sense.
Yes, at the time I was assuming being as close to the 3 deg glide slope as possible once turning final. This is why I assumed trying to get to that slope and altitude before base. This is not my goal anymore.
 
Thanks fellas. The answers received made my question worthwhile. I've been looking out the window, but I'm an engineer and I want to know the numbers. Just looked at Google maps satellite view and I realize that my actual pattern is about a mile away. I had it in my head to shoot for 1/2 to 1 mile from runway downwind, and that's why I asked the original question. I now know not to fixate on the PAPI lights, or at least not be concerned about being a bit high on long finals, especially when doing straight-in landings (looking forward to discussing this with my CFI).

But keep asking interesting questions. It makes the rest of us think (and annoys the rest ;->)
 
Back
Top