Printer Friendly

R U down with VDP's? Visual descent points are one of those IFR subtleties that separate the hacks from the pros. (Don't worry. It's easy to go pro.).

Pop quiz: What are the three conditions required to descend below MDA or DA? If you answered, "Ability to make a normal descent and landing, flight vis at or above published vis, and runway environment in sight", you get a B+.

If you answered, "Aren't there four conditions?" then go to the head of the class. The fourth is unknown to the vast majority of pilots: The airplane must have reached or passed the visual descent point (VDP), if published.

Why Bother with the V?

I can hear the head scratching from many of you now. VDPs are one of those little IFR tidbits that slip from the awareness of many pilots. VDPs aren't frequently used (and become less important every day with vertical guidance courtesy of WAAS), yet they can still be a bacon saver and are worthy of a minute's review.

Only found on non-precision approaches where some means of along-track-distance determination exists (DME or GPS), a VDP is displayed by a "V" on the profile view. It represents the point in space where an aircraft at MDA would intersect a three-degree descent path to the runway and where most VASIs/PAPIs would show white and red.

The purpose of a VDP is to ensure that a pilot does not leave MDA too early and compromise terrain clearance. In low visibility, particularly on "black hole" approaches where the area under the final approach course and surrounding the airport is not lit, there can be a powerful illusion of being too high. On a non-precision approach, the terrain clearance at MDA can be as little as 250 feet. Starting down for the runway too early has intimately acquainted more than one aircraft with the terrain short of the runway.

[ILLUSTRATION OMITTED]

The AIM states that a "pilot should not descend below the MDA prior to reaching the VDP and acquiring the necessary visual reference." Additionally, leaving MDA significantly after the VDP may not be wise. Every bit of distance traveled at MDA beyond the VDP will cause the descent angle to the runway to steepen. Depending on the length of the runway, the flight characteristics of the airplane and exactly how far past the VDP the pilot has traveled, it may be impossible to make a safe descent to a straight-in landing (unless you're flying a Wilga or approaching a really long runway).

[ILLUSTRATION OMITTED]

Many turbine operators flying aircraft unforgiving of steep descents to the runway use the VDP as the actual missed approach point. If the runway is not in sight at the VDR the missed is initiated by beginning a climb while continuing to track the final approach course. Once the official MAP is reached, the appropriate missed approach procedure can commence.

This represents a two-fold increase in safety: The temptation to perform a screaming 1500 FPM descent to the runway is eliminated, and much better terrain clearance is provided on the missed.

Figure Your Own VDP

Not all approaches have a published VDP, but it's easy to calculate one on the fly. A standard three-degree path will descend 300 feet per mile. Divide the MDA in feet above touchdown by 300. The resulting number is the distance from the runway threshold to where the VDP is located. With an IFR GPS and a MAP at the threshold itself, we can usually read this number right off the unit. If we're using DME, we'll have to convert it to a DME number based on how far the DME source is from the threshold. If the MAP is before the threshold, we have to subtract that distance from the calculated VDP to get the real point from which we should descend.

As an example, we'll compute VDP for the VOR Rwy 16 approach to Beverly, Mass. The MDA of 720 feet is listed as 613 above touchdown. Divided by 300, we get 2.0 miles from the threshold to the VDR If we don't have GPS distance to the threshold, we can see that the threshold is at 11.8 DME on the approach. So we know that our VDP will be at 9.8 DME. Writing this directly on the profile view of the approach plate is highly recommended.

You can twist this number a bit for long runways. Suppose your destination is a former military field that's been retired to civilian air service. It sports a 9000-foot runway but only a non-precision approach. You calculate the VDP at two miles from the threshold, but you feel comfortable landing in the last 3000 feet. So, your early VDP is at two miles, but you know you can go an extra mile before clearly getting the runway and descending, and still have a reasonable approach angle to the last third of the runway.

Published VDPs are not in GPS databases, even VDPs shown on a GPS approach plate, so don't go looking for them in your GPS flight plan.

You'll always need to be watching for a specific number on the GPS or DME. But considering the significant safety improvement VDPs add to non-precision approaches, it's well worth the extra trouble to watch for them.

QUIZ

1. If you choose to fly to the LNAV/VNAV minimums for an RNAV (GPS) approach that lists both LNAV and LNAV/ VNAV minimums, you must:

a. Cross the FAF and descend as quickly as possible to the MDA, level off and proceed to the MAP.

b. Follow the glideslope/glidepath to the DA and then either land or immediately start your missed approach.

c. Follow the glideslope/glidepath to the DA and then level off and proceed to the MAP.

d. Usually b, but in some cases c is acceptable.

2. For straight-in approaches (such as a VOR Rwy 18 approach), the minimums section shows you the height above touchdown zone. For approaches with only circling minimums (such as a VOR-A approach), the minimums are height above airport. What about circling minimums published on straight-in approaches?

a. They show height above airport.

b. They show height above the touchdown for the straight-in.

c. They show average height above all available runways.

d. No figure is published.

3. How many aircraft approach categories does TERPS recognize? (Bonus points if you know which ones helicopters use.)

a. Four categories: A, B, C and D

b. Five categories: A, B, C, D and E

c. Five categories: A, B, C, D and Copter

d. Six categories: A, B, C, D, E and Copter

Answers on page 23

QUIZ ANSWERS (questions on page 19)

1. d. LNAV/VNAV is designed to be flown like an ILS where you descend following a glidepath to a DA and then either land or go missed. There are uncommon cases where the minimums for the LNAV/VNAV are actually higher than the LNAV minimums with the identical final approach course. In these cases, you could follow the LNAV/VNAV glidepath to the LNAV MDA and then continue to the MAP. Essentially, you're flying the LNAV approach in this case, but using the LNAVIVNAV glidepath as an advisory glidepath instead of a dive and drive.

[ILLUSTRATION OMITTED]

2. a. Just like an approach with no straight-in minimums, circling always shows height above airport,

3. d. There are five for fixed wing, although Cat E minimums don't normally appear on civilian plates. Vref for Cat E is 165 knots, which is a bit faster than most aircraft require for shooting an approach. If this Vref was 1.3 Vso, that would imply a stalling speed of 123 knots in the landing configuration, Helicopters use the Copter minimums, or Cat A if no Copter minimums are published.

Neil Singer scribbles on his approach plates as a mentor pilot in the northeast.
COPYRIGHT 2009 Belvoir Media Group, LLC
No portion of this article can be reproduced without the express written permission from the copyright holder.
Copyright 2009 Gale, Cengage Learning. All rights reserved.

Article Details
Printer friendly Cite/link Email Feedback
Title Annotation:APPROACH CLINIC; instrument flight rule
Author:Singer, Neil
Publication:IFR
Geographic Code:1USA
Date:Aug 1, 2009
Words:1290
Previous Article:Taking it one leg too far: most accidents require multiple factors coming into alignment. But breaking the chain takes a pilot alert enough to see...
Next Article:IFR by the sun and stars: not that long ago crews flew thousands of miles with no navigational aids except the sky itself. It's such an elegant...
Topics:

Terms of use | Privacy policy | Copyright © 2020 Farlex, Inc. | Feedback | For webmasters