For a non-ILS approach, what altitude should be set in the MCP when using VNAV to meet altitude constraints prior to the published FAF?

Prepare for the Delta 737 PA-LOD Exam with flashcards and multiple choice questions. Each question includes hints and explanations, ensuring you're ready for exam day!

Multiple Choice

For a non-ILS approach, what altitude should be set in the MCP when using VNAV to meet altitude constraints prior to the published FAF?

When flying a non-precision approach with VNAV and you have altitude constraints before the final approach fix, you set the MCP to the published minimum altitude (DA/DDA/MDA) rounded up to the next 100 feet. This ensures you stay at or above the required altitude as you descend toward the FAF, preserving obstacle and constraint clearance in the VNAV logic. The 100-foot rounding matches typical autopilot/ FMC altitude step increments and provides a safety margin against rounding or system tolerance. Setting to runway elevation or using a 50-foot rounding could let you undershoot the constraint, and there isn’t a precision Final Approach Fix altitude for a non-precision approach to use.

When flying a non-precision approach with VNAV and you have altitude constraints before the final approach fix, you set the MCP to the published minimum altitude (DA/DDA/MDA) rounded up to the next 100 feet. This ensures you stay at or above the required altitude as you descend toward the FAF, preserving obstacle and constraint clearance in the VNAV logic. The 100-foot rounding matches typical autopilot/ FMC altitude step increments and provides a safety margin against rounding or system tolerance. Setting to runway elevation or using a 50-foot rounding could let you undershoot the constraint, and there isn’t a precision Final Approach Fix altitude for a non-precision approach to use.

More practice questions