ATP Checkride Study Guide

Answers come from the POH/AFM and the type-specific FSB Report — almost every good answer starts with your airplane's numbers, not generic ones. Differently than at commercial, the ACS expects you to:

• Explain and describe the operation of the aircraft systems and components using correct terminology (AA.I.A.S1)
• Recall immediate action items or memory items (AA.I.A.S2)
• Identify system or component limitations listed in the POH/AFM (AA.I.A.S3)

The knowledge elements sweep every system from landing gear to HUD (AA.I.A.K1–K16), but the evaluator samples; what's graded throughout is whether you answer in your airplane's terms and know where the limitation lives. The systems fundamentals — landing gear, brakes, and anti-skid (K1), powerplant (K2), fuel (K4), oil (K5), hydraulics (K6), flight controls (K12), and pitot-static (K13) — are built card-by-card in the Commercial guide's systems task; the ATP layer on each is your type's architecture and AFM limitations. K9's avionics sweep (ADS-B, CPDLC, GNSS, ELT, EFB) lives in the Instrument and Commercial guides, and TCAS and terrain warning systems are covered under Task I.E. Deferring inoperative equipment (AA.I.A.S4, K17) is exercised under Task II.A — the MEL and CDL cards live there.

Conditioned air is delivered to the cabin continuously; cabin altitude is controlled by regulating how fast that air leaves, through the outflow valve (PHAK ch. 7). The control system provides:

• A cabin pressure regulator — controls cabin pressure to the selected value in the isobaric range and limits it to a preset value in the differential range
• The outflow valve — the working muscle that meters exit air
• A safety valve — combination pressure relief (prevents exceeding the predetermined differential), vacuum relief (lets ambient air in if outside pressure exceeds cabin pressure), and dump valve (flight deck switch dumps cabin air)

A typical system holds a cabin altitude of about 8,000 feet at the airplane's maximum designed cruising altitude. Monitoring instruments: cabin differential pressure gauge, cabin altimeter, and cabin rate-of-climb indicator (PHAK ch. 7).

Structure. The fuselage is designed to withstand a particular maximum cabin differential pressure — the difference between cabin and ambient pressure — set by the structural strength of the cabin and the relationship of cabin size to probable rupture areas such as windows and doors (PHAK ch. 7).

Isobaric range: the system holds a constant cabin altitude as you climb.

Differential control: when the airplane reaches the altitude where the inside-outside difference equals the maximum differential, the system shifts over — any further climb produces a corresponding climb in cabin altitude, because the controller will not let the structural limit be exceeded (PHAK ch. 7).

That's why max operating altitude and max differential are paired limitations in the AFM — know both numbers for your type.

Target reversers: clamshell doors that swivel from the stowed position at the tailpipe to redirect exhaust forward.

Cascade reversers: normally on turbofans, often reversing only the fan air — blocking doors obstruct forward fan thrust and redirect it through cascade vanes.

The flow never fully reverses — the final exhaust path is about 45° from straight ahead, so efficiency is limited, and less than maximum rpm in reverse reduces it further. Reverse thrust is more effective at high speed than at low speed, so use it as soon as prudent after touchdown. Some types pitch nose-up when reverse is selected (worse combined with spoiler pitch-up) and must be firmly on the ground, nosewheel down, first. And remember the contrast with props: idle reverse on a propeller produces large drag; idle reverse on a jet produces very little (AFH ch. 16).

Uncommanded or inadvertent deployment of a thrust reverser while airborne is an emergency (AFH ch. 16). The design protections are layered:

• A lock system to keep reversers from operating in the air
• Another lock preventing operation with the thrust levers out of the idle detent
• An auto-stow circuit commanding reverser stowage any time deployment would be inappropriate — such as during takeoff and while airborne

The ACS names uncommanded reverse procedures explicitly (AA.I.A.K3), so know your AFM's procedure as a recall item: which lever motions are prohibited, what the airplane's controllability penalty is, and any airspeed limits the AFM imposes after a deploy. This is a place where the honest oral answer is your type's procedure, verbatim.

NTS is the automatic backstop for engine failure on a fixed-shaft turboprop: when propeller torque starts driving the engine, the system limits the torque the engine can extract and drives the blades toward feather to reduce drag (AFH ch. 15). The fixed-shaft engine needs it because a failed engine's windmilling propeller drives the compressor, absorbing large amounts of power — a control threat in a twin unless the propeller is feathered immediately. Two cautions for the oral:

• NTS is an emergency backup, not a substitute for feathering with the condition lever
• Contrast with a free power-turbine (split-shaft) engine like the PT6: the propeller isn't on the engine shaft, so it can be feathered with the basic engine still running, and prop rpm is selectable independent of gas generator rpm (AFH ch. 15)

A propeller synchronizer precisely matches rpm between engines. A synchrophaser goes one step further: it matches rpm and compares and adjusts the blade phase angle between propellers (AFH ch. 13). From the pilot's seat they operate similarly — the point of both is noise and vibration reduction. The ACS lists synchronizing and synchrophasing among the propeller knowledge elements alongside feathering, auto-feather, and NTS (AA.I.A.K3); if your type has a phase-control knob, be able to say what it's actually adjusting.

Flight director: computes and displays steering commands on the ADI — it incorporates the attitude display within its system, driven by a mode controller and flight director computer (IFH ch. 5).

Autopilot: can fly those same computed commands, and integrated systems allow more flight director modes as capability grows (IFH ch. 5).

FMS: supplies the navigation and performance problem the autoflight system is solving.

The crew discipline the ACS is probing (AA.I.A.R3 — monitoring and management of automated systems) shows up on the ground first: both pilots should review takeoff data entered in an FMS, or separately compute it and cross-check against the takeoff data card — and recalculate if plans change while taxiing (AFH ch. 16). State your operator's automation policy: who makes mode selections, who verifies, and what gets announced.

It means the evaluator is watching how you use the paper, not whether you can find it. The Task requires demonstrating the systems through the use of the appropriate checklists and normal and abnormal procedures (AA.I.A.S6), and separately requires recall of immediate action items or memory items, if appropriate (AA.I.A.S2) — so you must know which items your AFM designates as memory items, execute those from recall, and then confirm with the checklist. Detection and management of a malfunction (AA.I.A.R1, R2) is graded as a sequence:

1. Recognize from the indications
2. Silence and confirm the alert
3. Memory items, if published
4. The QRH/abnormal checklist
5. The follow-on decisions

Reciting a checklist item-by-item from memory when it isn't a memory item reads as worse discipline, not better.

Most turbojet airplanes capable of Mach-range cruise have some form of trim and autopilot Mach compensating device — a stick puller — to alert the pilot to inadvertent excursions beyond certificated MMO (AC 61-107, para 3-2). Two things the AC is blunt about:

• If a malfunction requires disabling the stick puller, the aircraft must be operated at speeds well below MMO, per the AFM procedures
• The stick puller should never be disabled during normal flight operations — the AC recounts operators disabling airspeed/Mach warnings to run past VMO/MMO, and the chain it invites: flutter, control-surface flow separation, aileron buzz or snatch, Mach tuck, and loss of the airplane (AC 61-107, para 3-2)

Pair this with your type's answer: which protections exist in normal law or with all systems up, and what remains in each degraded mode. That mapping comes from the AFM and the FSB report, and "it depends on the control law" is only a passing answer if you can then say what each law provides.

