Descend the A320 Like a REAL Airline Pilot

Main ideas / lessons

• Real airline descents aren’t usually “FMGC from A to B then smooth autopilot landing.” In real operations, ATC restrictions, busy frequencies, traffic below/around, and airspace limitations often prevent hitting the planned top-of-descent/altitude constraints—so pilots must manage energy and rejoin the path safely.

• Descent management is fundamentally energy management. The Airbus carries huge energy relative to small aircraft. If you arrive at the profile too high, you must manage how quickly you lose altitude and how you slow down to avoid overspeed or “blowing through” the profile.

• A practical mental math method (“three times table”) is used to plan distance to the runway.

• Wind adjustments refine the required distance.

• If you’re too high: mitigate by changing descent mode (managed vs open descent), adjusting speed, and using a 757-style “how far low per how fast” trick to regain the profile.

• If you’re off the path in the other direction (too low): use a Constant Descent Approach (CDA) and carefully manage configuration/VS to regain a stable ILS capture later.

• A stable, repeatable approach briefing is portrayed as the most important procedural skill. It includes a “mental model,” threats/traps, and who will remind/monitor key callouts.

• Flap 3 landing (modern Airbus practice) is presented as efficient and quieter, with specific checklist/PERF/GPWS configuration steps and handling notes.

---

Methodology / instructions

1) Distance planning for descent (the “three times table”)

Use a mental rule:

• Distance (miles) to land ≈ 3 × altitude (in thousands of feet)

Example given:

• At 33,000 ft: (33 × 3 = 99) → about 99 NM to land

Then add margin for deceleration:

• Add ~10 NM to account for slowing down
  • 99 + 10 = 109 NM total distance needed

---

2) Wind correction to landing distance

For track/miles planning:

• Tailwind: for every 10 kt tailwind, add 1 mile
• Headwind: for every 10 kt headwind, subtract 1 mile

---

3) What to do when ATC keeps you high / you miss the restriction

ATC may not grant clearance due to:

• Busy frequency → you miss the top-of-descent opportunity
• Traffic below / crossing traffic
• Airspace restrictions causing step descents

When you finally get clearance but you’re over/above the profile:

• Switch from managed descent to open descent (as described in the example)
• Manage speed manually to control energy:
  • Airbus managed speed target referenced: ~270 kt (example)
  • If too high/too fast, select an appropriate speed rather than allowing it to run away toward overspeed limits
• Monitor the Airbus overspeed boundary (“barber pole”) as altitude decreases and speed increases

---

4) Recovering from excess energy (too fast/too high): the “757 trick”

Rule stated:

• For every 10 kt you are fast, be ~300 ft low on the profile

Example workflow:

• FMGC wants 270 kt, but aircraft is at 310 kt
• Fast by 40 kt → target low:
  • ((40/10) × 300 = 1,200 ft) low
• Descend below the magenta path/VDEV to bleed energy
• Then switch back to managed descent speed (or manage speed) when nearing the target low point

Timing guidance:

• Don’t wait until exactly 1,200 ft because pitch/speed response takes time
• Example: start the transition around ~1,120–1,150 ft, then it should rejoin the profile as managed speed takes over

---

5) When you’re off the profile due to vectoring / heading changes (track mileage corrections)

If ATC headings cause incorrect track miles and/or profile alignment:

• “Clean up” the FMC points:
  • Remove incorrect points and insert correct ones so track miles become accurate again
• If you’re short of miles / need more distance:
  • Request or fly a heading away from the airport to gain time/distance
  • Then update FMC/approach activation so it recalculates the needed segment distance

---

6) If you become too low: use CDA (Constant Descent Approach) / re-join later

Intentions stated:

• Fly an efficient approach
• Save fuel
• Reduce noise impact

Operational constraints mentioned for the Manchester example:

• During CDA below certain altitude:
  • Must not have a straight-and-level segment for more than 6 miles
  • CDA guidance references “measured anything below 6,000 ft”

“Gold” aim:

• Achieve double capture of:
  • glide slope + localizer at the “center fix”
• Use VS to control being on-target for intercept/fix timing

---

7) Approach configuration and flap schedule (as taught)

Flap logic depends on the airport; general approach described:

• Inside 15 NM and outside 11 NM: take flaps 1 in that band
• Around glide interception:
  • Flaps 2 typically used either:
    • just before the glide, or
    • just after the glide
• Reminder:
  • When selecting flaps 2, expect ballooning—don’t balloon through the glide slope

Example handling with ILS:

• Intercept and stabilize glide slope/localizer
• Fine-tune VS near intercept

---

8) Flaps for landing: selecting and validating Flap 3

Rationale stated:

• Becoming standard
• Quieter
• Lower engine power → better for neighbors
• Slight fuel savings accumulate over many flights

Procedure / steps described:

• In the MCDU PERF page:
  • Select Config 3 (with a star)
  • Activate Flap 3
• In the GPWS panel:
  • Set landing configuration to flap 3 so GPWS alarms match
• Confirm on the upper display that flaps config 3 is set
• Brief/callout emphasis:
  • “Flap three” repeated so the crew won’t discover late

Handling / performance notes:

• Flap 3 landing pitch is higher (example ~5° vs typical approach ~2.5–3°)
• Mitigation:
  • Add speed so the aircraft lowers pitch
  • Rule given: for every 2 kt added, pitch drops ~0.5°
• Requires performance checking:
  • Additional speed can increase landing distance
  • CEO/NEO V speeds mentioned as increasing (example values given)
• Braking caution after landing:
  • Use brake fans to cool brakes
  • Fire risk mentioned if hot brakes meet Skydrol temperatures (flashover context)

---

9) Mode/tool usage cues mentioned during descent and approach

• Airbus descent mode concepts referenced:
  • managed vs open descent
• Boeing equivalents referenced:
  • VNAV / level change
• Airbus “expedite descent” discussed:
  • Could be used to descend quickly, but not recommended at height
  • Prefer manual speed / open descent handling instead
• FCU metric alt button mentioned (flight-sim only benefit):
  • Use it to quickly estimate distance with the three-times-table style mental method

---

10) The “real-world” emphasis: brief and assign monitoring

Descent success depends on briefing:

• Provide the “mental model” of how the descent will be flown
• Identify threats/traps (e.g., terrain/speedbrake considerations)
• Define when to use VS near runway:
  • Example brief target: inside 15 NM / outside 11 NM
  • Gear reminder callout at “by 3 by 5 miles” (as stated)

Crew role:

• First officer/partner should actively question deviations:
  • “Did you not want to do that then?”

---

Speakers / sources featured

• Captain Mark: speaker; real-life Airbus captain based in Manchester; also references prior training/trainer “Tony Layfield”
• WingFlex: sponsor/source of cockpit hardware mentioned (MCDU, EFIS/FCU/RMP combo, mounts/kit)