Stabilized Approach Criteria: The Interview Answer

Short answer: Per FAA Advisory Circular (AC) 91-79A, an approach must be stabilized before descending through 1,000 feet above touchdown zone elevation (TDZE) in instrument meteorological conditions (IMC) or 500 feet above TDZE in visual meteorological conditions (VMC). The airplane must be in the landing configuration with checklists complete, on the proper 3-degree glidepath and lateral track using only normal bracketing, and at an indicated airspeed between VREF and VREF + 5 knots (plus wind adjustments). If the airplane is not stabilized at the gate, you must execute an immediate go-around.

Last checked November 6, 2026.

The FAA Stabilized Approach Criteria and Gates (AC 91-79A)

When an interview panel asks you to define a stabilized approach, they want the exact parameters and altitude gates from FAA guidance. Per AC 91-79A (Mitigating the Risks of a Runway Overrun Upon Landing, with Change 2 issued 2/20/18), a stabilized approach is the first line of defense in preventing a runway overrun. You confirm your stabilized parameters at 1,000 feet above TDZE in IMC or 500 feet above TDZE in VMC, which is about 1 to 2 minutes from touchdown.

To meet the stabilized approach concept in AC 91-79A Appendix 1, your aircraft must meet six core elements before passing through the gate:

  • Landing configuration established early: landing gear down, landing flaps selected, trim set, fuel balanced per the Airplane Flight Manual (AFM) or Pilot's Operating Handbook (POH), and landing checklist items completed.
  • Stabilized on profile: established on the correct lateral track and vertical glidepath (typically an electronic or visual 3-degree glidepath) requiring only normal bracketing corrections before descending through 1,000 feet above TDZE in IMC or 500 feet above TDZE in VMC.
  • Indicated airspeed within limits: not more than VREF + 5 knots (or the POH published approach airspeed) with appropriate wind or gust adjustments, and never less than VREF.
  • Controlled descent rate: matched to your groundspeed for the approach path, which you can estimate in feet per minute by multiplying your groundspeed in knots by 5.
  • Turbojet engine speed spooled: set at a power setting that allows the best engine response if you need a rapid power increase.
  • Target touchdown point discipline: flown onto the runway firmly in the first third of the runway (the target touchdown point in the Airplane Flying Handbook is approximately 1,000 feet down the runway, within the 500-to-3,000-foot touchdown zone) rather than floating in an extended flare to bleed off speed.
  • If your approach requires abnormal bracketing to stay on the lateral or vertical track, or if you do not cross the runway threshold at your planned airspeed, the approach is unstabilized and you must initiate an immediate go-around or balked landing.

The Interview Trap: AC 120-71B vs. AC 91-79A

A common trap in pilot technical interview questions is asking where the FAA publishes stabilized approach criteria. For years, pilots cited AC 120-71A (Standard Operating Procedures for Flight Deck Crewmembers).

On 1/10/17, the FAA issued AC 120-71B (Standard Operating Procedures and Pilot Monitoring Duties for Flight Deck Crewmembers), which canceled AC 120-71A. In AC 120-71B Paragraph 1.3, the FAA removed the stabilized approach criteria from the SOP advisory circular and relocated them to AC 91-79A.

Mentioning this regulatory shift in your interview shows the panel that you read current FAA documents rather than memorizing old study guides. You can explain that AC 120-71B now governs how airlines design SOPs, checklists, and Pilot Monitoring (PM) intervention policies, while AC 91-79A houses the specific stabilized approach gates and landing performance physics.

Why the Criteria Exist: Runway Overrun Physics and Compound Penalties

Interviewers often follow up a technical definition by asking what happens if you push through a gate slightly fast or high. According to FAA and National Transportation Safety Board (NTSB) data cited in AC 91-79A, runway overruns during the landing phase account for about 10 incidents or accidents every year, with many resulting in fatalities. Operator training programs for runway overrun mitigation must include the go-around maneuver and the reasons to initiate a go-around.

A study of FAA and NTSB data indicates that the following hazards increase the risk of a runway overrun: an unstabilized approach, high airport elevation or high density altitude, excess airspeed over the threshold, high airplane landing weight, landing beyond the touchdown point, downhill runway slope, excessive height over the runway threshold, delayed use of deceleration devices, landing with a tailwind, and a wet or contaminated runway. These factors are cumulative.

When you assess your actual landing distance at the time of arrival (TOA) based on existing weather, runway conditions, weight, and configuration, AC 91-79A states that you must add a minimum acceptable safety margin of at least 15 percent. That adjusted landing distance must fit within the Landing Distance Available (LDA).

  • Excess airspeed: A 10-percent increase in final approach speed results in a 20-percent increase in landing distance, assuming a normal flare and touchdown. In Appendix 1, the FAA notes that a 10-percent excess landing speed causes at least a 21-percent increase in landing distance and reduces normal force on the braking surfaces because of increased lift.
  • Excessive Threshold Crossing Height (TCH): Certified AFM landing distances assume the landing gear crosses at 50 feet over the runway threshold. Every 10 feet above the standard 50-foot height increases your landing air distance by 200 feet. Crossing at 100 feet adds 1,000 feet to your landing distance.
  • Tailwind penalty: A tailwind increases your touchdown groundspeed. The first 10 knots of tailwind increases landing distance by 21 percent.
  • Downhill runway slope: Every 1 percent of downhill runway slope increases landing distance by 10 percent (a factor of 1.1). Performance computations often only account for downhill slope when it exceeds 2 percent.
  • Landing weight: A 10-percent increase in landing gross weight increases landing velocity by 5 percent and landing distance by 10 percent.
  • Delayed deceleration devices: AFM landing data typically assumes a 1-second increment between successive actions to deploy manual deceleration devices (spoilers, thrust reversers, and wheel brakes). At 118 knots (200 feet per second), a 2-second delay in deploying manual spoilers can add almost 400 feet to stopping distance. A conservative rule is to add 200 feet to the landing distance for every second beyond 2 seconds taken to deploy deceleration devices.
  • Relaxed braking: If you do not maintain maximum braking until the airplane reaches a full stop, add 20 percent to the rollout distance.
Approach or Landing Deviation FAA Distance Penalty Rule Resulting Distance on a 3,000-ft Baseline
On speed, 50-ft TCH, zero wind, level runway Baseline certified AFM distance 3,000 feet
10% excess airspeed over threshold +20% landing distance (1.20 x 3,000) 3,600 feet (+600 feet, or +2,400 feet if all four deviations below combine, by our calculation from AC 91-79A examples, before the 15% safety margin for time-of-arrival assessment is applied to actual landing distance.)
100-ft TCH (50 ft above standard 50-ft TCH) +200 feet per 10 feet above 50 feet 4,000 feet (+1,000 feet alone on a 3,000-ft baseline, per AC 91-79A Note, Paragraph 8g)
10-knot tailwind +21% landing distance (1.21 x 3,000) 3,630 feet (+630 feet alone on a 3,000-ft baseline, per AC 91-79A Paragraph 8i(3))
3-second deceleration deployment (1 sec over 2-sec baseline) +200 feet per second over 2 seconds 3,200 feet (+200 feet alone on a 3,000-ft baseline, per AC 91-79A Paragraph 8h(4))

Pilot Monitoring Duties, Callouts, and Go-Around Intervention (AC 120-71B)

Knowing the numbers is only half of the interview answer. Panel captains use pilot scenario interview questions to test what you actually do when the other pilot flies an unstabilized approach. AC 120-71B Chapter 6 defines effective monitoring and cross-checking as the last barrier or line of defense against accidents.

In a two-pilot crew, one pilot is always designated as Pilot Flying (PF) and one as Pilot Monitoring (PM). The PF manages, and the PM monitors, the current and projected flightpath (defined as aircraft trajectory and energy state in flight) at all times. During IFR operations below 10,000 feet in a terminal area, which AC 120-71B defines as a high workload environment, only one pilot should be heads-down at any time, and the pilot going heads-down must make a verbal callout.