Three layers beyond the commercial-level anti-ice/deice distinction (that groundwork is in the Commercial guide's systems task):

• Coverage map — the ACS expects anti-ice/deice knowledge across pitot-static protection, turbine inlet, propeller, windshield, and airfoil surfaces (AA.I.A.K10). Know which method protects each surface on your type and what the AFM requires to be on, and when
• Supply side — pneumatic and environmental systems knowledge includes the supply for ice protection systems (AA.I.A.K8): if your protection is bleed-air fed, know where the air comes from and what using it costs (that performance conversation continues in Task I.B)
• Limitations — icing operating limitations are AFM material (AA.I.A.S3), and ground deicing, holdover times, and the clean wing concept are exercised under Tasks I.B and II.A

Systems side: pure AFM material — know your type's detection loops and warnings, and which extinguishing bottles protect the engines, APU, cargo compartments, and lavatories, plus the discharge procedure and any limitations.

Crew side: regulated by 121.417, which requires:

• Emergency training in fire in flight or on the surface, and smoke control procedures with emphasis on electrical equipment and related circuit breakers in cabin areas — including galleys and lavatories (121.417(b)(3)(ii))
• Training in portable fire extinguishers, with emphasis on the type of extinguisher to be used on different classes of fires (121.417(b)(2)(iii))
• A protective breathing equipment (PBE) drill by every crewmember, combatting an actual or simulated fire (121.417(c)(1))
• Recurrent training every 24 calendar months operating each type of installed hand extinguisher (121.417(c)(2))

For the oral: name your type's fire memory items and where the smoke-removal procedure lives.

Three buckets, and know your evacuation duties cold:

• Oxygen — the flight-crew supply quantities and mask-wear rules of 121.333 are covered under Task I.E; the system mechanics (source, quick-donning masks, passenger drop-out) are your type's AFM material
• Exits and equipment — 121.417 requires individual instruction in the location, function, and operation of emergency equipment, including ditching and evacuation equipment and emergency exits in the emergency mode with the evacuation slide/raft pack attached, with emphasis on operating exits under adverse conditions (121.417(b)(2))
• Evacuation duties — training covers emergency assignments and coordination among crewmembers, and evacuation of persons who need the assistance of another person to reach an exit (121.417(b)(1), (b)(3)(iii)); crewmembers serving above 25,000 feet also get physiology training — respiration, hypoxia, duration of consciousness, gas expansion and bubble formation, decompression phenomena (121.417(e))

The expanded definition from AC 120-62 via the AFH: V1 is the speed selected for each takeoff, based upon approved performance data and specified conditions, representing both the maximum speed by which a rejected takeoff assures a safe stop within the remaining runway or runway and stopway, and the minimum speed which assures the takeoff can be safely completed within the remaining runway, or runway and clearway, after failure of the most critical engine at the designated speed (AFH ch. 16).

Certification anchors it: V1 may not be less than VEF plus the speed gained during the interval between engine failure and the pilot's first stopping action — applying brakes, reducing thrust, or deploying speed brakes (25.107(a)(2)). So V1 already contains recognition time; there is no cushion left for deciding at V1.

VEF is the calibrated airspeed at which the critical engine is assumed to fail for certification purposes. It is selected by the applicant but may not be less than VMCG determined under 25.149(e) (25.107(a)(1)). The chain matters for the oral: VMCG floors VEF, VEF plus the recognition increment floors V1, and V1 floors VR. If the engine fails before VEF-like speeds — below VMCG — the reject isn't a performance question at all; it's the only controllable option, because rudder alone cannot hold the centerline (25.149(e)).

VR may not be less than:

• V1
• 105 percent of VMC
• The speed that allows reaching V2 before 35 feet above the takeoff surface
• A speed producing VLOF margins over VMU (the minimum unstick speed) — e.g., 110 percent of VMU all-engines / 105 percent one-engine-inoperative (108/104 if geometry-limited) (25.107(e))

V2MIN may not be less than 1.13 VSR for two- and three-engine turboprops — and for any turbojet without provisions for a significant one-engine-inoperative stall-speed reduction, regardless of engine count — 1.08 VSR for the others, and 1.10 times VMC (25.107(b)). V2 itself must also give at least the second-segment climb gradient of 25.121(b) (25.107(c)). Never quote type numbers — they come off the takeoff data for that runway, that weight, that day (AFH ch. 16).

The minimum control speed on the ground: the calibrated airspeed during the takeoff run at which, when the critical engine is suddenly made inoperative, it is possible to maintain control using the rudder alone — without nosewheel steering — as limited by 150 pounds of force, with lateral control only to keep the wings level, and continue the takeoff safely. The demonstration standard: from the point of failure to recovery parallel to centerline, the path may not deviate more than 30 feet laterally from the centerline (25.149(e)). Established with maximum takeoff thrust, most unfavorable CG and weight, and the airplane trimmed for takeoff. Operationally this is why the pilot flying's hand comes off nosewheel steering and onto the wheel around 80 knots or VMCG (AFH ch. 16) — the certification case assumed rudder only.

The calibrated airspeed at which, when the critical engine is suddenly made inoperative, it is possible to maintain control with not more than 5° of bank in straight flight. Certification conditions: maximum available takeoff thrust, most unfavorable CG, airplane trimmed for takeoff, and VMC may not exceed 1.13 VSR (25.149(c)). During recovery, rudder force may not exceed 150 pounds, no reduction of thrust on the operating engines, and no dangerous attitude or heading change of more than 20° (25.149(d)). There are also approach/landing minimum control speeds — VMCL (and VMCL-2 for three-plus engines) with go-around thrust and 5° bank (25.149(f), (g)) — worth naming if your type publishes them.

From the AFH glossary: accelerate-stop distance is the distance to accelerate to V1 with all engines at takeoff power, experience an engine failure at V1, and bring the airplane to a stop; accelerate-go distance is the distance to accelerate to V1, fail the critical engine at V1, and continue the takeoff on the remaining engine(s) (AFH ch. 16). Takeoff distance itself is the greater of the one-engine-inoperative distance to 35 feet, or 115 percent of the all-engines distance to 35 feet (25.113(a)); on a wet runway the screen height drops to 15 feet (25.113(b)). When V1 is selected so the stop case and the go case need the same pavement, the field is balanced — that field length is the shortest runway that covers both outcomes, and moving V1 trades one distance against the other.

For turbine airplanes certificated under current rules, takeoff weight must allow:

• Accelerate-stop distance not exceeding runway plus stopway
• Takeoff distance not exceeding runway plus clearway, with the clearway credit limited to not greater than one-half the length of the runway
• Takeoff run not greater than the runway (121.189(c))

Corrections are required for runway, elevation, effective gradient, ambient temperature, wind component, and — where AFM limitations exist — wet versus dry surface; wet-grooved/PFC data may only be used on runways actually grooved or PFC-treated and maintained acceptably (121.189(e)).

• First segment (gear extended, between VLOF and gear fully retracted): steady gradient positive (0.3 percent for three engines, 0.5 for four)
• Second segment (gear retracted, takeoff flaps, at V2, takeoff thrust): 2.4 percent (2.7 three-engine, 3.0 four-engine), carried to at least 400 feet above the surface (25.121(b))
• Final takeoff (en route configuration, at VFTO, maximum continuous thrust): 1.2 percent (1.5/1.7) (25.121(c))
• Approach climb (go-around configuration, one engine inoperative, at not more than 1.4 VSR, gear retracted, maximum landing weight): 2.1 percent (2.4/2.7) (25.121(d))

These are certification gradients — the AFM's climb-limited takeoff weight is where they bite on a hot, high day. Second segment is almost always the limiting one; be able to say why for your type.

Takeoff weight must allow a net takeoff flight path that clears all obstacles by at least 35 feet vertically, or by 200 feet horizontally within the airport boundaries and 300 feet horizontally after passing them (121.189(d)(2)). The assumptions matter: the airplane is not banked before reaching 50 feet, and thereafter bank is limited to 15 degrees (121.189(f)) — which is why engine-out special procedures fly the published track and modest banks rather than an early turn toward downwind. "Net" means the demonstrated gradient reduced by the regulatory decrement, so the paper path sits below what the airplane should actually achieve.

No takeoff unless arrival weight allows a full-stop landing within 60 percent of the effective length of the runway from a point 50 feet above the threshold plane, at both the destination (121.195(b)) and the alternate (121.197), on the most favorable runway in still air and on the most suitable runway for the expected wind. Two modifiers: turboprop — may dispatch failing the "most suitable runway" test if an alternate is specified where it can stop within 70 percent (121.195(c)); turbojet, wet or slippery forecast — effective runway length must be at least 115 percent of the dry requirement, unless a shorter approved wet distance is in the AFM (121.195(d)).

This is a preflight gate. The separate landing distance assessment at time of arrival — and its 15 percent margin — is covered under Task III.B.

Airports report non-dry surface conditions using the Runway Condition Assessment Matrix, assigning Runway Condition Codes to each third of the runway — touchdown, mid-point, roll-out (AIM 4-3-9); the codes run from 6 (dry) down through 5–1 to 0 (nil), and the report includes the type and depth of contaminant when the runway is contaminated (SAFO 19001; AIM 4-3-9). Pair them with pilot braking action reports: Good, Good to Medium, Medium, Medium to Poor, Poor, and Nil — Nil meaning deceleration is minimal to non-existent or directional control uncertain. Two ATP-level points: friction (Mu) measurements are no longer used to report surface conditions because they don't correlate reliably with airplane braking performance, and a braking report is only reliable from a similar weight and class of airplane and recent enough for the conditions (SAFO 19001). Wet-runway definition: neither dry nor contaminated.

LAHSO — landing and holding short of an intersecting runway, an intersecting taxiway, or another designated point. The performance gate: accept only if the PIC determines the airplane can safely land and stop within the Available Landing Distance (ALD) — published in the Chart Supplement and U.S. Terminal Procedures Publications, and available from the controller on request (AIM 4-3-11). The command points:

• The PIC has final authority to accept or decline any LAHSO clearance, and pilots are expected to decline one that would compromise safety — ideally before it's issued
• Once accepted, it must be adhered to like any other ATC clearance, unless amended or an emergency occurs — but it does not preclude a rejected landing
• Read back the clearance in full, including “hold short of (runway/taxiway/point)” (AIM 4-3-11)

Preflight planning should already have determined which LAHSO combinations at the destination work for your required landing distance.

• Ill-advised reject decisions and improper technique contribute to a majority of takeoff-related commercial aviation accidents worldwide; although only about 2 percent of rejects fall in the high-speed category, aborts above 120 knots account for the vast majority of RTO overrun accidents
• The decision should be made before V1 so deceleration can begin no later than V1; if braking hasn't begun by V1, continuing is the decision by default
• Delaying the maneuver one second beyond V1 adds 4 to 6 knots on average, and crews need 3 to 7 seconds to identify and execute a reject
• Certified stopping data assumes ideal conditions — clean dry runway, maximum braking, no reverse-thrust credit; reality subtracts through contamination, wind, low density, worn brakes or tires, inoperative anti-skid, penalizing MEL or CDL items, and technique (AFH ch. 16)

State your operator's low-speed/high-speed reject split and who calls it — the PIC makes the continue/reject decision (AFH ch. 16).

Holdover time is the estimated time deicing/anti-icing fluid will prevent the formation of frost or ice and the accumulation of snow on the protected surfaces — it begins when the final application of fluid commences and expires when the fluid loses effectiveness (121.629(c)(3)). The carrier's approved ground deicing program contains the holdover timetables and procedures for adjusting HOT up or down in changing conditions. If the maximum holdover time is exceeded, takeoff is permitted only when at least one of these is true:

• A pretakeoff contamination check — conducted within five minutes prior to beginning takeoff, from outside the aircraft unless the program specifies otherwise — finds the critical surfaces free of frost, ice, and snow
• An approved alternate procedure makes that determination
• The airplane is re-deiced and a new holdover time is established (121.629(c)(3), (c)(4))

Why the clean-wing concept exists at all: contamination disrupts the smooth airflow so the boundary layer separates at an AOA lower than the critical angle — lift is greatly reduced, and as little as 0.8 millimeter of ice on the upper wing surface increases drag and reduces lift by 25 percent (PHAK ch. 5). A contaminated wing therefore stalls earlier than a stall warning system calibrated for the clean wing expects. The underlying prohibition — no takeoff with frost, ice, or snow adhering to critical surfaces — and its one authorized exception are covered under Task II.A.

Carriers load by approved average weights rather than weighing each occupant. Standard average passenger weights are built from CDC/NHANES survey data plus a clothing allowance — 5 pounds summer, 10 pounds winter — with summer weights usable May 1 to October 31 and winter November 1 to April 30; where no gender is given, the averages assume a 50/50 male-female split (AC 120-27, table 3-1 and para 3.2.1). Operators with seasonal variation that want one year-round number should use the winter weight, and baggage weights come from operator survey data (AC 120-27). The mechanics of shifting weight and resolving an out-of-limits CG are unchanged from the commercial computation you already know — the ATP layer is knowing that the whole system runs on approved averages, curtailed CG envelopes, and load planners, with the PIC still responsible for the result.

Because certified data is a flight-test ceiling, not a line-operations average. The AFH's degradation list for stopping performance is the template answer: reduced runway friction, mechanical and natural contaminants, wind, low air density, flap and bleed configuration, underinflated or failing tires, deficient brakes or RTO auto-brakes, inoperative anti-skid, penalizing MEL/CDL items, and pilot technique and proficiency (AFH ch. 16). The certified landing distance similarly excludes reverse thrust credit (AFH ch. 16). The professional response is structural, not heroic: apply the operator's required factors, prefer conservative condition inputs, and treat any performance-credit assumption (reverse, autobrakes, grooved runway) as something you must actually deliver in the deceleration.

Three ceilings compete, and the lowest wins:

• Certificated maximum operating altitude — an AFM limitation
• Thrust-limited altitude — at high altitude little excess thrust may be available for maneuvering; it is often impossible for a jet to climb and turn simultaneously (AC 61-107, para 3-3)
• Buffet-limited (aerodynamic) altitude — the margin between low-speed buffet and Mach buffet narrows with altitude and load factor: a typical jet has a 135-knot buffet-free spread at FL350 that shrinks to about 26 knots at FL450, and only 1.4 G — a 30°-bank-plus-gust kind of number — can put a heavy airplane at buffet at its optimum cruise Mach (AC 61-107, para 3-3)

So the day's optimum altitude moves with weight and temperature: burn off fuel and the buffet-limited ceiling rises, which is the logic of step climbs. Select a maximum cruising altitude that preserves buffet margin for maneuvering and expected gusts, using the type's cruise maneuver/buffet limit chart (AC 61-107). The aerodynamics behind this — coffin corner and the buffet boundaries — is Task I.D's territory, and so is descent performance (AA.I.B.K2e): the idle-descent-at-L/DMAX efficiency picture is covered there.

What changes is who decides and against what limits — the products themselves don't. METAR/SPECI, TAF, GFA, FB, AIRMETs, SIGMETs, and Convective SIGMETs (AA.I.C.K2) are the same ones covered card-by-card in the Instrument and Commercial guides. The same is true of the meteorology core in K3 — atmospheric stability, wind and windshear, temperature, moisture, air masses and fronts, clouds, thunderstorms and microbursts, fog, and frost (AA.I.C.K3a–f, h, j, k) are all built in those guides, and the ACS note warns that if K3 is selected the evaluator must assess at least three sub-elements — so refresh them there before the oral. At the ATP level:

• Joint responsibility: in domestic and flag operations, the PIC and the aircraft dispatcher share responsibility for preflight planning, delay, and dispatch release (121.533(b), 121.535(b)) — your weather analysis has a professional counterpart checking the same charts
• Flight monitoring: the dispatcher monitors each flight, issues information necessary for safety, and can cancel or redispatch when a flight cannot continue safely as released (121.533(c))
• Minima: from operator and aircraft operational limitations — ops specs — not personal preference (AA.I.C.R1d)

Expect scenario questions where the right answer includes the phrase "and I'd be on with dispatch."

The planning ladder, with all required components operative (IPH ch. 4, fig. 4-41):

• CAT I: DH 200 feet, RVR 2,400 (1,800 with touchdown zone and centerline lighting)
• CAT II: DH 100 feet, RVR 1,200
• CAT III: RVR floors fall from 700 (IIIa) to 150 (IIIb) to no DH and no RVR limitation at IIIc — which no U.S. operator has OpSpecs approval to use

The category-by-category details — including the DH-versus-Alert-Height distinction — are covered under Task VI.E. The weather-planning point this Task adds: the minimums you may plan on are not the chart's lowest line but the lowest category your OpSpecs authorize for this crew, this airframe, and the equipment working today — the trend you watch en route is measured against that number.

CAT II and III require special certification for operators, pilots, aircraft, and airborne and ground equipment — the primary authorization and minimum RVRs live in OpSpecs Part C (IPH ch. 4). Details worth volunteering:

• While CAT I permits substituting midfield RVR for an unavailable TDZ report, CAT II permits no substitution — the touchdown zone RVR system is required and controlling (IPH ch. 4)
• The surface side is regulated too: the FAA requires an approved low visibility operations/SMGCS program for new CAT III-supported runways, with the low-visibility taxi plan applying at RVR below 1,200 feet and controllable stop bars required for operations below 500 feet RVR (IPH ch. 1 and 4) — the taxi-plan details are covered under Task II.C

A structured preflight form that assigns numbers to specific risks and situations, making it easier to see when a particular flight carries a higher level of risk (PHAK ch. 2). It complements — not replaces — the continuous perceive-process-perform loop and predetermined personal minimums developed away from any pressure to fly (PHAK ch. 2). At a carrier, the FRAT's thresholds typically trigger the conversation this Task keeps pointing at: elevated score, talk to dispatch or a supervisor before the flight goes. The skill element is explicit that you should interpret the weather, apply ADM, and use a Flight Risk Assessment Tool if available (AA.I.C.S1) — so if your operator has one, walk the evaluator through its categories and what happens at each scoring band.

The margin you're protecting is aerodynamic. At cruise altitude the spread between low-speed and Mach buffet may be a couple hundred knots at FL350 but only about 26 knots at FL450 for a typical jet, and gust loading or bank can erase a 1.4 G margin entirely — so altitude selection in expected turbulence is itself a weather decision (AC 61-107, para 3-3). If a thunderstorm cannot be avoided, follow high-altitude penetration procedures and avoid over-action of the thrust levers; speed brakes can manage excessive airspeed buildup, with the caveat that when they're part of the lateral control system, deploying them may change the roll rate with lateral input (AC 61-107, para 3-3). The full coffin-corner story is Task I.D.

Three channels, each worth naming:

• SIGMETs (WS) — the non-convective advisories that cover volcanic ash, along with severe icing not associated with thunderstorms, severe or extreme turbulence or CAT, and dust storms or sandstorms lowering surface or inflight visibility below three miles; valid 4 hours (6 for hurricanes) (PHAK ch. 13)
• ASHTAM — the NOTAM issued for an operationally significant change in volcanic ash or other dust contamination (PHAK ch. 1)
• METAR coding — present-weather code VA for volcanic ash (PHAK ch. 13)

The operational posture for a jet crew is avoidance and routing — ash is a dispatch-level planning problem before it is ever an inflight one, which is why it appears in the ATP task rather than as a light-airplane concern.

Both of you, at every phase: no person may dispatch or release, continue en route, or land when in the opinion of the pilot in command or aircraft dispatcher (domestic and flag), icing conditions are expected or met that might adversely affect the safety of the flight (121.629(a)). Note the standard — might adversely affect — is lower than "exceeds certification." Freezing-level products and structural icing theory are covered in the Instrument guide; the ground-icing program, holdover times, and the pretakeoff contamination check are under Tasks I.B and II.A. What this Task adds is the decision architecture: either seat can stop the flight for ice, before or during.

As a planning aid with known failure modes, not ground truth — the ACS explicitly tests equipment limitations alongside use, and that is the evidence the evaluator wants. State the limits before the strategy:

• Datalink (FIS-B/NEXRAD): latency and mosaic limitations are covered in the Commercial guide's weather task and carry over unchanged — strategic, not tactical
• Installed equipment — weather radar, predictive windshear, turbulence detection: the honest oral answer is your AFM/FCOM's operating procedures and your operator's deviation SOPs — what the display actually senses and what it cannot see
• Deviation coordination: heading change agreed, PM works the ATC request, dispatch advised if the reroute is significant, per the joint-responsibility structure of 121.533

Structure the answer around the shared-responsibility machinery rather than raw stick-and-rudder judgment:

1. Re-gather — latest METAR/SPECI and trend, TAF amendments, PIREPs, and the RVR values that actually control your approach category (IPH ch. 4)
2. Compare against authorization — the minima that matter are the OpSpecs values for the approach you can fly with the equipment working right now, not the chart's lowest line (IPH ch. 4)
3. Confer — the dispatcher is monitoring the flight and holds joint responsibility; either of you can conclude the flight cannot continue safely as released, and the dispatcher can redispatch you to the alternate with amended fuel and weather analysis (121.533(c))
4. Decide with the fuel — the release was built to reach destination, most distant required alternate, plus reserve (121.639, covered under Task I.E); the moment holding erodes that plan, the decision timeline compresses

The examiner is listening for the reflex of bringing dispatch in early — silence until minimum fuel is the classic ATP-oral failure mode.

Yes — as the conservative inner ring inside the regulatory ones. The ACS keeps personal weather minimums as a risk element even for ATP applicants, and the PHAK's guidance still applies: set them in a non-flying environment, before any pressure to make a specific trip exists, so they serve as a clear reference point for go/no-go and continue/discontinue decisions (PHAK ch. 2). At a carrier they express themselves differently — as the judgment margin you apply inside OpSpecs limits: electing the autoland when you're legal to hand-fly, taking the extra fuel when the TAF's PROB30 looks generous, declining the visual at night into terrain. The strong oral answer names a specific case where your minimums are tighter than what's legal, and why.

From the pilot's viewpoint, Mach is the ratio of the aircraft's true airspeed to the local speed of sound. At sea level on a standard day (15 °C), the speed of sound is approximately 660 knots; Mach .75 there equals a TAS of roughly 498 knots. The speed of sound is directly related only to temperature — as the atmosphere cools with altitude, the speed of sound decreases, up to about 36,000 feet MSL where the standard temperature lapse stops (AC 61-107, paras 3-2a and 3-2b(2)). That single fact drives most of this Task: a colder, higher sky means any given TAS is a higher Mach number.

Two effects run in opposite directions:

• IAS falls away from TAS — an airplane's indicated airspeed decreases in relation to TAS as altitude increases, because of reduced air density; to hold the same lift coefficient, AOA must increase with altitude for the same calibrated airspeed (AC 61-107, paras 3-2b(5) and 3-3c(3))
• Mach rises against TAS — the low temperatures aloft decrease the speed of sound, so for a given TAS, Mach number is significantly higher at altitude than at sea level; compressibility effects arrive at slower indicated speeds up high (AC 61-107, para 3-3b(2))

Practically: climb at constant indicated and your Mach climbs toward the limit; that's why the climb transitions from an IAS schedule to a Mach schedule, and descent does the reverse. The result of the squeeze — slow-speed problems and Mach problems arriving at the same time — is the next card.

Coffin corner is the point where high-speed Mach buffet, IAS, and the low-speed buffet boundary merge: the airplane's absolute or aerodynamic ceiling. It forms because IAS decreases with altitude toward the low-speed buffet boundary (prestall buffet at 1.0 G) while Mach buffet arrives at ever-lower indicated speeds. There, the aircraft can neither go faster without activating the stick puller at the Mach limit, nor slower without activating the stick shaker or pusher — encountering this critical envelope region can end in loss of control (AC 61-107, para 3-2b(5)). Note the trap in the definition: the aerodynamic ceiling can sit above the AFM's certificated altitude limit, but maneuvering or turbulence effectively lowers it toward you.

AC 61-107's worked example:

• At 51,000 feet and 1.0 G: a typical turbojet might meet Mach buffet slightly above its MMO of 0.82 and low-speed buffet at 0.60 Mach — a comfortable spread
• At 1.4 G — an increase of just 0.4 G — buffet can come on at the optimum cruise speed of 0.73 Mach, and any change in airspeed, bank, or gust loading can reduce that 1.4 G protection to none
• Altitude trend: a 1.0 G buffet-free margin of 135 knots at FL350 shrinks to about 26 knots at FL450 (AC 61-107, para 3-3c(5))

Increasing either gross weight or G raises the low-speed buffet speed and lowers the Mach buffet speed simultaneously (para 3-2b(6)) — the corner closes from both sides. Hence the requirement: pick cruise altitude from the cruise maneuver/buffet limit chart, with margin for maneuvering and gusts.

Two factors, principally:

• Shock-wave-induced flow separation — normally beginning near the wing root, it decreases downwash velocity over the elevator and produces a nose-down tendency
• Aft movement of the center of pressure — the CG ends up farther ahead of the aerodynamic center than in subsonic flight, dramatically increasing the nose-down pitching tendency (AC 61-107, para 3-2b(1))

Supersonic flow over the wing is responsible for the package deal: shock waves (drag rise), the aft lift shift (Mach tuck), and airflow separation behind the shocks (Mach buffet) (para 3-3c(4)). The nose-down moment steepens the dive and accelerates you further past the limit — which is why the Mach compensating stick puller exists and must never be disabled in normal operations (para 3-2b(3); see Task I.A for the systems side).

AC 61-107's sequence for intentional or accidental excursions beyond the certificated maximum operating limit speed (para 3-2b):

• Possible onset of aerodynamic flutter
• Excessive G-loading in maneuvering
• Induced flow separation over the ailerons and elevators, potentially followed by physical loss of a control surface
• Aileron buzz or snatch, coupled with Mach tuck
• Catastrophic loss of the airplane

The convergence point of this Task: at high altitude, VMO (a structural/indicated limit) and MMO (a compressibility limit) converge with the stall AOA boundary, so both the fast edge and the slow edge of the envelope are closer than the flight deck feels. Respecting the barber pole up high is respecting a margin measured in tens of knots, not hundreds.

• Why sweep exists: sweeping the wing raises the critical Mach number — airflow travels over an effectively different cross-section with less effective camber, reducing the acceleration of flow over the wing and allowing a higher speed before critical Mach (AC 61-107, para 3-3a(3))
• Lift behavior: a straight wing builds lift steeply with AOA and then stalls abruptly with rapid lift deterioration; the swept wing produces a much more gradual buildup of lift (para 3-3a(6)) — which sounds benign but means degraded low-speed cues and deep AOA excursions
• Stall pattern: swept-wing stalls begin at the tips (AFH ch. 16) — outboard, behind the CG, aggravating pitch-up tendencies
• Fixes on the airframe: vortex generators and boundary-layer energizers delay shock-induced separation and permit a higher MMO (AC 61-107, para 3-3a(5))

A coupled oscillation in roll and yaw that becomes objectionable when roll (lateral) stability is reduced in comparison with yaw (directional) stability. When it's objectionable or affects certification control-stability requirements, a stability augmentation system is required; the yaw damper — a gyro-operated autocontrol providing rudder input — cancels the yaw tendencies (AC 61-107, para 3-3c(3)(a)). The altitude connection: reduced air density at high altitude reduces aerodynamic damping and overall stability, so jets at high altitude and high Mach can simultaneously experience slow-speed problems like Dutch roll, adverse yaw, and stall (para 3-3c(3)). Know your type's answer for a yaw damper failure at altitude — typically an altitude restriction from the AFM.

Because the ceilings that matter are margins, and both weight and temperature eat margins:

• Thrust: jets cruise at altitudes where operation is close to rpm or EGT limits — little excess thrust may be available for maneuvering, and it is often impossible to climb and turn simultaneously; all maneuvering must fit within available thrust (AC 61-107, para 3-3b(1)). A hot day moves you closer to those limits
• Buffet: higher weight raises the 1.0 G low-speed buffet boundary and narrows the corner (para 3-2b(6)), so the buffet-limited altitude falls as weight rises — and recovers as fuel burns off, which is the step-climb logic covered under Task I.B
• Efficiency: the reason to be up there at all — specific fuel consumption decreases as outside air temperature decreases, so high altitude is where fuel economy and cruise speed are best (para 3-3b(1))

L/DMAX is the minimum-drag speed: flying faster than it requires more power, and — the counterintuitive half — flying slower than it also requires more power (AFH ch. 5). Below L/DMAX the airplane sits on the backside of the power curve with speed instability: a disturbance that slows the airplane increases drag, which slows it further (AFH ch. 5). At high altitude, where excess thrust is already thin (AC 61-107, para 3-3b(1)), a slowdown below optimum speed can leave the airplane unable to hold both altitude and speed — the "high altitude slow-down" the risk elements name (AA.I.D.R3). L/DMAX is also the efficiency anchor: the smoothest, most fuel-efficient descent is idle thrust at L/DMAX (AFH ch. 16), and best-range and best-endurance speeds for your type are AFM/FMS numbers keyed off this same drag curve.

An airplane in flight unintentionally exceeding the parameters normally experienced in line operations or training:

• Pitch attitude greater than 25° nose up
• Pitch attitude greater than 10° nose down
• Bank angle greater than 45°
• Or within those parameters but at airspeeds inappropriate for the conditions (AC 120-111, para 1-6a)

That last clause is the high-altitude one — wings level, pitch normal, and 20 knots slow at FL410 is a developing upset by definition, because the airplane is diverging from the intended flightpath (AC 120-111's "developing upset condition," para 1-6e). The prevention emphasis follows: recognize the energy divergence before the attitude ever moves.

The setup is everything this Task has covered: thin thrust margins, narrow buffet spreads, reduced aerodynamic damping, and automation quietly trading speed for altitude until the airplane is behind the power curve (AC 61-107, para 3-3; AFH ch. 5 speed instability). On the recovery side, AC 120-111's warnings for the oral:

• Manage the energy state and the rate at which it is changing — it determines how much maneuvering capability you have (AC 120-111, ch. 4)
• For nose-high recoveries, pilots are instructed to push to achieve less than 1 G (AC 120-111, app. 1)
• Rudder is still effective at high AOA — and that is exactly why special care is required: guard against control reversals, and avoid rapid full-scale reversals of control deflections to maintain structural integrity (AC 120-111, app. 1). The rudder-reversal discussion continues under Task I.E
• Excessive use of pitch trim or rudder may aggravate the upset (AC 120-111, ch. 4 warnings)

Expect the scenario question as a slowdown at cruise: the correct first move is trading altitude for energy early — a descent you choose beats a stall recovery you don't.

The certificate holder is always responsible for operational control; who shares the working authority depends on the kind of operation:

• Domestic and flag: the PIC and the aircraft dispatcher are jointly responsible for preflight planning, delay, and dispatch release (121.533(b), 121.535(b))
• Supplemental: the PIC and the director of operations are jointly responsible for initiation, continuation, diversion, and termination; the DO may delegate the functions but not the responsibility, and everyone authorized to exercise operational control must be listed in the operations manual (121.537(a), (b))

In every kind, during flight time the PIC is in command of the aircraft and crew and responsible for the safety of passengers, crewmembers, cargo, and airplane, with full control and authority over other crewmembers without limitation — whether or not the PIC holds their certificates (121.533(d), (e)).

The difference is who authorizes: a dispatch release comes from a certificated aircraft dispatcher (domestic and flag), while a supplemental flight release has no dispatcher behind it. The machinery:

• Domestic: no person may start a flight unless an aircraft dispatcher specifically authorizes it; the exception is an intermediate stop named in the original release lasting not more than one hour (121.593)
• Flag: dispatcher authorization required, and a new dispatch is required to continue from an intermediate airport after more than six hours on the ground (121.595)
• Supplemental: there is no dispatcher — a flight release is executed by the PIC or the person the operator authorized to exercise operational control, and the PIC may sign only when both believe the flight can be made with safety; a new release is needed after more than six hours at an intermediate airport (121.597)

The certificated-dispatcher system is what distinguishes scheduled 121 operations from everything else you've flown; contents of the release itself are covered under Task II.A.

Three duties, verbatim from the reg — the dispatcher is responsible for:

1. Monitoring the progress of each flight
2. Issuing necessary information for the safety of the flight
3. Cancelling or redispatching a flight if, in the dispatcher's opinion or the opinion of the pilot in command, it cannot operate or continue safely as planned or released (121.533(c); same structure for flag under 121.535(c))

Note the "or": either seat's opinion is sufficient to stop the plan. The emergency-case split — including the dispatcher's authority to declare when unable to communicate with the PIC, and the 10-day written reports — is covered under Task VII.A.

Enough fuel to:

• Fly to the airport to which it is dispatched
• Then fly to and land at the most distant alternate (where an alternate is required)
• Then fly for 45 minutes at normal cruising fuel consumption (121.639)

That's the domestic formula — flag and supplemental have their own international variants built around a 10-percent en route contingency and holding requirements, so identify which rule set your operation uses. The release is built on this math, which is why en route holding or a reroute immediately becomes a dispatch conversation (121.533(c); see Task I.C for the weather-diversion decision flow).

• Above FL250: each flight crewmember on duty must be provided a mask designed for rapid donning; one pilot at the controls must wear and use a mask — unless each crewmember has a quick-donning mask (donnable with one hand within five seconds), in which case wear is not required at or below FL410 for airplanes with more than 30 passenger seats or more than 7,500 pounds payload (at or below FL350 for the smaller category) (121.333(c)(1), (c)(2))
• Above FL410: if one pilot leaves the controls, the remaining pilot puts on and uses the mask until the other returns (121.333(c)(3))
• Crew supply: above 10,000 feet, at least a two-hour supply — defined as the quantity for a constant-rate descent from max certificated altitude to 10,000 feet in ten minutes, followed by 110 minutes at 10,000 feet (121.333(b))
• Preflight: each crewmember personally preflights their oxygen equipment before takeoff (121.333(c)(4))

Decompression is the inability of the pressurization system to maintain its designed pressure differential — caused by a system malfunction or structural damage (PHAK ch. 7). Physiologically it splits two ways:

• Explosive decompression — cabin pressure changes faster than the lungs can decompress (authorities treat anything under 0.5 second as explosive); potential lung damage
• Rapid decompression — the lungs decompress faster than the cabin (PHAK ch. 7)

Recognition cues: noise, momentary daze, cabin fog from the temperature and humidity drop, dust and flying debris, air rushing from mouth and nose (PHAK ch. 7). Rapid decompression reduces effective performance time by one-third to one-fourth because the oxygen in your lungs is exhaled rapidly — the reason quick-donning masks and immediate crew response exist (PHAK ch. 7). The emergency descent itself, the TUC numbers, and the memory-item response are covered under Task VII.A; the system mechanics are under Task I.A.

Follow the RA. RAs are vertical maneuvers, so an RA and a turn instruction can coexist — the IPH makes the split explicit in its simultaneous close parallel (PRM) breakout guidance: if the climb or descend instruction differs from the RA, follow the RA while continuing to follow the controller's turn instruction, and report the deviation to ATC as soon as practical (IPH ch. 4). The system logic backs this up: TCAS II analyzes the projected flightpath of approaching aircraft and issues resolution advisories, and when the other aircraft is also TCAS II-equipped, the two systems coordinate their resolution advisories (IFH ch. 5) — an opposite-direction maneuver by one crew defeats the coordination for both. Know your type's RA guidance display and your operator's callouts, and note the NTSB reporting hook for certain RAs under 49 CFR 830 (Task I.G).

Two generations, one discipline:

• GPWS watches radio altitude, speed, landing gear status, flap position, and ILS glideslope deviation for unsafe operation relative to terrain — excessive descent rate, excessive closure with terrain, unsafe clearance while not configured to land, glideslope deviation — and provides advisory callouts. It's typically wired to the hot bus so it can't be inadvertently switched off; the IFH recounts a turboprop crew that ignored and tried to disable a valid warning, gear-up on final (IFH ch. 5)
• TAWS adds GPS position against a terrain and obstruction database for true predictability ahead of the aircraft, with aural and visual warnings instructing specific action, compensating for aircraft performance and speed (IFH ch. 5)

The response expectation the ACS is probing (AA.I.E.R3): treat a warning as valid and act on it — the accident record is crews explaining away the box.

It's the sequence of large, alternating rudder inputs — and the guidance exists because rudder control remains effective at high AOA, so special care is required in its use during upset prevention and recovery: guard against control reversals, and avoid rapid full-scale reversal of control deflections to maintain structural integrity (AC 120-111, app. 1). The same AC's recovery templates carry the standing warning that excessive use of pitch trim or rudder may aggravate an upset (AC 120-111, ch. 4). Note what the AC's structural-integrity language implies: the danger is not one large input but the reversal — alternating full deflections build loads the airframe was never required to withstand. Fly roll with ailerons and spoilers; use rudder smoothly, and never in rapid opposite cycles.

OpSpecs are the FAA-issued document set that turns the certificate into a specific, bounded operation:

• Issued for each kind of operation and each class and size of aircraft (119.1(b)(2))
• A carrier may not operate in a geographic area unless its ops specs specifically authorize it (119.5(j))
• No one may operate in violation of the ops specs (119.5(l))

"Kind of operation" is itself a defined term — domestic, flag, supplemental, commuter, or on-demand, as specified in the ops specs (110.2). You met OpSpecs Part C as the source of your CAT II/III authority in Task I.C; how they constrain a specific preflight is exercised under Task II.A. For the oral, be able to name two or three concrete things your OpSpecs authorize that plain part 121 would not.

The Aviation Safety Action Program: under an FAA-accepted memorandum of understanding, employees of participating carriers voluntarily report safety issues to management and to the FAA for resolution — including events that may involve apparent violations (AC 120-66).

• Review: each accepted report goes to an Event Review Committee (FAA, company, and labor representatives) that reviews the event and recommends corrective action; the ERC has discretion on timeliness and acceptance based on the best interest of safety (AC 120-66)
• Incentive: the FAA assures no enforcement action will be used to address apparent violations reported under the program, unless specifically excluded — and since October 1, 2015, administrative actions are not processed for accepted ASAP reports (AC 120-66, paras 9–10)
• Purpose: generating safety enhancements from data the FAA would otherwise never see

CRM is the effective use of all available resources — human resources, hardware, and information — with training focused on situation awareness, communication skills, teamwork, task allocation, and decisionmaking within a comprehensive framework of SOPs (AC 120-51). Points the AC emphasizes that fit ATP oral questions:

• Crew monitoring and cross-checking: the pilot monitoring's role is critical — monitoring matters most during approach and landing, where CFIT accidents are most common (AC 120-51)
• Briefings are a core CRM behavior, expanded to cover safety and security concerns (AC 120-51); the AFH frames the captain's briefing before takeoff as an essential part of CRM procedures (AFH ch. 16)
• CRM lives inside SOPs, and its central concept is communication, supported by a culture that encourages it (AC 120-51)
• Parallel programs exist for the rest of the operation — dispatch resource management for aircraft dispatchers is required just as CRM is for pilots and flight attendants (AC 120-51)

Two concrete anchors keep this from being a platitude question:

• The regulation puts the weight on you personally: during flight time the PIC has full control and authority in the operation of the aircraft, without limitation — and correspondingly is responsible for the safety of the passengers, crewmembers, cargo, and airplane (121.533(d), (e)). Leadership is the job description, not a virtue
• The training footprint is mandated: the ATP certification training program requires at least six hours of instruction on leadership, professional development, crew resource management, and safety culture (61.156(a)(4))

Good oral answers translate these into behavior: running disciplined briefings, inviting and acting on FO/PM challenges, protecting sterile-flight-deck compliance, using the safety-reporting systems (ASAP above), and making the conservative call visibly and early. Threat and error management — recognizing threats, trapping errors before they become undesired aircraft states — is the framework your operator's program will attach to all of it (AA.I.E.K13).

What's new at ATP is the layer around the physiology — the aeromedical fundamentals (AA.I.F.K1's twelve sub-elements, hypoxia through scuba nitrogen) are the same material covered card-by-card in the Commercial guide's human factors task, and the evaluator must assess at least three sub-elements if K1 is selected (FAA-S-ACS-11A, Task I.F note). The ATP layer:

• Fatigue stops being advice and becomes part 117 law, with a required reporting and affirmation system
• ADM becomes CRM in a crew (AA.I.F.K3) — resource management with two pilots, cabin crew, and a dispatcher
• The risk elements go cognitive: distractions, task prioritization, loss of situational awareness (AA.I.F.R3) and confirmation and expectation bias (AA.I.F.R4)

Build answers that start from the commercial-level physiology and end with what the crew system does about it.

Fatigue: a physiological state of reduced mental or physical performance capability resulting from lack of sleep or increased physical activity that can reduce a flightcrew member's alertness and ability to safely operate an aircraft or perform safety-related duties (117.3). The system around it:

• Fitness for duty is regulatory — you may not accept a flight duty period if too fatigued, the carrier may not let you continue once you've reported it, and every crewmember affirmatively states fitness for duty as part of the dispatch or flight release (117.5; the self-assessment mechanics are covered under Task II.A)
• Education is mandatory — every certificate holder runs an approved fatigue education and awareness training program, annually, for crews, dispatchers, schedulers, and their management, updated every two years (117.9)
• FRMS — a fatigue risk management system is a data-driven, systematic method to continuously monitor and manage fatigue risk in the operator's specific operations (117.3)

Part 117 defines the WOCL as 0200–0559 during a physiological night (117.3). The science behind it: people on a normal routine have two periods of maximum sleepiness — roughly 3 a.m. to 5 a.m., when physiological sleepiness is greatest and performance capability lowest, and again roughly 3 p.m. to 5 p.m. (AC 120-100). Circadian rhythms are driven by an internal biological clock and entrained by light and social cues; operating against them — night work, shift work, jet lag — is the "circadian challenge" (AC 120-100).

This is why FDP limits in Table B are shortest for report times in the early morning hours (Task I.G carries the tables), and why the afternoon window is the sanctioned nap opportunity on augmented operations.

Sleep loss is cumulative: shorten sleep across consecutive days and the debt builds, aggravated by extended duty days (AC 120-100). Two findings worth quoting:

• Recovery is not hour-for-hour — studies show recovery from accumulated debt requires deliberately extended sleep; crews should be trained to use recovery periods to sleep more than their usual amount to prevent debt building across an extended schedule (AC 120-100)
• Impairment from fatigue may be severe, last from minutes to hours, and can persist right through a nap or sleep period taken too late (AC 120-100)

The regulatory backstops exist to protect the opportunity: a rest period of at least 10 consecutive hours immediately before an FDP, which must provide at least 8 uninterrupted hours of sleep opportunity — and if you determine it won't, you must notify the carrier and cannot report until you receive a compliant rest period (117.25(e), (f)).

The one with the strongest evidence is the nap: short naps of 25–30 minutes have beneficial effects on alertness, and controlled studies showed napped pilots performed measurably better than un-napped ones — which is why crew augmentation to permit napping outside the cockpit is a viable fatigue countermeasure under current FAA rules (AC 120-100). Strategy notes from the AC:

• The afternoon secondary WOCL is a relatively good time for a brief nap
• Scheduled sleep can aggregate a major sleep period plus a nap and still restore performance
• Naps have limits — even after a 3-hour morning nap, evening performance runs about 10 percent below what it would be on a normal schedule (AC 120-100)

Pair the physiology with the regulatory tools: the rest notification of 117.25(f) and the fitness-for-duty gate of 117.5 are the countermeasures with teeth.

• CRM — crew resource management: effective use of all available resources (human, hardware, information), trained around situation awareness, communication, teamwork, task allocation, and decisionmaking within SOPs; required for part 121 pilots and flight attendants (AC 120-51)
• DRM — dispatch resource management: the same discipline required for aircraft dispatchers (AC 120-51) — a reminder that your crew includes the person who signed your release
• SRM — single-pilot resource management: the one-seat translation, comprising ADM, risk management, task management, automation management, CFIT awareness, and situational awareness (PHAK ch. 2)

The ACS asks for ADM "using CRM or SRM, as appropriate" (AA.I.F.K3) — at the ATP practical in a crew airplane, appropriate means CRM, and your worked examples should involve delegating, cross-checking, and verbalizing rather than solo mental math.

The crew's defense is CRM behaviors that force contrary evidence into the open — the biases survive by keeping it unspoken, so the countermeasures are structural (the definitions and single-pilot picture are in the Commercial guide):

• Monitoring and cross-checking as a defined duty: AC 120-51 elevates the pilot monitoring's role precisely because approach and landing — where expectation runs strongest — is where CFIT accidents are most common (AC 120-51)
• Verbalization within SOPs: communication is the central CRM concept, and a culture in which every level of management promotes it is what makes a challenge speakable (AC 120-51)
• Briefings that pre-commit: a briefed bottom line — stabilized gates, required calls, missed approach triggers — converts "I expected it to work out" into a detectable deviation (AC 120-51; AFH ch. 16 captain's briefing)

A strong oral answer gives one personal example: a time the other pilot's callout broke your expectation loop, or vice versa.

Run the same IMSAFE inventory you've used since private — illness, medication, stress, alcohol, fatigue, emotion/eating (PHAK ch. 2) — then add the three ATP-specific layers:

1. The affirmation: your conclusion becomes a formal act — each flightcrew member affirmatively states fitness for duty as part of the dispatch or flight release (117.5(d); exercised under Task II.A)
2. The fatigue gate: if the honest answer on the F is no, the regulation removes the discretion — you may not accept the FDP, and the carrier may not assign it (117.5(b))
3. The crew dimension: fitness is mutual. You are assessing the other pilot too, and CRM's monitoring role begins at the briefing table — degraded crewmember performance is a threat to be named and managed, not politely ignored (AC 120-51)

Alcohol, drugs, and OTC medication rules (AA.I.F.K2) carry over unchanged from the commercial-level cards; the operational difference is that carrier drug and alcohol programs and the release paperwork make the honest self-report the only survivable strategy.

The five hazardous attitudes and their antidotes (PHAK ch. 2) don't disappear with a second pilot — they get social. Anti-authority sounds like briefing around an SOP; machismo sounds like hand-flying a CAT II to prove a point; resignation sounds like a first officer who stops challenging. The crew-level defenses:

• Task prioritization and distraction management are regulated during critical phases: the sterile flight deck rule exists because nonessential conversation at low altitude is a documented killer (121.542; exercised under Task II.C)
• Leadership training is mandated — six hours on leadership, professional development, CRM, and safety culture in the ATP-CTP (61.156(a)(4)) — because the captain sets whether challenges are welcome
• Loss of situational awareness is answered by the monitoring/cross-checking discipline of AC 120-51: defined PM duties, deviation callouts, and briefed gates

For each attitude, the examiner wants the crew-context antidote: not just "I recognize invulnerability in myself," but "our SOPs make the PM's callout mandatory, and I acknowledge it every time so the next one comes."

• Part 61, subparts A, B, G — your certificate: eligibility, privileges, and the ATP-specific rules (61.151–61.171)
• Part 91 — the floor under everything; subparts A, B, C, F, G, H are the ACS scope (AA.I.G.K2)
• Part 110 — the definitions (kinds of operations) that decide which operating part applies
• Part 119 — certification of air carriers and commercial operators: which certificate, which operating rules, which ops specs
• Part 117 — flight and duty limitations and rest for flightcrew (AMEL/AMES applicants)
• Part 121 — scheduled air carrier operating rules; part 135 — commuter and on-demand (the ASEL/ASES scope)
• Part 111 — the Pilot Records Database
• 49 CFR part 830 — NTSB notification and reporting

The skill element is applying them to a scenario (AA.I.G.S1): given an operation, name the governing part and the specific section that decides the question.

• Domestic: scheduled operations with turbojets, airplanes over 9 passenger seats, or over 7,500 pounds payload, between points within the 48 contiguous states/DC (or entirely within a state, territory, or possession) (110.2)
• Flag: same airplane sizes, scheduled, between a point in the 48 contiguous states/DC and any point outside the 48 states/DC — including Alaska and Hawaii — between Alaska/Hawaii/a territory and a point outside it, or between two foreign points (110.2). The trap: JFK–Anchorage and LAX–Honolulu are flag, not domestic
• Supplemental: common carriage where departure time and locations are specifically negotiated with the customer — charter — with more than 30 seats or 7,500 pounds payload, plus all-cargo and part 380 public charters (110.2)
• Commuter: scheduled, at least five round trips per week on at least one route, with non-turbojet airplanes of 9 seats or fewer and 7,500 pounds payload or less (110.2)
• On-demand: the unscheduled remainder for compensation or hire (110.2)

Per 119.21: domestic, flag, and supplemental operate under part 121; commuter and on-demand under part 135.

• A person authorized to conduct operations as a direct air carrier — common carriage — is issued an Air Carrier Certificate (119.5(a))
• A U.S. commercial operator not authorized as a direct air carrier gets an Operating Certificate (119.5(b))
• Only one certificate is issued for common carriage under parts 121/135, regardless of kinds of operations or aircraft flown (119.5(d))
• No one may operate without, or in violation of, the certificate and appropriate operations specifications (119.5(g), (l)), operate in a geographic area not authorized in the ops specs (119.5(j)), or advertise an operation they aren't authorized to conduct (119.5(k))
• A direct air carrier also needs economic authority from the Department of Transportation (119.5(i)) — the FAA certificate covers safety; DOT covers the commerce

• Be at least 23 years old (or 21 for the restricted-privileges certificate under 61.160)
• Read, speak, write, and understand English
• Be of good moral character
• Hold a commercial pilot certificate with an instrument rating (or qualifying military or ICAO foreign equivalents)
• For an airplane multiengine class rating (or ATP concurrent with a multiengine type rating): present a graduation certificate from an ATP certification training program (ATP-CTP) before taking the knowledge test (61.153(e))
• Pass the knowledge test (61.155(c) areas) and the practical test, and meet the aeronautical experience of subpart G (61.153(f)–(h))

At least 1,500 hours total time as a pilot, including:

• 500 hours cross-country
• 100 hours night — with a substitution: beyond 20 night full-stop landings, each additional one credits one hour of night time, up to 25 hours (61.159(b))
• 50 hours in the class of airplane for the rating (up to 25 creditable in a full flight simulator as part of an approved 121/135/141/142 course)
• 75 hours instrument time, actual or simulated (simulator/FTD credit capped at 25 hours, or 50 in a part 142 course)
• 250 hours PIC — or SIC performing PIC duties under supervision — including 100 hours cross-country and 25 night (61.159(a)(5))
• Overall FSTD ceiling: not more than 100 hours of the total toward the requirement (61.159(a)(6))

SIC time in approved part 135 professional development programs and certain flight-engineer time can also credit toward the totals (61.159(c), (d)).

The R-ATP lowers the 1,500-hour requirement for the airplane multiengine rating (and the age to 21):

• 750 hours — current or former U.S. military pilots who graduated from a UPT school
• 1,000 hours — holders of a bachelor's degree with an aviation major plus 60 aviation credit hours from an institution with a 61.169 letter of authorization, with commercial/instrument training under the school's part 141 program
• 1,250 hours — the associate's degree version with at least 30 aviation credit hours, or bachelor's graduates with 30–59 credit hours
• All paths require only 200 hours cross-country instead of 500 (61.160(e))

The certificate carries the limitation "Restricted in accordance with 14 CFR 61.167" — the holder may not act as PIC in part 121 operations (or 91.1053(a)(2)(i)/135.243(a)(1) operations) until meeting 61.159 experience and age 23, and may not serve as SIC in flag or supplemental operations requiring three or more pilots (61.167(b), 61.160(g)).

The prerequisite training program for the multiengine ATP knowledge test, completed with an authorized 121/135/141/142 provider:

• 30 hours of academics, at minimum (61.156(a)):
  • 8 hours — aerodynamics, including high-altitude operations
  • 2 hours — meteorology
  • 14 hours — air carrier operations: physiology, communications, checklist philosophy, operational control, MEL/CDL, ground operations, turbine engines, transport category performance, automation/navigation/flightpath warning systems
  • 6 hours — leadership, professional development, CRM, and safety culture
• 10 hours of FSTD training: at least 6 hours in a Level C or higher full flight simulator representing a multiengine turbine airplane of 40,000 pounds MTOW or greater, covering low-energy states/stalls, upset recovery, and adverse weather; the remainder in a Level 4+ device on FMS navigation and automation (61.156(b))

Notice the syllabus is essentially a table of contents for this Area of Operation — the FAA built the course from the same material this guide covers.

An ATP holds the same privileges as a commercial pilot with an instrument rating (61.167(a)(1)) — plus the signature air-carrier privilege: an ATP who meets the full experience and age requirements may instruct other pilots in air transportation service in aircraft of the category, class, and type for which the ATP is rated, and endorse their training records (61.167(a)(2)). Limits on that instruction:

• Not more than 8 hours in any 24-consecutive-hour period, nor 36 hours in any 7-consecutive-day period (excluding briefings and debriefings) (61.167(a)(3))
• No instructing in Category II or III operations unless trained and tested in them (61.167(a)(4))
• In aircraft, only with functioning dual controls (61.167(a)(2)(iv))

A separate flight instructor certificate is still what authorizes ordinary subpart-H instruction outside air transportation service (61.167(a)(2)(iii)).

• Every pilot — PIC and SIC — must hold an ATP certificate and an appropriate aircraft type rating for the airplane flown; an SIC type rating obtained under 61.55 doesn't satisfy this (121.436(a), (b))
• The PIC must additionally hold an unrestricted ATP (not subject to 61.167 limitations) and have 1,000 hours as: SIC in part 121 operations, PIC in 91K fractional operations (91.1053(a)(2)(i)), PIC in 135.243(a)(1) operations, PIC in eligible on-demand operations, or any combination (121.436(a)(3))
• 500 hours of military PIC time in multiengine turbine fixed-wing/powered-lift aircraft in multi-pilot operations may credit toward the 1,000 (121.436(c))

The parallel thresholds elsewhere: 91K fractional multiengine turbine PICs need an ATP and 1,500 hours (91.1053), and 135 PICs of turbojets or airplanes with 10 or more passenger seats need an ATP (135.243(a)(1)).

• Flight time (unaugmented, Table A): maximum 9 hours for report times 0500–1959, 8 hours for 0000–0459 and 2000–2359; augmented: 13 hours (3 pilots) or 17 hours (4 pilots) (117.11(a))
• FDP (unaugmented, Table B): 9 to 14 hours, driven by acclimated report time and number of segments — maximum 14 for 1–2 segments reporting 0700–1159, bottoming at 9 for the WOCL report times; reduce by 30 minutes if not acclimated (117.13). Augmented FDPs (Table C) run up to 19 hours for a 4-pilot crew with a Class 1 rest facility
• Cumulative: 100 flight hours in any 672 consecutive hours, 1,000 hours in any 365 days; FDP totals capped at 60 hours in 168 and 190 in 672 (117.23(b), (c))
• Rest: at least 10 consecutive hours immediately before FDP, with 8 hours of uninterrupted sleep opportunity — you must notify the carrier if it won't be — plus 30 consecutive hours free from duty in the preceding 168 (117.25)
• Exceeding limits for unforeseen circumstances after takeoff is permitted to land safely, with a report to the FAA within 10 days (117.11(b), (c))

Part 135 keeps the older flight-time architecture for unscheduled one- and two-pilot crews:

• Daily: total flight time in any 24 consecutive hours not exceeding 8 hours for a single pilot, 10 hours for a two-pilot crew (135.267(b))
• Quarterly/annual: 500 hours per calendar quarter, 800 in two consecutive quarters, 1,400 per calendar year (135.267(a))
• Rest: each assignment must provide at least 10 consecutive hours of rest in the 24 hours preceding planned completion; exceeding daily limits for reasons beyond the operator's control drives graduated rest of 11, 12, or 16 hours (135.267(d), (e)); plus 13 rest periods of at least 24 consecutive hours each calendar quarter (135.267(f))
• PIC qualifications: an ATP certificate is required to serve as PIC in passenger operations of turbojets, airplanes with 10 or more passenger seats, or multiengine airplanes in commuter operations (135.243(a))

After any aircraft accident, and after these serious incidents — the air-carrier-relevant ones especially:

• Flight control system malfunction or failure
• Required crewmember unable to perform normal flight duties from injury or illness
• Turbine engine failure with escape of debris other than out the exhaust
• In-flight fire; aircraft collision in flight; property damage over $25,000
• For large multiengine aircraft (over 12,500 pounds): sustained reliance on emergency bus or sole remaining hydraulic system, loss of thrust on two or more engines, and evacuation using an emergency egress system
• Loss of information from more than 50 percent of cockpit displays (EFIS/EICAS/ECAM)
• An ACAS/TCAS resolution advisory issued on an IFR flight plan when compliance was necessary to avert a substantial risk of collision
• An air carrier that lands or departs on a taxiway or incorrect runway, or a runway incursion requiring immediate corrective action (830.5(a))
• An aircraft overdue and believed to be in an accident (830.5(b))

The formal report on Form 6120.1/2 is due within 10 days of an accident (7 days for a still-missing overdue aircraft); incident reports only if requested (830.15).

• Aircraft accident: an occurrence between the time any person boards with the intention of flight until all have disembarked, in which any person suffers death or serious injury or the aircraft receives substantial damage
• Serious injury: hospitalization more than 48 hours starting within 7 days, fracture of any bone (except simple fractures of fingers, toes, or nose), severe hemorrhage or nerve/muscle/tendon damage, internal organ involvement, or second/third-degree burns or burns over more than 5 percent of the body
• Substantial damage: damage adversely affecting structural strength, performance, or flight characteristics, normally requiring major repair or replacement — explicitly excluding engine failure limited to one engine, bent fairings, dented skin, small punctured holes, ground-damaged props, and damage to gear, wheels, tires, flaps, brakes, or wingtips
• Fatal injury: death within 30 days of the accident (830.2)

These definitions are the whole game on 830 scenario questions: a blown tire and damaged flap on landing is neither serious injury nor substantial damage — an incident, reportable only if it hits an 830.5 trigger.

The PRD is the FAA's electronic database of pilot records, and part 111 prescribes the rules governing its use (111.1(a)). It applies to (111.1(b)):

• Every part 119 certificate holder operating under 121, 125, or 135
• Fractional ownership program managers under 91 subpart K
• Air tour operators holding a 91.147 letter of authorization
• Certain part 91 corporate operators of type-rated airplanes and turbine rotorcraft
• Public aircraft entities, their bankruptcy trustees
• Each person employed as a pilot by, or seeking employment as a pilot with, any of them

That last clause is why the ACS assigns subparts A and D to you: the pilot is a regulated party in the system, not just its subject. Practical takeaway for the oral: training and employment events at a carrier become professional records that follow you between employers.

The ATP oral revisits the interplay between part 91 and the carrier rules — the part 91 corpus itself (currency, equipment, airspace, IFR rules) is covered in depth in the Instrument and Commercial guides:

• 91.3 still makes the PIC directly responsible and the final authority, and its emergency deviation power persists under 121 — but with the carrier overlay of 121.557's reporting and the dispatcher's parallel duties (Task VII.A)
• Part 91 is the floor: persons subject to part 119 must comply with the rest of the chapter except where part 119, 121, 125, or 135 modifies or adds requirements (119.1(c)). Where both speak, the stricter carrier rule governs your operation
• The ACS scope adds subparts F, G, and H — the rules for large and turbine-powered airplanes and operations outside the U.S. Part 119 itself points into that territory: 119.1(a)(3) excepts operations conducted under 91.501(b) from the certification requirement, which is where part 91 subpart F's regime for large and turbine-powered airplanes begins — so know where subpart F applies to the airplane you fly

The efficient study move: for each scenario, ask "what would part 91 allow, and which 117/121/135 rule takes it away?"

I work outside-in:

• Size, location, and protection — protected water shelters you from wind and swell; unprotected areas add both
• Surface wind and waves — read direction and strength from the water itself; wave systems have direction and height, and a swell system encountered on the step can itself initiate porpoising (FAA-H-8083-23 ch. 4)
• Current — it's stronger than intuition suggests: a 5-knot current can carry the seaplane against a 25-knot wind (FAA-H-8083-23 ch. 4), so plan taxi and sailing with both vectors
• Debris, sandbars, islands, and shoals — floating and partially submerged hazards, plus depth
• Vessel traffic and wakes — a boat wake crossed on the step can trigger skipping (FAA-H-8083-23 ch. 4)

The AMES layer: with two engines you also have differential power to aid steering on the water (FAA-H-8083-23 ch. 4), which changes your taxi options in wind.

Porpoising is a rhythmic pitching motion caused by dynamic instability in forces along the float bottoms while on the step — an incorrect planing attitude sets off a cyclic oscillation that steadily increases in amplitude unless the proper pitch attitude is reestablished. Nose too low builds a water crest under the bows that the floats ride over and dig into again; nose too high can also porpoise, or cause a premature lift-off at extreme AOA, stall, and a nose-down drop (FAA-H-8083-23 ch. 4).

Correction:

• Apply timely back pressure and hold it until the porpoising stops
• If it hasn't stopped by the second oscillation: power to idle, elevator control held firmly back, and let the seaplane settle with no further instability
• Never chase the oscillations — that makes them worse (FAA-H-8083-23 ch. 4)

Limits shift with gross weight, flap position, and CG — a forward CG increases the chance of high-angle porpoising, especially during landing (FAA-H-8083-23 ch. 4).

Skipping is instability from landing at excessive speed with the nose at too high a pitch angle — at the upper trim limit the seaplane enters a cyclic oscillation on touching the water and bounces across the surface like a skipped stone. It can also occur crossing a boat wake while taxiing on the step or during takeoff.

Telling them apart by feel: a skip gives vertical G forces like a bounced landplane landing; porpoising is a rocking-chair, forward-and-aft motion.

Correction: increase back pressure and add sufficient power to keep the floats off the water, establish the proper pitch attitude, then reduce power gradually and settle on.

Skipping oscillations don't grow in amplitude the way porpoising does, but they pound the floats and airframe — and can lead to porpoising (FAA-H-8083-23 ch. 4).

Through drag and its phases:

• Displacement (at rest and idle taxi): buoyancy carries the weight and the wetted area — the float surface below the waterline — is the drag driver; heavier means deeper means more wetted area
• Plowing: hydrodynamic lift raises the bows while the aft floats dig deeper, and water drag peaks at "the hump" just before the planing attitude
• The step: the specially shaped forward float bottom converts motion into hydrodynamic lift, wetted area shrinks, and acceleration to lift-off becomes possible without additional power (FAA-H-8083-23 ch. 4)

Hull differences matter to handling too: with the engine shut down, most flying boats sail backward and toward wherever the nose points, because a hull gives proportionally less keel effect than floats (FAA-H-8083-23 ch. 4).

• Charts: seaplane landing areas use symbols like land airports with an anchor in the center; tick marks mean fuel and services, a double ring means military (FAA-H-8083-23 ch. 1)
• Directories: the Chart Supplement lists data on record with the FAA for all open-to-the-public airports, seaplane bases, and heliports (AFH glossary) — including services and operating restrictions
• At night: the rotating beacon for a lighted water landing area alternates white and yellow; a double white flash alternating with yellow marks a military seaplane base (FAA-H-8083-23 ch. 1)

Restrictions extend onto the water itself: when circling the landing area, note buoys marking preferred channels, hidden dangers, or off-limits areas such as no-wake zones and swimming beaches (FAA-H-8083-23 ch. 6). Services at many bases are minimal, which the ACS flags as its own risk (AA.I.H.R4).

• General: keep clear of all vessels insofar as possible and avoid impeding their navigation; give way to anything with the right-of-way
• Crossing: the aircraft or vessel to the other's right has the right-of-way
• Head-on: each alters course to the right
• Overtaking: the one being overtaken has the right-of-way; the overtaking craft keeps well clear
• Special circumstances: when risk of collision exists, proceed with careful regard for circumstances including the limitations of the respective craft (91.115)

And the jurisdiction point examiners like: under Coast Guard regulations a seaplane on the water is a vessel — inshore of the demarcation line you follow the Inland Rules, seaward of it the International Rules, and all seaplanes must carry a current copy of the rules when operating in international waters (FAA-H-8083-23 ch. 1).

Both bind you because a seaplane on the water is a vessel:

• Naval vessel protection zone — a 500-yard regulated area of water surrounding any large U.S. naval vessel (greater than 100 feet in length), in effect whether the vessel is underway, anchored, moored, or in a floating dry dock (33 CFR 165.2015, 165.2025, 165.2030). Within the zone, operate at the minimum speed necessary to maintain a safe course and proceed as directed by the Coast Guard, the senior naval officer present in command, or the official patrol; no vessel or person may come within 100 yards of the naval vessel unless authorized — request authorization on VHF-FM channel 16
• No-wake zones — locally designated areas, marked by buoys, where vessels must hold to a minimum speed that produces no wake — typically near docks, marinas, and swimming areas. For a seaplane that means displacement (idle) taxi through them: step taxi throws a wake. Note them while circling the landing area, along with other off-limits areas (FAA-H-8083-23 ch. 6)

The U.S. buoyage system is built for vessels running channels to and from the sea, so read it from seaward:

• Can buoys — cylindrical, black or green, odd-numbered, mark the left (port) side of the channel approaching from seaward
• Nun buoys — conical, red, even-numbered, mark the right side: "red, right, returning" to home port
• Black and white vertically striped buoys mark the middle of the channel or fairway
• Daybeacons — the shallow-water equivalent, markers on pilings
• Numbers increase from seaward toward the coast; only the more important buoys are lighted (FAA-H-8083-23 ch. 1)

Practical caution: the mooring chain may be several times the water depth, so the buoy can float a good distance from its charted spot and from the hazard it marks — don't cut close to one (FAA-H-8083-23 ch. 1). Nautical charts come from NOAA's Office of Coast Survey, and Coast Guard light lists describe the lighted aids (FAA-H-8083-23 ch. 1).

At this certificate it stops being a private checklist and becomes a regulatory act under part 117:

• You must report for any flight duty period rested and prepared to perform your assigned duties (117.5(a))
• The carrier may not assign — and you may not accept — a flight duty period if you've reported too fatigued to safely perform (117.5(b))
• Once you report yourself too fatigued, the carrier may not let you continue the FDP (117.5(c))
• As part of the dispatch or flight release, each flightcrew member must affirmatively state he or she is fit for duty prior to commencing flight (117.5(d))

That last one is the answer the examiner is fishing for: signing the release is your self-assessment, on the record. The IMSAFE-style personal inventory you've used since private pilot is how you back the signature up.

All of the following:

• An approved Minimum Equipment List exists for that airplane
• The operations specifications authorize operations in accordance with the MEL, and the flight crew has direct access at all times prior to flight to all the information in it
• The MEL provides for operation with those items inoperative
• Records identifying the inoperative instruments and equipment — and the required MEL information — are available to the pilot
• The airplane is operated under all applicable conditions and limitations in the MEL and the ops specs (121.628(a))

One phrase worth quoting: an approved MEL "constitutes an approved change to the type design without requiring recertification" (121.628(a)(2)). You are legally flying a slightly different airplane, which is why the conditions and limitations attach.

Three categories:

• Instruments and equipment required by the airworthiness requirements under which the airplane was type certificated and which are essential for safe operations under all operating conditions
• Items an airworthiness directive requires to be operable, unless the AD provides otherwise
• Instruments and equipment required for specific operations by part 121

The escape hatch: an airplane whose inoperative item falls under the first or third category may still be moved under a special flight permit under 21.197 and 21.199 — 121.628(c) says "notwithstanding paragraphs (b)(1) and (b)(3)," so an AD-grounded item gets no ferry relief unless the AD itself provides it. A ferry flight, not a revenue flight.

The MEL addresses inoperative instruments and equipment — failing internal systems and their parts; the CDL (Configuration Deviation List) is used the same way but addresses missing external parts of the aircraft.

AFH ch. 16's CDL examples: service doors, power receptacle doors, slat track doors, landing gear doors, APU ram air doors, flap fairings, nose-wheel spray deflectors, position light lens covers, slat segment seals, static dischargers. Both can carry performance penalties, and both must be acknowledged before you compute takeoff data — the AFH's rejected-takeoff discussion lists "penalizing MEL or CDL items" among the factors that degrade stopping performance.

The deferral is documented, placarded, and time-limited (AFH ch. 16):

• The MEL entry may impose conditional requirements — operational, mechanical, or both — such as precautionary preflight checks, partial repairs, or isolating and securing parts of the affected system
• Required procedures are flagged "O" (operations) or "M" (maintenance) — the letter tells you whose job the compliance step is
• An authorized person makes an entry in the MEL Deferral Record and issues a temporary placard, affixed onto or next to the affected instrument or control to remind the crew of the limitations
• The deferral authorizes operation for a limited time before permanent repair

Your job at the flight deck (AA.II.A.S3): confirm the placard, the O-procedures, and the operational limitations — and be able to explain how the deferral changes today's flight.

At liftoff. AFH ch. 16 is explicit: the MEL applies only while the aircraft is on the ground awaiting departure or takeoff — it is essentially a dispatching reference. Once airborne, mechanical failures are handled with the appropriate checklists and the approved AFM (abnormal/emergency sections), not the MEL. You may look at the MEL in flight for background, but actions are based strictly on the AFM. The distinction matters in the oral: an item that would ground the airplane at the gate does not require an emergency response to the same failure in cruise.

The document by which a domestic or flag flight legally exists. Under 121.593, no person may start a domestic flight unless an aircraft dispatcher specifically authorizes it (exception: an intermediate stop specified in the original release, on the ground not more than one hour). The release may be in any form but must contain at least:

• Aircraft identification number and trip number
• Departure airport, intermediate stops, destination airports, and alternate airports
• A statement of the type of operation (e.g., IFR, VFR)
• Minimum fuel supply
• For ETOPS flights, the ETOPS diversion time for which the flight is dispatched (121.687(a))

It must also contain or attach the latest available weather reports and forecasts for destination, intermediate stops, and alternates as of the time the release is signed by the pilot in command and dispatcher (121.687(b)) — the signature line where your preflight assessment and the dispatcher's meet.

• All available current reports or information on airport conditions and irregularities of navigation facilities that may affect the safety of the flight
• Before the flight: all available weather reports and forecasts of weather phenomena that may affect the safety of flight — the reg names clear air turbulence, thunderstorms, and low altitude wind shear — for each route to be flown and each airport to be used
• During the flight: any additional available information of meteorological conditions and irregularities of facilities and services that may affect safety

This is why the ATP preflight-assessment conversation is about a shared system, not a solo brief: dispatch is regulatory obligated to feed you, and joint responsibility runs through the release you both signed.

Ops specs are the fine print on the certificate. Under 119.5, no person may:

• Operate as an air carrier without, or in violation of, an appropriate certificate and appropriate operations specifications (119.5(g))
• Operate in a geographical area unless the ops specs specifically authorize it (119.5(j))
• Operate in violation of the ops specs (119.5(l))

Practically, they're also where your MEL authority lives (121.628(a)(2)). The skill element (AA.II.A.S5) expects you to identify and comply — know where in your operator's manuals the ops specs paragraphs relevant to today's flight sit (deicing program, lower-than-standard minimums, ETOPS), and check the airplane and route against them.

• Airborne navigation databases run on a 28-day revision cycle (IPH ch. 6)
• Pilots using the databases are ultimately responsible for ensuring the database they are operating with is current — including checking NOTAM-type information on database errors supplied by the avionics manufacturer or database provider (IPH ch. 6)
• Part 121, 125, and 135 operators must update databases in accordance with their approved maintenance program (IPH ch. 6) — loading the data is a maintenance function, but confirming the cycle's effective dates on the flight deck is a crew item
• Naming conventions and system capabilities vary by manufacturer, so cross-check the loaded procedure against the chart before you rely on it (IPH ch. 6)

Prohibited: taking off when frost, ice, or snow is adhering to the wings, control surfaces, propellers, engine inlets, or other critical surfaces — the clean aircraft concept.

The one exception: takeoffs with frost under the wing in the area of the fuel tanks may be authorized by the Administrator (121.629(b)).

The preflight-assessment piece (AA.II.A.S7) is ensuring surfaces are free of ice, snow, and frost and knowing the deicing procedures if conditions demand them — the holdover-time and pretakeoff-check machinery is covered under Task II.E, where the ACS puts it.

The inspection is divided and proceduralized rather than reduced:

• The walkaround and flight deck setup are split between crewmembers per the operator's checklist, and the check is coordinated — each pilot must know which items belong to whom (AA.II.A.S1)
• Nothing gets moved — doors, hatches, flight control surfaces — without coordinating with ground crew and confirming clearance (AA.II.A.S2); people and equipment live around a transport airplane in ways they don't around a trainer
• What you find goes into the system: document any discrepancies, take corrective action, and acknowledge the limitations imposed by MEL/CDL deferrals (AA.II.A.S3). At a carrier, "corrective action" means the logbook and maintenance control, not a screwdriver
• The output is still a single judgment call: the aircraft is airworthy and in condition for safe flight (AA.II.A.S4) — and the PIC owns it regardless of how many people touched the airplane first

Preventive maintenance is simple or minor preservation operations and the replacement of small standard parts, not involving complex assembly operations, limited to the items listed in part 43, appendix A(c) (PHAK ch. 9). Any pilot who performs it must make a maintenance record entry: a description of the work, the date of completion, and the pilot's name, signature, certificate number, and type of certificate (PHAK ch. 9). The ATP framing for the oral (AA.II.A.K3): know the authority exists and what it covers, and then explain that in air carrier operations the practical answer to a discrepancy is the maintenance program and maintenance control — not the crew — with the MEL/CDL as the deferral instrument.

1. Write it up. An undocumented discrepancy is not a deferral — the MEL process starts with the entry (AA.II.A.S3)
2. Consult the MEL with maintenance control: is the item deferrable, in what quantity, with what O and M procedures, and with what operational limitations (AFH ch. 16)
3. Confirm the deferral is executed — Deferral Record entry, placard on or next to the affected control (AFH ch. 16)
4. Trace the operational consequences before you accept the airplane: performance penalties, weather or equipment restrictions, and any interaction with today's route — an MEL/CDL penalty is on the AFH's list of factors that degrade rejected-takeoff stopping performance
5. Then decide whether the airplane is in condition for safe flight for this flight (AA.II.A.S4). The MEL makes the flight legal; it does not make it wise on every day the deferral is technically available

The external-pressure risk element (AA.II.A.R4) lives in this scenario: the schedule leans on the deferral decision, and the fit-for-duty signature you gave under 117.5(d) is the same signature that accepts this airplane.

All of it — dispatch shares the work, not the accountability. The dispatcher must give you airport conditions, facility irregularities, and hazardous weather for every route and airport (121.601), and the release carries the latest weather when you sign it (121.687(b)). Your side (AA.II.A.K5, S6): assess weather, airports, airspace, terrain, and obstructions against this airplane, this deferral list, and this crew. The ACS also names aviation security concerns as a risk element (AA.II.A.R5) — at a carrier that means following your operator's security procedures and treating anything anomalous around the airplane or its servicing as a stop-and-resolve item, not a keep-the-push-moving item.

The same documents you've always confirmed — airworthiness and registration certificates, operating limitations and manuals, weight and balance data (AA.II.A.K2) — plus the carrier overlay: the MEL/CDL and its deferral record, and the dispatch release as the required documentation for the operation (AA.II.A.K2e names it directly). Inspection status in a 121 operation is tracked by the operator's maintenance program, so the flight-deck check is confirmation the paperwork on board matches the airplane: deferral placards agree with the release, and nothing on the release surprises the crew. If the release says one thing and the logbook says another, that conflict is resolved before the airplane moves.

Because engine temperatures get hotter during starting than at any other time, and a turbine engine cannot tolerate an over-temperature for more than a very few seconds without serious damage (AFH ch. 15). That's why turbine engines have minimum rotational speeds for introducing fuel into the combustion chambers during startup — fuel before sufficient airflow means heat with nothing to carry it away. After light-off, the heat rise happens very quickly: temperatures may approach the maximum in a matter of 2 or 3 seconds before the engine stabilizes and falls into the normal range. Vigilant monitoring of temperature and acceleration is the pilot's whole job until the engine is stable, with a hand ready to cut off fuel (AFH ch. 15).

A hot start is an engine tendency to exceed maximum starting temperature limits (AFH ch. 15) — a start with normal rotation but exhaust temperature beyond prescribed limits (AFH glossary). The causes: too much fuel entering the combustion chamber or insufficient turbine rpm (PHAK ch. 7).

First clue: it may come before the gauge peaks — the temperature rise may be preceded by unusually high initial fuel flow (AFH ch. 15).

Response: cut off fuel promptly — serious engine damage occurs if the hot start is allowed to continue. And it isn't over when the engine is shut down: any time an engine has a hot start, refer to the AFM or maintenance manual for inspection requirements (PHAK ch. 7). A hot start you don't write up is a hot section someone else inherits.

A hung (false) start is a normal light-off with rpm remaining at some low value rather than increasing to normal idle — the engine is accelerating more slowly than normal and stabilizes at an rpm that won't sustain itself without the starter (AFH ch. 15 and glossary). Usual causes: an insufficient starting power source (low battery, weak ground power) or the starter not turning the engine fast enough, and PHAK adds a possible fuel control malfunction (PHAK ch. 7). The response is to shut the engine down (PHAK/AFH glossary) — an engine hung below idle is running hot at low airflow, which is the hot-start mechanism waiting to happen.

Because voltage is temperature margin. When battery voltage is low, its ability to turn the compressor for engine start is greatly diminished, and the possibility of engine damage due to a hot start increases — which is why the AFH says to check the battery's condition before every engine start (AFH ch. 15). Successful starting depends on assuring the correct minimum battery voltage before initiating start, or employing a ground power unit (GPU) of adequate output (AFH ch. 15). A marginal battery isn't a reason to try anyway and watch the gauges harder — it's the decision point for external power.

Type-dependent — which is exactly what the knowledge element wants you to say before you say anything else. The building blocks:

• Starter/generators — in turboprops the DC generator doubles as the starter motor, using electrical power to crank and then producing power once running (AFH ch. 15)
• A ground power unit (GPU) — a small gas turbine that provides electrical power and/or air pressure for starting, connected when needed; "similar to an aircraft-installed auxiliary power unit" (AFH glossary)
• An APU — the installed equivalent, giving you the same electrical/pneumatic start capability without ground equipment

External power is especially valuable for cold weather starting, and the rule is always the manufacturer's: follow the AFM procedures for engine starting using a GPU (PHAK ch. 7). Know for your type which sources can start which engine, and the associated limits — those numbers live in the AFM, not in this guide.

A closed communication loop through all three phases the ACS names — before start, start, and after start (AA.II.B.S1):

• Before start: confirm with ground crew the area is clear of personnel, vehicles, FOD, and other aircraft (AA.II.B.R4), doors and hatches closed, external power connected or ready to disconnect as required
• Start: signal the start — intercom or standard hand signals — and turn on the rotating beacon whenever an engine is running (AC 120-74, exterior-light guidance), so the ramp has the same cue you do
• After start: confirm start-source disconnection and stowage, chocks as briefed, and a clear salute/handoff before the airplane moves

The skill elements are blunt about the standard: use appropriate ground personnel (S2), and complete the appropriate checklists prior to and after start, coordinated with the crew (S3).

There's no propeller to indicate visually whether the engine is running — and even at idle, a jet engine is a threat from both ends: enough air is being drawn into the intake to pull a nearby person into the fan, and the exhaust is hot and moving fast enough to blow a person down (AFH ch. 16). It scales up with thrust: adding too much power to start moving can pull damaging debris off the ground and the jet blast can damage equipment well behind the aircraft (AFH ch. 16). This is the substance of the propeller-and-turbine-safety risk element (AA.II.B.R2) — brief it as two hazard zones, front and back, that exist whenever the beacon is on.

Some engine inlets form a vortex between the ground and the inlet during ground operations — a vacuum-cleaner effect — which is why vortex dissipaters, screens, or deflectors may be installed (PHAK ch. 7). Typical foreign object damage is small nicks and dents in the compressor and turbine sections from ramp debris, but ingestion can destroy an engine outright (PHAK ch. 7). Preflight procedures therefore include a visual inspection for any sign of FOD — both the inlet and the pavement around it. During start and taxi, the mitigation is the crew's eyes plus ground crew reports: debris, loose equipment, and unsecured items near the start area are a stop-the-start item (AA.II.B.R4).

During every start you're monitoring temperature and acceleration against the AFM's limits (AFH ch. 15). The triggers:

• Fuel flow unusually high at light-off — precursor to a hot start; be ready on the cutoff (AFH ch. 15)
• Temperature rising toward the starting limit — cut off fuel; do not ride it and hope (AFH ch. 15)
• RPM stops accelerating below idle — hung start; shut down (PHAK/AFH glossary) and investigate the start source (PHAK ch. 7)
• No light-off — fuel in a hot engine with no flame is its own hazard; end the attempt and follow the AFM's procedure before another try

After any abnormal start, the write-up matters as much as the response: a hot start carries AFM/maintenance-manual inspection requirements (PHAK ch. 7), and the associated limitations (starter duty cycles, motoring procedures) are type-specific AFM material (AA.II.B.K3).

Stop the start — fuel off, start source safed, brakes set — and get maintenance involved. The ACS deliberately asks how you manage situations where specific instructions or checklist items are not published, and on the ground during start the conservative move is nearly always available and nearly always right: nothing about a parked airplane requires improvisation. The regulatory backstop if a genuine emergency does develop is 91.3(b): in an in-flight emergency requiring immediate action, the PIC may deviate from any rule of part 91 to the extent required. But the honest answer for a start malfunction is that you should never need it: the airplane isn't going anywhere, so time is on your side — use it, and don't invent procedures around engine limits.

As a coordinated sequence, not a solo recitation:

• Before start: the flow is completed, then the checklist confirms it — with the ground crew's clearance received before anything turns
• During start: one pilot commands and sequences the start; both monitor the engine indications, because the abort triggers (temperature, acceleration, fuel flow) need eyes that aren't also on the overhead panel
• After start: the after-start flow and checklist, ground equipment disconnected and confirmed, and only then the taxi phase begins

AC 120-74 carries this into the next phase: complete as many checklist items as possible before initial taxi — once the aircraft is clear of equipment and personnel — so that taxi attention goes outside. The standard the evaluator applies is simple: no phase's checklist bleeds into the next phase's attention.

• The starter/generator does double duty, so electrical system status is start-system status (AFH ch. 15)
• Heat sensitivity is identical to a jet's — minimum rotational speed before fuel, light-off temperature spike in 2–3 seconds, and the same hot-start consequences (AFH ch. 15)
• After start, a split-shaft/free turbine engine's power output lags several seconds behind power lever movement — anticipate and lead power changes rather than chasing them (AFH ch. 15)
• Ground handling adds the beta range: aft of flight idle the power lever directly controls blade angle down into reverse; operating there requires the specific techniques, parameters, and limitations of your airplane (AFH ch. 15)

"Starting under various conditions" (AA.II.B.K2) — cold soak, hot ambient, tailwind on the ramp, battery vs. external — is where the AFM's supplementary procedures live; know where they are and which apply today.

Per AC 120-74, the pretaxi planning conversation covers:

• The expected taxi route — reviewed on the current airport diagram — including any hold short lines and runways to cross, and hot spots and complex intersections along it
• The anticipated duration of the taxi and the visibility along the route
• When the checklists get run: if conditions permit, conduct predeparture checklists at the gate — including setting takeoff flaps — or while stopped or taxiing straight ahead on a taxiway without complex intersections or hot spots
• Critical locations where verbal PIC/SIC coordination is required: hot spots, runway crossings, entering and lining up on the runway
• Single-engine taxi, if applicable, and any unusual procedures at this airport — different pushback, communication requirements, previous experience worth sharing
• In low visibility: the low visibility taxi chart and ILS critical area holds

The AC's caution is worth quoting to the examiner: the pitfall of pretaxi planning is setting expectations and then receiving different instructions — fly the clearance you actually received, not the one you briefed (AA.II.C.R2).

ICAO's definition, via the Instrument Procedures Handbook: a location on an aerodrome movement area with a history or potential risk of collision or runway incursion, and where heightened attention by pilots and drivers is necessary. They flag complex or potentially confusing taxiway geometry — the intersections that have already caught crews. They're depicted as circled areas on airport charts and included with the airport diagrams in the Chart Supplement (IPH ch. 1; PHAK ch. 14 shows them labeled "HS1" style). The briefing standard: identify every hot spot on or near your taxi route by name before taxi, and treat each one as a slow-down-and-confirm point.

NOTAM review: before taxi, check the current airport NOTAMs and ATIS for runway and taxiway closures, construction activity, and other airport-specific risks (AC 120-74).

Clearance conflict: ATC is assumed to have firsthand knowledge of runway and taxiway status, but if a clearance is received to use a runway or taxiway that a NOTAM or ATIS broadcast indicates is closed, query the controller for verification of the clearance (AC 120-74).

The NOTAM review pairs with the current airport diagram, hot spots, and — where published — the textual description of standard taxi routes to build the "big picture" of the airport and its potential incursion areas before the airplane ever moves.

The FAA definition (IPH ch. 1): "Any occurrence at an aerodrome involving the incorrect presence of an aircraft, vehicle, or person on the protected area of a surface designated for the landing and takeoff of aircraft." The categories:

• Category A — a serious incident in which a collision was narrowly avoided
• Category B — separation decreases with significant potential for collision, which may require a time-critical corrective or evasive response
• Category C — an incident with ample time and/or distance to avoid a collision
• Category D — incorrect presence on the protected area with no immediate safety consequences

Note what the definition doesn't require: no near-miss, no traffic. A single aircraft nosewheel over a hold line with nobody around is an incursion.

The sterile flight deck rule. Critical phases of flight include all ground operations involving taxi, takeoff, and landing, and all other flight operations below 10,000 feet except cruise flight (121.542(c)) — with taxi defined as movement of an airplane under its own power on the surface. During those phases:

• No crewmember may perform, and no carrier may require, any duties except those required for the safe operation of the aircraft — the reg's own examples of prohibited duties include company calls, galley orders, and passenger PR announcements (121.542(a))
• No activity which could distract any crewmember is permitted — eating, nonessential conversation in the cockpit or with the cabin, reading unrelated publications (121.542(b))
• Separately and during all flight time: no personal wireless communications device or laptop at a duty station unless the use is directly related to operation of the aircraft or for emergency/safety-related/employment-related communications per approved procedures (121.542(d))

AC 120-74 adds the crew-culture half: brief sterile cockpit, but encourage anyone to speak up if they see a conflict or interpret a clearance differently — sterile means no chatter, not no safety calls.

• Write it down — AC 120-74 recommends written taxi instructions when routes are complex or the airport is unfamiliar; shorthand works: clearance "taxi 9R via Bravo, Echo, Juliet, hold short 4L at Echo" becomes written "9R B E J 4L E" with the 4L-at-Echo clearance limit circled, or "9R BEJ/4L E" in an FMC scratchpad, where the forward slash represents the hold short line
• Read back all hold short instructions in full, with the complete call sign and the runway designator; avoid "Roger" or "Wilco" when the instruction involves entering, crossing, or holding short of a runway (AC 120-74)
• Verbalize the plan between pilots and trace it on the airport diagram before the airplane moves — a common understanding is established by repeating the instructions and getting agreement, and any persistent disagreement is resolved by asking ATC
• State your position on initial contact with every ground or tower controller, even if you already told the previous one (AC 120-74)

The read-back-in-full habit exists because incursions happen even after the pilot reads back the hold short — so the AC also suggests a physical reminder technique, like placing an object on the instrument panel or yoke until the hold-short is complied with.

• Be positive that ATC has cleared you to cross — if there's any doubt, stop (clear of the protected area) and ask
• Approaching the hold line, verbalize "approaching (runway) hold short line"; before crossing, visually scan left and right, the full length of the runway and its approach paths, and coordinate verbally — "clear left, clear right" or that the scan is not clear (AC 120-74)
• When approaching an entrance to a runway, come to a complete stop, or be in a phase of taxiing with no incursion risk, before continuing operational duties and checklists (AC 120-74)
• All exterior lights on when crossing a runway — with judgment about blinding others with forward-facing lights (AC 120-74)
• Extra vigilance taxiing between active parallel runways, and cross expeditiously once cleared

At night or in low visibility, the same procedure slows down; it never abbreviates.

• Expect communication from ATC within 90 seconds of the LUAW clearance if you weren't told the reason for the wait or can't see it — if you hear nothing in 90 seconds, query ATC (AC 120-74)
• TCAS/TAS on to build awareness of traffic that may be landing on your runway; scan the full length of the runway and the final approach as you taxi on
• Monitor the tower frequency actively; if the radio goes unusually quiet or a stuck mic is suspected, contact ATC and watch for light gun signals
• Lights: everything that highlights your silhouette except landing lights — landing lights come on with the takeoff clearance (AC 120-74)
• At night, consider lining up slightly left or right of centerline (approximately 3 feet) so a landing aircraft can distinguish your lights from the runway lights (AC 120-74)

Be especially vigilant with LUAW at night or in reduced visibility — that's the AC's own emphasis, and the geometry — an aircraft holding on an active runway — is behind some of the worst accidents in aviation history.

AC 120-74's convention, adjusted for your airplane's equipment and limitations:

The lights are a signal system: the airplane silhouette announces "on the runway," and landing lights announce "rolling." The AC's caveat — adherence is voluntary and equipment varies, so never rely solely on another aircraft's lights to judge its intent.

The Surface Movement Guidance and Control System — a low-visibility taxi plan for airports where air carriers operate at RVR below 1,200 feet (IPH ch. 1, per AC 120-57 and FAA Order 8000.94). Its pieces:

• Controllable stop bar lights — a row of red, unidirectional in-pavement lights controlled by ATC; required for operations below 500 ft RVR. Non-controllable stop bars mark intersections where movement is restricted and operate continuously below 500 RVR
• Taxiway centerline lead-on lights — alternating green/yellow in-pavement lights guiding traffic in low visibility and at night
• Runway guard lights — elevated or in-pavement alternately flashing yellow lights marking taxiway access to an active runway
• Geographic position markings — the "pink spots," outlined in a black-and-white circle, used by ATC as hold points or for position reporting
• Clearance bar lights — three yellow in-pavement lights denoting holding positions

Part 121 and 135 flight and ground crews are required to comply with SMGCS plans where implemented, and anyone operating under the plan must have the low visibility taxi route chart for that airport (IPH ch. 1). Brief it before you need it — the chart is useless discovered at the hold line in 600 RVR.

• AC 120-74 files pushback under the unusual-procedures briefing item: address previous experience at the airport and procedures "not typically used on an everyday basis, such as different pushback procedures or communication requirements" — the brief happens before the airplane moves, not while the tug is connected
• The operation runs on an agreed-upon signal set with ground personnel: the AFH's ramp guidance is that whether the standard AIM hand signals or a modified set is used matters less than that each operation uses a suitable, agreed-upon set (AFH ch. 2; at night the Emergency Stop signal is used for all stop indications)
• Before any movement, confirm the area around the airplane is clear of persons, equipment, and other hazards (AFH ch. 2)
• The specifics — brake use while under tow, the nosewheel steering disconnect or bypass pin, and when the ground crew disconnects and is confirmed clear — belong to your operator's SOPs; be ready to walk them type-specifically

AC 120-74's directive is about time, not technique: brief single-engine taxi, including allowing enough time to complete all required checklists without any crewmember feeling rushed — and do not accept any ATC clearance if it appears you will be unable to properly complete all required checklist items. The engine you start during taxi injects a start sequence, an after-start flow, and a config change into exactly the phase where heads-down time causes incursions — so the briefing decides in advance where on the route the start happens and who is outside eyes while it does. The actual procedure — which engine, warm-up times, system limitations on one generator or hydraulic pump — is your AFM's and your operator's; know it cold and say it type-specifically.

By announcing it, bounding it, and locating it:

• Announce the handoff both directions: "I'm heads-down, right turn ahead at Alpha" when dropping off the frequency or into the FMS, and "I'm back, any changes?" on return — reiterating any upcoming hold short instructions that could be misinterpreted (AC 120-74)
• Bound it: any instructions received while a crewmember was away from the frequency are briefed and reviewed on return
• Locate it: heads-down work happens only when the aircraft is taxiing straight ahead or stopped, with no upcoming hold short lines or hot spots — and time away from monitoring should be avoided entirely with complex routing or runway crossings (AC 120-74)

The distraction and task-prioritization risk element (AA.II.C.R1) and the partial-checklist risk (AA.II.C.R4) are both answered by the same discipline: checklists run at planned pauses, not dribbled through turns.

Five fixed points:

1. When the clearance is issued — confirm and verbalize the assigned runway and taxi route against the airport diagram, including hold-short and crossing instructions
2. At complex intersections — verbally confirm the intersection's identity using the diagram and the heading indicator before transitioning through it
3. Approaching any hold short line — "approaching (runway) hold short line," then the scan and "clear left/right"
4. Before entering a runway for takeoff — verbally coordinate the flap setting, runway identification, compass heading, FMC entry, and receipt of the proper ATC clearance for that runway
5. When anything changes — a route change, a return to the gate, an out-of-the-ordinary flow demands heightened awareness from every crewmember

The compass check embedded in points 2 and 4 is the cheapest incursion insurance there is: the heading display confirms taxiway or runway alignment at every intersection where geometry could deceive you (AC 120-74).

• Never stop on a runway — that is the AC's one absolute in a disorientation event (AC 120-74)
• Confirm which surface you're on: runways have white centerline markings; taxiways have continuous yellow centerlines (AC 120-74)
• Stop the aircraft (clear of any runway) and advise ATC immediately; request progressive taxi — step-by-step routing that controllers also issue on their own initiative for traffic or construction (AC 120-74, IPH ch. 1)
• Rebuild orientation with everything available: airport diagram, heading indicator, signs, markings, lighting — and in low visibility, the geographic position markings

Asking for progressive taxi is a professionalism marker on this checkride, not a confession. The unprofessional version is pressing on while lost, and that's how Category A incursions start.

The airport information doesn't change; your access to it does.

• Lighting becomes signal and hazard: the full AC 120-74 lighting scheme carries your intent to others — and their lights are your traffic picture, with the caution that equipage varies and lights alone never confirm intent
• Judgment calls on your own lights: strobes off during taxi where they'll blind other pilots or ground crew; forward-facing lights managed at runway crossings
• Geometry gets harder: the cues that keep you found by day — pavement edges, signage seen peripherally — shrink to what's lit, so the diagram-plus-heading-indicator discipline does more of the work, exactly as in low visibility (AC 120-74)
• LUAW at night carries the AC's specific mitigations: the ~3-foot centerline offset so landing traffic can distinguish you, and heightened vigilance because the 90-second rule matters most when nobody can see you

If the checkride happens entirely in daylight, expect to explain all of this — the ACS explicitly requires the explanation when the condition isn't available.

From AC 120-74 Appendix 1:

• Verify tower status first — part-time towers are the trap; if in doubt, attempt contact on the tower frequency
• Communicate intentions on CTAF before taxi and listen for traffic operating to and from the airport; monitor and communicate from engine start until 10 miles from the airport unless regulations or OpSpecs direct otherwise
• State the airport name at the beginning and end of each transmission, and remember some aircraft have no radio at all
• Expect instrument traffic where VFR habits wouldn't: aircraft may be flying an instrument approach to a different runway than the one in visual use — possibly the opposite end of yours
• Don't line up and hold on the departure runway any longer than absolutely necessary
• Without ATC to stop you, the visual cues do ATC's job: signs, hold short lines, markings, lighting, and the airport diagram

The scan before entering any runway grows to include the full length plus both final approach and departure paths — on the appropriate frequency, with your own eyes as the only clearance you'll get.

The ACS skill element requires positive control, proper speed, appropriate use of wheel brakes and reverse thrust, and separation from aircraft, vehicles, and persons:

• Thrust: breakaway thrust that's too aggressive pulls damaging debris off the ground and sends jet blast at everything behind you — loose equipment included — so power comes up gently and comes off early (AFH ch. 16)
• Speed: managed with thrust at idle and brakes applied deliberately rather than ridden
• Reverse thrust: ground use is type- and operator-specific — FOD and visibility implications belong to your AFM and SOPs, so give the checkride answer that's your airplane's, not a generic one
• Separation: universal regardless of type — a transport airplane's momentum and blast field mean you protect people and equipment with distance arranged in advance, not reactions

The three positions are idling (displacement), plowing, and planing (step) (FAA-H-8083-23, ch. 4):

• Idling (displacement): the buoyancy of the floats supports the entire weight; attitude is similar to at-rest on the water
• Plowing: power application shifts the center of buoyancy aft; the sterns dig in, drag is high, and it is normally just the transition between idle and planing — taxiing in it is not recommended
• Planing (step): most of the weight is supported by hydrodynamic lift rather than buoyancy; the rear portions of the floats ride clear of the water, drastically reducing water drag

A seaplane is virtually always in motion and has no brakes — wind, current, thrust, and inertia keep acting on it from the moment it's untied — so the pilot must know the wind and water conditions, plan the course of action, and stay mentally ahead of the airplane.

• Elevator all the way back to keep the nose high — it minimizes spray damage to the propeller and improves maneuverability by keeping more of the water rudder underwater. The exception: with a strong tailwind component or heavy swells, hold the elevator forward enough to keep the tail down so the wind can't lift it and flip the airplane
• RPM as low as possible — for speed control, engine cooling, and spray
• Keep speeds below 6–7 knots to limit spray to the propeller; in congested or confined areas, low speed also limits the coasting that inertia produces, because even minor collisions cause serious damage
• Cross boat wakes or swells at a 45° angle where possible, to minimize pitching, rolling, and the chance of an upset (FAA-H-8083-23 ch. 4)

Step taxi covers long distances on the water at high speed but well below flying speed — reduce power carefully as the seaplane comes onto the step to stop the acceleration; 65 to 70 percent of maximum power is a good starting point, more when heavy. The rules (FAA-H-8083-23 ch. 4):

• Only where you're confident of sufficient water depth, no floating debris, no hidden obstructions, and no other water traffic nearby — a floating log can tear open a float, and never step taxi in shallow water: floats touching bottom at speed will likely flip the airplane
• Water rudders retracted — at speed the dynamic pressure pounds them and they're ineffective anyway; steer with the air rudder and ailerons, holding a precise planing attitude with elevator
• If a wake crossing is coming, reduce to idle and idle-taxi across it at an angle
• Turns from downwind to upwind at step speed are proportionately more dangerous — centrifugal force and wind gang up on the outside float; if it starts to submerge, immediate full rudder out of the turn and power reduction may save it

Plowing is the high-drag transitional phase — nose high, sterns deep, lots of power for little speed. Prolonged plowing risks engine overheating (high power, low cooling airflow) and spray damage to the propeller despite the nose-high attitude.

Plow turn: exploits the plowing attitude to neutralize weathervaning when turning downwind in strong wind — the exposed forward float area plus the aft-shifted center of buoyancy lets the airplane turn away from the wind, tracing a question-mark path.

Why a last resort: it's only effective in certain seaplanes, and floatplanes are least stable in the plowing attitude and very susceptible to capsizing — never attempt it in rough water or gusty conditions. In most windy situations it is much safer to sail the seaplane backward instead (FAA-H-8083-23 ch. 4).

Sailing is guiding the seaplane on the water using the wind as the main motive force — usually moving backward, since the seaplane weathervanes nose-into-wind. Use it when wind, water conditions, or limited space make a conventional taxi turn impractical or unsafe — maneuvering into docks and confined spaces, and as the safer alternative to a plow turn. The mechanics (FAA-H-8083-23 ch. 4):

• Swing the tail with the air rudder: keel effect pushes the seaplane in the direction the sterns point — so water rudders up, since their action is counter to what you want
• With power balancing the wind so there's no motion through the water, keel effect disappears and the wind pushes the seaplane toward the side the nose is pointed — combining the two techniques sails you diagonally
• With the engine off, lowering flaps and opening doors adds air resistance and sailing speed downwind
• In strong wind, use full forward elevator to keep the float sterns from submerging — combined with wind lift on the wings, a buried stern can conceivably flip the airplane over backward

Wind, current, and space — evaluated before entering a confined area, because afterward the forces are driving you into the obstructions.

• Current: the handbook's benchmark for how much it matters — for an average seaplane at idle, a 5-knot current can offset a wind of 25 knots blowing the opposite direction; the current wins far more than intuition suggests
• Keel effect: only works when the floats move through the water; if the current carries the seaplane, there may be little relative motion and the rudders go quiet even though you're moving over the bottom
• Planning: plan the course using wind, current, and thrust together; remember each type sails differently (flying boats sail backward and toward the side the nose points regardless of wind velocity), and in multiengine seaplanes use differential power to aid steering (FAA-H-8083-23 ch. 4)

A rhythmic pitching motion caused by dynamic instability in the forces along the float bottoms while on the step — an incorrect planing attitude (nose too low or too high, roughly a degree or two beyond the acceptable range) sets off a cyclic oscillation that steadily increases in amplitude unless the proper pitch attitude is reestablished. Uncorrected, it noses the airplane into the water.

Correction: timely back pressure to keep the float bows from digging in, held until the porpoising stops. If it hasn't stopped by the second oscillation, reduce power to idle and hold the elevator firmly back so the seaplane settles on with no further instability — and never chase the oscillations, which amplifies them.

Weight, flap position, and CG all shift the acceptable attitude band; a forward CG increases the tendency (FAA-H-8083-23 ch. 4).

Skipping is a cyclic oscillation entered at the upper trim limit — excessive speed with the nose too high — and it can also be triggered by crossing a boat wake while on the step.

Body-feel distinction: a skip delivers vertical G forces, like bouncing a landplane; porpoising feels like a rocking-chair forward-and-aft motion. Skipping's amplitude doesn't grow the way porpoising does, but the pounding hammers the floats and airframe and can lead to porpoising.

Correction: increase back pressure and add enough power to keep the floats off the water, establish the proper pitch attitude, then reduce power gradually to settle on gently (FAA-H-8083-23 ch. 4).

The land-side lighting and taxi discipline from Task II.C carries over; the water adds an environment that is mostly unlit:

• A lighted seaplane landing area is identified by a rotating beacon alternating white and yellow — a double white flash alternating with yellow marks a military seaplane base (FAA-H-8083-23 ch. 1)
• Usually only the more important buoys are lighted; some unlighted buoys carry red, white, or green reflectors with the same significance as lights. Red buoys carry red or white lights, green/black buoys green or white lights, and a light flashing Morse code "A" marks a mid-channel buoy (ch. 1)
• Anchored craft — including an anchored seaplane — show an anchor light where maritime regulations require it (ch. 6)
• The handbook's night-water caution names the hazard: the difficulty of seeing objects in the water and judging surface conditions (ch. 6) — so at night or in low visibility, slow down, work from lighted and known references, and treat unlighted water as uninspected

Backwards from every landplane instinct: on water, wheels up. A wheels-down landing on water is almost certain to capsize the seaplane — far more serious than a wheels-up landing on pavement. The handbook's technique: make it verbal and visual — many experienced pilots say out loud, "This is a water landing, so the wheels should be up," then confirm each wheel using externally mounted mirrors and other visual indicators, not just the gear position indicators (FAA-H-8083-23 ch. 6). For this task the same check belongs to taxi phases: confirm gear position any time you transition between ramp, land, and water operations, and brief it as a crew callout where a crew exists.

A sequence of flows verified by checklists, run at planned pauses so nothing competes with taxiing. AC 120-74's placement guidance: complete predeparture checklist items at the gate when possible — including setting takeoff flaps — or while stopped or taxiing straight ahead without complex intersections or hot spots ahead. The skill element adds the word that gets applicants: complete the checklists in a timely manner — meaning done before the runway, never finishing a checklist while taking the runway. During the checks you must be able to explain, on request, any system's operating characteristics, limitations, and the corrective action for a malfunction (AA.II.E.S3) — in a type-rated airplane, the run-up of your commercial days is replaced by systems verification against the AFM's acceptable ranges.

Takeoff data — V1/VR and V2, takeoff power settings, and required field length — is computed prior to each takeoff from: airplane weight, runway length available, runway gradient, field temperature, field barometric pressure, wind, icing conditions, and runway condition (AFH ch. 16). The crew procedure:

• Without an FMS, record it on a takeoff data card
• Both pilots review the data entered in the FMS, or separately compute and cross-check against the data card
• If takeoff plans change while taxiing — recalculate (AFH ch. 16)

That last line is the risk element about a runway change (AA.II.E.R2) in one sentence: new runway, new data, new brief. No exceptions for "it's longer anyway."

Working definition: takeoff decision speed — the speed by which the continue/stop decision must be made; below V1 it's considered safer to stop within the accelerate-stop distance (AFH ch. 16). The FAA's expanded definition (from the Takeoff Safety Training Aid, AC 120-62, via AFH ch. 16) — V1 is the speed selected for each takeoff, based on approved performance data and specified conditions, which represents:

1. The maximum speed by which a rejected takeoff assures a safe stop within the remaining runway (or runway and stopway)
2. The minimum speed which assures the takeoff can be safely completed within the remaining runway (or runway and clearway) after failure of the most critical engine at the designated speed
3. The single speed permitting both, when operating at the minimum allowable field length for a particular weight

In certification, V1 hangs on VEF — the speed at which the critical engine is assumed to fail, itself not less than VMCG — plus the speed gained during recognition before the pilot's first stopping action (25.107(a)).

• VR — rotation speed: rotation to the takeoff attitude begins. It may not be less than V1, nor less than 105 percent of VMC, nor less than the speed that allows reaching V2 before 35 feet above the takeoff surface (25.107(e); AFH ch. 16)
• VLOF — lift-off speed: the calibrated airspeed at which the airplane first becomes airborne (25.107(f))
• V2 — takeoff safety speed: the speed at which the required one-engine-inoperative climb performance can be achieved after lift-off (AFH ch. 16). Its floor, V2MIN: not less than 1.13 VSR for two- and three-engine turboprops and jets without provision for reducing the OEI stall speed, 1.08 VSR for turboprops with more than three engines and jets with that provision — and in all cases at least 1.10 times VMC (25.107(b))

The numbers for your airplane on today's runway are AFM output — the concept you must own is that V1/VR/V2 encode the entire engine-failure plan before brake release.

Most manufacturers recommend identifying a low-speed regime (80 knots and below) and a high-speed regime (100 knots and above) of the takeoff run (AFH ch. 16):

• Low speed: abort for any malfunction or abnormality, actual or suspected
• High speed: reject only for catastrophic malfunctions or life-threatening situations — weighing the threat against the risk of an overrun

The statistics behind the split: although only 2 percent of rejected takeoffs are high-speed aborts above 120 knots, they account for the vast majority of RTO overrun accidents (AFH ch. 16). SOPs add a speed callout at the regime transition — a last crosscheck of airspeed and thrust, and an incapacitation check by challenge-and-response. The briefing states this split out loud so that at 130 knots nobody is inventing criteria. The maneuver itself is Task III.I; the plan is this task.

Because V1 is where deceleration must begin, not where deciding starts. The go/no-go decision should be made before V1 so that deceleration can begin no later than V1 — if braking has not begun by V1, the decision to continue has been made by default. Delaying the RTO just one second beyond V1 adds 4 to 6 knots on average, and crews require 3 to 7 seconds to identify an impending RTO and execute it (AFH ch. 16).

Execution order matters too — the instinctive "normal landing" sequence delays the primary deceleration force when every second counts:

1. Apply maximum braking immediately while simultaneously retarding the throttles
2. Extend spoilers
3. Deploy reversers

A rejected takeoff should be perceived as an emergency (AFH ch. 16).

FAA-approved takeoff data is demonstrated in ideal conditions: a clean, dry runway and maximum braking — reverse thrust is not used to compute stopping distance (AFH ch. 16). The AFH lists these degraders:

• Reduced runway friction
• Mechanical contaminants (rubber, oily residue)
• Natural contaminants (standing water, snow, slush, ice)
• Wind
• Low air density
• Flap and bleed configuration
• Underinflated or failing tires
• Penalizing MEL or CDL items
• Deficient brakes or RTO autobrakes
• Inoperative anti-skid
• Pilot technique

One mitigation to know by name: a reduced V1 — less than normal or maximum V1 but above minimum V1 — properly adjusts the RTO stopping distance for the degraded stopping capability of wet or contaminated runways, while adding roughly 2 seconds of recognition time for the crew (AFH ch. 16).

The captain's briefing is an essential part of CRM, accomplished prior to takeoff (AFH ch. 16). Built from the ACS skill element, AC 120-74, and the AFH's sample captain's briefing (AFH Figure 16-12), a complete brief covers:

• Runway and intersection, verified against the clearance — plus airport NOTAMs and closed taxiways/runways
• Takeoff performance: the computed V-speeds and thrust setting, obstacle clearance and minimum climb gradients, and any MEL/CDL special considerations
• Departure: SID or IFR departure, initial heading, altitude, and fix
• Terrain and weather: significant terrain or obstacles relative to the departure routing, significant weather — windshear gets its planned response stated (AA.II.E.S5)
• The abnormal plan: reject criteria by regime before V1, and for powerplant failure after V1 — continue, fly the engine-out profile (the maneuver is Task VII.B; the commitment happens here)
• Who does what: the PM's callouts and monitoring duties during the roll are set "as directed in the captain's briefing" (AFH ch. 16)

The test of a good brief: if the engine fails at 200 feet tonight, was every first action already spoken aloud on the ground?

Holdover time is the estimated time deicing/anti-icing fluid will prevent the formation of frost or ice and the accumulation of snow on the protected surfaces. It begins when the final application of fluid commences and expires when the fluid loses its effectiveness (121.629(c)(3)). The carrier's program must provide procedures to increase or decrease the determined time in changing conditions. After any maximum holdover time is exceeded, takeoff is permitted only when at least one of these is true:

1. A pretakeoff contamination check determines the wings, control surfaces, and other critical surfaces are free of frost, ice, or snow
2. An alternate procedure approved by the Administrator in the carrier's program makes that determination
3. The aircraft is redeiced and a new holdover time determined (121.629(c)(3))

• A pretakeoff check is a check of the wings or representative aircraft surfaces for frost, ice, or snow, conducted within the holdover time — the routine confirmation that the fluid is still doing its job
• A pretakeoff contamination check verifies the wings, control surfaces, and other critical surfaces are free of frost, ice, and snow after the holdover time has been exceeded. It must be conducted within five minutes prior to beginning takeoff, and from outside the aircraft unless the carrier's program specifies otherwise (121.629(c)(4))

A carrier operating without an approved deicing program lives under 121.629(d): whenever contamination could reasonably adhere, no takeoff unless the aircraft is checked free of it within five minutes prior to takeoff, from outside the aircraft. And behind all of it stands the clean aircraft concept — no takeoff with frost, ice, or snow adhering to critical surfaces (121.629(b)), with dispatch into expected icing itself conditioned on the opinion of the PIC or aircraft dispatcher that safety won't be adversely affected (121.629(a)).

• Bugs and instruments: V-speeds set from the cross-checked data; flight instruments set and checked for the departure (the AFH ch. 2 discipline — heading indicators verified against the compass, bug to runway heading or as assigned — scales directly into the glass flight deck)
• Avionics: frequencies, initial navigation sources and courses, autopilot preselects, and transponder configured to the clearance (AFH ch. 2)
• Flight director: set to the modes your operator's profile calls for on this departure — and stated in the brief, so both pilots expect the same commands at rotation
• The verification gate: before entering the runway, verbally coordinate flap setting, runway identification, compass heading, FMC entry, and receipt of the proper ATC clearance for that runway (AC 120-74)

The autopilot/flight-director risk element (AA.II.E.R5) is really a mode-awareness question: be ready to state what the FD will command at liftoff and what happens if you engage the autopilot with the wrong lateral mode armed — in your airplane's terms, from your AFM.

Everything downstream of the runway assumption gets redone:

• New performance: recalculate the takeoff data — weight didn't change, but runway length, intersection distance, gradient, and wind component did (AFH ch. 16: if takeoff plans change while taxiing, recalculate)
• New setup: FMC runway and departure, bugs if the speeds changed, nav/comm as required — heads-down work done stopped, not rolling (AC 120-74)
• New brief: the abnormal plan was runway-specific — reject margins, engine-out routing, terrain
• New taxi picture: route to the new runway, hold lines, hot spots — expectation bias is exactly the trap AC 120-74 warns about: fly the clearance received, not the one you briefed (AA.II.E.R2)

If the frequency pressure doesn't allow all of that before the runway, the professional answer is "unable" — a transport airplane is never obligated to accept a takeoff clearance faster than the crew can rebuild the plan.

• Read back takeoff and landing clearances including the runway designator, and state "intersection departure" when applicable (AC 120-74)
• Use the complete call sign — clipped call signs are how another aircraft's clearance becomes yours, and the AC flags similar call signs on frequency as a specific hazard
• LUAW is not a takeoff clearance: expect ATC communication within 90 seconds or query, keep TCAS on, and monitor for traffic on your runway (AC 120-74, developed in Task II.C)
• Confirm the runway physically: the verbal coordination gate — runway identification and compass heading against the clearance — happens as you take the runway (AC 120-74), the last defense against a wrong-surface departure
• Landing lights on when takeoff clearance is received — the lighting signal that tells everyone else you're rolling (AC 120-74)

The chain, assembled from 121.629:

1. Dispatch into icing at all rides on the judgment of the PIC or aircraft dispatcher that expected icing won't adversely affect safety (121.629(a))
2. Conditions that could produce adherence trigger the carrier's approved ground deicing/anti-icing program — which defines who decides procedures are in effect, each group's duties, and the fluid types and procedures in use (121.629(c)(1))
3. Fluid application starts the holdover clock at the final application's commencement (121.629(c)(3))
4. Inside the holdover time, a pretakeoff check of the wings or representative surfaces confirms the fluid is holding; beyond it, the three options apply — contamination check, approved alternate procedure, or redeice with a new holdover time (121.629(c)(3)–(4))
5. The takeoff itself must satisfy the clean aircraft concept — nothing adhering to wings, control surfaces, propellers, engine inlets, or other critical surfaces (121.629(b))

Crew training on all of this — holdover use, fluid characteristics, contamination recognition, communications — is a required element of the program itself (121.629(c)(2)), which is why the examiner can expect fluent answers rather than a shrug toward the ground crew.

• Contaminated or slick runway: shifts the accelerate-stop problem — the reduced-V1 logic and the degraded-stopping-factor list (AFH ch. 16) become today's numbers, not trivia
• Gusting crosswinds: in strong, gusty wind it is advisable to carry an extra margin of speed before the airplane is allowed to leave the ground (AFH ch. 6) — in transport practice, applied per your AFM/operator gust-additive policy, and briefed with the crosswind technique for the roll
• Windshear: the ACS names it in the briefing element (AA.II.E.S5) — the planned response is stated before takeoff, and the escape maneuver belongs to your operator's procedures
• Low visibility: ties the takeoff clearance to the taxi problem — SMGCS routes and the verification gate against a wrong-surface line-up (Task II.C)

The common thread: every one of these changes either the data, the brief, or both. Weather that changes nothing you compute or say out loud hasn't been assessed yet.

• Climb airspeed/V-speed ±5 knots for each climb segment (AA.III.A.S13)
• Desired heading ±5° (AA.III.A.S14)

Around those two numbers sits the crew dimension the lower certificates never graded:

• Coordinate with the crew and complete the appropriate checklists prior to takeoff in a timely manner (AA.III.A.S1)
• Confirm takeoff power and proper engine and flight instrument indications prior to rotation, making callouts per the airplane or the operator's procedures (AA.III.A.S10)
• Retract gear and flaps in accordance with manufacturer or operator procedures and limitations (AA.III.A.S15)

The examiner is watching a crew procedure, not a stick-and-rudder maneuver.

From AFH ch. 16:

• VS — stalling speed or minimum steady flight speed at which the airplane is controllable
• VEF — the speed used during certification at which the critical engine is assumed to fail
• V1 — critical engine failure speed or takeoff decision speed: at speeds less than V1 it is considered safer to stop within the accelerate-stop distance; it is also the minimum speed, following a failure of the critical engine at VEF, at which the takeoff can be continued and the required height reached within the takeoff distance
• VR — rotation speed; cannot be less than V1 or less than 1.05 × VMC, and on an engine-out takeoff allows acceleration to V2 at the 35-foot height
• VLOF — lift-off speed, the engineering term for when the airplane first becomes airborne
• V2 — takeoff safety speed: the referenced airspeed obtained after lift-off at which the required one-engine-inoperative climb performance can be achieved

The actual numbers are weight- and type-specific — they come from your AFM data, never from memory.

Every applicant must brief before each takeoff. If the operator or manufacturer hasn't specified one, ACS Appendix 3 requires the briefing to cover the items appropriate to the conditions:

• Departure runway and departure procedure
• Power settings and speeds
• Abnormal or emergency procedures prior to or after reaching decision speed (V1 or VMC)
• Emergency return intentions
• Go-around/rejected landing procedures and initial rate of descent (for the landing briefing)
• What is expected of the other crewmembers during the takeoff and landing

If the first briefing is satisfactory, the evaluator may allow you to brief only the changes for the rest of the test. Single-pilot applicants must verbalize the briefings — silence is not an option.

Per AFH ch. 16:

• Pilot flying — concentrates on directional control, keeps the airplane exactly on centerline with wings level, holds slight forward pressure to keep the nose-wheel rolling firmly, monitors nose-wheel steering to about 80 knots (or VMCG), and keeps the other hand on the thrust levers until at least V1
• Pilot monitoring (not flying) — makes the final engine power adjustments (takeoff thrust set prior to reaching 60 knots), holds forward column pressure once the PF's hand comes up to the wheel, closely monitors aircraft systems, and calls out the V-speeds as directed in the captain's briefing

Although the PM watches the engine instruments throughout, the pilot flying (pilot in command) makes the decision to continue or reject — and a reject decision requires immediate retarding of the thrust levers.

Takeoff data — V1/VR and V2 speeds, takeoff power settings, and required field length — must be computed prior to each takeoff, based on:

• Airplane weight
• Runway length available and gradient
• Field temperature and barometric pressure
• Wind and icing conditions
• Runway condition

Without an FMS the data goes on a takeoff data card; with one, both pilots review the FMS entries or separately compute and cross-check against the card. If takeoff plans change while taxiing — new runway, new intersection — the crew recalculates (AFH ch. 16). This is the practical backbone of AA.III.A.R1: runway selection against aircraft limitations, available distance, surface conditions, and wind.

At VR the pilot monitoring makes the callout and the pilot flying rotates smoothly but deliberately at a constant rate — approximately 2.5° to 3° per second — to the airplane's specific takeoff pitch attitude, normally between 10° and 15° nose up, which stays constant regardless of weight. The objective is to accelerate through VLOF and attain V2 at 35 feet AGL (AFH ch. 16).

• Early or fast rotation extends the takeoff roll or produces an early lift-off, a lower climb rate, and divergence from the predicted flightpath
• Late rotation lengthens the roll, overshoots V2, and puts the takeoff and climb path below the predicted path — critical when runway or obstacle clearance is limited, and on some airplanes the achieved flightpath can fall below the engine-out scheduled flightpath

• Landing gear — retract after a positive rate of climb has been established and confirmed (AA.III.A.S15). Beware: the VSI and altimeter may not show a positive climb until 35 to 50 feet above the runway due to ground effect, and gear-door transit can temporarily add drag
• Flaps — not until passing obstruction clearance altitude or 400 feet AGL; hold the climb pitch attitude and let ground effect plus gear-drag reduction accelerate the airplane to flap retraction speed
• Trim — trim out longitudinal stick forces as a steady climb develops; if reducing power, reduce pitch simultaneously as needed
• Speed — limited to 250 KIAS below 10,000 feet MSL (91.117(a)); above that, climb at the AFM's best rate speed

(AFH ch. 16.) The Task closes with the after-takeoff checklist completed in a timely manner (AA.III.A.S18).

Position the flight controls for the existing wind (AA.III.A.S5): during the roll, keep the wings level by displacing the control wheel into the crosswind — there is no torque-produced yaw to fight in a jet, which makes centerline control somewhat easier and automatically positions you well for an engine failure (AFH ch. 16). Know two test-specific facts:

• If no crosswind exists on test day, your crosswind knowledge is evaluated orally (Task note)
• In a full flight simulator, the evaluator sets a crosswind component between 10 and 15 knots, with discretion to go higher — but never above the operator's or AFM's demonstrated maximum (ACS Appendix 3)

ACS Appendix 3 defines it: a normal takeoff begins from a standing or rolling start — not from a touch-and-go — with all engines operating normally during the takeoff and initial climb phase. Area III as a whole requires at least three actual landings, at least one to a full stop, and the evaluator may combine landing Tasks with those in the Instrument Procedures and Emergency Operations Areas of Operation.

Verify the assigned/correct runway (AA.III.A.S3) with more than the sign at the hold-short line: before beginning the takeoff roll, ensure the runway numbers agree with the magnetic compass and heading indicators (AFH takeoff checks), and confirm the runway and position match expectations before aligning on centerline (AFH ch. 16). The takeoff briefing itself should include visual verification of the correct surface and direction to preclude a wrong-surface departure (AFH ch. 2). Wrong-surface events are the departure-side twin of the SAFO 17010 landing problem covered under Task III.B.

From PHAK ch. 14:

• Runway holding position markings — four yellow lines, two solid, two dashed; stop before the solid pair and never cross without a clearance
• Displaced threshold — the portion of runway behind it is available for takeoffs in either direction, or landings from the opposite direction; displacement only reduces the length available for landing
• Runway distance remaining signs — black background, white numeral, runway remaining in thousands of feet; the natural cross-check for the reject decision
• Lighting — runway edge lights are white (amber over the last 2,000 feet or half the runway, whichever is less, on instrument runways) with red end lights; runway centerline lights run white, alternate red and white for the next 2,000 feet, and turn all red for the last 1,000 feet

• Static: when runway length is limited, hold the brakes while the thrust levers come up to the AFM-specified setting, let the engines stabilize, and check the engine instruments before brake release — this assures symmetrical thrust and prevents overshooting the target setting. After release, set the pre-computed takeoff power
• Rolling: with sufficient runway, advance the thrust levers smoothly to the recommended intermediate setting as the airplane rolls onto the runway, let the engines stabilize, then proceed as in the static procedure; a rolling takeoff can also be made from the runway end by advancing thrust from idle as the brakes release

(AFH ch. 16.) Either way, takeoff thrust adjustments are complete prior to 60 knots, and a thrust lever comes back only if an engine exceeds a limitation.

The pilot flying keeps a hand on the thrust levers until V1 because that is the last point at which the reject option remains available: the PF (pilot in command) owns the continue/reject decision, and a reject requires immediate retarding of thrust. After V1, keeping a hand on the levers is no longer mandatory — the point for abort has passed — and both hands go to the control wheel for rotation (AFH ch. 16). Moving the hand is a deliberate signal, to yourself and the other pilot, that the airplane is now committed to fly. The decision logic itself is Task III.I's territory.

The takeoff and climb-out should be accomplished in accordance with a standard takeoff and departure profile developed for the particular make and model (AFH ch. 16) — a published picture of when rotation happens, when gear and flaps come up, what speed each climb segment is flown at, and where power changes occur. It is what makes AA.III.A.S13's "±5 knots for each climb segment" testable: each segment has a briefed target speed from the AFM or operator profile, and you fly it. Noise abatement procedures are folded in as practicable (AA.III.A.S17).

Increasing pitch slightly increases climb rate as airspeed bleeds off — down to L/DMAX, which is best angle-of-climb speed, where the rate of climb is actually less than it was at best rate speed. Trading airspeed for altitude beyond that is a zoom climb: an increased rate for a few thousand feet that ultimately reduces overall climb performance (AFH ch. 16). Comply with the request, but know where the energy is coming from.

Wingtip vortices are strongest when the generating aircraft is heavy, clean, and slow — exactly the departure case. From PHAK ch. 5:

• Rotate prior to the point at which the preceding aircraft rotated
• Avoid following another aircraft on a similar flight path within 1,000 feet vertically
• Vortices drift with the wind — a 10-knot wind moves them about 1,000 feet per minute, so factor wind into your lift-off point and initial track
• If unsure where the preceding aircraft rotated or touched down, approximately 3 minutes provides a margin

At ATP weight you are often the generator — but behind a heavier type, the geometry problem is yours to solve before brake release, as part of the briefing.

• Recommended approach and landing configuration and airspeed ±5 knots, adjusting pitch and power to maintain a stabilized approach (AA.III.B.S7)
• Touch down with the runway centerline between the main landing gear at the appropriate speed and pitch attitude, at the runway aiming point markings −250/+500 feet — or, where there are no runway markings, 750 to 1,500 feet from the approach threshold (AA.III.B.S10)
• Seaplanes: contact the water at the proper pitch attitude within 200 feet beyond a specified point; for AMES, touchdown must also be within the first one-third of the water landing area (AA.III.B.S11, ASES/AMES)
• Decelerate to taxi speed — 20 knots or less on dry pavement, 10 knots or less on contaminated pavement — within the calculated landing distance plus 25% for the actual conditions, centerline still between the main gear, on at least one landing (AA.III.B.S12)
• Use spoilers, prop reverse, thrust reverse, wheel brakes, and other drag/braking devices as appropriate; at least one landing to a full stop (AA.III.B.S13)
• Execute a timely go-around if the approach cannot be made within these tolerances or for any other unsafe condition (AA.III.B.S14)

From ACS Appendix 3: at least three actual landings, at least one to a full stop; the evaluator may combine landing Tasks with those in the Instrument Procedures and Emergency Operations Areas of Operation.

• Crosswind: the evaluator should test at least one required landing while you manually control the airplane in a crosswind — though in an airplane they may have no option but the crosswind that exists on the active runway. In a full flight simulator the crosswind component is set between 10 and 15 knots, with evaluator discretion to go higher — but never above the operator's aircraft operating manual limit or the AFM's maximum demonstrated value
• Briefing: precedes every takeoff and landing; after one satisfactory briefing, you may brief only the changes

From AFH ch. 16:

• Landing configuration by 1,000 feet AGL — gear down, landing flaps selected, trim set, fuel balanced
• On profile before descending below 1,000 feet — configuration, trim, speed, and glidepath at or near optimum, with an optimum glidepath angle of about 3°
• Indicated airspeed between zero and 10 knots above target by 500 feet AGL
• Descent rate matched to ground speed — rule of thumb: half the ground speed × 10 (130 knots GS → 650 fpm); typical rates fall between 500 and 700 fpm, and an excessive vertical speed flags a problem

Every approach is evaluated at 500 feet — about one minute from touchdown in a typical jet. Not stabilized there? Go around.

AFH ch. 16 lists the reasons jets are less forgiving than propeller airplanes:

• No propeller slipstream to produce instant extra lift or lower the power-on stall speed — you cannot salvage a misjudged glidepath with a burst of power, and there's virtually no difference between power-on and power-off stall speed
• Slow engine response at low rpm — the approach must be flown at a stable speed and power setting so thrust is available quickly
• Greater weight and momentum — speed and course corrections take more force and more time
• Little tendency to re-acquire the original speed after a deviation
• Drag increases faster than lift at low speed: a developing sink rate demands a pitch increase that rapidly deepens the sink unless significant power comes in promptly

The AFM performance data assumes an exact 50-foot threshold crossing at exactly 1.3 VSO and touchdown in a zone about 1,000 feet down the runway — the stabilized approach is what delivers the airplane to that window.

From AFH ch. 16:

• VSO — stall speed in the landing configuration
• VREF — 1.3 × VSO, the final approach reference (airplanes certified under the current part 25 standard schedule VREF at not less than 1.23 VSR, the reference stall speed — 25.125(b)(2) — which is what a modern AFM will show)
• Approach climb — the speed that guarantees adequate go-around performance with an inoperative engine
• Landing climb — the speed that guarantees the descent can be arrested and a go-around made from the final stages of landing, in full landing configuration, with maximum takeoff power on all engines

Speeds are calculated for every landing and posted where both pilots can see them. Never let airspeed decay below VREF — a high sink rate can develop. Type-specific values come from your AFM.

AFH ch. 16 gives the arithmetic:

• Excess approach speed carried through the threshold adds 20–30 feet per knot of minimum stopping distance on a dry runway, 40–50 feet per knot on a wet one
• Excess speed also invites an extended flare, adding roughly 250 feet per excess knot to the touchdown point
• An extra 50 feet of height over the threshold adds approximately 1,000 feet to landing distance
• A flat approach costs too: 2° instead of 3° adds about 500 feet

These numbers are why the ATP standard grades your touchdown against the aiming point at −250/+500 feet — drift outside it and the certified stopping numbers no longer describe your landing.

A jet should be flown onto the runway rather than held off — it is aerodynamically clean even in landing configuration and the engines produce residual thrust at idle, so holding off greatly increases landing distance. A firm landing is normal and desirable (deliberate and positive, not hard).

Typical geometry (AFH ch. 16):

1. Gear crosses the threshold 30–45 feet up
2. 5–7 seconds from threshold to touchdown
3. Flare initiated at roughly 15 feet, with a pitch increase of only 1° to 3°, reducing sink to 100–200 fpm
4. Thrust smoothly to idle as the flare progresses

Fly it to the target touchdown point even if speed is excessive — the extended flare is the classic overrun setup and can end in a tail strike.

Wheel brakes, reverse thrust, and aerodynamic drag (AFH ch. 16). Sequencing:

1. Lower the nose-wheel immediately — landing distance charts assume it is down within 4 seconds of touchdown; it reduces AOA and lift, loads the tires, and aids directional control
2. Spoilers immediately — most effective at high speed; they dump lift, load the wheels, and make maximum tire braking force available
3. Brakes — the most effective and most important stopping force for most landings; begin as soon after touchdown and wheel spin-up as possible
4. Reversers quickly, but no significant reverse until the nose-wheel is on the ground — asymmetric deployment demands nose-wheel steering authority; reverse and aerodynamic drag dominate only at high speed and on very slippery runways

Remember directional control and braking share the same tire-ground friction — increasing either subtracts from the other.

No regulation requires it, but the FAA encourages all operators (parts 121, 125, 135, 91) to assess landing distance at time of arrival — around top of descent, when current weather and field conditions are in hand, and no later than commencing the approach. It was born of the TALPA Aviation Rulemaking Committee after the December 2005 737 overrun at Chicago Midway, implemented October 1, 2016. Key pieces:

• Airports report conditions via the Runway Condition Assessment Matrix (RCAM) and Runway Condition Codes; friction measuring values are no longer used because they don't correlate reliably with airplane braking performance
• Pilot braking action reports run Good, Good to Medium, Medium, Medium to Poor, Poor, Nil — and their reliability depends on aircraft similarity and time since the report
• Time-of-arrival data (or the SAFO's Landing Distance Factors applied to unfactored AFM distance) includes a 15 percent safety margin
• Preflight wet/slippery dispatch data (121.195, 135.385, 91.1037) may not provide adequate runway for actual wet or contaminated conditions at arrival

Land and hold short operations support simultaneous operations on intersecting runways. From PHAK ch. 14:

• Know the landing distance available to the hold-short point and the signs/markings there
• Advise ATC if you cannot comply — accepting means you either exit before the intersecting runway or stop at the holding position
• LAHSO is generally not authorized at night, and not authorized on wet runways
• At many airports, air carrier aircraft are not authorized to participate when the other aircraft is general aviation

The ATP-specific trap is the go-around after acceptance — that scenario belongs to Task III.J.

SAFO 17010 asks two things of you on every visual approach:

• Fly a stabilized approach — an unstable approach consumes both pilots' attention and starves situational awareness
• Back up visual approaches with technology: tune a published approach (ILS, LOC, VOR, RNAV) to the assigned runway to verify alignment

It followed the July 2017 San Francisco incident: an airliner cleared for Runway 28R at night lined up on Taxiway C — with four airliners holding on it — and began a go-around while directly over them. This is the modern content of AA.III.B.S4 (ensure alignment with the correct/assigned runway) and the "incorrect airport surface approach" risk element.

14 CFR 25.125 defines it: the horizontal distance to land and come to a complete stop from a point 50 feet above the landing surface. Manufacturers determine it on a dry, level runway at standard temperatures, with speed brakes deployed and maximum wheel braking — and without thrust reversers, autobrakes, or auto-land (AFH ch. 16; SAFO 19001 adds that the unfactored AFM distance may reflect aggressive flight-test air distances). So the book number assumes a stop you will rarely fly on the line — which is exactly why arrival-time assessments and safety margins exist. Reversers should absolutely still be used when available; they are margin, not credit.

As an accepted safety practice from AFH ch. 16: divide the usable runway length by 1.67 — the result should equal or exceed the AFM-calculated landing distance for a dry runway. For a wet runway, increase the required distance by an additional 15% (equivalently, divide the runway by 1.92). Put the other way around: minimum dry field length is at least 1.4 times the calculated air-and-ground distance, and wet field length at least 1.61 times. Careful planning may mean limiting payload or fuel to protect the margin at the destination.

• Crab — a coordinated heading change into the wind that keeps the wings-level ground track on the extended centerline; the crab must be removed just prior to touchdown with rudder to align the longitudinal axis, or the gear takes side loads (AFH ch. 9)
• Wing-low (sideslip) — upwind wing lowered, opposite rudder holding the axis on centerline; touchdown occurs on the upwind main gear first, then the downwind main, then the nose, with aileron into the wind increasing toward full deflection in the rollout
• In multiengine airplanes the two are typically used in conjunction — crab down final, transition to the sideslip prior to touchdown (AFH ch. 13)
• Speed: adjust the approach for wind and gusts with VREF plus an additive (e.g., VREF+5) per your operator or AFM (AFH ch. 13) — and never below VREF

From PHAK ch. 5: when landing behind another aircraft, approach above the preceding aircraft's path and touch down beyond the point where its wheels contacted the runway. Vortices are strongest when the generator is heavy, clean, and slow, sink below the flight path, and drift with the wind — about 1,000 feet per minute in a 10-knot wind, which can push a departed aircraft's vortices onto a parallel runway or hold them over your touchdown zone. If the other aircraft's touchdown point is uncertain, roughly 3 minutes of spacing provides a margin. Fold the geometry into the approach briefing, not the flare.

When the approach cannot be completed within the tolerances of this Task — configuration and speed ±5 knots on a stabilized path to a touchdown inside −250/+500 feet of the aiming point — or when any other condition would make the approach or landing unsafe. The evaluation gate is the AFH's 500-foot check: stabilized there or go around. The maneuver itself, its callouts, and the LAHSO complication are Task III.J; what this Task grades is that the decision is timely — made at the trigger, not after the float has eaten your touchdown zone.

Three markings/lighting items your standards are literally written against:

• Runway aiming point markings — anchor the −250/+500-foot touchdown window; where markings are absent, the 750-to-1,500-foot band from the threshold applies instead (AA.III.B.S10)
• Displaced threshold — the portion of runway behind it is available for takeoffs in either direction, or landings from the opposite direction; displacement reduces the length available for your landing (PHAK ch. 14)
• Touchdown zone lights — two rows of transverse light bars disposed symmetrically about the centerline in the touchdown zone, giving you the same aiming reference at night that the painted markings give you by day (AFH glossary)

Tie each one back to the standard: they exist so the crew can put the mains down where the performance data assumes.

Glassy water works against me in two ways (FAA-H-8083-23 ch. 4):

Increased drag: the smooth surface can feel like suction between the water and the floats, maintaining a continuous drag force that can prevent accelerating the last few knots to lift-off speed. A little surface roughness actually helps break the contact by introducing turbulence and air bubbles under the float bottoms.

No height cues once airborne: the lack of visual cues to height above the water is dangerous unless a positive rate of climb is maintained — I can fly back into the water without ever seeing it coming.

Identical to a normal takeoff until the seaplane is on the step and nearly at flying speed (FAA-H-8083-23 ch. 4). Then, to break the water's grip:

• Apply enough aileron to lift one float just out of the water, and let the airplane continue accelerating on the step of the other float until lift-off
• Allow the seaplane to turn slightly in the direction the aileron is held rather than holding opposite rudder — this eliminates considerable aerodynamic drag
• Don't lift the wing so far that the opposite wing contacts the water
• After lift-off, establish a positive rate of climb to prevent inadvertently flying back into the surface

I rock the seaplane onto the step with timed elevator pressure, if conditions aren't excessive (FAA-H-8083-23 ch. 4):

1. From the highest nose-up point of the plow, with full back elevator, decrease back pressure — the nose drops if the seaplane is on the verge of the step.
2. When the nose starts back up, reinforce the rise with firm back pressure, and repeat.
3. After several cycles the nose rides higher and speed builds; then push the elevator well forward and hold it — the seaplane flattens onto the step, and the controls ease back to neutral.

Why it happens: at maximum weight the floats sink deeper, wetting more surface and adding water drag, so the seaplane may sit in a plowing position without developing enough hydrodynamic lift for the step. The careful pilot always plans for aborting the takeoff (AA.III.C.R2a).

I brief the plan before power comes in — like the abort point, it can't be worked out after the failure:

• Where the usable water ahead is, and what shoreline features could substitute as height references — the ch. 6 illusion mitigations
• That a positive rate of climb is confirmed before anything else — without it I can fly back into an invisible surface (ch. 4)

Glassy water makes that plan uniquely demanding: the handbook's glassy landing technique is flown with power — touchdown attitude, no more than 150 fpm of descent, about 10 knots above stall (FAA-H-8083-23 ch. 6) — and a failed engine takes that option away over a surface with no height cues. That is why the ACS pairs the abort plan with planning for engine failure in the takeoff/climb phase.

Roughen it yourself: taxi around in a circle so your wake spreads and reflects from shorelines, creating a slightly rougher surface that both helps the floats break free during takeoff and provides some visual depth (FAA-H-8083-23 ch. 4).

Beyond the standard crew/checklist/radio items (AA.III.C.S1, S2):

• Water rudders: retracted (S6)
• Power: set and confirm takeoff power (S7), avoiding excessive water spray on the propellers (S8)
• Directional control and attitude: maintain an appropriate planing attitude, correcting for porpoising, skipping, and increases in water drag (S9, S10)
• Lift-off: use appropriate technique considering surface conditions (S11)
• Climb: adjust power and pitch to hold the appropriate climb airspeed/V-speed ±5 knots for each climb segment (S12)
• Flaps: retract after a positive rate of climb is verified, or per manufacturer/operator procedures (S13)
• Noise abatement: as practicable (S14)

Gear position. An amphibious airplane taking off from water must have the wheels retracted — the ACS carries "gear position in an amphibious airplane" as a standing risk element across every seaplane takeoff and landing Task, and the takeoff configuration verification (AA.III.C.S4) is where you prove it. Make gear position an explicit checklist response and callout, not an assumption, every time the surface changes between pavement and water.

It removes your height perception — the lack of surface features makes depth perception very difficult even for experienced seaplane pilots. The mirror surface reproduces clouds and shore features in convincing detail, and in crystal-clear water the surface itself is invisible — pilots may inadvertently judge height off the bottom of the lake (FAA-H-8083-23 ch. 6). The consequences of misjudging: flare too high and stall — the seaplane pitches down, hits on the float bows, and can flip; flare too late or not at all — it flies into the water at speed, drives the bows under, and flips. There's also a physical effect: the smooth surface increases wetted drag at touchdown, tugging the nose down — easily controlled with back pressure if you expect it.

When visual references are inadequate, land on instruments-and-attitude, not judgment of height (FAA-H-8083-23 ch. 6):

1. Perform a normal approach but prepare as though intending to land well above the surface — for example, around 200 feet above it when no current altimeter setting is available
2. At that target altitude, raise the nose to the touchdown attitude and set power for a descent of no more than 150 fpm at approximately 10 knots above stall speed
3. Maintain that attitude, airspeed, and descent rate all the way to the water — do not flare; change power only if airspeed or descent rate deviates
4. Always perform glassy water landings with power

The long shallow glide consumes considerable distance — be certain there's room for the glide, touchdown, and water run.

At contact, apply gentle back pressure to hold the same pitch attitude. Close the throttle only after the seaplane is firmly on the water, verified through three senses: you see a slight nose-down pitch (and perhaps spray), hear the water against the floats, and feel the deceleration (FAA-H-8083-23 ch. 6). The accident case the handbook cites: a skip occurs, the pilot chops power — and the seaplane is actually 10 to 15 feet in the air, stalling onto the surface. After settling into a displacement taxi, complete the after-landing checklist and lower the water rudders.

Two techniques restore a real height reference (FAA-H-8083-23 ch. 6): land near the shoreline, using shore features to gauge altitude, after first inspecting from a safe altitude that the water is deep enough and free of obstructions; or make the final approach over land, crossing the shoreline at the lowest safe altitude so a reliable height reference carries to within a few feet of the surface. An accurately set altimeter can also let you start the stabilized 150-fpm descent closer to the surface, shortening the total landing distance.

The ACS grades seven skill elements for this Task (AA.III.D.S3–S9):

• Ensure the landing gear and water rudders are retracted as applicable (S3)
• Select the approach and landing path considering the landing surface, visual attitude references, water depth, and collision hazards (S4)
• Establish the recommended configuration, airspeed, and trim (S5)
• Maintain a stabilized approach and recommended airspeed ±5 knots (S6)
• Make smooth, timely power and control adjustments to hold pitch attitude and rate of descent to touchdown (S7)
• Maintain directional control throughout (S8)
• Contact the water in a proper pitch attitude, slowing to idle taxi speed (S9)

Because glassy conditions and clear water go together: when the surface is invisible, the lake bottom becomes both a false height reference and a real hazard. The handbook's shoreline-landing technique carries the same caveat — be certain the water is sufficiently deep and free of obstructions by inspecting from a safe altitude first (FAA-H-8083-23 ch. 6). A stabilized 150-fpm descent to touchdown assumes the touchdown zone is actually water you can use, and shallow areas or submerged obstructions are found before the approach, never during it.

Same discipline as every water landing: whenever landing conditions are not satisfactory — conflicts with aircraft, vessels, or swimmers, hazards on the water, an unstabilized approach — execute a go-around, climb to a safe altitude while running the go-around checklist, evaluate, and re-approach (FAA-H-8083-23 ch. 6). On glassy water specifically, honor the profile: if the stabilized attitude/descent-rate combination is broken low over an invisible surface, the safe move is power and climb, not salvage. The full maneuver is Task III.J.

The objective matches a rough- or soft-field takeoff in a landplane (FAA-H-8083-23 ch. 4):

1. Transfer the weight to the wings as soon as possible
2. Get airborne at minimum airspeed
3. Accelerate in ground effect to a safe climb speed
4. Climb out

The ACS grades that same profile: establish the proper attitude and airspeed, then lift off at minimum airspeed and accelerate to the appropriate climb airspeed/V-speed ±5 knots before leaving ground effect (AA.III.E.S11). One mercy of physics: wind strong enough to roughen the water also produces aerodynamic lift earlier, so the run is usually short.

From FAA-H-8083-23 ch. 4:

• Open the throttle to takeoff power just as the floats begin rising on a wave — this keeps the float bows from digging in and helps keep spray away from the propeller (AA.III.E.S8)
• Hold a little more back elevator pressure than on smooth water, raising the nose to keep the bows clear
• Once on the step, the seaplane can bounce crest to crest, nose rising with each bounce so each successive wave hits harder — counter with smooth elevator pressure toward a fairly constant pitch attitude that lets the seaplane skim across the wave tops as speed builds
• Maintain control pressure to keep the bows from being pushed under and to keep the airplane from being thrown into the air at a high pitch angle and low airspeed (stall prevention, AA.III.E.R4)

Two go/no-go rules from FAA-H-8083-23 ch. 4:

• Wavelength versus float length: if the wavelength is less than half the float length, at least two waves support the seaplane at all times; if the wavelength is longer than the floats, only one wave supports it — creating dangerous pitching motions, and takeoff should not be attempted
• Wave height: as a general rule, if waves measure more than half the height of the floats from keel to deck (trough to crest), takeoffs should not be attempted except by expert seaplane pilots

The overall decision weighs seaplane size, wing loading, power loading, and — most importantly — pilot ability.

The waves respond to the relative velocity between water and wind. A 10-knot current flowing against a 15-knot wind gives a relative velocity of 25 knots — waves as high as a 25-knot wind would raise on still water (FAA-H-8083-23 ch. 4). Read the water, not just the windsock, when deciding whether the surface is takeoff-able and which direction to run.

Retract the flaps only after a positive rate of climb is established and a safe altitude has been achieved (AA.III.E.S12), then maintain takeoff power to a safe maneuvering altitude before setting climb power (S13). This follows liftoff at minimum airspeed and acceleration in ground effect to climb speed ±5 knots (S11) — the rough-water profile deliberately keeps energy and lift margin in hand longer than a normal takeoff. Directional control and wind-drift correction are graded throughout (S9), along with planing attitude and correction for porpoising and skipping (S10).

• Takeoff path selection against aircraft limitations, available distance, surface conditions, and wind — including the wavelength and wave-height rules above
• Abnormal operations planning: the rejected takeoff (where on the run you can still close the throttle and stop in the water remaining) and a potential engine failure in the takeoff/climb phase — briefed before power comes in, exactly as Task III.I demands on a runway
• Gear position in an amphibian — wheels up for water, verified as part of the takeoff configuration (S4)

Because "rough" is subjective and relative: water that troubles small boats may be fine for a large seaplane, and conditions harmless to an experienced pilot in a big hull can be dangerous to a smaller seaplane or newer pilot. Too many variables affect the surface — wind direction and speed weighed against the water's condition — for one ideal profile (FAA-H-8083-23 ch. 6). In most instances the approach itself is flown the same as any other water landing; what changes is the touchdown attitude, the power management, and the standing readiness to go around (AA.III.F.S9).

• Touch down at a somewhat flatter pitch attitude than usual — this prevents the seaplane being tossed back into the air at dangerously low airspeed, and helps the floats slice through the wave tops rather than slamming against them
• Reduce power as the seaplane settles into the water
• Apply back pressure as it comes off the step to keep the float bows from digging into a wave face

(FAA-H-8083-23 ch. 6.) The ACS grades exactly this: contact the water at the correct pitch attitude and touchdown speed (AA.III.F.S8), with smooth, timely power and control application during the landing (S9), and positive after-landing control (S10).

Be ready with full power to go around (FAA-H-8083-23 ch. 6). The skill element writes the mindset into the standard: remain alert for a go-around should conditions be too rough (AA.III.F.S9) — the go-around option stays armed through the entire water run, not just the approach. One intermediate option when the surface looks marginal: level off just above the water with enough power to hold a rather flat attitude, wait until conditions appear more acceptable, then reduce power to touch down; if severe bounces occur after touchdown, add power and lift off to find a smoother spot.

• Downwind: rough water usually means strong wind, and wind velocity added to normal landing speed produces a much higher groundspeed — excessive stress on the floats, increased nose-down tendency at touchdown, and a prolonged water run (more kinetic energy to dissipate). As the seaplane slows, weathervaning plus wave motion creates an unstable situation. Upwind means lower touchdown speed, shorter run, less pounding
• Crosswind: the pitching and rolling from the rough surface increases the likelihood of the wind lifting a wing and flipping the seaplane (FAA-H-8083-23 ch. 6)

Wind-correction technique remains a graded knowledge element (AA.III.F.K3), and the airspeed standard carries a gust factor applied, ±5 knots (AA.III.F.S6).

• Ensure landing gear and water rudders are retracted as applicable (AA.III.F.S3 — gear position in an amphibian is the standing risk, R6)
• Select the approach and landing path considering the landing surface, visual attitude references, water depth, and collision hazards (S4)
• Establish the recommended configuration, airspeed, and trim on a stabilized approach (S5)
• Hold recommended airspeed with gust factor applied, ±5 knots (S6)
• Make smooth, timely, correct power and control adjustments to maintain proper attitude and rate of descent to touchdown (S7)

Apply the same limits that govern the rough water takeoff, because they bound what you can get back out of (and survive touching down on): waves more than half the float height from keel to deck are for expert pilots only, and a wavelength longer than the floats produces dangerous pitching (FAA-H-8083-23 ch. 4). Add the current-versus-wind effect — a 10-knot current against a 15-knot wind builds waves like a 25-knot wind on still water — and weigh seaplane size, wing loading, power loading, and your own ability. The approach-path selection element (AA.III.F.R1) is graded on exactly this assessment.

ACS Appendix 3 defines two required scenarios: a takeoff and spiral climb, and a straight-ahead takeoff and climb from a narrow waterway with obstructions at either end. The evaluator must assess both. In multiengine seaplanes or amphibians with VX within 5 knots of VMC, you and the evaluator may brief using VY or the manufacturer's recommendation if more appropriate for the demonstration.

• Rotate and lift off at the appropriate airspeed and accelerate to the recommended obstacle clearance airspeed or VX, using appropriate bank angles to maintain terrain clearance as needed (S11)
• Climb at the recommended airspeed — or absent one, VX, +5/−0 knots — until the obstacle is cleared or the airplane is 50 feet above the surface; where VX is within 5 knots of VMC in a multiengine airplane, VY or the manufacturer's recommendation is acceptable (S12)
• After clearing all obstacles, accelerate to VY ±5 knots (S13)
• Retract flaps and adjust power as needed to maintain VY or the appropriate climb airspeed ±5 knots to a safe maneuvering altitude (S14)

Begin the takeoff run headed downwind, then turn to complete the takeoff into the wind: put the seaplane on the step while downwind, then make a step turn into the wind to finish the takeoff (FAA-H-8083-23 ch. 4). Two cautions apply: during the turn, wind and centrifugal force act in the same direction and could tip the seaplane over, and the water area must permit a wide step turn with winds light enough to attempt it.

Because the same surrounding high terrain that confines the area also blocks the wind, producing a glassy surface — and when combined with high density altitude, conditions can turn dangerous even though the landing was easy (FAA-H-8083-23 ch. 4). Mitigations the handbook lists:

• If the departure path crosses high terrain, circle back over the water after takeoff to gain altitude
• If temperatures rose since landing, re-figure performance for the new density altitude — or wait for cooler morning air
• Consider leaving cargo or passengers behind and making a second trip rather than ending the takeoff in the trees

Density altitude hits a seaplane doubly: high, hot, and humid air robs the engine and propeller of thrust and the wings of lift while water drag still has to be overcome (FAA-H-8083-23 ch. 5).

The same discipline as Task III.I with the geometry tightened: before power comes in, know the point on the water beyond which you can no longer close the throttle and stop in the distance remaining — remembering that FAA-approved landplane thinking doesn't transfer cleanly, since water drag, waves, and current change the stopping picture. The handbook's standing advice applies: the careful seaplane pilot always plans ahead and considers the possibility of aborting the takeoff (FAA-H-8083-23 ch. 4), and the ACS pairs the reject with planning for a potential engine failure in the takeoff/climb phase (R2b) — in a confined area, that plan should include whether a climbing turn back over the water beats straight ahead into terrain.

The full stack from the normal water takeoff, under tighter geometry:

• Checklists and crew coordination in a timely manner (AA.III.G.S1)
• Radio calls (S2)
• Flight controls positioned for the wind (S3)
• Takeoff configuration verified, including gear up in an amphibian (S4, R6)
• Area cleared and takeoff path selected for surface conditions and collision hazards (S5)
• Water rudders retracted (S6)
• Takeoff power set and confirmed (S7)
• Spray kept off the propellers (S8)
• Directional control with wind-drift correction (S9)
• Planing attitude with porpoising/skipping corrections (S10)
• Noise abatement as practicable (S15)

This Task simulates two landing scenarios: an approach and landing to a small pond requiring a spiral approach, wings-level landing, and step turn upon landing; and a straight-ahead approach and landing to a narrow waterway with obstructions at either end. The evaluator must assess both landing situations (ACS Appendix 3).

Whether it is possible to get out again. For most seaplanes the takeoff run is much longer than the landing run, and the ACS carries the risk explicitly: "landing in an area or in conditions where a takeoff/climb may not be possible." Before touchdown, evaluate the wind and surface conditions expected at departure time — landing into a stiff breeze on small waves may mean waking up to calm, glassy water that won't release the floats — and the density altitude at departure, since a cool-morning landing can precede a hot-afternoon takeoff with a serious performance loss (FAA-H-8083-23 ch. 6).

The takeoff-side mitigations (circle climb over the water, wait for cooler air, offload) are Task III.G's material.

Carefully inspect the landing area from altitude for shallow areas, obstructions, and other hazards — after touchdown is not the time to discover the area is smaller or less usable than supposed. The evaluation must include approach and departure paths: terrain that rises faster than the seaplane can climb matters both for the eventual takeoff and for a go-around during the landing; if climbout over terrain isn't easily within the airplane's capability, be certain there's room for a gentle turn back over the water (FAA-H-8083-23 ch. 6). The skill element frames this as considering, in selecting the approach and landing path:

• The landing surface
• Visual attitude references
• Water depth
• Collision hazards

• Maintain a stabilized approach and recommended airspeed with gust factor applied, ±5 knots (AA.III.H.S6)
• Touch down smoothly at the recommended airspeed and pitch attitude, beyond and within 100 feet of a specified point/area (S8) — the tightest touchdown standard in Area III, because a confined area gives away nothing
• Maintain directional control and appropriate crosswind correction throughout the approach and landing (S9)

Supporting skills:

• Checklists and crew coordination (S1)
• Radio calls (S2)
• Gear and water rudders retracted as applicable (S3, with amphibian gear position as risk R6)
• Recommended configuration/airspeed/trim on a stabilized approach (S5)
• Smooth, timely power and control adjustments for attitude and descent rate to touchdown (S7)

The escape must be planned against the terrain before the approach begins. Whenever landing conditions are unsatisfactory, go around, climb to a safe altitude while executing the go-around checklist, and re-approach — but in a confined area, remember it is often best to make a gentle climbing turn back over the water rather than climbing toward a shoreline with rising terrain (FAA-H-8083-23 ch. 6). If the spiral-approach geometry of this Task was needed to get in, assume the go-around needs the same spiral thinking to get out — decided at the first sign the approach won't work, not at the trees.

Because the confined area removes the buffer that normally absorbs energy errors. A stabilized approach at the recommended airspeed plus gust factor is what makes a touchdown beyond and within 100 feet of a point achievable at all — excess speed floats the touchdown deep into a landing area that has no "deep," and a low-energy approach over an obstruction at the water's edge has no margin to arrest sink. The stabilized approach concepts are developed at transport depth under Task III.B; here they're applied at their least forgiving scale.

V1 is the speed selected for each takeoff, based on approved performance data and specified conditions. It represents:

1. The maximum speed by which a rejected takeoff assures a safe stop within the remaining runway or runway and stopway
2. The minimum speed which assures the takeoff can be safely completed within the remaining runway, or runway and clearway, after failure of the most critical engine at the designated speed
3. The single speed that permits either a successful stop or a continued takeoff when operating at the minimum allowable field length for a particular weight

The operational bite: the go/no-go decision is made before V1 so that deceleration can begin no later than V1. If braking has not begun by V1, the decision to continue has been made by default (AC 120-62, "Takeoff Safety Training Aid," quoted in AFH ch. 16).

Most manufacturers have operators identify a low-speed regime (80 knots and below) and a high-speed regime (100 knots and above) (AFH ch. 16):

• Low-speed regime: abort for any malfunction or abnormality, actual or suspected
• High-speed regime: reject only for catastrophic malfunctions or life-threatening situations — engine failure, fire or smoke, a takeoff warning system, loss of directional control — weighing the threat against the risk of an overrun

AA.III.I.K1 lists the classic triggers: takeoff warning systems, powerplant failure, other systems warnings or failures. AFH adds unsuspected equipment on the runway, bird strike, blown tires, ATC instruction, and significant abnormalities like split airspeed indications. Above the split, most of that list becomes a reason to continue and handle it airborne.

Although only about 2 percent of rejected takeoffs are high-speed, aborts above 120 knots account for the vast majority of RTO overrun accidents (AFH ch. 16). The physics behind it:

• Delaying the maneuver just one second beyond V1 adds 4 to 6 knots on average
• Crews require 3 to 7 seconds to identify an impending RTO and execute the maneuver
• Ill-advised reject decisions and improper technique together contribute to a majority of takeoff-related commercial aviation accidents worldwide

A brief moment of indecision is the difference between stopping on pavement and running off the end — which is why the decision architecture is briefed before brake release, not improvised at 130 knots.

The stopping sequence (AFH ch. 16):

1. Maximum braking immediately, simultaneously retarding the throttles
2. Spoiler extension
3. Thrust reverser deployment, following in short sequence

This is not normal after-landing braking; treating it like one is the documented failure mode. Brakes provide the most effective stopping force; delaying them when every second counts stretches the stopping distance. Cautions:

• Differential braking for directional control diminishes total braking effectiveness — tire friction is shared between stopping and steering
• A blown tire eliminates braking on that wheel and can cascade to adjacent tires

The ACS skill: promptly reduce power and maintain positive aircraft control, using drag and braking devices as appropriate, to come to a stop (AA.III.I.S3).

• Minimum V1 — the lowest permissible V1 from which the takeoff can still be safely completed after critical engine failure at the designated speed
• Maximum V1 — the highest V1 at which a reject can be initiated and the airplane stopped within the remaining runway or runway and stopway
• Reduced V1 — a V1 below maximum (or normal) V1 but above minimum V1, selected to shrink the required RTO stopping distance — used chiefly to offset degraded stopping capability on wet or contaminated runways, while buying roughly 2 seconds of recognition time for the crew (AC 120-62 terms, reproduced in AFH ch. 16)

FAA-approved takeoff data reflects performance demonstrated in ideal conditions — a clean, dry runway with maximum braking — and does not credit reverse thrust in computing stopping distance (AFH ch. 16). Real stopping performance can be degraded by, among others:

• Reduced runway friction and contaminants — rubber and oily residue, standing water, snow, slush, ice
• Wind direction and velocity, and low air density
• Flap and bleed configuration
• Underinflated or failing tires, deficient brakes or RTO autobrakes, inoperative anti-skid
• Penalizing MEL or CDL items
• Pilot technique and proficiency

This is why the runway selection risk element (AA.III.I.R1) is graded against limitations, available distance, surface conditions, and wind — the paper number is a ceiling, not a promise.

• ASEL/ASES: reject the takeoff if the powerplant failure occurs prior to becoming airborne (AA.III.I.S1) — there is no continue option
• AMEL/AMES: reject if the powerplant failure occurs at a point where the rejected takeoff procedure can be initiated and the airplane can be safely stopped on the remaining runway/waterway (AA.III.I.S2)

Test-day safety note from ACS Appendix 3: in a multiengine airplane, the simulated powerplant failure must be introduced before reaching 50 percent of VMC.

• Coordinate with the crew: complete the appropriate procedures, checklists, and radio calls in a timely manner (AA.III.I.S4)
• Treat it as an emergency: a rejected takeoff should be perceived as an emergency (AFH ch. 16)
• Keep priorities straight: the primary objective is not necessarily to stop in the shortest distance, but to maintain control of the airplane as it decelerates; in some situations it is preferable to continue into the overrun area under control rather than risk directional control loss, landing gear collapse, or tire/brake failure trying to stop short (AFH ch. 13)

SOPs should include a speed callout during the transition from the low-speed to the high-speed regime (AFH ch. 16). It does four jobs at once:

• Reminds both pilots the critical decision window is opening
• Provides a last opportunity to crosscheck instruments and verify airspeed
• Confirms adequate takeoff thrust is set
• Performs a pilot incapacitation check through the challenge-and-response ritual — a callout that goes unanswered is itself a reject trigger

Fly your operator's phrasing; the point is that the callout is a checklist item disguised as a number.

To keep the crew from trading a manageable airborne problem for an unnecessary high-speed reject: some manufacturers inhibit aural or visual malfunction warnings of non-critical equipment beyond a preset speed to prevent overreaction and a risky high-speed RTO when a safer option is to take the non-critical malfunction into the air (AFH ch. 16). Know your type's inhibit logic — it is part of the answer to "what would make you reject at 130 knots?" because the airplane has already filtered the list for you.

The pilot flying (pilot in command) makes the decision to continue or reject a takeoff for any reason, even though the pilot monitoring watches the engine instruments throughout the roll; a reject decision requires immediate retarding of the thrust levers (AFH ch. 16). But the decision criteria were fixed before brake release: the ACS-required takeoff briefing covers abnormal or emergency procedures prior to or after reaching decision speed (V1 or VMC) and what each crewmember does (ACS Appendix 3). On the roll you are not deciding what justifies a reject — you are pattern-matching against a briefed list, which is what makes a 1-to-2-second response physically possible.

Five measures stand out — useful when the examiner asks how operators manage this risk (AFH ch. 16):

• SOPs advancing the expanded V1 definitions, including progressive callouts marking the low-to-high-speed transition
• CRM training that sharpens recognition of emergency versus abnormal situations
• Crews carefully considering factors that compromise published performance data
• Expanded practical training in the proper use of brakes, throttles, spoilers, and reverse thrust during RTO demonstrations
• Manufacturers eliminating non-critical malfunction warnings during the roll at preset speeds

Task III.I is one of the load-bearing Tasks of the ACS, showing up across certificate actions (Appendix 1):

• An AMEL type rating tests Area III Tasks A, B, I, and J (sea classes test all of Area III)
• Removing a Second-in-Command Required limitation requires demonstrating single-pilot competency on Area III Tasks including Task I
• Center-thrust limitation removal requires Task III.I in a multiengine airplane with a published VMC

If your certificate action involves a multiengine airplane, plan on flying this maneuver.

Light twin: accelerate-stop distance is typically advisory data in the AFM/POH — it becomes a limitation only when published in the limitations section, and no regulation requires the runway to equal or exceed it. Experienced multiengine pilots still treat runway length of at least accelerate-stop distance as a matter of safety and good operating practice (AFH ch. 13).

Transport jet: the picture inverts — V1 exists precisely because the takeoff data ties decision speed, field length, and engine-out continuation together, and your operator's performance system enforces it on every takeoff (AFH ch. 16).

If your checkride is in a jet, answer from the V1 framework; if it is in a piston twin, know that the "balanced" guarantee may not exist in your AFM at all.

• Make a timely decision to go around or reject the landing (AA.III.J.S1)
• Apply the appropriate power setting for the flight condition and establish the pitch attitude for the desired performance (AA.III.J.S2)
• Establish a positive rate of climb and the appropriate airspeed/V-speed, ±5 knots (AA.III.J.S3)
• Configure and trim the airplane when appropriate (AA.III.J.S4)
• Make radio calls as appropriate (AA.III.J.S5)
• Maintain the ground track, heading, or course appropriate for the conditions, or as specified by ATC or the evaluator (AA.III.J.S6)
• Complete the appropriate procedures and checklists in a timely manner (AA.III.J.S7)

From ACS Appendix 3:

• Initiated at approximately 50 feet above the runway or landing area, approximately over the runway threshold — this is a rejected landing from the flare window, not a missed approach at minimums
• Instrument conditions need not be simulated below 100 feet above the runway
• Completion of this Task may count as one of the three required landings — and wheel contact with the runway is not required
• For a VFR-only type rating flown with a simulated engine failure, the failure is not initiated below the AFM/POH-recommended speeds or altitudes

The task references also include the FSB Report (type specific) — your type's Flight Standardization Board report can carry go-around training emphases that the examiner is entitled to probe.

Power, attitude, configuration — in that order (AFH ch. 9). The instant you decide, apply full or maximum allowable takeoff power smoothly and without hesitation; a settling airplane has inertia, and sufficient power is what stops the descent.

What changes in a jet: engine response at low rpm is slower, and there's no propeller slipstream to give instant lift at constant airspeed (AFH ch. 16) — so the power decision must come earlier, and the stabilized approach exists partly to keep the engines spooled so power is available quickly.

The ±5-knot climb speed and positive rate (AA.III.J.S3) are the graded output of getting the order right.

AFH ch. 9's list, which the ACS mirrors, plus the ACS's own addition:

• ATC requirements
• Unexpected hazards on the runway
• Overtaking another airplane
• Wind shear
• Wake turbulence
• Mechanical failure
• An unstable approach
• Inability to comply with a LAHSO clearance (the ACS's own addition)

The framing matters as much as the list: a go-around is a normal maneuver, to be practiced and perfected like any other. The assumption that an aborted landing means a botched approach "is a fallacy" — the ATP-level answer treats the go-around as a planned outcome, briefed before every landing (ACS Appendix 3 briefing items include go-around/rejected landing procedures).

AFH ch. 9 names the two sources:

1. Landing expectancy, or set — the anticipatory belief that conditions are not as threatening as they are and the approach will surely end in a safe landing
2. Pride — the mistaken belief that going around is an admission of failure

The maneuver is not inherently dangerous; it becomes dangerous only when delayed unduly or executed improperly, and the most critical go-around is the one started closest to the ground. That is precisely why the ATP test initiates it at 50 feet over the threshold — the examiner wants to see the decision made and flown at the worst point.

After power is in and the climb attitude established:

• Flaps first, partially — retract landing flaps to the takeoff position (or per the manufacturer), in increments if altitude and airspeed demand, because sudden full retraction can cost enough lift to settle the airplane onto the ground
• Gear after a positive rate of climb is established — and note the AFH's reasoning: full flaps usually make more drag than the gear, and if the airplane touches down during the go-around you want the gear down and locked
• Trim — the airplane was trimmed for approach speed; the sudden addition of power pitches the nose up, so anticipate considerable forward pressure, rough-trim once climbing, fine-trim when stable

(AFH ch. 9.) The pitch-up-with-power trap is the same out-of-trim mechanism developed in Task V.A's stall prevention material — at 50 feet it is unforgiving.

They are the certification guarantees behind the go-around (AFH ch. 16):

• Approach climb — the speed that guarantees adequate go-around performance with an inoperative engine (flown from the approach configuration)
• Landing climb — the speed that guarantees the descent can be arrested and a go-around made from the final stages of landing, in full landing configuration, with maximum takeoff power on all engines

When AA.III.J.S3 says "the appropriate airspeed/V-speed, ±5 knots," these — as scheduled in your AFM for weight and configuration — are what "appropriate" means. Density altitude and wind (AA.III.J.K2) shrink the real margins those guarantees describe, which is one more reason the decision must be timely rather than late-and-low.

Obligation: accepting "cleared to land, hold short" bound you to either exit before the intersecting runway or stop at the holding position — and to advise ATC if you cannot comply (PHAK ch. 14).

The rejected landing after acceptance is exactly why you must know the landing distance available and the LAHSO markings before accepting, and why the ACS folds "managing a go-around/rejected landing after accepting a LAHSO clearance" into this Task's risks: your climb-out now happens in the geometry of intersecting-runway traffic.

What you do:

• Fly the go-around
• Comply with ATC or the briefed procedure for the ground track (AA.III.J.S6)
• Communicate immediately (AA.III.J.S5)

The best mitigation was upstream — do not accept a LAHSO clearance your performance or the conditions make doubtful.

No — on two grounds (AFH ch. 9):

• Wheel contact with the runway is not required — the ACS says so explicitly (Appendix 3), so touching down doesn't bust the maneuver
• During an extremely low go-around the airplane may settle onto the runway and bounce — that "is not particularly dangerous" if you keep the airplane straight and hold a constant, safe pitch attitude; with power applied, the airplane reaches flying speed quickly, and the advanced power cushions any secondary touchdown

What would bust the maneuver is chasing the bounce with pitch, or freezing the configuration sequence.

It is made at the trigger, not after confirmation bias has run its course. Task III.B fixes the trigger objectively: go around when the approach cannot be completed within the Task tolerances — stabilized, ±5 knots, touchdown inside −250/+500 feet of the aiming point — or for any other unsafe condition (AA.III.B.S14), with the AFH's stabilized-approach evaluation at 500 feet as the standing gate (AFH ch. 16). By the time you are floating past the touchdown window at 20 feet, "timely" has already expired: the decision points were briefed (ACS Appendix 3), and the examiner is watching whether you honor them under landing expectancy — the pull AFH ch. 9 warns about.

Because an airplane cannot fly below stall speed and cannot climb below minimum power required speed (AFH ch. 9). At the moment of decision the airplane is trimmed nose-up for approach speed and may be decelerating; pitching for a climb before energy exists invites a stall at an altitude with no recovery room — the ACS's low-altitude stall/CFIT risk element (AA.III.J.R6). In some circumstances it is proper to briefly lower the nose to gain airspeed and get off the back side of the power curve. Power first, then attitude for the performance available, then configuration — and on airplanes with heavy control forces at maximum power, keep flying the airplane before reaching for handles (airplane control is the first consideration in this high-workload phase).

The ground track, heading, or course appropriate to the conditions, or as ATC or the evaluator specifies.

Wind correction is part of that track (AA.III.J.K3): the landing crosswind correction doesn't end at the decision — as the climb is established, turn the nose into the wind, bring the wings level, and crab to hold the extended centerline, rechecking the ground track frequently because the crosswind can vary markedly within a few hundred feet of the ground (AFH ch. 6).

Two collision-hazard geometries to name in the oral:

• The aircraft or vehicle on the runway that triggered the reject — offset as your operator's procedure directs while keeping it in sight
• After a LAHSO-related go-around, the intersecting-runway traffic whose protection depended on your hold-short

Radio calls come as appropriate (AA.III.J.S5), but aviate-navigate-communicate ordering holds: the ACS's distraction and task-prioritization risk (AA.III.J.R7) is aimed at crews who talk before they climb.

The Seaplane Handbook (FAA-H-8083-23 ch. 6) lists the water-specific triggers:

• Conflicts with other aircraft, surface vessels, or swimmers in the landing area
• Hazards on the water
• Wind shear
• Wake turbulence
• Water surface conditions
• Mechanical failure
• An unstabilized approach

Climb to a safe altitude while executing the go-around checklist, then evaluate and re-approach under better conditions. The terrain nuance: it's often best to make a gentle climbing turn back over the water to gain altitude rather than climbing out over a shoreline with rising terrain or noise-sensitive areas — the same maneuver-planning that Tasks III.G and III.H demand for confined areas.

• Bank at least 45°, established solely by reference to instruments, through at least 180° of turn as specified by the evaluator (AA.IV.A.S3) — then the same thing in the opposite direction (AA.IV.A.S4)
• Entry altitude ±100 feet, airspeed ±10 knots, bank ±5°, rollout on the specified heading ±10° (AA.IV.A.S6)
• Entry altitude selected so the Task finishes no lower than 3,000 feet AGL (AA.IV.A.S1)

The tolerances match the commercial numbers, but everything else moved: the commercial maneuver is 50° of bank through 360° flown visually — the ATP version is flown on the gauges, and Appendix 3 adds that you must control the airplane manually, without any intervention from the pilot monitoring or the evaluator (FAA-S-ACS-11A, Task IV.A).

The manufacturer's recommended airspeed; if one is not available, an airspeed not to exceed maneuvering speed (VA) (AA.IV.A.S2). In a type-rating course that number comes from your AFM and the operator's maneuver profile — there is no generic answer, and quoting one for "a jet" is how you get a follow-up question you can't win. Know where your type's number comes from and why it sits below VA.

The airplane must be flown manually — no autopilot, and no help from the pilot monitoring — but Appendix 3 says the use of available aircraft instrumentation is acceptable (FAA-S-ACS-11A, App. 3). Whether the flight director stays on is between your training program and the evaluator; be ready to fly it raw-data either way. For a VFR-only type rating, the Task is flown in visual conditions instead, the area must be cleared of traffic first, and the by-reference-to-instruments requirement of AA.IV.A.S3 does not apply (App. 3).

For instrument flight the IFH calls any turn greater than standard rate steep — the exact bank angle is unimportant (IFH ch. 7). What matters is that the effects of aerodynamic forces on control change pronouncedly at progressively greater bank, so skill in cross-check, interpretation, and control must rise in proportion. The payoff the IFH names is exactly why the ATP test keeps the maneuver: practice enables smooth, quick, and confident reactions to unexpected abnormal flight attitudes under instrument conditions (IFH ch. 7) — this Task is the warm-up for Task IV.B.

Total mechanical energy is altitude plus airspeed — potential plus kinetic — and the balance of thrust minus drag decides whether the total grows or shrinks (AFH ch. 4). Rolling to 45°+ while holding altitude forces a higher AOA so the shrunken vertical lift component still supports the airplane; the higher AOA drives up induced drag, so with fixed thrust you are now energy-negative and the airspeed decays. The fix is on the thrust levers: the power necessary to maintain constant airspeed increases as the bank and drag increase (IFH ch. 7). Power up going in, power off rolling out — done smoothly per AA.IV.A.S5.

A level 45° banked turn produces 1.41 G regardless of airspeed or airplane; 60° produces 2.0 G (AFH ch. 10). Stall speed rises with the square root of the load factor — the AFH's example airplane that stalls level at 50 knots stalls at 60 knots in a 45° level turn (AFH ch. 10). So at test bank the stall margin is already trimmed, and the margin between stalling speed and maneuvering speed decreases as bank increases (AFH ch. 10). That is the aerodynamics behind AA.IV.A.S7: no impending stall indication, no abnormal attitude, no structural or operating limit exceeded at any point.

VA decreases as weight decreases: the PHAK's example airplane has a VA of 100 knots heavily loaded but only 90 knots with a light load, because the lightly loaded wing reaches limit load at a lower speed (PHAK ch. 8). VA itself is the maximum speed at which the structural design's limit load can be imposed — by gusts or full deflection of a control surface — without structural damage. Two caveats worth stating: VA protects one full input, one axis, one time, in smooth air — it provides no structural protection for multiple full inputs in one axis or full inputs in more than one axis at once (PHAK ch. 5). At airline weights the spread between max-landing-weight VA and max-takeoff-weight VA is real; the AFM carries the numbers.

I correct adverse yaw with rudder throughout the turn, checking the ball in the turn-and-slip indicator or turn coordinator (IFH ch. 4).

• Entry and exit: aileron deflection produces adverse yaw — the down-aileron wing makes more lift and more induced drag, so the nose initially swings opposite the turn, which is why rudder correction here is necessary for precise instrument control
• Established in the turn: the faster outboard wing produces more lift and more drag, causing a slight slip that should be corrected with rudder (AFH ch. 3) — compounded by holding opposite aileron against overbanking, which feeds the same yaw
• Slip vs. skid: slipping means banked too much for the rate of turn, falling toward the inside; skidding means the rate is too great for the bank, pulled toward the outside (IFH ch. 4)

AA.IV.A.S3 requires a coordinated steep turn, and R5 names uncoordinated flight as its own risk.

Past shallow bank angles the airplane loses its positive/neutral stability about the longitudinal axis and keeps rolling into the turn unless deliberate opposite aileron is held (AFH ch. 10) — the outside wing flies a longer, faster arc and makes more lift. On the gauges the trap is letting it develop unnoticed: overbanking without a pitch adjustment demands ever more back pressure, until further back elevator only tightens the turn without raising the nose (IFH ch. 7). The tell is a rapid downward altimeter and VSI movement with increasing airspeed despite back pressure — a diving spiral. Recovery: shallow the bank first, hold or slightly relax elevator, reduce power if the airspeed increase is rapid (IFH ch. 7).

At a given airspeed, increasing bank increases the rate of turn; at a given bank angle, higher true airspeed slows the turning rate and makes the radius larger (AFH ch. 3, fig. 3-14).

The transport-category consequence: at jet maneuvering speeds the same 45° of bank buys far less turn rate and a much bigger circle than the numbers you carry from piston flying — which is why the evaluator specifies the amount of turn and why the rollout takes planning. The AFH rule of thumb: lead the rollout by one-half the angle of bank (AFH ch. 3).

Two illusions dominate. In a prolonged, coordinated, constant-rate turn the vestibular fluid catches up and the turning sensation disappears; on the rollout you feel a turn in the opposite direction, inviting a re-entry — the setup for the graveyard spiral, where the pilot feels a level descent and pulls, tightening the spiral (IFH ch. 3). The other is the Coriolis illusion — a head movement in a different plane mid-turn (glancing at an FMS page, a dropped chart) can create the illusion of rotating on an entirely different axis (IFH ch. 3).

Mitigations: a cross-check with minimal head movement, and believing the instruments over the seat of your pants. The maneuver is coordinated throughout (AA.IV.A.S3, R5) — a slipping or skidding turn only adds conflicting cues.

Enter the same way as a shallower turn, but prepare to cross-check rapidly as the turn steepens — because of the greatly reduced vertical lift component, a pitch change missed for even a moment shows up as rapid movement of the altimeter, vertical speed, and airspeed needles, and the faster the rate of bank change, the more suddenly the lift changes occur (IFH ch. 7). If the cross-check is fast enough to catch the need, smooth, steady back-elevator holds altitude. The IFH's priority rule: attend to the most important task first — keep pitch attitude relatively constant and the rest of the cross-check gets easier (IFH ch. 7).

Power required grows with bank and drag; with practice the power settings appropriate to specific bank attitudes are learned, so adjustments happen without staring at the airspeed and power instruments (IFH ch. 7). During the recovery to straight-and-level, elevator and power must be coordinated with bank control in proportion to the changing aerodynamic forces — back pressure comes out and power comes off together (IFH ch. 7). Errors on the rollout are the mirror image of the entry: hold the back pressure too long and you balloon through the entry altitude just as the vertical lift returns.

Roll out immediately to straight-and-level and analyze the errors — then practice shallower turns first, learn the attitude changes and control responses required, and increase the bank as the cross-check and control techniques sharpen (IFH ch. 7). In the sim that discipline matters more than pride: errors in steep turns are more exaggerated, more difficult to correct, and more difficult to analyze unless entry and recovery rates match your proficiency in the three basic instrument skills (IFH ch. 7).

• The 3,000-foot AGL floor (AA.IV.A.S1) is the CFIT and low-altitude-maneuvering mitigation baked into the skill elements — a botched steep turn decays into a stall, spiral, or spin, and the floor buys the recovery altitude (AA.IV.A.R3)
• Collision hazards remain even under IFR: Appendix 3 directs that if IFR, the pilots should be situationally aware of location and any potential traffic; in the airplane that means TCAS and party-line awareness, not just a clearance (AA.IV.A.R2; FAA-S-ACS-11A, App. 3)
• Distraction and task saturation (AA.IV.A.R4) hit hardest exactly when the cross-check must be fastest — brief the maneuver so nothing else competes for the scan

The instrument-rating version tests the light-airplane IFH recoveries. The ATP version references AC 120-111 — the upset prevention and recovery training (UPRT) AC — and its skill element demands more than a recovery: identify the attitude (both nose-high and nose-low) by proper instrument cross-check and interpretation, then apply flight control, power input, and aircraft configuration in the correct sequence to return to a stabilized level flight attitude, all solely by reference to instruments (AA.IV.B.S1). The sequence is the graded item — and in a transport airplane the sequence comes from the manufacturer's procedure or the industry recovery templates, not from instinct.

An upset is an airplane in flight unintentionally exceeding the parameters normally experienced in line operations or training:

• Pitch greater than 25° nose up
• Pitch greater than 10° nose down
• Bank greater than 45°
• Or within those parameters but at airspeeds inappropriate for the conditions (AC 120-111, para 1-6a)

An unusual attitude is any unintended or unexpected attitude in instrument flight; an upset has defined parameters, includes stall events and overspeeds, and centers on unintentional situations that may lead to a startle effect — in training, an instructor-set 30° bank with 15° nose-up is an unusual attitude but not an upset (AFH ch. 5).

The recovery priorities, in order (AC 120-111, para 2-2e):

1. Manage the energy
2. Arrest the flightpath divergence
3. Recover to a stabilized flightpath

Two governing rules sit on top:

• When an upset is precipitated by stall, recover from the stall before initiating other recovery actions — the templates assume the airplane is not stalled (AC 120-111, para 2-2e and ch. 4 NOTE, pointing to AC 120-109 for the stall procedure)
• The manufacturer's procedures take precedence over the AC's templates (AC 120-111, para 4-2 NOTE)

The templates themselves were built by Airbus, ATR, Boeing, Bombardier, and Embraer to give commonality across types (para 4-1).

Either pilot recognizes and confirms the developing situation and announces "Nose High." Then the pilot flying:

1. AP — DISCONNECT (expect a possible large out-of-trim condition)
2. A/THR — OFF
3. PITCH — apply as much nose-down control input as required to obtain a nose-down pitch rate (may take full nose-down; use nose-down trim if sustained column force is needed)
4. THRUST — adjust if required (consider reducing thrust on underwing-engine airplanes to aid the nose-down pitch rate)
5. When airspeed is sufficiently increasing — RECOVER to level flight, targeting a slightly nose-low attitude to avoid entering another upset

WARNING: excessive use of pitch trim or rudder may aggravate the upset or cause high structural loads (AC 120-111, Tables 1 and 3).

Roll. If nose-down inputs are unsuccessful, pitch can be controlled by rolling the airplane — a large bank angle helps reduce excessively high pitch attitudes, though the bank should not normally exceed approximately 60°. Continuous nose-down elevator keeps the wing's AOA low, which keeps the normal roll controls effective, and the rolling maneuver converts the pitch rate into a turning maneuver, letting the pitch fall (AC 120-111, Table 3). As the nose approaches the horizon, roll back to wings level, check airspeed, and adjust thrust and pitch.

Either pilot announces "Nose Low." Pilot flying:

1. AP — DISCONNECT, A/THR — OFF
2. RECOVER from stall if required — even nose-low and slow, the airplane may be stalled at a relatively low pitch, and the fix is nose-down elevator, which may not be intuitive
3. ROLL in the shortest direction to wings level — do not increase positive G or feed in nose-up elevator or stabilizer trim until approaching wings level; it may be necessary to unload (reduce back pressure) to improve roll effectiveness, and past 90° of bank unloading may feel like pushing
4. THRUST and DRAG — adjust: airspeed low, add thrust; airspeed high, reduce thrust and extend speedbrakes if necessary
5. RECOVER to level flight, avoiding stall from premature recovery or excessive G loading (AC 120-111, Tables 2 and 4)

The lift vector is both the recovery tool and the hazard: unloading is necessary to improve roll control and to prevent pointing a large lift vector toward the ground (AC 120-111, Table 4), but once the wings are level the instinct is to pull hard. The template's repeated warning: avoid stall from premature recovery or excessive G loading (AC 120-111, Tables 2 and 4).

At altitude the margins are thinner than they feel — increased G raises the low-speed buffet speed while cutting the margin below Mach buffet. A jet cruising at 51,000 feet with buffet boundaries at 0.60 and just above 0.82 Mach at 1.0 G can meet buffet at 0.73 Mach with only 1.4 G (AC 61-107, para 3-2). A smooth, measured pull is not timidity; it is the recovery.

• Pitch trim: sparingly. Use it to relieve sustained column forces, not to fly the recovery — recovery to level flight may require it, but excessive use of pitch trim may aggravate the upset or result in high structural loads (AC 120-111, para 4-2b and Table WARNINGs)
• Rudder: only if roll control is ineffective, and carefully — the same structural warning applies (para 4-2b)
• Anticipate the trim state: disconnecting the autopilot may hand you a large out-of-trim condition at the worst possible moment (Table footnotes)

MONITOR airspeed and attitude throughout the recovery and ANNOUNCE any continued divergence — the templates assign that line to the PM verbatim, and the explanation is blunt: evidence shows the PM is often in a better position than the PF to recognize adverse trends in airplane state (AC 120-111, Tables 3 and 4). Recognition itself belongs to either pilot — whoever sees it announces "Nose High" or "Nose Low." The AFH's crew-response standard adds: communicate and confirm the situation clearly and concisely, transfer control to the most situationally-aware crewmember, and work as a team through standardized interactions (AFH ch. 5).

• Environmental — turbulence from clear air, mountain wave, wind shear, thunderstorms and microbursts; wake turbulence from other aircraft; icing destroying the smooth flow over the airfoil (AFH ch. 5)
• Mechanical — failures that directly depart normal flight: asymmetrical flaps, malfunctioning or binding flight controls, runaway trim; and malfunction or misuse of the autoflight system, where advanced automation may mask the cause of the anomaly — disengaging the autopilot and autothrottles lets the pilot control the airplane directly and possibly eliminate the cause (AFH ch. 5)
• Human — VMC into IMC, diversion of attention, task saturation, sensory overload, and spatial disorientation (AFH ch. 5); the ACS compresses these into AA.IV.B.R1

The automation point carries a duty: maintain proficiency to manually fly the airplane in all flight conditions without the autopilot/autothrottles (AFH ch. 5).

Startle: an uncontrollable, automatic muscle reflex — raised heart rate and blood pressure — elicited by a sudden, intense event that violates expectations (AC 120-111, para 1-6p). Surprise: an unexpected event that violates expectations and can affect the mental processes used to respond (para 1-6q).

Upsets in line operations are unplanned, so startle or surprise can adversely impact recognition or recovery — which is why instructors deliberately build both into scenarios (AC 120-111, para 2-5m). Contrast the classic unusual-attitude drill where you close your eyes and any element of surprise disappears (AFH ch. 5). The countermeasure is a recovery sequence trained until it survives the reflex.

Proportional counter-response is the timely manipulation of flight controls and thrust to manage an unintended attitude or envelope excursion, on a time scale of seconds or fractions of seconds — recognizing a developing upset and taking proportionally-appropriate avoidance action before the airplane reaches full upset parameters (AFH ch. 5).

It prevents escalation by front-running the psychological risk: the AFH warns that the sudden, surprising nature of a developing upset creates a high risk of panic and overreaction that aggravates the situation. Two completion standards formalize the idea: recognition — timely action to recognize divergence from the intended flightpath and interrupt progression toward a potential upset (AC 120-111, para 2-2d); prevention — timely action to avoid progression toward a potential upset (para 2-2c).

• Reduced air density reduces aerodynamic damping, overall stability, and control — at high altitude and high Mach the airplane can simultaneously exhibit slow-speed problems like Dutch roll, adverse yaw, and stall (AC 61-107, para 3-3)
• The buffet margins converge: increasing gross weight or load factor raises the low-speed buffet speed and lowers the Mach buffet speed, and a maneuvering pull can erase a 1.4 G straight-and-level buffet protection entirely — any change in airspeed, bank, or gust load may reduce it to no protection (AC 61-107, para 3-2)
• Thrust is scarce: thrust available varies significantly with altitude — the AC's demonstration is timing how long a 25-knot level-flight speed change takes at low versus high altitude (AC 120-111, para 2-5l) — so energy mistakes cannot be bought back quickly

A pilot in a typical FSTD feels less than 10 percent of the actual airplane G, and pilot control inputs are highly influenced by load factor — so the sim systematically under-teaches how a real recovery feels (AC 120-111, App. 3, para 4). The same appendix warns that upset recoveries in an FSTD at high altitudes can be prone to oscillations that go unnoticed unless the full suite of displays is used. Say this in the oral and you demonstrate exactly the risk understanding AA.IV.B.R6 (control input errors) is probing: the airplane will load up in ways the box never showed you.

• Underwing engines — thrust produces a nose-up pitching moment, which is why the nose-high template offers reducing thrust as a tool for achieving a nose-down pitch rate, and why thrust is adjusted rather than firewalled (AC 120-111, Table 3); if pitch is being managed with trim and elevator, reducing thrust is not recommended
• Swept wings — tip-stall tendency moves the center of lift forward at high AOA, and the type-specific behaviors (Task IV.C) shape what the recovery feels like
• T-tails — susceptible types can reach a deep stall where the tail is immersed in the wing wake and loses effectiveness; high AOA can exist at any pitch attitude, even nose below the horizon, so the correct action — push further nose-down — may seem counterintuitive (AFH ch. 16)

The honest oral answer is type-specific: AC 120-111 directs carriers to consult the FSB report for the type, including its Training Areas of Special Emphasis on in-flight handling (para 3-2b).

• Incorrect assessment of what kind of upset the airplane is in — the templates begin with recognize-and-confirm for a reason; energy state and its rate of change drive how the PF handles the recovery (AC 120-111, Tables 3 and 4)
• Failure to disconnect the wing leveler or autopilot
• Failure to unload the airplane when necessary
• Failure to roll in the correct direction — shortest way to wings level
• Inappropriate airspeed management during the recovery

Each maps onto a risk element: assessment is AA.IV.B.R5, interpretation is R4, the control-input errors are R6.

Mostly after it — a recovery can leave the airplane well off its assigned altitude and heading. The AC's training-scenario emphasis names five items to reestablish situational awareness on while returning to the desired flightpath after the recovery (AC 120-111, App. 2):

• Heading
• Terrain
• Altitude
• Other aircraft
• Flight deck automation

The paired common error is losing situational awareness and failing to return to the assigned flightpath or follow ATC instructions after recovery (AC 120-111, App. 2). Two more traffic hooks: searching for traffic is on the AC's list of distractions that can lead to an upset in the first place, and overcontrolling for a TCAS resolution advisory is a pilot error that can itself create an undesired aircraft state (AC 120-111, para 2-5). Once stabilized: check TCAS, talk to ATC, get back on the clearance.

121.423, Pilots: Extended Envelope Training, whose required maneuvers include upset recovery maneuvers (121.423(b)(4)) along with manually controlled slow flight, loss of reliable airspeed, and instrument departure and arrival — all conducted in a Level C or higher full flight simulator (AC 120-111, para 3-2d). Recurrent extended envelope training on those items is required within 24 calendar months preceding service as a pilot (121.423(d)). Full-stall and stick-pusher training under the same rule is developed in the Area V tasks.

Only conditionally: the evaluator only tests this Task if the airplane has specific flight characteristics identified in the Flight Standardization Board Report (FSBR) (FAA-S-ACS-11A, App. 3). If it is tested, the skill element requires proper techniques, checklists, and procedures to enter into, operate within, and recover from the specific flight situations (AA.IV.C.S1) — meaning the demonstration is flown from your type's published procedure, not improvised. The knowledge element is deliberately open-ended: all specific flight and performance characteristics associated with the aircraft (AA.IV.C.K1).

The FSB report is the FAA's type-specific training document; the UPRT and stall-prevention ACs both direct carriers to consult the FSB report, if available, for the specific airplane type when building training programs, and to review its Training Areas of Special Emphasis and any other recommendations on in-flight handling (AC 120-111, para 3-2b; AC 120-109, para 2-6). For this Task the FSBR is literally the exam blueprint — it is the document that decides whether the Task is tested at all and which characteristic gets flown (FAA-S-ACS-11A, App. 3).

A nose-down pitching tendency in the transonic range, caused principally by:

1. Shock-wave-induced flow separation — beginning normally near the wing root, it decreases the downwash velocity over the elevator, producing a nose-down tendency
2. Aft movement of the center of pressure — the CG ends up farther ahead of the aerodynamic center than in slower flight, dramatically increasing the nose-down pitch tendency (AC 61-107, para 3-2)

Mach tuck develops gradually; the condition must not be allowed to progress to where there is no longer enough elevator authority to prevent entry into a steep, sometimes unrecoverable, dive — respond to excessive airspeed, buffeting, or warning devices before extreme nose-down forces set in (AFH ch. 16).

Most jets capable of Mach-range flight use automated Mach tuck compensation (Mach trim); if the system is inoperative, the airplane is typically limited to a reduced maximum Mach number (AFH ch. 16). Separately, types operating near MMO carry a trim/autopilot Mach compensating device — a stick puller — to alert the pilot to excursions beyond certificated MMO; if a malfunction requires disabling it, the aircraft must be operated well below MMO per the AFM, and the AC is emphatic that the stick puller should never be disabled in normal operations (AC 61-107, para 3-2). Your type's specific system and its MEL/AFM penalties are the answer the evaluator wants.

Mach buffet is airflow separation on the upper wing surface behind a shock wave — it is a function of the speed of the airflow over the wing, not necessarily the forward speed of the airplane, and the shock wave strength, rather than a stall, creates the separation (AFH ch. 16). It appears in two cruise conditions: at high-speed cruise, an overly strong shock; at low-speed cruise, high AOA accelerates the flow over the upper surface past Mach 1 locally, and the separated flow acts over a larger portion of the chord, with a more significant effect on control (AFH ch. 16). A buffet at altitude could be your first indication of a problem — you must know which side of the envelope it is coming from to respond correctly.

Coffin corner, the aerodynamic ceiling, is the altitude where the low-speed buffet boundary IAS and the high-speed Mach limit converge, as increasing altitude drops IAS relative to TAS: fly any faster and you exceed MMO into high-speed Mach buffet; fly any slower and the required AOA brings low-speed buffet (AFH ch. 16). At that point the airplane can neither go faster without activating the stick puller nor slower without activating the stick shaker or pusher (AC 61-107, para 3-2). This region carries loss-of-control consequences, which is why cruise altitude selection must preserve buffet margin.

Increasing gross weight or G-loading raises the low-speed buffet speed and lowers the Mach buffet speed at once. The AC's example: a turbojet at 51,000 feet and 1.0 G with MMO 0.82 may see Mach buffet slightly above MMO and low-speed buffet at 0.60 Mach — but only 1.4 G brings buffet on at the optimum 0.73 Mach, and any change in airspeed, bank angle, or gust loading can reduce that protection to none (AC 61-107, para 3-2). Mitigations:

• Select a maximum cruising altitude that leaves buffet margin for maneuvering and gusts
• Use the cruise maneuvering/buffet limit charts
• Know the manufacturer's turbulence penetration speed, which normally gives the greatest margin between the buffets (AFH ch. 16)

• Lift builds more gradually with AOA, with a less well-defined maximum — so the loss of lift past the peak is less dramatic, but the high-lift condition brings high drag and possibly a high rate of descent (AFH ch. 16)
• An unmodified swept wing tends to stall at the tips first because the boundary layer flows spanwise toward the tips; tip stall lets the center of lift move forward (a pitch-up tendency), worst when sweep and taper are combined (AFH ch. 16)
• Manufacturers counter with twist, airfoil-section changes, and vortex generators so roll control survives an inadvertent stall entry — and airplanes without vortex generators may stall with little to no buffet (AFH ch. 16)

Some T-tail configurations can reach a stall where the tail is immersed in the wing wake at very high AOA and loses effectiveness, possibly with a high descent rate. Since high AOA can occur at any pitch attitude — even nose below the horizon — the correct recovery, pushing the nose down further, may seem counterintuitive. Deep stalls may be unrecoverable, but they are easily avoided by observing published limitations; susceptible types carry stick shakers as standard, and a stick pusher automatically reduces AOA before a dangerous stall condition, or aids recovery where natural aerodynamic recovery is weak (AFH ch. 16). Avoid situations that would fire the pusher close to the ground.

A coupled oscillation in roll and yaw that becomes objectionable when roll (lateral) stability is reduced relative to yaw (directional) stability. Certification requires a stability augmentation system where the tendency is objectionable or adversely affects control stability — the yaw damper, a gyro-operated system providing rudder inputs to cancel the yaw (AC 61-107, para 3-3). On swept-wing airplanes the yaw damper's ride-smoothing function is secondary; damping Dutch roll is the more vital function (AFH ch. 13). Know your type's dispatch and handling implications with the yaw damper inoperative — that is exactly the kind of item an FSBR flags.

Speed instability is what the AFH calls one of the most important aspects of jet-airplane flying: a jet's minimum-drag speed (VMD) is typically 1.5–1.6 VS — well above a piston airplane's well-identified 1.3 VS — and flight around it produces no obvious change in feel except a lack of speed stability. A decrease in speed increases drag, which decreases speed further: a potential speed divergence. A pilot unaware of the divergence can develop a serious sink rate at a constant power setting while the pitch attitude appears normal (AFH ch. 16).

Reduced density means CAS is much slower than TAS, and AOA must increase to maintain the same lift coefficient with altitude — so a jet at high altitude and high Mach can simultaneously experience slow-speed problems: Dutch roll, adverse yaw, and stall. The thin air also reduces aerodynamic damping, overall stability, and control (AC 61-107, para 3-3). Design features — swept wings, tailored airfoils, vortex generators as boundary-layer energizers — reduce but do not eliminate these behaviors in the modern turbojet (AC 61-107, para 3-3).

Three linked effects (AC 61-107, para 3-3):

• Shock waves forming on the wing — drag rise
• Aft shift in the center of lift — the nose-down pitching moment called Mach tuck
• Airflow separation behind the shock waves — Mach buffet

One shock wave, three symptoms — the oral answer that connects them beats three memorized definitions.

Work from the documents the ACS itself references: the FSB Report (type specific) and the POH/AFM (FAA-S-ACS-11A, Task IV.C references). Build your list from three places:

• The FSBR's Training Areas of Special Emphasis and handling recommendations (AC 120-111, para 3-2b)
• The AFM's limitations and non-normal procedures tied to the characteristics above — Mach trim, yaw damper, stall protection systems
• Your program's maneuver profiles for entering, operating within, and recovering from each characteristic, since the skill element grades checklist and procedure use (AA.IV.C.S1)

The risk element pairs each characteristic with its effects and applicable procedures (AA.IV.C.R1) — for every item on your list, be able to say what it does to the airplane and which procedure answers it.

These characteristics announce themselves through warnings — buffet, stick shaker, stick puller, overspeed cues — and a pilot in such an event can be rapidly confronted with multiple or simultaneous visual, auditory, and tactile warnings, while an expected warning that doesn't fire can distract a pilot as much as multiple warnings can (AFH ch. 5). Separating the time-critical information from the distractions takes practice, experience, and knowledge of the airplane and its systems, plus a cross-check that catches missing or invalid cues — a failed stall warning still leaves buffet, loss of roll authority, and an unarrested descent as tells (AFH ch. 5). Task-prioritize accordingly: the margin of safety is task requirements versus pilot capabilities (AFH ch. 5) — fly the airplane first, run the associated non-normal procedure second.

Because the event being graded is the impending stall, not the break. AC 120-109 defines an impending stall as an AOA that causes a stall warning — the same thing the AC calls "approach-to-stall" or "the first indication of stall." The Task requires you to acknowledge the cue(s) and promptly recover at the first indication of an impending stall — buffet, stall horn, stick shaker (AA.V.A.S5). You are being checked on recognition and response, not on riding it into a full stall.

Not for this Task. AC 120-109 para 4-2a is explicit: in maneuver-based stall prevention training and checking, pilots should apply the stall recovery at stall warning as defined in para 1-7 — not at a low speed alert or low energy alert (e.g., "airspeed low, airspeed low," "speed, speed, speed," or a flashing airspeed warning cue). Starting the recovery at the low-speed alert does not satisfy the objective of training or checking the recovery procedure, so an otherwise clean recovery can be graded as the maneuver not having been performed. Two caveats worth saying out loud: in scenario-based training the opposite applies — you should return the airplane to a desired state on any low airspeed or low energy alert; and on the line, an energy alert is exactly what you want to act on, since this is a checking-context rule, not an airmanship rule.

This is the practical edge of AA.V.A.R2 (range and limitations of stall warning indicators) and R3 (stall warning awareness): know which of your annunciations is a stall warning and which is merely a low energy alert.

• Clear the area and pick an entry altitude that lets the recovery finish no lower than 3,000 feet AGL (non-transport category) or 5,000 feet AGL (transport category) (AA.V.A.S1)
• Bank angle 15°–30°, adjusted smoothly along with pitch and power per the evaluator's instructions, to an impending stall (AA.V.A.S4)
• Coordinated flight maintained in simulated or actual instrument conditions throughout the maneuver (AA.V.A.S3)

Note what is not there: no altitude-loss number, no airspeed tolerance, no heading tolerance. That absence is deliberate.

No — and it is a core principle of the guidance, not an oversight. Evaluation criteria for a recovery from an impending stall should not include a predetermined value for altitude loss; criteria should instead consider the multitude of external and internal variables that affect the recovery altitude. Para 4-5 gives the three checking criteria instead:

• Prompt recognition of the impending stall
• Correct application of the stall recovery procedure
• Recovering without exceeding the airplane's limitations

Pilots must accept that reducing AOA will normally result in altitude loss.

1. Autopilot and autothrottle/autothrust — disconnect. Manual control is essential in all situations.
2. Pitch — a) nose-down pitch control, apply until impending stall indications are eliminated; b) nose-down pitch trim, as needed.
3. Bank — wings level. This orients the lift vector for recovery.
4. Thrust — as needed. Maximum thrust is not always needed.
5. Speed brakes/spoilers — retract. Improves lift and stall margin.
6. Return to the desired flightpath with gentle action, to avoid secondary stalls.

(AC 120-109, Appendix 1, Table 1.) The Task itself requires the recovery in accordance with the POH/FM for your airplane (AA.V.A.S6) — the template is the fallback when the manufacturer has not published a procedure.

Because thrust does not fix AOA, and in some airframes it makes the AOA worse. AC 120-109 eliminated the old profiles that emphasized immediate advancement of maximum thrust — a stall can occur at high thrust or idle thrust, so thrust is adjusted accordingly. Three airframe types react differently:

• Engines below the wing: applying maximum thrust may create a strong nose-up pitching moment at low airspeed
• Engines above the wing: thrust creates a helpful pitch-down tendency
• Propeller-driven airplanes: thrust application increases the airflow around the wing, assisting in stall recovery

Know which of those three your airplane is.

An abrupt pitch-up or trim change can occur when the autopilot unexpectedly disconnects during a stall event, adding an unexpected physical challenge exactly when you are trying to reduce AOA. In some airplanes this is aggravated by an additional pitch-up when the pilot increases thrust during the recovery (AC 120-109, para 4-2). On a departure, the airplane is already trimmed nose-up, thrust is high, and underwing engines add their own couple — so step 1 (disconnect) and step 2b (nose-down trim as needed) are doing real work, not ceremony.

AC 120-109 defines a secondary stall as a premature increase in AOA producing another full stall during the recovery, before a stable flight condition is established; a secondary stall warning is simply a reoccurrence of the stall warning. The AC is blunt about diagnosis: secondary stall warnings are indicative of a pilot prioritizing minimum loss of altitude over proper stall recovery, or of flight control inputs that are too aggressive.

But do not read it as an automatic bust: in some airplanes it may be difficult to determine the point where pitch can begin to be increased, and a secondary stall warning is acceptable as long as AOA is promptly reduced and the airplane's limitations are not exceeded (para 4-2a). What the evaluator is grading is whether you reduced AOA promptly and stayed inside the limits — not whether the warning chirped a second time.

Range: a stick shaker is an artificial stall warning device that vibrates the control column (AFH glossary) and normally activates around 107 percent of the actual stall speed (AFH ch. 16) — a thin margin, not a comfortable buffer. Part 25 requires stall warning to be clear and distinctive to the pilot in straight and turning flight (25.207(a)); AC 120-109's own definition adds that the alert — aerodynamic buffet or a synthetic cue — must give clear indications prior to a full stall to allow a pilot to prevent a full stall (para 1-7o, which points at 25.207).

Limitation: airplanes without vortex generators may stall with little to no buffet (AFH ch. 16), so aerodynamic cues can be nearly absent; malfunctioning or deferred equipment can also degrade stall protection and stick pusher systems (AC 120-109, para 4-2).

AA.V.A.K2 asks for recognition using sight, sound, or feel, and AC 61-67 catalogs the raw cues:

• Feel — a mushy feeling in the flight controls and less control effect as speed is reduced, attributed in part to reduced airflow over the control surfaces; kinesthesia — the sensing of changes in direction or speed of motion — warns of a decrease in speed or the beginning of a mushing
• Sound — a reduction in the sound of air flowing along the fuselage; in fixed-pitch propeller airplanes, a loss of rpm in power-on conditions
• Buffet — just before the stall: buffeting, uncontrollable pitching, or vibrations
• Synthetic — stall warning devices that alert the pilot 4 to 8 knots prior to the onset of the stall

When one or more of these indicators is noted, initiation of a recovery should be instinctive (AC 61-67, para 103) — which is the S5 standard in different words: acknowledge the cue, recover promptly.

AC 120-109 lists any one or combination of:

• An uncommanded nose-down pitch that cannot be readily arrested, possibly with an uncommanded rolling motion
• Buffeting of a magnitude and severity that is a strong and effective deterrent to further increase in AOA
• No further increase in pitch when the pitch control is held at the full aft stop for 2 seconds, leading to an inability to arrest descent rate
• Activation of a stick pusher

On the ATP practical test you are not being asked to produce any of these — a full stall in the partial flap configuration means you missed the cue.

121.423, Pilots: Extended Envelope Training. It requires instructor-guided hands-on experience of recovery from full stall and stick pusher activation, if equipped (121.423(c)), conducted in a Level C or higher full flight simulator (121.423(a)). Recurrent extended envelope training is required within 24 calendar months preceding service as a pilot for the stall, upset, slow flight, unreliable airspeed, and manual departure/arrival items, and within 36 calendar months for recovery from a bounced landing (121.423(d)). AC 120-109 explicitly reflects the full stall training requirement of Public Law 111-216.

• Windshear or a microburst on departure or a low approach — performance loss the crew tries to fly through with pitch
• Turbulence and high density altitude eroding the margin between the current and the critical AOA (AA.V.A.R6)
• A level-off or altitude capture with thrust still at climb and the flight director commanding pitch the thrust cannot support
• A premature or unbriefed flap retraction below the maneuvering speed for the next configuration
• Distraction and task saturation during a config change — the ACS names distractions, task prioritization, loss of situational awareness, and disorientation as risks (AA.V.A.R8). The emphasis is earned: stall/spin accidents account for roughly one-quarter of all fatal general aviation accidents, and NTSB statistics indicate most result when a pilot is momentarily distracted from the primary task of flying (AC 61-67)
• Sideslip from an unfeathered or asymmetric-thrust condition, which AA.V.A.K1 calls out specifically for this Task

Compare the knowledge elements: AA.V.A.K1 and AA.V.C.K1 both list sideslip effects among the relationships you must understand; AA.V.B.K1 (clean) does not. The reason is operational — the partial flap and landing configurations are the ones flown near the ground with asymmetric thrust, crosswind corrections, and rudder trim in play. Uncoordinated flight at high AOA is how an impending stall becomes a spin, and the ACS lists inadvertent stall, spin, and loss of control during takeoff or while on approach as the risk (AA.V.A.R1). The skill element answers it: coordinated flight throughout the maneuver (AA.V.A.S3).

AC 61-67 names the scenario directly: a go-around or short field takeoff — high pitch attitude, high power setting, and low airspeed — is the classic situation where P-factor (asymmetric propeller loading) can precipitate a stall/spin accident. At high AOA the downward-moving blade carries a higher AOA and more thrust, yawing the airplane left; insufficient or excessive rudder correction leaves the airplane uncoordinated. Two compounding traps apply (AC 61-67, para 109): in an uncoordinated maneuver the pitot/static instruments — especially the altimeter and airspeed indicator — are unreliable, so the stall warning may be your first honest cue that a critical AOA is approaching; and if a stall recovery is not promptly initiated, the airplane is more likely to enter an inadvertent spin, the primary cause of which is exceeding the critical AOA while applying excessive or insufficient rudder.

The jet-era version swaps P-factor for the underwing thrust couple, but the risk it grounds is the same one the ACS names: inadvertent stall, spin, and loss of control during takeoff or while on approach (AA.V.A.R1).

The entry changes; the recovery does not. AC 120-109 directs that training include disconnecting the autopilot and autothrottle/autothrust during stall prevention training and, where the autoflight integration permits, scenarios with the autothrottle/autothrust engaged. With the autopilot flying the entry, the airplane arrives at the stall warning already trimmed well nose-up, which is precisely the out-of-trim condition step 1 of the template warns about — you must ensure the pitch attitude does not increase when disconnecting the autopilot. Expect to need forward column force and nose-down trim.

The honest answer for the oral is type-specific — it belongs to your AFM and FSB report, not a memorized generality. AA.V.A.K4 requires knowledge of flight envelope protection in normal and degraded modes and of unexpected disconnects of the autopilot or autothrottle/autothrust: protections vary by manufacturer and by control law, and a degraded law may hand you an airplane with no alpha protection at all. AC 120-109 directs operators to consult the FSB report for the specific type, reviewing the Training Areas of Special Emphasis and any stall-related recommendations (para 2-6). Say what your airplane does; never generalize.

Treat it as a memory-item maneuver with a division of labor:

• The pilot flying announces the recovery ("stall — my controls" or the operator's phrasing), disconnects the autopilot and autothrottle/autothrust, and applies nose-down pitch until the warning stops
• The pilot monitoring confirms the disconnects, calls the airspeed and altitude trend, sets thrust as directed, and retracts speed brakes/spoilers
• Configuration changes are commanded and confirmed, not silent — the Task requires flaps and other lift/drag devices to the recommended setting, and the landing gear retracted after a positive rate of climb is established, if applicable (AA.V.A.S7)

Fly your operator's published callouts; the point is that both pilots must be able to state the sequence out loud.

Priority order (AC 120-109, para 4-2):

1. Recognize the stall and return the airplane to a controlled, safe state — the most important factor in surviving a stall event
2. Recover to a safe maneuvering speed and AOA
3. Re-establish the assigned heading, altitude, and airspeed
4. Return to the desired flight path as specified by the evaluator (AA.V.A.S7)

Chasing the clearance during the recovery is how a stall event becomes an accident.

Two things. First, the entry is while in cruise flight — there is no configuration to establish, so the skill element only requires coordinated flight in simulated or actual instrument conditions throughout (AA.V.B.S3). Second, the recovery ends simply with return to the desired flight path as specified by the evaluator (AA.V.B.S7) — there is no flap or gear retraction step, because there is nothing extended. The added knowledge element is the one that matters: effects of altitude on performance (e.g., thrust available) and flight control effectiveness during a recovery (AA.V.B.K6).

• Entry altitude allowing the recovery to be completed no lower than 3,000 feet AGL (non-transport category) or 5,000 feet AGL (transport category), after clearing the area (AA.V.B.S1)
• Bank angle 15°–30°, with pitch and power adjusted smoothly per the evaluator's instructions to an impending stall (AA.V.B.S4)
• Coordinated flight in simulated or actual instrument conditions throughout (AA.V.B.S3)
• Recovery promptly at the first indication of an impending stall, with the cue(s) acknowledged (AA.V.B.S5)

Same numbers as the partial flap and landing Tasks. There is still no altitude-loss, airspeed, or heading tolerance.

Weight, G loading, CG, bank angle, altitude, and icing all move it — AC 120-109 names exactly this list of factors affecting handling characteristics and stall speed (para 4-2b). AA.V.B.K1 tests the same relationship: AOA, airspeed, load factor, power setting, aircraft weight and balance, and attitude. Start from the AFH's warning that a published level-flight 1G stall speed is valid only:

1. In unaccelerated 1G flight
2. In coordinated flight (slip-skid indicator centered)
3. At one weight (typically maximum gross)
4. At one CG (typically maximum forward)

Break any of those four and the number on the page is optimistic. For a clean, uncontaminated wing the critical AOA does not move — only the speed at which you reach it does. (Icing is the exception: contamination changes the critical AOA itself — see the cruise-scenarios card.)

Stalling speed increases at the square root of the load factor (AFH ch. 10; AC 61-67 states the same rule). The Task is flown at 15°–30° (AA.V.B.S4), so the penalty is modest — but it stacks on top of weight and altitude. The AFH and AC 61-67 give matching examples:

• Level flight: stalls at 50 knots
• 45° bank: stalls at 60 knots
• 60° bank: stalls at 70 knots
• 4 G load factor: a 45-knot airplane stalls at 90 knots — an accelerated maneuver stall, so named because it arrives at a higher indicated airspeed than any stall you practiced

Two consequences for the check:

• As bank steepens, the margin between stalling speed and maneuvering speed decreases (AFH ch. 10). An accelerated stall — one of the risk items in AA.V.B.R5 — is simply reaching the critical AOA at a higher-than-normal airspeed, so the cues arrive sooner than your airspeed instinct expects.
• Weight and CG shift it too: forward CG gives a slightly higher stalling speed but favorable stall characteristics; aft CG gives a slightly lower stalling speed and less desirable stall characteristics (AFH ch. 13).

The simulator can also mask this: AC 120-109 lists G loading awareness / accelerated stall among the FFS limitations instructors must brief, since those cues can be absent from the device (para 2-4).

AC 120-109: at high altitudes, stall recovery will likely require losing several thousand feet. The AFH agrees — at high altitude, where available thrust is significantly less than at lower altitudes, recovery may require significant pitch down to regain airspeed, and several thousand feet or more of altitude loss may occur (AFH ch. 16). This is why there is no altitude-loss criterion in the ACS, and why an applicant who tries to fly a high-altitude recovery like a low-altitude one usually earns a secondary stall warning. Note that the warning itself is not the bust: AC 120-109 says a secondary stall warning is acceptable as long as AOA is promptly reduced and the airplane's limitations are not exceeded (para 4-2a). What fails you is chasing the altimeter instead of the AOA.

No. AC 120-109 is explicit: declare an emergency if necessary — do not delay recovery due to degrading airspeed or a stall event to obtain ATC clearance to a lower altitude (para 4-2). The altitude is yours to trade, and the coordination happens afterward. The pilot monitoring handles the declaration and the deviation call while the pilot flying flies the recovery.

Because the aerodynamics are the same: reducing AOA eliminates the stall regardless of altitude. The AFH says the high-altitude technique is the same — lower the nose until the stall warning stops — but adds that after the AOA is reduced to where the wing is again developing efficient lift, the airplane will still likely need to accelerate to a desired airspeed (AFH ch. 16). What changes is not the procedure but the energy budget: down low there is thrust to stop the descent quickly; up high there is not, so the altitude does the work the thrust cannot.

Two effects, and AC 120-109 names both under altitude effects: thrust available for recovery is reduced, and there is a lack of airflow through the engines at high AOA. The AC draws the conclusion for you — this reinforces that reduction of AOA must precede any increase of thrust (para 4-2). Adding thrust into a high-AOA, high-altitude condition may buy you very little and can cost you a compressor stall or an unhelpful pitch couple.

AC 120-109 lists pitch rate sensitivity of flight controls due to lack of aerodynamic damping among the differences between high and low altitude stalls (para 4-2). Thin air means less damping in pitch and roll, so a given control input produces a larger and faster response than the same input produces at low altitude. Practically: your nose-down input needs to be positive but smooth, and the recapture of the flight path needs to be gentle — the AC's rationale for step 6 is to apply gentle action for recovery to avoid secondary stalls.

AA.V.B.K3 and R1 ask for exactly this. Realistic ones:

• Loss of reliable airspeed — blocked or iced pitot inputs feeding both the pilots and the autoflight
• An autopilot holding altitude while drag rises or thrust falls, trimming nose-up as speed decays
• Turbulence, mountain wave, or a temperature shear at an altitude with a thin maneuver margin (AA.V.B.R6)
• An inadvertent climb above the airplane's capability for the weight and temperature
• Icing changing the wing's critical AOA, so the stall arrives at a speed and attitude that look normal
• Distraction and task saturation, plus loss of situational awareness or disorientation (AA.V.B.R8)

Because the low-speed and high-speed buffet boundaries converge as altitude increases; the point where they merge is the aerodynamic ceiling, known as coffin corner. At cruise altitude you are boxed in from both sides: slowing brings you to the low-speed buffet boundary, where prestall buffet begins, and accelerating brings Mach buffet — airflow separation behind a shock wave (AC 61-107). Increasing weight or G loading raises the low-speed buffet speed and lowers the Mach buffet speed — AC 61-107's example turbojet at 51,000 feet meets buffet at only 1.4 G, so a bank, a gust, or a speed change can erase the margin. This is why AC 120-109 lists Mach effects among the factors leading to a stall event and expects knowledge of your buffet boundary and margins — including the different buffet cues on the high-speed versus low-speed side (paras 3-2b, 3-2d). Select a cruise altitude that leaves sufficient buffet margin for the maneuvering and gusts expected (AC 61-107).

Turbulence can cause an aircraft to stall at a significantly higher airspeed than in stable conditions — a vertical gust or windshear produces a sudden change in the relative wind and an abrupt increase in AOA (AC 61-67). Even a gust too brief to develop a stall by itself can stall the airplane while you are correcting the flightpath. The speed guidance (AC 61-67, para 100):

• In moderate or severe turbulence in cruise, fly an airspeed well above the indicated stall speed and below maneuvering speed (VA)
• Remember VA is lower at a lower weight
• Respect what VA does not protect: do not use full or abrupt control movements at or above VA — and rapid, large alternating control inputs, especially combined with large changes in pitch, roll, or yaw, can produce structural failure at any speed, even below VA

This is the mechanism behind the turbulence item in AA.V.B.R6: the margin problem is an AOA problem before it is an airspeed problem.

Per AC 120-109, para 4-5:

• Prompt recognition of the impending stall
• Correct application of the stall recovery procedure
• Recovering without exceeding the airplane's limitations

The AC adds that the check pilot establishes the flight conditions and that you may fly the entry profile but are not being checked on the entry — except for recognition of the deteriorating flight situation (para 4-4). You are graded from the cue forward, plus whether you saw it coming.

The one set forth in the POH/Flight Manual for the airplane (AA.V.B.S6). AC 120-109 defines the stall recovery procedure as the correct, airplane-specific actions developed by the operator in consultation with the airplane manufacturer; only if consultation is impracticable does the stall recovery template in Appendix 1 apply. Know your operator's procedure verbatim, and know that it maps onto the template:

1. Disconnect the autoflight
2. Reduce AOA
3. Roll wings level
4. Manage thrust
5. Retract speed brakes
6. Return to the flightpath

The boundary layer on a swept wing tends to flow spanwise toward the tips, and the tendency for tip stall — allowing the center of lift to move forward — is greatest when wing sweep and taper are combined (AFH ch. 16). A forward shift in the center of lift is a nose-up pitching moment at exactly the wrong moment. Manufacturers fight it by modifying the wing spanwise with twist, changes in airfoil section, vortex generators, or a combination, which helps you retain roll control initially if a stall is entered inadvertently. Note the consequence for cues: airplanes without vortex generators may stall with little to no buffet (AFH ch. 16).

Some T-tail configurations are prone to deep stalls, where the tail becomes immersed in the wing wake at very high angles of attack and loses effectiveness, often with a high rate of descent (AFH ch. 16). It feels wrong because high angles of attack can occur at any pitch attitude — even with the nose below the horizon — so the correct action is to push the nose down even further. The AFH warning: deep stalls may be unrecoverable, but they are easily avoided as long as published limitations are observed. On susceptible types, stick shakers are standard equipment and a stick pusher may be fitted.

A stick pusher applies an abrupt and large forward force on the control column (AFH glossary) to automatically reduce the airplane's AOA before the airplane reaches a dangerous stall condition, or to aid recovery where the airplane's natural aerodynamic characteristics do so weakly (AFH ch. 16). Two conclusions. First, pusher activation is an indication of a full stall (AC 120-109 definition; AFH ch. 5) — if it fires on the check, the impending stall was not prevented. Second, avoid situations that would activate a stick pusher when close to the ground (AFH ch. 16). Under 121.423(c), full stall and stick pusher activation recovery is instructor-guided training in a Level C or higher FFS, not a check maneuver.

The AFH states the training standard directly: pilots undergoing training in jet airplanes are taught to recover at the first indication of an impending stall instead of going beyond those initial cues and into a full stall — normally indicated by aural stall warning devices, annunciators, or activation of the stick shaker. The proper action is a nose-down input until the stall warning stops (pitch trim may be necessary), then roll wings level, then adjust thrust to return to normal flight (AFH ch. 16). The AFH also frames the division of labor cleanly: reducing AOA eliminates the stall, but added thrust allows the descent to be stopped once the wing is flying again.

By doing exactly what it was told. An autopilot holding an altitude or a vertical path will trim nose-up as speed decays, quietly consuming your maneuver margin, and AC 120-109 notes that reducing AOA in the recovery also addresses autopilot-induced excessive nose-up trim (Appendix 1 rationale, step 2a). When it can hold no longer, the abrupt pitch-up or trim change at an unexpected autopilot disconnect hands you a physical problem on top of an aerodynamic one, and in some airplanes an additional pitch-up when thrust is increased (para 4-2). AA.V.B.K4 asks about envelope protection in normal and degraded modes — answer for your type from the AFM and FSB report, never generically.

AC 120-109 defines startle as an uncontrollable, automatic muscle reflex, raised heart rate, blood pressure, etc., elicited by exposure to a sudden, intense event that violates a pilot's expectations — and identifies surprise as a factor in stall incidents and accidents. The AC therefore encourages using surprise in training, to reinforce timely application of the recovery under confusing circumstances, while stating that surprise should not be used during checking (definition at para 1-7p; the training guidance is para 4-3, "Using Surprise in Training"). It also notes the practical confusion source: noises associated with stick shakers, autopilot, and autothrottle/autothrust disconnect alarms can cause confusion in the cockpit (para 4-2). This is why the procedure is memorized in an order — startle is survived by sequence, not by improvisation.

AC 120-109 defines maneuver-based training as training that focuses on a single event or maneuver in isolation, and scenario-based training (SBT) as training that incorporates maneuvers into real-world experiences to build practical skills in an operational environment. SBT normally comes after you demonstrate proficiency in maneuver-based training, during upgrade and recurrent training, and its scenarios should draw on accident, incident, ASAP, FOQA, and ASRS data. Pilots are not normally briefed that they are receiving SBT — and if you recognize and prevent the stall before the scenario fully unfolds, that is the desired objective (para 4-2). Area V is the maneuver-based half; the line-oriented half is where the prevention skill is actually proven.

Landing configuration means the landing gear extended and the flaps set at an approved setting for a normal landing (AC 120-109). The skill element requires you to establish that configuration — lift/drag devices set and landing gear extended — and maintain coordinated flight throughout the maneuver, in simulated or actual instrument conditions (AA.V.C.S3). If your operator authorizes more than one landing flap setting, know which one the evaluator specified and say it back.

• Clear the area; entry altitude must allow the recovery to be completed no lower than 3,000 feet AGL (non-transport category) or 5,000 feet AGL (transport category) (AA.V.C.S1)
• Bank 15°–30°, with pitch attitude and power adjusted smoothly per the evaluator's instructions to an impending stall, manually or with the autopilot engaged (AA.V.C.S4)
• Coordinated flight in simulated or actual instrument conditions throughout (AA.V.C.S3)
• Acknowledge the cue(s) and promptly recover at the first indication of an impending stall (AA.V.C.S5)

Note the entry altitude is identical across all three stall prevention Tasks — the landing configuration is not flown at a lower entry altitude just because it models a low-altitude event.

Stalls at a low altitude (AA.V.C.R7). The other two Tasks stop at inadvertent stall, spin, and loss of control; this one names the altitude problem directly, because the landing configuration is the one you are actually in when close to the ground. The practical content of that risk: there may be no altitude available to trade, which is precisely why the standard is prevention at the first indication rather than recovery from a developed stall. AC 120-109 directs training at low altitudes within 500 feet AGL as well as near maximum altitude (para 4-2).

No — this is the single most important reversal in modern stall training. AC 120-109: reducing AOA is the most important pilot action in recovering from an impending or full stall, and pilots must accept that doing so will normally result in altitude loss. Recovery profiles that emphasized zero or minimal altitude loss and immediate maximum thrust have been eliminated (para 2-5). The AFH makes the same point from the accident record: pilots who did not first reduce AOA and instead prioritized power and maintaining altitude lost control (AFH ch. 5). Low altitude raises the stakes of getting the wing flying again; it does not change the method.

Fly your POH/FM procedure (AA.V.C.S6), which should map onto the AC 120-109 template:

1. Autopilot and autothrottle/autothrust — disconnect
2. Nose-down pitch control until impending stall indications are eliminated; nose-down trim as needed
3. Bank — wings level
4. Thrust — as needed
5. Speed brakes/spoilers — retract
6. Return to the desired flightpath, gently

Configuration cleanup: retract flaps or other lift/drag devices to the recommended setting, and retract the landing gear after a positive rate of climb is established, before returning to the flight path the evaluator specifies (AA.V.C.S7).

Because the ACS requires it — retract the landing gear only after a positive rate of climb is established, if applicable (AA.V.C.S7) — and because sequence matters when you are trading altitude for AOA. Neither the ACS nor AC 120-109 explains the why; take the rest of this as instructor reasoning rather than standard: until the wing is flying and the vertical trend has reversed, the gear is your evidence of state, and an early retraction removes the option of touching down on wheels if the recovery is at low altitude. Flaps go to the recommended setting, not to zero: retracting flaps fully at low speed raises the stall speed at exactly the wrong moment. Command and confirm each change with the pilot monitoring.

Icing is the one environmental element unique to the landing configuration among the three stall prevention Tasks (AA.V.C.R6). Its effects:

• Earlier stall: contamination changes the wing's critical AOA so the stall arrives earlier than the airspeed suggests; the AFH warns that wing contamination limits the effectiveness of an AOA indicator (AFH ch. 5)
• Weaker cues: with ice, aerodynamic stall may occur with little or none of the usual advance cues — buffet, reduced control effectiveness, stall warning horn, shaker, or pusher — and stall speed increases as high as 50 knots have been observed in post-upset data review (AC 61-67, para 102)
• Recovery: a prompt pitch-down with aggressive power application gives the most rapid recovery with minimum altitude loss; note the AOA (or airspeed) at the upset and do not approach it again during the recovery, since it may be well below the normal stall AOA
• Equipment: AC 120-109 also lists the effects of malfunctioning or deferred equipment on stall protection and stick pusher systems (para 4-2) — a deferred heated probe or an inoperative ice protection component changes what your warnings are worth

Refer to the AFM for contaminated-wing approach speed additives; this guide will not assert them.

AA.V.C.K3 asks for the factors and the prevention. Realistic ones:

• An unstabilized approach — high, fast, and configuring late, then decelerating below target with idle thrust and spool-up time working against you
• A slam-dunk or short-notice runway change compressing the descent and the configuration schedule
• Windshear or a microburst on short final (AA.V.C.R6)
• An overshooting base-to-final turn corrected with rudder — the classic cross-control, which the ACS lists under R5
• A late go-around with the airplane already slow, trimmed nose-up, and about to receive a large pitch couple with thrust
• Distraction and task prioritization failures during a busy, low-altitude segment (AA.V.C.R9)

Prevention is a go-around, taken early. The prevention decision is the checkride answer.

AA.V.C.R8 (and AA.V.A.R7 / AA.V.B.R7 in the sibling Tasks) names collision hazards, including aircraft and terrain. It shows up in three places:

• Before the entry — the skill element opens with clear the area and an entry altitude that lets the recovery finish no lower than 3,000 ft AGL (non-transport) or 5,000 ft AGL (transport) (AA.V.C.S1). The altitude floor is the terrain mitigation for the maneuver.
• During the recovery — AC 120-109 is unambiguous about the conflict you are most likely to meet down low: if a TAWS warning is encountered during recovery from a low-altitude stall event, recovery from the stall warning takes precedence; you fly the TAWS escape maneuver only once the airplane has recovered from the stall event (para 3-2a). You cannot pull to a terrain escape with the wing still stalled.
• After the recovery — situational awareness while returning to the desired flightpath — heading, terrain, altitude, other aircraft, and flight deck automation — is among the emphasis areas in the AC's sample lesson plans (Appendices 3–4). This is where the pilot monitoring's traffic and terrain scan, and the deviation call to ATC, belong.

The ACS lists secondary stalls, accelerated stalls, elevator trim stalls, and cross-control stalls among the risks for all three stall prevention Tasks (AA.V.C.R5), but the elevator trim case belongs to the landing configuration by scenario: the airplane is trimmed for a low approach speed, then thrust is applied for a go-around, and the nose-up trim plus the thrust couple produce a pitch-up the pilot must physically overpower. AC 120-109 anticipates the same physics from the other direction — an abrupt pitch-up or trim change at an unexpected autopilot disconnect, aggravated in some airplanes by an additional pitch-up when the pilot increases thrust (para 4-2). The answer in both cases is forward column plus nose-down trim as needed — template step 2.

Measure yourself against the AC 120-109 checking criteria (para 4-5): prompt recognition of the impending stall, correct application of the stall recovery procedure, and recovering without exceeding the airplane's limitations. Concretely, that means failing to acknowledge the cue and recover at the first indication (AA.V.C.S5); letting it progress to a full stall or a stick pusher activation; losing coordinated flight (AA.V.C.S3); exceeding an airplane limitation to get out of it; or mishandling the cleanup sequence.

Two things commonly assumed to be bust items are not:

• Altitude loss: not a failure item by itself — criteria "should not focus on altitude loss" (para 4-5), and there is no predetermined value
• Secondary stall warning: not automatically a failure item either — AC 120-109 notes it can be difficult in some airplanes to judge where pitch can begin to be increased, and a secondary warning is acceptable as long as AOA is promptly reduced and the airplane's limitations are not exceeded (para 4-2a). What fails you is not reducing AOA promptly, or exceeding a limitation — not the second chirp.

Anchor it to your operator's manual, not to a number you memorized elsewhere — stabilized approach gates are operator- and type-specific, published in the FOM or GOM, and the ACS points you to the FSB Report (type specific) and POH/AFM. State these without needing a reference:

• The gate is a decision point
• The required outcome when the criteria are not met is a go-around
• An early go-around is the answer the evaluator is looking for — the ACS frames K3 as the actions that can be taken to prevent the stall, and a go-around taken before the margin is gone is that action

Treat the relative grading weight of a go-around as instructor judgment, not published criteria; the only published checking criteria are the three in AC 120-109 para 4-5. Frame the prevention as an energy-management call: configuration, thrust, and flight path committed early enough that the airplane is never asked to fly slower than it can.

It costs you the classic overshooting-turn skid at high AOA — corrected with bottom rudder on the turn to final, more than you'd risk in cruise. The ACS risk for this Task is inadvertent stall, spin, and loss of control during landing (AA.V.C.R1), and sideslip effects appear in the knowledge element (AA.V.C.K1). The AFH warns that even the instinct to pick up a dropping wing with aileron can make it worse — a downward-deflected aileron produces greater AOA and more induced drag on that wing and a more complete stall at the tip, why it's important to first reduce AOA before attempting to roll (AFH ch. 5). Template order — pitch, then bank — exists for this reason.

Enough to explain why prevention is the only real answer down low.

• Definition: a spin is an aggravated stall that results in autorotation — the rising wing is less stalled than the descending wing, and the airplane follows a downward corkscrew path (AC 61-67)
• Cause: exceeding the critical AOA while applying excessive or insufficient rudder (para 109)
• Direction: follows the feet — in a skidding turn (aileron and rudder in the same direction), rotation goes in the direction the controls are applied; in a slipping turn, the spin usually breaks opposite the aileron being held
• Recovery: the PARE order you learned in primary training — power to idle, ailerons neutral, full opposite rudder, then briskly move the elevator forward to about neutral; neutralize the rudder when rotation stops and gradually recover from the dive. Abrupt aft elevator or rudder/aileron inputs during the recovery can produce a secondary stall and another spin (AC 61-67, para 111)
• Altitude: roughly 500 feet of altitude loss per 3-second turn in most small aircraft in which spins are authorized, more at high density altitude

A base-to-final spin has no recovery altitude — which is why the graded skill is coordination throughout (AA.V.C.S3), not spin recovery.

• Synthetic cues come first and are what you act on: stick shaker, aural warning, annunciator. A shaker normally activates around 107 percent of the actual stall speed (AFH ch. 16) — roughly a 7 percent margin, a handful of knots at approach speeds.
• Aerodynamic buffet may be a poor cue — airplanes without vortex generators may stall with little to no buffet (AFH ch. 16); buffet severe enough to be a strong and effective deterrent to further AOA increase is a full stall indication, not an impending one (AC 120-109 definition).
• Feel: control pressures lighten and larger control movements are needed for the same response, with increased reaction time (AFH ch. 5).
• Descent rate: in a power-off, 1G stall the predominant cues may be full-up elevator against the stops and a high descent rate (AFH ch. 5) — a cue that is nearly invisible from inside a stabilized-looking approach attitude.

The procedure does not change; the margins do. AC 120-109 directs that training include stall events at low altitudes within 500 feet AGL (para 4-2), because the crew has to execute the identical sequence with a fraction of the altitude. Practically:

• The pilot monitoring's most valuable call is the prevention call — deviation from the approach criteria, sink rate, or speed trend — before any warning fires
• Once the cue fires, the pilot flying announces and flies the recovery; the pilot monitoring confirms the autoflight disconnects, calls radio altitude and vertical trend, and handles the go-around, ATC, and any emergency declaration
• Configuration changes stay commanded and confirmed — flaps to the recommended setting, gear up after a positive rate (AA.V.C.S7)

AC 120-109 defines CRM as the effective use of all available resources: human resources, hardware, and information (para 1-7b) — at 500 feet, the pilot monitoring's voice is the resource that matters.

You can't — AC 120-109 says so directly: do not delay recovery due to degrading airspeed or a stall event to obtain ATC clearance to a lower altitude; declare an emergency if necessary (para 4-2). On a low approach the practical version is that you may deviate from the assigned altitude, the missed approach path, or the speed assignment to fly the recovery, and you coordinate afterward. Priority order: only after recovering to a safe maneuvering speed and AOA do you re-establish the assigned heading, altitude, and airspeed.

Under 121.423, stall prevention lives inside extended envelope training:

• Simulator: conducted in a Level C or higher full flight simulator approved under 121.407, with instructor-guided hands-on experience of recovery from full stall and stick pusher activation, if equipped (121.423(a), (c))
• Maneuvers: the neighborhood this Task lives in also includes manually controlled slow flight, manually controlled loss of reliable airspeed, manually controlled instrument departure and arrival, upset recovery maneuvers, and recovery from bounced landing (121.423(b))
• Recurrency: 24 calendar months for items (b)(1) through (4) and (c); 36 calendar months for the bounced landing item (121.423(d))
• Deviations: from the Level C simulator requirement may be approved for periods not to exceed 12 months (121.423(e)(4))

Two things: how early the visual world disappears, and how tight the numbers are. The evaluator simulates IMC at or before 100 feet AGL — and in a full flight simulator the visibility is set to no greater than ¼ mile, or as specified by the applicable operations specifications, whichever is lower (AA.VI.A.S7; ACS Appendix 3). From there you must hold heading ±5° and airspeed ±5 knots (AA.VI.A.S12) while retracting gear and flaps, following the flight director, and complying with the clearance. The task is graded as a crew evolution: checklists coordinated and completed in a timely manner before takeoff (S1) and after (S14), with callouts per the operator's procedures (S9).

Takeoff minimums apply to operations under parts 121, 125, 129, and 135 — not part 91. Use the minimums prescribed for the airport under part 97; if none are prescribed:

• Two engines or less — 1 statute mile visibility
• More than two engines — ½ statute mile visibility (91.175(f)(2))

And notwithstanding any ATC clearance, no takeoff when reported weather is below the certificate holder's OpSpecs minimums (121.651(a)). Through OpSpecs, operators with the required equipment, training, and runway visual aids — HIRL, centerline lights, centerline markings — can be authorized lower-than-standard minimums as low as 1600 RVR or ¼ SM with those basic visual aids (IPH ch. 1) — and lower still with additional RVR reporting, lighting, and equipment authorizations in the OpSpecs.

Yes — takeoff minimums are typically lower than landing minimums (IPH ch. 1) — but the release must name a takeoff alternate (121.617). If departure weather is below the landing minimums in the OpSpecs for that airport, the dispatch or flight release must specify an alternate within:

• 1 hour at normal cruising speed, still air, one engine inoperative — airplanes with two engines
• 2 hours, same conditions — airplanes with three or more engines (121.617(a))

That distance rule exists for exactly the risk this task names: engine failure in the takeoff/climb phase with ceiling or visibility below approach minimums at the departure airport (AA.VI.A.R3b). Brief where you're going before you need it.

The ACS expects the briefing to cover, as appropriate (ACS Appendix 3):

• Departure runway
• Departure procedure
• Power settings
• Speeds
• Abnormal or emergency procedures before or after decision speed (V1 or VMC)
• Emergency return intentions
• What the applicant expects other crewmembers to do during the takeoff and departure

If the operator or manufacturer hasn't specified one, brief it once well; the evaluator may then let you brief only the changes for the rest of the test. Single pilot? You still verbalize it.

• Avionics and flight instruments properly set — FMS, flight director, heading bug, altitude preselect, nav sources (S2)
• Assigned/correct runway verified (S4) — then clear the area, taxi into position, and align on the centerline (S6)
• Flight controls positioned for the existing wind (S5)
• Radio calls as appropriate (S3)

The instrument takeoff punishes a rushed lineup: the IFH lists improper runway alignment — creeping after alignment, nosewheel cocked — as a classic error, a built-in directional control problem before the roll even starts (IFH ch. 7).

Maintain centerline with proper flight control inputs during the roll (AA.VI.A.S8), and confirm takeoff power and proper engine and flight instrument indications prior to rotation, making callouts for the airplane or per the operator's procedures (S9). Then rotate at the recommended airspeed, establish the desired pitch attitude, and accelerate to the desired airspeed/V-speed (S10). Which speeds and which callouts are type- and operator-specific — fly your AFM numbers and your company's flow. What's universal is the discipline: power set and verified, instruments alive and agreeing, before VR.

Smoothly and on schedule — the cues may be gone by 100 feet AGL. A sudden, rapid transition from visual to instrument flight can cause serious disorientation and control problems, the whole reason instrument-takeoff competency exists (IFH ch. 7). The handbook's practical discipline:

• Hold the established pitch attitude on the attitude indicator through gear and flap retraction — control pressures change and overcontrolling is likely unless you read the pitch indications accurately
• Trim off the pressures
• Keep the cross-check rapid through every configuration and power change (IFH ch. 7)

Failure to maintain attitude after liftoff — chasing seat-of-the-pants sensations — is on the IFH's common-error list. The ACS names the underlying risks: distractions, task prioritization, loss of situational awareness, or disorientation (AA.VI.A.R6).

The knowledge element is a planning checklist for the low-visibility case:

• Runway length, lighting, and surface conditions — enough runway and enough visual aids to keep centerline at ¼ mile vis
• Wind and wake turbulence (also AA.VI.A.R2)
• Icing conditions
• Obstructions in the departure path
• Available instrument approaches or alternate airports in the event of an emergency after takeoff — can you get back in, and if not, where exactly are you going?

Each of these feeds the runway-selection risk element (R1) and the abnormal-ops planning element (R3): rejected takeoff, and engine failure with weather below approach minimums.

• Collision hazards (R4) — at ¼-mile visibility they live mostly on the surface: aircraft and vehicles you won't see until they matter. The mitigations are procedural: verify the assigned/correct runway (S4), clear the area before lineup (S6), comply exactly with ATC clearances and hold-short instructions (S13), and use published low-visibility taxi routes where they exist. Airborne, separation is ATC's — precise clearance compliance is what keeps it that way.
• Low altitude maneuvering — stall, spin, or CFIT (R5) — over-rotating or chasing the flight director at low energy erodes stall margin you can't see out the window; turning early or drifting off the departure procedure gives away the obstacle protection the departure design assumed (Task VI.B). The defense is the task's own standard: pitch attitude set and held, heading ±5°, airspeed ±5 knots (S12), nothing nonessential until clean and climbing on the procedure.

The decision itself is briefed the same way — abnormals before or after decision speed (ACS Appendix 3) — but the margins shrink. A reject in ¼-mile visibility means stopping on a runway you can barely see, so the brief must be concrete: who calls it, who does what, and what the stop margins are for today's weight and surface condition. The ACS treats rejected takeoff as a planning risk for this task (AA.VI.A.R3a); the maneuver itself is tested under Area III, Task I. The low-visibility twist that belongs here: after any reject, hold your instrument discipline — taxiing clear in low visibility is its own threat.

Adapted for any airplane (IFH ch. 7):

1. Align with the centerline, nosewheel straight; hold the brakes to avoid creeping
2. Set the heading reference on the runway heading so any swerve shows instantly
3. Power smoothly to takeoff setting — abrupt application complicates directional control
4. Rudder for heading during the roll; avoid brakes except as a last resort
5. Approaching flying speed, smoothly set the takeoff attitude on the attitude indicator
6. At a safe altitude, gear and flaps up, holding attitude on the AI through the trim changes
7. Confirm the climb: altimeter and airspeed increasing, vertical speed stable — then trim and set climb power

In a transport-category airplane the same skeleton holds; your operator's callouts and the flight director overlay it, they don't replace it.

From IFH ch. 7:

• Inadequate flight deck check — pilots have attempted instrument takeoffs with obstructed pitot tubes, caged gyros, and locked controls. This one is fatal to AA.VI.A.S2.
• Improper runway alignment — a built-in directional problem (S6)
• Abrupt power application (S8)
• Overcontrolling the rudder — late recognition, correcting the wrong way
• Failure to maintain attitude after liftoff — pitch by guesswork (S10, S11)
• Inadequate cross-check — fixating during trim, gear, flap, and power changes

The last one is the quiet killer of the ±5° / ±5-knot standard (S12): every fixation shows up as a drift.

The ACS grades coordination explicitly — coordinate with crew and complete the appropriate checklists in a timely manner before takeoff (AA.VI.A.S1) and after (S14), with callouts per the operator's procedures before rotation (S9). Fly your company's split; the pattern to be able to describe:

• Pilot flying: centerline, rotation, attitude, flight path
• Pilot monitoring: verifies takeoff power set, monitors engine and flight instruments, makes the deviation and standard speed callouts, handles radio calls (S3), and backs up the after-takeoff flow

The task also requires complying with ATC clearances and instructions issued by ATC or the evaluator (S13) — in a crew, that's the PM's radio and the PF's execution, cross-verified.

The tolerances are:

• Airspeed: ±10 knots
• Heading: ±10°
• Altitude: ±100 feet

These apply while accurately tracking a course, radial, or bearing (AA.VI.B.S8). Intercepts must be timely (S6), all charted procedures complied with (S7), and the departure flown until the evaluator judges the transition to the en route environment complete (S9). Note the contrast with this Area's approach tasks: the ±5-knot, ¼-scale world starts on final — the departure standard is the familiar instrument-rating envelope, flown with a jet's momentum.

You must be able to say yes to all of it (IPH ch. 1):

• The ability to comply with the required performance — if you cannot meet the climb gradient in the SID, do not accept the clearance, and do not accept the procedure if ATC assigns it
• The ability to navigate to the required accuracy
• Possession of the charted procedure
• Personal understanding of the SID in its entirety

The ACS makes gradient compliance a named risk (AA.VI.B.R1). And remember what TERPS assumes: departure design considers obstacle protection only — it assumes all engines operating and does not consider your airplane's performance. Engine-out procedures are the operator's responsibility (IPH ch. 1).

"Climb via" is an abbreviated clearance requiring compliance with the procedure's lateral path and the associated speed and altitude restrictions along the cleared route (IPH ch. 1). It's the departure twin of "descend via" on a STAR. In an FMS airplane this is an automation-management item (AA.VI.B.R3): the charted restrictions must be in the box and verified against the chart — programming the FMS prior to departure and setting the flight director and autopilot controls for the departure is a graded skill (AA.VI.B.S2), and the database must be current and appropriate (S4).

Design assumes crossing the DER at least 35 feet up, climbing to 400 feet above DER elevation before the first turn, and a minimum climb gradient of 200 ft/NM unless a higher gradient is published (IPH ch. 1). Convert with groundspeed: the IPH example — a required gradient of 297 ft/NM at 180 knots groundspeed requires about 892 fpm (IPH ch. 1, rate-of-climb table). Every TPP booklet carries the table. The airline-scale trap: gradients are easy at V2 and harder as the airplane accelerates — groundspeed, not airspeed, sets the required rate.

A departure option for an IFR aircraft, operating in VMC at or above the specified ceiling and visibility, to conduct visual climbing turns over the airport to the published "climb-to" altitude, then proceed on the instrument portion of the departure. A VCOA is developed when obstacles farther than 3 SM from the airport require a climb gradient of more than 200 ft/NM — you trade the gradient for circling climbs in visual conditions. It's published in the Takeoff Minimums and (Obstacle) DP section of the TPP, and pilots are required to notify ATC when executing one (IPH ch. 1).

A DVA lets ATC issue random radar vectors to departing traffic below the MVA or minimum IFR altitude — the area has been assessed to diverse-departure TERPS criteria for obstacle and terrain avoidance. Its existence is noted in the Takeoff Minimums and ODP section of the TPP.

Cautions from the IPH:

• A DVA may require a climb gradient greater than the standard 200 ft/NM (stated in the DVA text)
• The assessment covers departures that remain within the specified area
• Obstacle clearance is not provided by ATC until the controller begins providing navigational guidance (IPH ch. 1)

91.185. If you encounter VFR conditions, continue VFR and land as soon as practicable (91.185(b)). Otherwise fly:

Route: assigned; if being vectored, direct to the fix, route, or airway specified in the vector clearance; then expected; then filed (91.185(c)(1)).

Altitude: the highest, for each route segment, of last assigned, the minimum IFR altitude, or the altitude ATC advised to expect (91.185(c)(2)).

The vector case is the departure-specific edge: on a radar SID, the "fix specified in the vector clearance" is your lifeline. Know the first fix and the top altitude before brake release — that's part of understanding the SID in its entirety (IPH ch. 1).

Obstacles within 1 NM of the DER that penetrate the 40:1 obstacle clearance surface — published in the TPP (IPH ch. 1). They're too close for a gradient to fix; the note tells you what and where they are so you can see and avoid, or plan the runway differently. For a jet with a long takeoff roll and screen-height crossing near 35 feet, the margin over a close-in obstacle can be thinner than the chart's tidy gradient suggests — this feeds the runway-selection and performance judgment the departure briefing has to carry.

• Load, don't build: select the procedure and transition from the current navigation database (S4) and compare the FMS legs — fixes, courses, altitude and speed restrictions — against the charted procedure
• Set the flight director and autopilot controls for the initial clearance: heading or nav mode, altitude preselect to the first limit, speed target per the profile (S2)
• Confirm the navigation source the guidance will follow, and identify ground-based facilities as necessary (S1)
• Brief the automation plan out loud: what mode flies the runway heading segment, where nav engages, what the first level-off is

The graded failure mode isn't a dead box — it's a clean-looking departure flown in the wrong mode. State mode changes, confirm captures, and keep raw data in the scan.

Reprogram, verify, rebrief — in that order, and before the takeoff if workload allows. The pilot not flying makes the FMS change; both pilots compare the new route against the amended clearance; the parts of the briefing that changed get rebriefed (ACS Appendix 3 allows briefing only the changes after the first satisfactory briefing). The task's communications skill wraps this: establish two-way communications, use proper phraseology, and comply in a timely manner with all ATC instructions and airspace restrictions (AA.VI.B.S5). A rushed runway change is exactly where a wrong-transition departure gets loaded and flown.

When you accept a SID or radar vectors, ATC is responsible for traffic separation — but you're expected to remain vigilant scanning for traffic when departing in visual conditions, and to notify ATC if a clearance would endanger safety (IPH ch. 1). The risk element pairs that with the limitations of traffic-avoidance equipment: your traffic display supplements see-and-avoid, it doesn't replace it. Fly the procedure as charted — the design considers obstacle clearance — and keep eyes outside while the weather allows it.

From IPH ch. 1:

• Non-RNAV DP — flown with conventional ground-based NAVAIDs (some FMSs are certified to fly these from conventional sensor inputs)
• RNAV DP — for RNAV-equipped aircraft (GPS, VOR/DME, DME/DME); automated vertical navigation is not required; RNAV procedures not requiring GPS carry "RADAR REQUIRED"
• Radar DP — ATC vectors you to a route, NAVAID, or fix; "RADAR REQUIRED" is annotated

The departure task expects you to select the appropriate procedure and the facilities that go with it (AA.VI.B.S1); AC 90-100 is the ACS's reference for U.S. terminal and en route RNAV operations.

Airspeed/V-speed ±10 knots, but not less than reference landing approach speed (VREF) if applicable; heading ±10°; altitude ±100 feet, accurately tracking radials, courses, and bearings (AA.VI.C.S10). The VREF floor is the transport-category tell: on an arrival you're decelerating on a schedule, and the standard forbids buying tolerance by getting slow. You must also adhere to airspeed restrictions required by regulation, procedure, aircraft limitation, ATC, or the evaluator (S8) and establish descent rates consistent with the route segment, airplane operating characteristics, and safety (S9).

• "Cleared HADLY ONE arrival" — lateral routing only; charted altitudes are not authorized
• "Cleared HADLY ONE arrival, descend and maintain FL240" — descend only to the assigned altitude and hold it until cleared lower
• "Descend via the HARIS ONE arrival" — fly the lateral path and descend per the charted altitude restrictions
• "Descend via … except cross BRUNO at one three thousand then maintain one zero thousand" — the arrival with named exceptions, then the assigned altitude
• "Proceed direct MAHEM, descend via the MAHEM TWO arrival" — direct to the fix, then lateral and vertical per the chart

The ACS's added risk element is exactly this: ATC instructions that modify an arrival or discontinue/resume lateral or vertical navigation (AA.VI.C.R5). Restate what's still yours to fly and what just changed.

Not by themselves. Expected altitudes and airspeeds on a STAR are not part of the clearance until ATC includes them verbally — a STAR is a published routing that does not have the force of a clearance until issued specifically by ATC. MEAs printed on a STAR are not valid unless stated in the clearance — or in cases of lost communication (IPH ch. 3). That last clause is the arrival version of the comm-failure question (AA.VI.C.K4): radios gone, the charted altitudes come alive as your minimum IFR altitudes under 91.185(c)(2).

STARs typically include a descent gradient of about 318 ft/NM — about three degrees — varying to meet altitude restrictions, and they allow deceleration segments at waypoints with speed restrictions, typically adding 1 NM of distance for each 10 knots of speed reduction (IPH ch. 3). Rules of thumb for the raw-data cross-check: divide altitude-to-lose by 300 for the distance to start down, and multiply groundspeed by 5 for the 3° descent rate — 120 knots means 600 fpm (IPH ch. 3). If the box's path and your mental math disagree, believe the disagreement and investigate.

RNAV STARs are designated RNAV 1 or RNAV 2; the designation appears in the chart notes. RNAV 1 STARs carry higher equipment requirements and often tighter RNP tolerances, and require pilots to use a CDI/flight director and/or autopilot in LNAV mode while operating on RNAV courses (IPH ch. 3).

Setup sequence:

1. Load the arrival from the current database (S4)
2. Verify legs against the chart
3. Set the guidance for the arrival (S2)

Know what your VNAV path is built from — aircraft performance, approach constraints, weather data, and weight — computed from top-of-descent to the end-of-descent waypoint (IPH ch. 3).

Nav-system fundamentals — orientation, interference, signal integrity (K5) — are unchanged from the instrument rating and covered in the IFR guide; the ATP delta is verifying the airplane and crew meet the arrival's RNAV 1 or RNAV 2 requirement before accepting it.

On the charted arrival or vectors, ATC provides IFR separation — but the ACS keeps the responsibility to use see-and-avoid techniques when possible on you (R3), and an arrival descends you through the busiest traffic mix of the flight, often in and out of visual conditions. The paired risk is the equipment (R2): the traffic display and its alerts supplement the scan, they don't replace it — they only show traffic equipped to be seen, and display range and update limits mean the picture is never complete. The departure-side version of this contract is developed under Task VI.B; the arrival deltas: eyes outside whenever the weather allows, and identify the traffic you're following before accepting a visual approach behind it.

The IPH's example schedule: plan 250 knots at 25 NM from the threshold, 200 knots at 20 NM, 150 knots at 15 NM until reaching gear and flap speeds — never below approach speed (IPH ch. 3). That last clause is the same floor the ACS writes into the tolerance (not less than VREF, AA.VI.C.S10). The planning point: energy is altitude plus speed, and a "slam-dunk" clearance that's fine on altitude can still be unflyable on speed — say "unable" early rather than diving and decelerating at the bottom.

Altitude is the highest, per route segment, of assigned, minimum IFR altitude, or expected (91.185(c)(2)) — and on a STAR the charted altitudes become valid minimums in lost comm (IPH ch. 3). At the clearance limit:

• If it's a fix from which an approach begins — start descent/approach as close as possible to the EFC if received, otherwise the flight-planned ETA (91.185(c)(3)(i))
• If it's not such a fix — leave the limit at the EFC, or if none, upon arrival over it, proceed to an approach fix, and begin descent/approach as close as possible to the ETA (91.185(c)(3)(ii))

Because the arrival is a critical phase of flight and altitude/course deviations cluster there. The IPH points at the sterile flight deck rules — no duties during a critical phase except those required for the safe operation of the aircraft, and no non-essential activity permitted by the PIC (IPH ch. 3, citing 135.100; the part 121 rule is its parallel). Company calls, PA announcements, paperwork — all deferred. On the checkride this shows up as crew coordination and checklists completed in a timely manner, without burying the monitoring pilot during the descent (AA.VI.C.S3).

Three questions, answered out loud as a crew:

• Lateral: am I still on the charted path, or on a vector? If vectored off, the arrival's altitudes and speeds no longer apply until ATC clears you to rejoin
• Vertical: what altitude am I cleared to right now — a "descend via" that was interrupted does not silently resume; expect ATC to restate the vertical clearance
• Speed: which restrictions were deleted — charted ones, ATC-assigned ones, or both — and what does the FMS think? The box may still command the old profile

Then make the FMS match the clearance, not the other way around. This is the automation-management risk (R4) in its most common form.

Monitor with the same raw-data habits the task grades for tracking (AA.VI.C.S10):

• Distance vs. altitude: divide altitude-to-lose by 300 for the distance a 3° path needs (IPH ch. 3) — check it at every crossing restriction
• Descent rate: groundspeed × 5 for the 3° rate; a rate wildly above that means the path is steep or the winds have shifted
• Next constraint: verbalize the next fix, its altitude and speed, and whether the airplane will make it — before the FMS has to prove it
• Deceleration: 1 NM per 10 knots (IPH ch. 3) — if the box needs to slow 60 knots in 3 miles, it won't

The MFD's profile awareness supplements this, but the barometric altimeter and the chart remain the authority.

The tasks in this Area share the ACS Appendix 3 briefing standard — cover what applies, then brief only changes later in the test. For the arrival, the load-bearing items:

• Runway and approach to expect — broadcast by ATIS or the controller when there are two or more published procedures, and possibly not provided when visibility is 3 SM or better and the ceiling is at or above the highest initial approach altitude (IPH ch. 3)
• Descend-via status
• Crossing restrictions you personally consider bust-risks
• Deceleration plan
• Transition from the STAR's termination — charted route to an IAF, or a plan for vectors if none is depicted (IPH ch. 3)

A STAR provides the transition from the en route structure to an approach gate, outer fix, instrument approach fix, or arrival waypoint, usually terminating with an instrument or visual approach procedure (IPH ch. 3). For STARs charted with radar vectors to final, look for routes from the terminating fixes to the IAF — if no route is depicted, have a predetermined plan of action to fly from the STAR's end (IPH ch. 3). That plan is also your comm-failure answer for the last ten miles: know which fix you'd proceed to and which approach you'd fly.

Everything tightens on final. Prior to the final approach segment: altitude ±100 feet, selected heading ±5°, airspeed ±10 knots, accurately tracking (AA.VI.D.S9). On the final approach segment: no more than ¼-scale CDI deflection, airspeed ±5 knots of the selected value, and altitude above MDA +50/−0 feet to the VDP or missed approach point (AA.VI.D.S12). Compare the instrument rating: ¾-scale, ±10 knots, MDA +100/−0. A third the lateral corridor, half the speed band, half the altitude window — flown in an airplane covering the final segment roughly twice as fast.

A ¼-scale deflection means the indication is displaced ¼ of the distance it may be deflected from the on-path indication (ACS Appendix 3, Vertical or Lateral Deviation Standard) — instrument markings vary, so the ACS defines it explicitly. On a five-dot display that's about one dot from center; on a two-dot display, half a dot. Know what a quarter of your scale looks like before the check, because the evaluator does.

At least two different non-precision approaches in simulated or actual IMC:

• At least one including a course reversal (procedure turn, hold-in-lieu, or the course reversal from an IAF on a Terminal Arrival Area (TAA))
• At least one from an IAF, without the autopilot and without radar vectors — the yaw damper and flight director are allowed
• One flown with backup or partial panel instrumentation or navigation display, representing a realistic failure mode for your avionics

Advisory vertical guidance may be used, and the evaluator decides whether each approach ends in a landing or a miss (ACS Appendix 3).

A DDA (derived decision altitude) is the altitude above the MDA where the go-around must begin, ensuring the airplane doesn't sink below the published MDA during the missed-approach transition (AC 120-108 para 3.7, citing 91.175) — necessary because pilots must not descend below the MDA once executing a miss. At the DDA there are exactly two courses of action: continue visually with the 91.175 references in sight, or execute the missed approach without descending below the MDA, proceeding on track to the MAP before any turn (AC 120-108 para 3.8.1). The +50/−0-foot skill tolerance (S12) is this discipline in miniature: the bottom of the window is hard.

Continuous descent final approach: a constant-rate, constant-angle descent from the FAF, timed to intersect the MDA near the point a normal landing descent continues to the runway — instead of dive-and-drive level-offs. It's built on the stabilized-approach concept: for turbojets, before descending below 1,000 feet above the airport or TDZE on any straight-in instrument approach —

• Approved landing (or circling) configuration
• Engines spooled up
• On speed and flight path
• Descent rate less than 1,000 fpm

(IPH ch. 4). The ACS folds the same components into its own definition — stable speed, stable descent rate, stable vertical path, and departure from the FAF configured for landing (ACS Appendix 3, Stabilized Approach Criteria). Cross the FAF at final approach speed, configured — especially on timing-dependent approaches (AC 120-108 para 3.6).

From the DDA:

1. Do not descend below the MDA
2. Unless ATC has issued climbout instructions, fly the published missed approach procedure
3. Proceed on track to the MAP before accomplishing any turn (AC 120-108 para 3.9)

The published miss provides obstacle clearance only from the missed approach segment at or above the MAP, assuming a climb of 200 ft/NM or higher as published (IPH ch. 4). Turning early trades protected airspace for hope.

What changes is the tolerance interaction: LP's sensitivity increases as you approach the runway, so the same ¼-scale standard demands progressively smaller corrections, exactly like a localizer. The definitions themselves don't change from the instrument rating — LNAV is linear-scaled lateral GPS guidance; LP uses WAAS for localizer-like angular guidance, published where terrain or obstacles preclude a vertically guided line — both flown to an MDA (covered in the IFR guide, Task VI.A). Know your navigator's annunciations cold (K2): the ACS expects you to recognize inaccurate or inoperative instrumentation and act (S5), and a mode that never activates is a mandatory miss, not a judgment call.

Select, tune, identify, and confirm the operational status of the navigation equipment to be used for the approach (AA.VI.D.S3). The risk the ACS names is selecting the wrong navigation frequency (R2) — classic setups: the localizer or VOR for a parallel or nearby procedure, the ILS tuned when the clearance is the VOR, or a CDI still showing GPS while the briefed needle is a localizer.

Defenses:

• Identify the facility (Morse ident or the navigator's decoded ident)
• Verify the loaded procedure's fixes against the chart
• Confirm the nav source annunciation on the display that's actually flying the approach

Signal-integrity and interference fundamentals (K3) are unchanged from the instrument rating — covered in the IFR guide; the ATP behavior is confirming status before the approach and acting on a loss-of-integrity annunciation when it appears (K2, S5).

Work the chart against reality:

• NOTAMs — procedure NOTAMs can raise minimums or make lines of minima unusable
• Inoperative aircraft or navigation equipment — losing a sensor may drop you to a higher line of minima
• Inoperative visual aids — apply the TPP's Inoperative Components Table; the IFH example: an ILS with a malfunctioning MALSR can be flown if minimum visibility is increased by ¼ mile — and watch for chart notes like "Inoperative Table does not apply to ALS" (IFH ch. 1)
• Aircraft approach category — flying final faster than your category's band means the higher category minimums apply (IPH ch. 4)

Under part 121 there's a gate before any of that matters: you may not continue past the FAF unless a weather report exists and reports visibility at or above the procedure's minimums (121.651(b)) — details under the precision task.

Unstable: any stabilized-approach component missing below the gate —

• Configuration not final
• Speed off target
• Descent rate excessive — greater than about 1,000 fpm below 1,000 feet is unacceptable in either the instrument or visual portion, a human-perception limit (IPH ch. 4)
• Flight path not established

Response: a go-around, decided by criteria, not by feel. The ACS treats attempting to salvage as the risk; the skill it wants is a stabilized descent to the appropriate altitude (S11) and a prompt miss when the picture isn't right (S13).

Plan to arrive at the DDA decision, not at a level-off. If the operator's CDFA procedure has you go missed at the DDA, the window takes care of itself — the airplane never levels at the MDA. If you do level (for example, running to a VDP on a timing approach), lead the level-off consistent with your descent rate, trim, and keep the FD or pitch reference on the horizon line rather than chasing the altimeter. The tolerance runs to the VDP or MAP (AA.VI.D.S12) — brief which of those points ends your level segment and what happens there before the FAF.

Fly your operator's flow; the pattern the evaluator expects to hear (per the ACS's briefing and CRM threads, Appendix 3; AA.VI.D.S7):

• Approaching the FAF: configuration confirmed, final approach speed set, missed approach reviewed
• FAF: time started if applicable, descent rate called
• Through each stepdown: altitude verified against the chart by the monitoring pilot
• Approaching minimums / minimums: the decision callout — runway cues or go-around
• Any deviation beyond the operator's limits: called immediately, corrected or rejected

The ACS grades the underlying skills directly: checklist timing (S7), configuration and airspeed for conditions (S8), and MFD use to monitor position and wind drift (S14).

The requirement is calibrated to your airplane: backup or partial panel instrumentation or navigation display, depending on the aircraft's avionics configuration, representing a realistic failure mode (ACS Appendix 3). In a glass transport that usually means standby instruments or a reverted/composite display, not a covered vacuum gyro. The graded skill is recognizing what failed and acting (AA.VI.D.S5) — which display survives, which nav source still feeds it, and how the ¼-scale standard will be judged on the surviving needle. Rehearse the reversion in your type before the check; the failure the evaluator picks will be one your airplane can actually have.

From the FAF to DA/DH: no more than ¼-scale deflection of either the vertical or lateral guidance indications, and airspeed ±5 knots of the desired value, on a stabilized final (AA.VI.E.S12). Before the final approach segment: altitude ±100 feet, selected heading ±5°, airspeed ±10 knots (S9). The ACS defines ¼ scale as the needle displaced ¼ of its total available deflection (ACS Appendix 3). The instrument-rating standard was ¾ scale and ±10 knots — the ATP corridor is a third the width, at transport final-approach speeds.

At least two precision approaches in simulated or actual IMC, flown to the DA using aircraft navigation equipment for centerline and vertical guidance:

• At least one without the autopilot, with the manually flown segment beginning no later than the FAF — raw data or flight director, at the evaluator's discretion
• One should be flown with backup or partial panel instrumentation or navigation display representing a realistic failure mode
• One may be flown via the autopilot, if equipped — provided the DA/DH does not violate the authorized minimum altitude for autopilot operation

The evaluator decides whether each ends in a landing or a missed approach (ACS Appendix 3).

Every autopilot has a minimum engagement/use height for approach — a certification and OpSpecs limit that varies by installation, which is why the ACS states the coupled-approach option only works provided the DA/DH does not violate the authorized minimum altitude for autopilot operation (ACS Appendix 3). The number itself is type-specific: it lives in your AFM and, for an operator, the OpSpecs. Expect the oral question in exactly that form: "Can you stay coupled to this DA?" — and answer from your airplane's limitation, not a generic figure.

Roughly groundspeed × 5 in fpm for a 3° path — 120 knots means 600 fpm (IPH ch. 3's descent rule of thumb). Compute it before the FAF so it's already established at the point where vertical guidance begins: the ACS calls for a predetermined rate of descent that approximates what's needed to follow the vertical guidance. Capturing the glideslope with the power and pitch already trending toward that rate is what makes the ¼-scale standard flyable; capturing it level at approach power and then chasing produces the classic porpoise the evaluator is watching for.

With all required ground and airborne components operative:

• CAT I — DH 200 feet, RVR 2,400 (RVR 1,800 with touchdown zone and centerline lighting)
• CAT II — DH 100 feet, RVR 1,200
• CAT IIIa — no DH or DH below 100 feet, RVR not less than 700
• CAT IIIb — no DH or DH below 50 feet, RVR less than 700 but not less than 150
• CAT IIIc — no DH and no RVR limitation — and to date, no U.S. operator has OpSpecs approval for IIIc

CAT II and III require special certification for operators, pilots, aircraft, and airborne/ground equipment; the authorizations and minimum RVRs live in OpSpecs Part C (IPH ch. 4).

Touchdown zone RVR is required, must be used, and is controlling for all CAT II ILS operations — and unlike CAT I (which permits substituting mid-field RVR when touchdown-zone RVR is unavailable), CAT II permits no substitutions for TDZ RVR (IPH ch. 4). Under part 121 the broader gate applies to every approach: you may not continue past the FAF unless the latest weather report puts visibility at or equal to or more than the procedure's minimums (121.651(b)).

Yes — this is the part 121 "look-see" provision. Having begun the final approach segment in compliance with 121.651(b), a later below-minimums report lets you continue to DA/DH or MDA. Below that, you may continue only if:

• The airplane is continuously in a position to land within the touchdown zone, using normal maneuvers and rate of descent
• Flight visibility is not less than prescribed
• A required visual reference is distinctly visible and identifiable

This is the same three-part logic as 91.175(c), with the TDZ-touchdown clause added for parts 121/135 (121.651(c)). And no landing when flight visibility is below the prescribed minimum (91.175(d)).

Depending on the autoflight systems, some aircraft require a DH to ensure landing in the touchdown zone, and some use an Alert Height as a final cross-check of the autoflight system's performance. Both are based on radio altitude, and the values come from the specific aircraft's AFM (IPH ch. 4). Conceptually: a DH is a decision about seeing; an alert height is a decision about the machine — below it, a fail-operational system continues the autoland unless a failure is announced. Which philosophy your airplane uses is a type question; answer it from the AFM.

No — as long as the descent doesn't continue. The ACS is explicit that continuing below DA/DH without the runway environment in sight is unsatisfactory, but most airplanes briefly descend below DA/DH from momentum when the miss is initiated at the DA — and that momentary descent does not constitute unsatisfactory performance as long as it does not continue (ACS Appendix 3, Task I discussion). The decision must be made at DA: immediately initiate the miss if the references aren't distinctly visible and identifiable (AA.VI.E.S13). What's graded is the promptness of the decision, not the physics after it.

Smaller and sooner. The needles' angular sensitivity increases all the way down, and at transport groundspeeds the same heading error builds displacement roughly twice as fast as it did in a trainer. The working method:

• Fly the flight director when authorized — but cross-check raw data; the manual approach may be raw-data at the evaluator's discretion (ACS Appendix 3)
• Heading changes of a degree or two; hold each correction and watch the trend rather than re-correcting on every needle twitch
• Pitch changes measured in tens of feet per minute against the precomputed rate (AA.VI.E.S11)
• Trim and thrust stable: on-speed ±5 knots (S12) is thrust discipline — configuration and airspeed established before the FAF for the conditions (S8), then leave it alone

Deviations you can't promptly stop are the cue to go around, not to work harder at salvage (AA.VI.E.R5).

Recognize, announce, act. On a precision final, the response is rarely creative: losing the vertical guidance below the point where another line of minima can be briefed means a missed approach; a disagreement between displays means reverting to the surviving source per your type's procedure and deciding whether the approach is still authorized. The skills behind this: select, tune, identify, and confirm the operational status of navigation equipment before the approach (S3), and recognize if any flight instrumentation is inaccurate or inoperative, and take appropriate action (S5). The oral version asks for your airplane's annunciations — flags, miscompare monitors, autoland status — from the AFM (K2).

Adjust the published DA/DH and visibility for NOTAMs, inoperative airplane or navigation equipment, or inoperative visual aids (S10). Mechanics: consult the TPP's Inoperative Components Table — the IFH's example raises visibility ¼ mile for a malfunctioning MALSR — and honor chart notes that exempt specific components (IFH ch. 1). Losing a required component of the guidance itself is different from losing a light: lights raise the visibility; a dead glideslope changes the approach into a localizer-only procedure flown to an MDA under the non-precision task's rules. Under 121, remember the OpSpecs may authorize different (including lower) minimums than the chart — the OpSpecs govern (121.651(a); IPH ch. 1).

Because the corridor is real: airports run simultaneous dependent, simultaneous independent, and simultaneous independent close parallel approaches, with diagonal separation as tight as 1 NM for dependent pairs (IPH ch. 4). Chart notes may impose flight director or autopilot requirements for simultaneous operations (IPH ch. 4). A localizer excursion on a close parallel isn't just a tolerance bust — it's an incursion into someone else's protected airspace. The ¼-scale ATP standard and the airline environment are the same requirement wearing two hats.

Two sets, stitched together:

• From DA/DH to the visual maneuvering point: desired airspeed ±5 knots, vertical and lateral guidance within ¼-scale deflection (AA.VI.F.S1) — the instrument standard doesn't relax just because you can see
• Touchdown: at the aiming point markings −250/+500 feet, or where there are no aiming point markings, 750 to 1,500 feet from the approach threshold (S4)

Then positive control through the rollout, using drag and braking devices as appropriate to a stop (S5), with SRM/CRM (S6) and runway incursion avoidance (S7).

Because the regulation writes it into the approach itself: below DA, operations under part 121 or 135 require the descent rate to allow touchdown within the touchdown zone of the runway of intended landing (91.175(c)(1); 121.651(c)(1)). Floating past the zone isn't a style problem — it invalidates the condition that authorized you below DA in the first place, and the answer is a go-around. The ACS touchdown window (−250/+500 feet from the aiming point) is the same idea expressed as a checkride tolerance.

Divide the work. In a crew, it's common practice for the PM to call out the vertical speed during the transition, confirming the instruments are being monitored so more of the PF's attention can go to the visual portion — and the PM announces any deviation from stabilized approach criteria (IPH ch. 4). Cautions from the IPH: transitioning to visual in shallow fog may leave inadequate visibility to flare, so always be prepared to go around; single-pilot transitions are markedly harder because one pilot must keep flying the instruments while acquiring the runway (IPH ch. 4). The instrument crosscheck continues to touchdown — that's what the ¼-scale-to-visual-maneuvering tolerance (S1) is measuring.

The approach light system alone. Descent below DA/MDA requires at least one of the ten listed visual references distinctly visible and identifiable — but using the approach lights as the sole reference, you may not descend below 100 feet above the touchdown zone elevation unless the red terminating bars or red side row bars are also distinctly visible and identifiable (91.175(c)(3)(i)). Those red bars are features of the ALSF-1/ALSF-2 systems that serve precision runways; a runway with a MALSR has no red bars to show you, so at 100 feet you need something else from the list — threshold, markings, lights, TDZ, or the runway itself.

Lower visibility minimums. Full configurations pair with the lowest RVRs — CAT I to RVR 1,800 requires touchdown zone and centerline lighting in addition to the approach lights (IPH ch. 4). Precision approaches get visibility credit for any approach light configuration, and a non-precision approach (250-foot HAT) configured with a MALSR, SSALR, or ALSF-1 normally results in published visibility of ½ SM (IPH ch. 4). Take the lights away and the Inoperative Components Table raises the visibility (IFH ch. 1). Runway markings matter to this task specifically: the aiming point markings are your touchdown reference (S4), and the signs/markings/lighting knowledge element (K2) extends through the rollout and taxi-in.

Advisories from ATC or the evaluator (S2):

• NOTAMs
• Windshear
• Wake turbulence
• Runway surface and braking conditions
• Other operational considerations

Each maps to a risk element: runway selection against aircraft limitations, available distance, surface, and wind (R1); wake turbulence (R2); attempting to land from an unstable approach (R7); and flying below the glidepath (R8) — short of the TDZ is as disqualifying as long. LAHSO acceptance (R11) is a crew decision against your operator's authorization and the available landing distance.

Yes. In an airplane, if you've flown the approach to a point where a safe landing and full stop could have been made but circumstances beyond your control prevent the landing, the evaluator may give credit — and credit may also be given for Task VI.I (Missed Approach) or Area III Task J (Go-Around/Rejected Landing) when the applicable criteria are met (ACS Appendix 3). Also remember the test-level requirement: at least three actual landings, at least one to a full stop, with landing tasks combinable across Areas (ACS Appendix 3, Area III notes).

Because the visual segment tempts you down. At DA the runway appears foreshortened in low visibility, and the common illusion-driven response is to push toward it. The protections you had on the guidance evaporate below it: obstacle surfaces near the threshold are assessed for the published path, and 91.175 requires a normal rate of descent using normal maneuvers to a TDZ touchdown (91.175(c)(1)). The ACS answer is mechanical: keep the glidepath needle inside ¼ scale all the way to the visual maneuvering point (S1), crossing the threshold at the nominal height the procedure was built for — the IPH's stabilized-approach material puts the threshold crossing at about 50 feet above TDZE (IPH ch. 4).

Positive airplane control throughout, using drag and braking devices as appropriate to come to a stop (S5). Fly the airplane onto the runway in the touchdown window — not floated beyond it hunting for smoothness — then work the sequence:

1. Speedbrakes/spoilers verified deployed
2. Reverse or beta as applicable
3. Braking appropriate to the reported braking action and the distance remaining

PM: deployment verification and speed callouts per the operator's procedures (S6). Runway incursion avoidance (S7): exit where planned, hold short of everything you haven't been cleared to cross, and finish the after-landing items only when clear of the protected area.

You may be landing behind traffic you never see. The defenses are procedural rather than visual:

• Note the preceding aircraft's type and position from ATC advisories (S2)
• Expect ATC's wake-separation spacing
• Keep the approach on or above the glidepath to touchdown at or beyond the preceding traffic's — enforced by the ¼-scale discipline (S1) and the aiming-point window (S4)

A go-around is the standing answer if spacing collapses inside the FAF.

The landing-side items from the ACS Appendix 3 briefing list:

• Landing runway
• Instrument approach procedure
• DA/DH
• Missed approach procedures
• Initial rate of descent
• Time to missed approach
• Expectations of the other crewmembers during the approach and landing

Add the day's variables from S2 — runway condition and braking reports, LAHSO in effect, windshear advisories — and the touchdown-zone commitment: the point at which, if not down, you go around. Briefing the go-around as the default outcome is what keeps R7 (landing from an unstable approach) from ever becoming the finding.

The scenario must include visual maneuvering from the final approach course to a base or downwind leg appropriate for the landing runway — not a token turn. You may circle to a runway less than 90° offset from the final approach course, provided you make at least 90° of total heading change (ACS Appendix 3, Task G). Skills demonstrated:

• Comply with the procedure considering turbulence, windshear, and your airplane's maneuvering capability and approach category (AA.VI.G.S1)
• Confirm traffic direction and comply with ATC restrictions (S2)
• Maintain crew coordination and checklists (S3)

Until descending below the MDA (or the preselected circling altitude above it), you must hold these tolerances (AA.VI.G.S5):

• Airspeed: ±5 knots
• Heading/track: ±5°
• Altitude: +100/−0 feet

The descent must also be planned: establish the approach and landing configuration and a descent rate that ensures arrival at the MDA — or the preselected circling altitude above it — prior to the missed approach point (S4). The −0 floor is the heart of it: the circling MDA is an obstacle-clearance surface, not a target.

Category comes from VREF, or 1.3 VSO at maximum certificated landing weight if VREF isn't specified — it's assigned at certification, is permanent, and you may never use a lower category's minimums. Speed bands: