Missed approach point (MAP or MAPt) is the point prescribed in each instrument approach at which a missed approach procedure shall be executed if the required visual reference does not exist.[1] It defines the point for both precision and non-precision approaches wherein the missed approach segment of an approach procedure begins. A pilot must execute a missed approach if a required visual reference (normally the runway or its environment) is not in sight upon reaching the MAP or the pilot decides it is unsafe to continue with the approach and landing to the runway. The missed approach point is published in the approach plates and contains instructions for missed approach procedures to be executed at this point.

MAPt during a non-precision approach

Definition of MAP depends on whether the approach flown is a precision or a non-precision one:[2][3]

In both cases, the pilot in command must make a clear and unequivocal Yes/No decision upon arrival at the MAP point – either the runway (or its specified environment) is positively visible and accessible for landing using a safe and stabilized approach (i.e. no excessively steep bank or descent angles required), in which case the approach to landing may be continued, or else the approach must be discontinued and the published missed approach procedure must be initiated immediately.

Visual descent point (U.S.) edit

A concept related to the missed approach point is the visual descent point (VDP). Determination of its location is done by the designers of the instrument approach procedure, but typically this is a point on the final approach course of a non-precision approach, from which the aircraft would be able to continue its descent from the MDA to the runway threshold while maintaining a standard 3° descent angle while being assured obstacle clearance.[5] In other words, usually it is the point (on the profile view of the approach) where a line depicting a 3° descent angle would intercept the horizontal line at the MDA. If the pilot does not have the required visual reference to continue the descent from the MDA at this point, he/she must continue to fly at or above the MDA, and the rapidly steepening descent angle required to complete a successful landing on the runway means that a safe and successful approach becomes less likely.

The concept of VDP was developed by the FAA to encourage pilots to decide to initiate a missed approach before reaching the MAP, in a situation where the runway or its environment is not visible at a normal descent angle. Conversely, if the runway is visible at the VDP, the pilot may continue descent, following a standard descent angle to the runway, while being assured terrain and obstacle clearance.[5] The VDP is always located before reaching the MAP, and is a more useful checkpoint for making the decision whether to continue on the approach or to go around than the MAP itself.[6]

The following is the official FAA definition of VDP:

"A defined point on the final approach course of a nonprecision straight-in approach procedure from which normal descent from the MDA to the runway touchdown point may be commenced, provided the approach threshold of that runway, or approach lights, or other markings identifiable with the approach end of that runway are clearly visible to the pilot."[1]

See also edit

References edit

  1. ^ a b Pilot/Controller Glossary. FAA. 2013-03-07. Archived from the original on 2009-09-27. Retrieved 2013-05-06.
  2. ^ "Section 5-4-20f4. Circling Minimums". Aeronautical Information Manual. FAA. 2013-03-07. Retrieved 2013-05-06.
  3. ^ "Section 5-4-21. Missed Approach". Aeronautical Information Manual. FAA. 2013-03-07. Retrieved 2013-05-06.
  4. ^ "Section 5-4-5j. Pilot Operational Considerations When Flying Nonprecision Approaches". Aeronautical Information Manual. FAA. 2013-03-07. Retrieved 2013-05-06.
  5. ^ a b "Section 5-4-5i. Vertical Descent Angle (VDA) on Nonprecision Approaches". Aeronautical Information Manual. FAA. 2013-03-07. Retrieved 2013-05-06.
  6. ^ "Constant-angle Nonprecision Approach" (PDF). Flight Safety Foundation. August–November 2000. Retrieved 2013-03-03.