Per AC 120-71B Paragraph 6.6, an operator's flightpath intervention policy must establish three elements: deviation parameters, required callouts, and conditions for takeover. When a flightpath deviation occurs on approach, the human-to-human intervention sequence works in clear steps:

  • Step 1 (Detect and Call Out): The PM detects a flightpath or energy deviation and makes a clear verbal callout, such as calling '1-dot high'.
  • Step 2 (Acknowledge and Correct): The PF responds verbally with 'correcting' and returns the aircraft to the glidepath in a timely manner.
  • Step 3 (Two-Challenge Takeover and Go-Around): If the PF does not respond or fails to correct the flightpath after two successive challenges (whether due to task saturation, channelized attention, or subtle incapacitation), and safety requires action, the PM calls 'I have control, going around' and initiates the go-around as PF.

Checklist Discipline and Autoflight Mode Awareness on Approach

Stabilized approaches break down when crews mismanage configurations or automation prior to the gate. AC 120-71B Chapter 5 states that a checklist should never be depended upon to initiate a change in aircraft configuration. Instead, configuration changes must be keyed to specific operational events, such as extending the landing gear at glideslope intercept, using a clear command from the PF and an acknowledgment from the PM.

Once configured, the checklist serves as a verification tool. On approach, flight guidance items are critical checklist items that require confirmation and response by both the PF and PM. In the before-landing phase, the landing gear and flaps are critical items requiring confirmation and response by both pilots. Instead of generic responses like 'set' or 'checked', AC 120-71B recommends responding with the actual system status, lever position, or specific value.

Similarly, autoflight mode confusion is a major vulnerability during approach transitions. The Flight Mode Annunciator (FMA) is the primary source depicting 'who is doing what' regarding aircraft trajectory and energy. Both pilots must check the FMA after any selection on the mode control panel. Many operators use structured callout protocols from AC 120-71B such as 'Confirm, Activate, Monitor, Intervene (CAMI)' or 'Verbalize, Verify, and Monitor (VVM)' so neither pilot misses a latent armed-to-active mode change or subtle mode reversion.

Tying Stabilized Approaches to CRM and Safety Culture (AC 120-51E)

When you answer CRM interview questions for pilots, connect your stabilized approach answer to AC 120-51E (Crew Resource Management Training, issued 1/22/04). Investigations into air carrier accidents show that human error is a contributing factor in 60 to 80 percent of all air carrier incidents and accidents, most often tied to poor group decision-making, ineffective communication, and inadequate task management rather than stick-and-rudder skill.

Both AC 120-71B and AC 120-51E state that effective crew coordination depends on the crew sharing a mental model of each task, and that shared mental model is founded on clear SOPs. Crew monitoring and cross-checking are especially critical during approach and landing, when controlled flight into terrain (CFIT) accidents are most common.

Finally, emphasize Inquiry, Advocacy, and Assertion. AC 120-51E states that manuals and training must make it clear that appropriate questioning of one pilot's decision or action by another pilot is encouraged and carries no negative repercussions. If ATC issues a slam-dunk clearance or requests excessive speed close to the airport, AC 91-79A Appendix 1 directs you to advise ATC whenever you cannot achieve a stabilized approach profile, and to decline the approach or execute a go-around rather than forcing an unstabilized landing.

Pre-Gate to Touchdown Crew Checklist for Interview Scenarios

When an interviewer walks you through a deteriorating approach scenario (such as a tailwind shift on short final in pilot interview weather questions), use this five-step operational checklist built from AC 91-79A and AC 120-71B to structure your response:

    1. Time-of-Arrival (TOA) Assessment Before the Approach: Pull current METAR/ATIS and Runway Condition Codes (RwyCC) from the Runway Condition Assessment Matrix (RCAM). Calculate actual landing distance for your current weight, configuration, wind, and slope, add the minimum 15% safety margin, and verify it fits within the LDA.
    1. Event-Keyed Configuration: Refuse or renegotiate ATC speed or altitude requests that prevent stabilization. Key gear and flap extensions to operational events (such as glideslope intercept) and verify gear, flaps, and flight guidance with both pilots confirming.
    1. The 1,000-ft IMC / 500-ft VMC Gate Check: Confirm landing configuration, checklists complete, 3-degree glidepath and lateral track with normal bracketing only, airspeed between VREF and VREF + 5 knots, sink rate matched to 5 x groundspeed, and engines spooled.
    1. Active PM Monitoring and Two-Challenge Rule Below the Gate: If a deviation develops below the gate, the PM calls it out immediately. If the PF does not correct after two challenges, or if the aircraft becomes unstabilized at or below the gate, call 'I have control, going around' and execute the missed approach.
    1. Touchdown and Immediate Deceleration: Cross the threshold at 50 feet on target airspeed. Fly a firm touchdown in the touchdown zone (do not float), confirm automatic ground spoilers and autobrakes deploy (which increases wheel loading by up to 200 percent), lower the nosewheel immediately for directional control, and apply reverse thrust and maximum antiskid braking.
  • After you walk through these five steps in your answer, you can tie the decision back to your company SOPs and non-punitive safety culture.

