Selected passages from the existing NFA article. This public introduction offers an operational overview; the complete study is in the member library.
Stabilization is not a point. It is a state.
A stabilized approach is often associated only with crossing a predetermined altitude. That concept is incomplete. An aircraft may cross that altitude apparently within parameters and become unstable seconds later.
Before the gate, a condition still being adjusted must converge clearly and in a controlled manner. The crew continuously monitors speed, flight path, descent rate, configuration, thrust, alignment, workload and monitoring capacity. At and below the gate, operator criteria and go-around policy govern: a favorable trend does not authorize continuation outside mandatory criteria. Monitoring continues through landing.
Energy tells the story of the approach
The aircraft carries potential energy associated with altitude and kinetic energy associated with speed. When both high and fast, it must dissipate both. The closer it is to the runway, the less time is available. Excess or insufficient energy can compromise flight path, control and landing performance.
An extended speed restriction, late descent, short vector, tailwind, runway change or late FMS programming can initiate a sequence that becomes obvious only after margins have narrowed. Energy should be anticipated, not merely corrected. Early recognition preserves options; late recognition accumulates tasks.
High, fast and still trying
Imagine arriving on final above the desired profile and at excessive speed. Increased descent rate, deceleration, device extension, automation changes, thrust adjustments, ATC interaction, configuration, checklist completion and additional briefing compete for the same time.
Individually, these actions may be normal. The problem is their concentration into an increasingly short period. The crew loses anticipation: instead of managing the approach, it starts chasing it. This transition is not always clearly recognized.
The most dangerous factor may be the trend
An isolated parameter describes the present condition. The trend describes where the aircraft is heading. A small speed deviation with predictable deceleration, correct profile, normal configuration and low workload is not equivalent to the same deviation combined with excess altitude, delayed configuration and repeated interventions.
The PM should ask not only “Are we within limits?” but also “Are we converging?”. Without convergence, the situation may deteriorate before a formal limit is exceeded. This assessment supplements criteria; it never replaces them.
The role of the PF
The Pilot Flying manages flight path, speed, energy, configuration and automation. When an approach deteriorates, attention may become excessively focused on recovering one parameter: speed first, then profile, configuration and descent rate. Narrowed attention can obscure the overall picture.
The question should remain simple: “Is the aircraft reaching a stable condition predictably, or am I trying to force that stability?”. Forcing an approach is different from managing it.
Educational material. Current aircraft and operator manuals, SOPs, mandatory criteria and required actions take precedence. These passages do not introduce new procedures or authorize exceptions.
Technical sources from the original article
- FAA — Stabilized Approach and Landing ↗
- FSF — ALAR 7.1: Stabilized Approach ↗
- FSF — ALAR: Automation, Energy Management, Being Prepared to Go Around, Manual Go-Around, Runway Excursions, Landing Distances ↗
- FSF — Go-Around Decision-Making and Execution Project ↗
- FAA — AC 120-71B: SOP and Pilot Monitoring Duties ↗
NFA PROFESSIONAL
Explore the complete study
Continue with the complete existing article, its operational analysis, examples and references in the member library.
Access the complete study in the member area →The professional plan is in preparation. Paid subscriptions are not yet open.CONTINUE THE COLLECTION
Go-Around Decision →
Member Login