Calculate VS in Feet per NM
Use this aviation calculator to convert an altitude change over a given nautical-mile distance into a vertical profile measured in feet per nautical mile. You can also estimate the vertical speed required in feet per minute when you add groundspeed.
This is useful for descent planning, climb planning, stabilized approach setup, and quick cross-checks of common rules such as a 3 degree descent path.
Expert Guide: How to Calculate VS in Feet per NM
When pilots, dispatchers, flight instructors, and advanced sim users talk about descent planning or climb performance, they often move between two related but different ideas: vertical speed measured in feet per minute and vertical gradient measured in feet per nautical mile. If your goal is to calculate VS in feet per NM, the key is understanding that feet per nautical mile describes how much altitude is gained or lost over distance, while feet per minute describes how quickly that altitude is gained or lost over time.
This distinction matters because time-based and distance-based planning answer different questions. A feet-per-minute target helps you fly the airplane right now. A feet-per-nautical-mile target helps you understand whether you can meet an altitude restriction over the distance remaining. For practical flight planning, both are valuable, and converting between them is a routine part of instrument procedures, descent setup, and energy management.
If you also know groundspeed in knots, then vertical speed (fpm) = feet per NM × groundspeed / 60
What “VS in feet per NM” really means
Strictly speaking, VS usually means vertical speed, and vertical speed is traditionally shown in feet per minute. However, many pilots casually say they want to “calculate VS in feet per NM” when they are really trying to determine the required vertical path gradient. For example, if you must lose 3,000 feet over 10 nautical miles, your required path is 300 feet per nautical mile. If your groundspeed is 120 knots, that same path requires about 600 feet per minute because 120 knots is 2 nautical miles per minute, and 300 × 2 = 600.
This is why feet per NM is such a clean planning unit. It tells you whether your path is shallow, normal, or steep regardless of how fast you are traveling. Then, once speed is known, you can convert the path into a vertical speed target.
Why pilots use feet per nautical mile
- It aligns naturally with distance-to-go and crossing restrictions.
- It stays stable even as groundspeed changes, unlike feet per minute.
- It makes 3 degree path checks simple and intuitive.
- It supports approach briefings, VNAV cross-checks, and manual descent planning.
- It helps compare published gradients and aircraft capability on departures and missed approaches.
The basic calculation step by step
To calculate feet per NM, start by taking your total altitude to lose or gain. Then divide that number by the number of nautical miles available. The result is your vertical gradient.
- Find the total altitude change in feet.
- Convert the available distance to nautical miles if needed.
- Divide altitude change by distance in NM.
- If you want a required vertical speed, multiply the feet-per-NM answer by NM per minute.
Example 1: Standard descent planning
Assume you need to descend 3,000 feet over 10 NM. The math is straightforward:
3,000 / 10 = 300 ft/NM
If your groundspeed is 120 knots, then you are covering 2 NM per minute:
120 / 60 = 2 NM/min
Now multiply the gradient by NM per minute:
300 × 2 = 600 fpm
So a 300 ft/NM path at 120 knots equals about 600 feet per minute.
Example 2: Steeper path
If you must lose 4,500 feet over 12 NM:
4,500 / 12 = 375 ft/NM
At 150 knots groundspeed, you are moving 2.5 NM per minute:
150 / 60 = 2.5 NM/min
Required vertical speed:
375 × 2.5 = 937.5 fpm
In practice, you would fly about 940 fpm and monitor whether the path remains stabilized.
How feet per NM relates to a 3 degree descent path
One of the most useful reference points in aviation is the 3 degree glide path. A 3 degree descent path is approximately 318 feet per nautical mile. That means if your calculated result is near 300 to 320 ft/NM, you are in the neighborhood of a normal, familiar descent path used on many instrument approaches.
This benchmark matters because it helps you instantly judge whether your planned descent is easy, normal, or aggressive. If your path requirement is 250 ft/NM, it is shallower than a standard 3 degree path. If it is 400 ft/NM, it is noticeably steeper. Once values start climbing toward 500 ft/NM or more, many operations require a careful look at aircraft configuration, weather, speed management, and stabilized approach criteria.
| Descent angle | Approximate feet per NM | Operational meaning |
|---|---|---|
| 2.5 degrees | 265 ft/NM | Shallow profile, often easy to manage with light drag |
| 3.0 degrees | 318 ft/NM | Common standard glide path reference |
| 3.5 degrees | 371 ft/NM | Steeper than normal, requires closer monitoring |
| 4.0 degrees | 424 ft/NM | Steep profile, often published with caution |
| 4.5 degrees | 477 ft/NM | Very steep for many routine operations |
The values above come from trigonometry. Specifically, feet per nautical mile can be approximated by multiplying the tangent of the path angle by the number of feet in a nautical mile, which is about 6,076 feet. For 3 degrees, the result is roughly 318 ft/NM. That single number is so useful that many pilots memorize it early in instrument training.
Converting feet per NM into feet per minute
After you compute the gradient, the next practical step is often finding the vertical speed target. To do that, multiply your feet per NM by your groundspeed in nautical miles per minute. Since knots already mean nautical miles per hour, divide knots by 60 to get nautical miles per minute.
The full formula is:
fpm = (ft/NM) × (knots / 60)
This is the same logic behind the familiar rule of thumb used on a 3 degree approach: groundspeed × 5 gives an approximate descent rate in feet per minute. The rule is approximate because 318 divided by 60 is about 5.3, but many pilots use 5 for a quick cockpit estimate.
| Groundspeed | Approx. vertical speed for 3 degree path | Exact value using 318 ft/NM |
|---|---|---|
| 90 knots | 450 fpm | 477 fpm |
| 120 knots | 600 fpm | 636 fpm |
| 140 knots | 700 fpm | 742 fpm |
| 160 knots | 800 fpm | 848 fpm |
| 180 knots | 900 fpm | 954 fpm |
These figures show why speed management matters so much. The same path becomes a very different required FPM target as groundspeed changes. A path that is comfortable at 110 knots might require a much higher, potentially destabilizing descent rate at 180 knots.
Using the calculator effectively
This calculator is built for practical use. You enter the altitude change, the distance available, and optionally a groundspeed. The tool converts everything to aviation-friendly units, computes feet per nautical mile, estimates gradient percent, and gives you a vertical speed target if speed is provided. It also compares your path to a standard 3 degree reference so you can quickly tell if your planned profile is shallow, normal, or steep.
Best use cases
- Planning a top-of-descent segment to meet an altitude restriction
- Checking whether a published departure climb gradient is achievable
- Cross-verifying VNAV behavior in training or simulation
- Understanding whether a nonstandard approach angle is manageable
- Converting metric distances or altitudes into standard aviation units
Common mistakes when calculating feet per NM
1. Mixing nautical miles with statute miles
Aviation navigation is built around nautical miles, not statute miles. One nautical mile is longer than one statute mile, so using the wrong unit can produce a misleading path requirement. This calculator accepts statute miles and kilometers but converts them to NM before solving.
2. Confusing feet per NM with feet per minute
Feet per NM tells you the shape of the path over distance. Feet per minute tells you the rate needed right now based on your speed. If your groundspeed changes, your required FPM changes too, even if the path in feet per NM stays exactly the same.
3. Ignoring tailwinds and headwinds
Groundspeed, not indicated airspeed, determines how many nautical miles you travel per minute. A strong tailwind on final can drive the required descent rate much higher than expected. A headwind can reduce the needed FPM for the same path.
4. Forgetting stabilization criteria
Even if the math says a path is technically possible, good airmanship still requires a stable profile, proper energy state, and compliance with aircraft limits and standard operating procedures. A steep path combined with high speed is often a setup for an unstable approach.
Climb gradients and regulatory context
Feet per NM is not just for descents. It is also widely used in departure procedure design. In the United States, many IFR departure procedures and obstacle departure procedures express minimum climb requirements in feet per nautical mile. Pilots must then convert that gradient into a required feet-per-minute climb based on actual groundspeed. This is one reason feet per NM remains so important in flight operations.
For example, if a procedure requires 300 ft/NM and your groundspeed after takeoff is 120 knots, the required climb rate is about 600 fpm. If the same procedure is flown at 150 knots, the required rate becomes about 750 fpm. The gradient has not changed, but the time-based demand has increased.
Quick mental math rules
- 3 degree path is about 318 ft/NM.
- For a quick descent-rate estimate, groundspeed × 5 is a useful approximation for a 3 degree path.
- Knots divided by 60 gives NM per minute.
- Altitude to lose divided by distance in NM gives feet per NM.
- If your result is much above 318 ft/NM, expect a steeper-than-normal profile.
Authoritative references and further reading
If you want to go deeper into approach geometry, IFR procedure design, and climb or descent gradients, these official and academic resources are highly useful:
- Federal Aviation Administration Aeronautical Information resources
- FAA Instrument Procedures Handbook
- MIT educational materials on flight path angle and performance concepts
Final takeaway
To calculate VS in feet per NM, divide the altitude change by the available distance in nautical miles. That gives you the vertical gradient of the path. If you also know groundspeed, convert the path into feet per minute by multiplying feet per NM by groundspeed divided by 60. This simple relationship supports descent planning, climb compliance, and approach stability decisions.
In day-to-day operations, the most important reference number to remember is that a 3 degree path is about 318 ft/NM. Once you know that, you can quickly compare almost any planned path against a familiar standard. Use the calculator above whenever you want a faster, cleaner, and more visual way to evaluate vertical profiles in aviation.