Practice question

What are the FAA stabilized approach criteria, and what would you do as Pilot Monitoring if the Captain is 15 knots fast and a dot high passing through the gate?

Example answer, written by us. It is not a real applicant's story. Per FAA AC 91-79A, since AC 120-71B moved the criteria there, an approach must be stabilized before descending through 1,000 feet above TDZE in IMC or 500 feet above TDZE in VMC. That means we are in the final landing configuration with gear down, landing flaps set, trim set, and the before-landing checklist complete. We need to be on the 3-degree glidepath and lateral track using only normal bracketing, with a descent rate matching roughly 5 times our groundspeed, engines spooled, and indicated airspeed between VREF and VREF plus 5 knots, adjusted for wind. If I am Pilot Monitoring and the Captain is 15 knots fast and 1 dot high approaching the gate, my duty under AC 120-71B is to call out the exact deviations immediately: 'Airspeed, 1 dot high.' I expect the Captain to respond 'correcting' and fix the profile before the gate. Once we pass through the 1,000-foot IMC or 500-foot VMC gate unstabilized, the decision is binary. I would call for an immediate go-around. If the Captain does not respond to two successive challenges, I would state, 'I have control, going around,' and execute the missed approach myself.

It names both AC 91-79A and the AC 120-71B regulatory change up front, gives the exact FAA gate altitudes and VREF + 5 knot tolerance, and walks through the exact AC 120-71B Paragraph 6.6.2 two-challenge takeover callout without hesitation.

Practice this on Fourstripe. A panel captain asks TMAAT, about-you, technical and scenario questions out loud, follows up on what you said, and scores every answer. 7-day trial, then from $149 a week. Start a practice interview

Fourstripe is not affiliated with any airline.

Frequently asked questions

Are stabilized approach criteria still in AC 120-71B?

No. When the FAA issued AC 120-71B on 1/10/17, canceling AC 120-71A, it removed the stabilized approach criteria from AC 120-71B and relocated them to AC 91-79A, Mitigating the Risks of a Runway Overrun Upon Landing.

What are the FAA altitude gates and airspeed limits for a stabilized approach?

Per AC 91-79A Appendix 1, the airplane must be stabilized before descending through 1,000 feet above TDZE in IMC or 500 feet above TDZE in VMC. Indicated airspeed must be no more than VREF + 5 knots (or POH approach speed) with appropriate wind adjustments, and never less than VREF.

What should the Pilot Monitoring do if the Pilot Flying ignores a deviation callout on approach?

Under AC 120-71B Paragraph 6.6.2, the PM verbalizes the deviation (such as '1-dot high') and expects the PF to respond 'correcting' and fix the flightpath. If the PF does not respond or correct the flightpath after two successive challenges, and safety indicates, the PM calls 'I have control, going around' and initiates the go-around as PF.

How do excess airspeed, high threshold crossing, and tailwinds affect landing distance?

Per AC 91-79A Paragraph 8, a 10-percent increase in final approach speed increases landing distance by 20 percent (and at least 21 percent in Appendix 1), while the first 10 knots of tailwind increases landing distance by 21 percent. Additionally, every 10 feet above the standard 50-foot threshold crossing height adds 200 feet to your landing air distance.

How do you estimate the required descent rate on approach?

Per AC 91-79A Appendix 1, multiply your groundspeed in knots by 5 to get a usable target descent rate in feet per minute. Combined with disciplined airspeed control, slight adjustments in the rate of descent will keep you on the glidepath.

Sources

Related guides