# How do you determine the proper rate of descent for landing?

I'm trying to use a simulator to learn to land properly. One part that I'm finding really tricky is picking a proper rate of descent. I know I'm supposed to do my best to keep it so I have two red lights and two white lights on the Precision Approach Path Indicator (PAPI), but at the moment I basically am just eyeballing it and adjusting my course whenever the lights aren't right.

I have to assume, though, that for any given airspeed there is a rate of descent I can maintain that will keep me right in the middle of the preferred glide slope for that airport. I just have no idea how to figure it out. Is there an application or formula that is preferred for this? Or is it time to learn Vector Calculus?

PS- I did check this question to see if it related. But that question is about starting the descent from cruise. I'm talking about rate of descent for final. I did also check this answer, but it's about using the PAPI/VASI lights. I'm looking for a formula to figure out the proper rate of descent during final for a given speed.

• The question is good and if I weren't on my phone I'd take a crack at the equations, but for practical purposes I'm willing to bet you'll have better luck eyeballing it than you will trying to fly that precise a rate of descent by instruments. Especially if the simulator isn't full-motion. Commented Feb 9, 2015 at 23:38
• Are you approaching VFR or IFR? IFR, you can take a look at the approach chart, it will give the descent rate for the glide path depending on groundspeed. For VFR... well, it's called VFR.. you just aim for the runway. It also depends on aircraft used, a TMG will drop from higher altitude and approach with higher descent rate than a SEP. Commented Feb 9, 2015 at 23:50
• The formula really shouldn't change if you are accounting for speed, descent rate and optimal descent angle. Commented Feb 9, 2015 at 23:53
• You have a good answer, but I will add this: As a pilot, I only use the VSI as a cross-check in this situation. I change the pitch to stay on the PAPI and adjust the power setting to keep the airspeed that I want. The VSI takes care of itself. Commented May 8, 2015 at 21:28

Assuming you want a 3 degree glide slope, just take 5 times your ground speed in knots as a starting point.

As an example, approaching at 90kt ground speed in a light aircraft, go for 450feet per minute. at 140kt in a jet, try 700fpm. If you're flying a jet outside of 4 miles, and the controller wants you to keep the speed up at 200kt then descend 1000fpm.

It's not perfect, but it works pretty well for a first guess, and you can adjust as necessary.

Of course, your ground speed is not the same as your air speed, and even for a constant IAS it will likely vary as you descend and the wind changes. Another way to think about this is that a 3 degree glideslope is almost exactly 300ft per nautical mile. If you're 2 miles out and 700 feet up, then you need to descend a bit faster, conversely, if you're at 500 feet, you need to descend slower.

A third related rule of thumb is that your final approach speed (in CAS, although IAS is good enough in most aircraft) is 1.3 times your stall speed in the landing configuration (Vso). So if you stall at 100 knots, you want to approach at 130KIAS.

IFR approaches are all about having an initial guess at these numbers in your head, trying them out, and then adjusting as the conditions require. If you're good at the guesses then the adjustments will be very small.

• approach speed in a jet is calculated on the FMS as Vref, not using the 1.3Vso speed.
– rbp
Commented Feb 10, 2015 at 19:39
• True, but in practice it will be pretty close to 1.3Vso for almost all types (concord excepted...) Commented Feb 18, 2015 at 18:13
• @rbp Typically Vref is defined as 1.3Vso. Commented May 8, 2015 at 21:29

For most purposes, if you're flying something with a jet engine, you can probably schwag -700fpm for a 3 degree glideslope and be fairly accurate. It will at least give you a starting point. You shouldn't be flying the approach solely off your VSI anyway, but it is useful to determine how large of a correction you are making, or if you're about to bust through the bottom.

It helps to know the pitch and power settings for your jet. That way you're not chasing the airspeed, VVI, etc. So how do we figure out what pitch and power settings to use?

Well if we look at our ADI in level-flight at our final approach speed we see we are 2 degree nose-high for example. And we know that for each degree of pitch change it equates to 100 ft/NM. With an average ILS the glideslope is around 3 degrees. So we know that this is about 3 degrees low from our 2 degree level flight attitude. This leaves us with about 1 degree nose-low.

Fly the approach at 1 degree nose-low, and adjust your power to maintain your airspeed which in the end should result in a VV of about 5 * your groundspeed. Or you can take your groundspeed and convert it to NM/min and then multiply that by 300 ft/NM. If we approach at 160 KTS (2.67 NM/min), we end up with a VV of 800 ft/min which is the same as using our rule of thumb of 5 times your groundspeed.

I know this is probably a little more math than what you wanted, but setting a known pitch and power setting and making minor adjustments from that will help improve your approaches tremendously.
{"found_math": false, "script_math_tex": 0, "script_math_asciimath": 0, "math_annotations": 0, "math_alttext": 0, "mathml": 0, "mathjax_tag": 0, "mathjax_inline_tex": 0, "mathjax_display_tex": 0, "mathjax_asciimath": 0, "img_math": 0, "codecogs_latex": 0, "wp_latex": 0, "mimetex.cgi": 0, "/images/math/codecogs": 0, "mathtex.cgi": 0, "katex": 0, "math-container": 0, "wp-katex-eq": 0, "align": 0, "equation": 0, "x-ck12": 0, "texerror": 0, "url": "https://aviation.stackexchange.com/questions/12572/how-do-you-determine-the-proper-rate-of-descent-for-landing", "fetch_time": 1723675182000000000, "content_mime_type": "text/html", "warc_filename": "crawl-data/CC-MAIN-2024-33/segments/1722641137585.92/warc/CC-MAIN-20240814221537-20240815011537-00715.warc.gz", "warc_record_offset": 82535668, "warc_record_length": 41354, "token_count": 1344, "char_count": 5406, "score": 3.578125, "int_score": 4, "crawl": "CC-MAIN-2024-33", "snapshot_type": "latest", "language": "en", "language_score": 0.9675337672233582, "file_path": "/sailhome/yjruan/project/latent-lm/data/processed/finemath-4plus/finemath-4plus/train-00038-of-00064.parquet"}