Private Pilot Checkride Study Guide

Be at least 17 years old; read, speak, write, and understand English; hold at least a current third-class medical; receive the required ground and flight training endorsements; meet the aeronautical experience requirements; and pass the knowledge and practical tests (61.103).

Your pilot certificate, government photo ID, and a current medical certificate or BasicMed qualification (61.3, 61.23).

Act as PIC and carry passengers; fly in IMC if instrument rated. You may not fly for compensation or hire, beyond limited cost-sharing where you pay no less than your pro-rata share of the operating expenses (fuel, oil, airport expenditures, rental). You may act as PIC incidental to a business if you carry no passengers or property for hire; conduct search-and-rescue; fly for charitable, non-profit, or community events meeting 91.146; and act as an aircraft salesman with 200+ hours (61.113).

• Category — Airplane, Rotorcraft, Glider, Lighter-Than-Air
• Class — Single-Engine Land/Sea, Multi-Engine Land/Sea
• Type — a specific make and model, required for aircraft over 12,500 lb, turbojets, or any aircraft the FAA specifies (61.5, 61.31)

Currency is meeting the regulatory recent-experience minimums — a legal threshold. Proficiency is actual competence and skill, which usually exceeds the regulatory minimum. You can be current but not proficient.

Log the training and aeronautical experience required for a certificate, rating, or recent-experience requirement. Recurrent currency need not be logged continuously but must be shown when you exercise that privilege (61.51). As a certificated private pilot you don't routinely carry the logbook.

No expiration date, but you must complete a flight review every 24 calendar months to act as PIC (61.56).

Three takeoffs and three landings in the preceding 90 days in the same category, class (and type if required). For night currency the three must be to a full stop, between 1 hour after sunset and 1 hour before sunrise (61.57). Night itself is the time between the end of evening civil twilight and the beginning of morning civil twilight (1.1).

Third class — 60 calendar months if under 40 at the exam, 24 calendar months if 40 or older. First and second class downgrade in steps to third-class privileges.

An alternative to a medical: you must have held a medical after July 14, 2006; hold a valid driver's license; take the online medical course every 24 months; get a physician exam (CMEC) every 48 months. Limits: 6 occupants or fewer, 6,000 lb or less; at or below 18,000 ft MSL, 250 kt or less (61.113(i), Part 68).

Notify the FAA in writing within 30 days; you cannot exercise your privileges after 30 days until you do (61.60).

As a student I could not carry passengers, carry property for compensation or hire, or fly in furtherance of a business. Solo flight also had weather floors: at least 3 SM flight or surface visibility by day and 5 SM at night, and I had to maintain visual reference to the surface — solo student flying is strictly VFR (61.89).

Only when acting as PIC — that is, on solo flights. Then I needed my student pilot certificate, medical, and government photo ID, plus my logbook to show the required endorsements. As a certificated private pilot the logbook stays home except when I need to show recent-experience or endorsements (61.3, 61.51).

Not anymore — student certificates issued after 2016 have no expiration date. (Older ones expired after 60 calendar months if issued under age 40, 24 if over.) A student stays "current" simply by holding a valid medical. PPL, commercial, CFI, ground instructor, and ATP certificates are likewise issued without an expiration date — you just have to keep them active with currency (61.19).

Every 24 calendar months, a minimum of 1 hour of ground training and 1 hour of flight training with an authorized instructor, covering the Part 91 rules and the maneuvers the instructor deems necessary. A practical test for a new certificate or rating resets the clock.

Complex, high-performance, high-altitude (pressurized above certain altitudes), and tailwheel airplanes each need a one-time instructor endorsement — no checkride, no new certificate.

No. A standard certificate stays valid as long as the aircraft is maintained and inspected per regulation, conforms to its type certificate, and registration is valid (91.7).

Yes — for most light aircraft built after 1975 the POH is the FAA-designated AFM, and you must operate within it, its markings, and placards (91.9).

The owner/operator is responsible for maintenance and inspections (91.403); the PIC is responsible for determining the aircraft is airworthy before each flight and must discontinue flight if it becomes unairworthy (91.7).

After 1 hour of cumulative use, or when half its useful life has expired (91.207c).

Not an annual — the only way past it is a special flight permit from the FSDO. A 100-hour may be exceeded by up to 10 hours, and only to reach a place of repair; the overage comes off the next interval. An annual can substitute for a 100-hour, but not the reverse (91.409).

An FAA order to correct a known unsafe condition. Compliance is mandatory and recorded. Types: emergency (comply before further flight), one-time, and recurring (comply at the specified interval) (PHAK ch 9).

Use the MEL if one exists. Otherwise use the 91.213(d) method: the item must not be required by the type certificate/equipment list, by 91.205, by an AD, or for the operation; then deactivate or remove it, placard it "INOP," and a pilot or mechanic determines it's safe.

Authorizes flying an aircraft that doesn't currently meet airworthiness requirements but is safe to fly, to a place of repair (Part 21, via 91.213/91.407).

An annual must be done by an A&P mechanic holding an Inspection Authorization (IA). A 100-hour can be done by any licensed A&P (91.409).

No — never. ADs split into urgent and non-urgent: emergency ADs must be complied with before further flight; the rest by their stated deadline or interval. There is no 10-hour grace like the 100-hour, and no ferry-permit workaround for an emergency AD (PHAK ch 8).

Technically no — the 100-hour applies to aircraft carrying persons for hire or used for flight instruction for hire, and the practical test itself isn't instruction. In practice a rental fleet keeps them current anyway.

Yes. The 91.207(f) exception that excuses training flights within 50 NM of the departure airport doesn't help here — a checkride is not training, so the ELT must be installed and current. One more detail: the half-of-battery-useful-life date is recorded by the mechanic in the maintenance logs, so that's where you go to prove ELT battery status.

Three separate records: airframe, engine, and propeller. Inspections and AD compliance get signed off in the applicable log.

First, when is it required? Only for night operations for hire (including instruction for hire) — a casual personal night flight doesn't legally need it, though flying at night without one is a judgment call I'd think hard about. If it's a day flight, or a night flight where it isn't required, I deactivate or remove it and placard it inoperative — deactivating can be as simple as pulling and collaring the circuit breaker. Depending on what the fix involves, either a mechanic or the pilot does the deactivation. One FLAPS footnote: the spare "fuses" requirement is satisfied by circuit breakers in modern aircraft.

Get a special flight (ferry) permit so the airplane can legally fly to where repairs can be made. The path: contact the FSDO, and the permit can be issued by the FAA or by a DAR — a Designated Airworthiness Representative, a private individual the FAA appoints to act on its behalf. So the practical answer is: call the FSDO, they connect you with a DAR, the DAR issues the ferry permit.

15°C (59°F) and 29.92 in Hg at sea level, with a −2°C per 1,000 ft lapse rate.

Connect points of equal pressure; close spacing means a steep pressure gradient and stronger winds.

Surface winds are slowed and turned by friction, crossing isobars at an angle. Winds aloft flow roughly parallel to the isobars because of the Coriolis effect.

Stable — stratiform clouds, steady precipitation, poor visibility, smooth air. Unstable — cumuliform clouds, showery precipitation, good visibility, turbulence.

High — descending, diverging air, generally fair. Low — rising, converging air, clouds and precip. A ridge is an elongated high; a trough is an elongated low.

Needs moisture, unstable air, and a lifting force. Stages: cumulus (building, updrafts), mature (most hazardous — up- and downdrafts, heavy precip, lightning, hail; rain reaching the ground marks onset), dissipating (downdrafts dominate; anvil points the direction of movement).

A sudden change in wind speed or direction at any altitude — abrupt airspeed changes and severe turbulence; associated with thunderstorms, microbursts, fronts, and temperature inversions.

As they converge (small spread), the air nears saturation — expect fog, clouds, or precipitation.

Radiation (clear, calm nights over land), advection (warm moist air over a cooler surface), upslope (moist air cooled climbing terrain), precipitation-induced (warm rain through cool air), and steam fog.

Structural — rime (rough, milky, leading-edge), clear (smooth, dense, hard to see, spreads aft), mixed. Plus induction (including carburetor) and instrument icing. Icing cuts lift, adds weight and drag, reduces thrust, and raises stall speed.

Standard (none gathered yet), abbreviated (supplement/update), outlook (departure 6+ hours out). From 1800wxbrief.com / Leidos Flight Service or aviationweather.gov.

METAR — routine hourly surface observation (SPECI for significant changes). TAF — Terminal Aerodrome Forecast, valid 24 or 30 hours for about 5 SM around the airport, issued every 6 hours. Change groups: FROM, BECMG, TEMPO, PROB.

The Graphical Forecasts for Aviation tool — replaced the textual Area Forecast for the CONUS.

AGL. A ceiling is the lowest broken or overcast layer.

AIRMET (valid 6 hr, now mainly the G-AIRMET graphic): Sierra (IFR/mountain obscuration), Tango (turbulence/strong surface winds/LLWS), Zulu (icing/freezing levels). SIGMET (valid 4 hr; 6 hr for volcanic ash/tropical cyclones): severe non-convective hazards to all aircraft. Convective SIGMET (valid 2 hr): severe thunderstorm activity.

FB — forecast wind and temperature at standard altitudes, twice daily (no winds within 1,500 ft of station elevation; no temps within 2,500 ft; above 24,000 ft temps assumed negative). PIREPs — actual in-flight reports; the best source for icing, turbulence, and cloud tops.

Surface analysis shows fronts and pressure systems; prog charts forecast significant weather. Now consolidated in the Aviation Weather Handbook.

Three, in increasing order of nastiness: single cell (isolated, short-lived), multicell (clusters or squall lines), and supercell (rotating, longest-lived, most violent — may be embedded in other clouds where you can't see it). A mature cell typically runs about 5–10 minutes of peak intensity over a footprint of a mile or two across.

A microburst is a small, intense downdraft from a convective cell — the most severe form of wind shear I can encounter. Downdrafts can reach 6,000 fpm, the outflow is typically under a mile wide, and an individual burst lasts only about 5–15 minutes — short-lived enough that the aircraft ahead of me may report nothing.

It's most dangerous during takeoff and landing (PIREPs code these DURC — during climb — and DURD — during descent): I'm low, slow, and configured with little energy to spare. The classic encounter sequence: entering the outflow I get a performance increase (headwind — airspeed and lift rise), then the downdraft, then the headwind becomes a tailwind — airspeed decays rapidly, the nose pitches down, and I'm losing altitude and attitude. The response is immediate: full power and go around. Heed low-level wind shear (LLWS) advisories and microburst alerts. (AIM 7-1; Aviation Weather Handbook)

Ceiling and/or visibility set the category — the worse of the two governs. Easiest to memorize in reverse order of severity, LIFR up to VFR:

These are the colored station dots on the GFA/METAR map — green good, blue marginal, red IFR, magenta the worst. MVFR is legal VFR but deserves real respect in a Warrior: 3 miles and a 1,000-ft ceiling leaves very little room over terrain.

6 | 4 | 2 — validity drops in reverse order of severity. The more severe the advisory, the shorter it lives:

SIGMET turbulence triggers include severe turbulence not associated with thunderstorms — think low-level wind shear, mountain waves (most dangerous on the leeward, downwind side), and building-induced mechanical turbulence.

An advisory is a forecast, not a prohibition — so legally, often yes, and the conditions aren't guaranteed to exist. But a PIREP confirming the hazard changes the analysis: flight into known severe icing or conditions exceeding the Warrior's operating limitations is where I'd actually be stopped. Advisories inform the go/no-go; PIREPs plus my aircraft's limitations decide it.

Rule of thumb: "if you read it, true. if you hear it, magnetic." Written products — METAR, TAF, FB — reference true north. Voice sources — tower, ATIS — give magnetic so they line up with runway numbers. Cloud heights in a METAR are AGL (the sensor is sitting on the ground measuring up).

• AO1 vs. AO2 — automated station type: AO2 has a precipitation discriminator (can tell rain from snow); AO1 cannot.
• SLP114 — sea level pressure; prefix a 10 (or 9) and insert the decimal: 1011.4 hPa.
• P6SM (TAF) — visibility Plus 6 statute miles, i.e., more than 6.
• FU — smoke (from the French fumée).
• $ — the station needs maintenance; treat the data with suspicion.

An initial RPM drop (hot, less-dense unfiltered air), then a further momentary roughness or dip as the melting ice passes through as water, then RPM rises and stabilizes as the ice clears. Knowing the sequence keeps me from panicking and pushing carb heat back off at exactly the wrong moment. Carb heat works by routing unfiltered air warmed by the exhaust over the intake — hot air is less dense, which is why performance drops while it's on.

A front is the boundary between two air masses — and it's named after the advancing (stronger) air mass.

One more sequencing fact worth having: lows form in response to highs — pressure systems come as a pair, and air flows out of the high (clockwise, descending) and into the low (counterclockwise, rising).

Time-critical information not known early enough to chart. Check during planning and again just before departure.

The Chart Supplement (formerly the A/FD), updated every 56 days.

A suitable backup field considering weather, fuel, and terrain. Formally required for IFR (91.169); a prudent VFR practice.

Enough to reach the first point of intended landing, then fly at normal cruise for at least 30 minutes (day) or 45 minutes (night).

Pilotage — navigating by visible landmarks. Dead reckoning — computing heading, time, distance, and fuel from known speed and wind.

The angular difference between true and magnetic north; apply it using the isogonic lines on the sectional. East is least (subtract); West is best (add).

The E6B (or electronic equivalent) solves the planning math: the wind side computes wind correction angle, ground speed, and true heading from the wind triangle; the calculator side handles time-speed-distance, fuel burn, true airspeed, density altitude, and unit conversions. Be ready to find ground speed and a heading correction given a wind, and to compute fuel required for a leg.

Time = distance ÷ ground speed; fuel = burn rate × time; the 60-to-1 rule for course corrections. Know how to update an ETA and a fuel state in the air from your actual ground speed.

Line-of-sight only — range limited by altitude and terrain. Service volumes: Terminal, Low, High (plus newer VOR MON). Always identify the Morse code before using it.

Satellite-based area navigation; verify the database is current and check integrity (RAIM/WAAS) before relying on it.

Build a call with four parts: who you're calling, who you are, where you are, what you want. Read back hold-short and runway-assignment instructions. Use the phonetic alphabet for the N-number and standard phrasing ("with you," "roger," "wilco," "unable").

Squawk 7600. Continue to the airport, watch for light gun signals from the tower, and use known procedures. If you can receive but not transmit, listen for ATC instructions and acknowledge by rocking the wings (or by transponder ident if asked).

Turn toward the alternate immediately, then estimate heading, distance, time, and fuel to it.

Four categories to know (AIM 5-1-3):

• NOTAM (D) — the general domestic category, disseminated for all public-use airports and navaids: runway/taxiway closures, lighting and navaid outages, new obstructions.
• FDC NOTAM — regulatory, issued by the Flight Data Center: changes to procedures — heavily IFR-related, but not always. TFRs are published as FDC NOTAMs, so a VFR pilot has to check these too.
• Military NOTAM — for military airports and navaids.
• NOTAM (I) — international; for operations outside the U.S.

Controlled = Classes A, B, C, D, E (ATC services available). Uncontrolled = Class G.

With an ATC clearance inside a surface area, fly with 1 SM visibility and clear of clouds. At night the pilot must be instrument rated and the aircraft IFR-equipped (91.157).

In and above Class B and C, within the 30-NM Mode C veil, and above 10,000 MSL (excluding at/below 2,500 AGL).

Class A, B, and C; above the lateral limits of B/C up to 10,000 MSL; Class E at/above 10,000 MSL (excluding at/below 2,500 AGL); within the Mode C veil; and over the Gulf at/above 3,000 MSL within 12 NM of the coast.

Prohibited, Restricted, Warning, Military Operations Area (MOA), Alert, Controlled Firing Area, National Security Area. In brief: Prohibited — flight prohibited; Restricted — invisible hazards, need permission when active; Warning — 3 NM+ off the coast; MOA — military training, use extreme caution; Alert — high training volume; Controlled Firing Area — not charted, activity stops when a spotter sees traffic; NSA — voluntary avoidance, may be temporarily prohibited.

Military Training Routes (MTRs), Temporary Flight Restrictions (TFRs, 91.137), published VFR routes (the LA Basin has several), TRSAs, parachute jump areas.

An aircraft in distress has right-of-way over all others; then balloon, glider, airship, then powered/airplane (aircraft towing or refueling have priority over other powered aircraft). Converging same-category: the aircraft on the other's right has right-of-way. Head-on: both turn right. Overtaking: pass on the right.

Below 10,000 MSL: 250 KIAS. Below a Class B shelf or in a VFR corridor through B: 200 KIAS. Within 4 NM of a Class C/D primary airport at/below 2,500 AGL: 200 KIAS.

Anywhere: high enough to land without undue hazard if the engine fails. Congested: 1,000 ft above the highest obstacle within 2,000 ft horizontally. Other than congested: 500 ft AGL, and not within 500 ft of any person, vessel, or structure.

Above 3,000 ft AGL: magnetic course 0–179° = odd thousand + 500 (3,500; 5,500); 180–359° = even thousand + 500 (4,500; 6,500).

A runway incursion is any unauthorized presence on a runway. Prevent it with a clear taxi plan and airport diagram, reading back all hold-short and runway-crossing instructions, positive identification of hold-short lines and signage, heightened vigilance at night and in low visibility, and a sterile cockpit while taxiing (AIM 4-3; SAFO 11004).

Be aware of TFRs and special security areas. Report suspicious activity to the TSA general-aviation hotline (1-866-GA-SECURE). Secure your aircraft when parked, and complete security-awareness training if your operation calls for it.

IR routes are flown IFR; VR routes are flown VFR, and only when visibility is 5 SM or better with ceilings of at least 3,000 ft. A four-digit number (like VR1205) means no segment of the route is above 1,500 ft AGL; a three-digit number means at least one segment goes above 1,500 ft AGL. Either way, expect military traffic faster than 250 knots (AIM 3-5-2).

A TRSA is charted with a solid gray band (Palm Springs is the local example) — TRACON radar services there are voluntary for VFR, but participation is encouraged. Published VFR routes appear on TACs to move VFR traffic around, under, or through complex airspace; the LA Basin has several named ones, including the Coastal Route, the Mini Route, and the Special Flight Rules Area over LAX.

Lift, weight, thrust, drag. In steady flight, lift opposes weight and thrust opposes drag; an imbalance produces a climb, descent, or speed change.

A combination of Newton's third law — the airfoil deflects airflow downward and gets an equal, opposite upward reaction — and Bernoulli's principle, where faster airflow over the cambered upper surface lowers pressure relative to below. The pilot controls lift through angle of attack, airspeed, and (with flaps) surface area (PHAK ch 5).

Parasite (form, skin friction, interference) increases with speed; induced is a byproduct of lift and decreases with speed. They're equal at L/D-max, which is best-glide speed (PHAK ch 5).

At low airspeed (behind the power curve), more power is needed to fly slower because induced drag dominates — relevant on short final and in slow flight. In the region of normal command, more power gives more speed.

Camber is the curvature of the wing; you change it with flaps. Angle of incidence is the fixed wing-to-longitudinal-axis angle and can't be changed in flight. Angle of attack is the angle between the chord line and the relative wind (PHAK ch 5).

Exceeding the critical angle of attack — which can happen at any airspeed, weight, or attitude (PHAK ch 5).

Forward CG: more stable, higher stall speed, heavier elevator forces, lower cruise speed, longer takeoff/landing, favorable stall recovery. Aft CG: less stable, lower stall speed, lighter controls, higher cruise; an excessively aft CG can make stall/spin recovery difficult or impossible (PHAK ch 5).

Longitudinal (pitch, lateral axis, set by CG/elevator); lateral (roll, longitudinal axis, helped by wing dihedral); directional (yaw, vertical axis, from the vertical stabilizer). Each can be static (initial tendency) or dynamic (over time), and positive, neutral, or negative (PHAK ch 5).

Higher-pressure air below the wing spills around the tip to the lower-pressure air above, creating vortices — strongest when the generating aircraft is heavy, clean, and slow. Avoid by staying above and upwind of a larger aircraft's flight path and landing beyond its touchdown point.

High temperature, high altitude, high humidity, and high weight all reduce performance and increase takeoff and landing distance (PHAK ch 11).

Airspeeds: IAS → CAS (corrected for installation/position error) → TAS (corrected for altitude/temperature) → GS (corrected for wind). Altitudes: indicated, pressure (set 29.92), density (pressure altitude corrected for nonstandard temp), true (MSL), absolute (AGL).

Pressure altitude = field elevation + (29.92 − altimeter setting) × 1,000. Density altitude = pressure altitude + ~120 ft per °C above standard. Air density is affected by altitude, temperature, humidity, and pressure.

Headwind shortens the ground roll and improves climb angle; tailwind lengthens it; crosswind requires drift correction.

Vx for maximum altitude gained per horizontal distance (clearing an obstacle); Vy for maximum altitude gained per unit of time (best overall climb) (AFH).

Yes — the published figure is at max gross; at lighter weight the speed is slower (the glide ratio stays about the same).

Working front to back (PHAK ch 5): the leading edge meets the relative wind first, and the trailing edge is where the upper and lower airflows rejoin. The chord line is the straight line connecting the two — it's the reference line for angle of attack. The mean camber line runs equidistant between the upper and lower surfaces; the more it bows away from the chord line, the more camber the airfoil has. The upper and lower surfaces each have their own camber, and on most wings the upper camber is greater — that asymmetry is what speeds up the airflow on top.

In a level turn the wing has to support the airplane's weight and generate the horizontal force that turns it, so load factor grows with bank: roughly 1.15 G at 30 degrees, 1.41 G at 45, and exactly 2 G at 60. Stall speed rises with the square root of load factor, so at 60 degrees of bank the wing stalls about 41 percent faster than in level flight. That's why a steep, slow turn — especially in the pattern — is a stall setup (PHAK ch 5).

At or below Va, one full control deflection drives the wing past the critical AoA and it stalls before it can generate enough lift to exceed the +3.8 G limit — the stall acts like an aerodynamic fuse. The wing's maximum force is the same at any weight; weight only decides which happens first, the stall or the structural limit. Heavier, the wing already needs a higher AoA just to hold 1 G, so it hits the critical AoA after fewer additional Gs — the fuse blows early, and Va can be higher. Lighter, level flight takes less AoA, which leaves room to pull well past 3.8 G before the stall arrives — so Va must come down to restore the protection (PHAK ch 5).

An aggravated stall with autorotation. Both wings are stalled, but one is stalled more deeply — it makes less lift and more drag than the other, and that imbalance keeps the airplane rotating around a steep, corkscrew path. The recipe is always the same: stall plus yaw. No yaw, no spin — which is why coordination is the real spin prevention (AFH ch 5).

In a skid (too much inside rudder), the low inside wing is the one that stalls first, so the airplane rolls into the turn and toward the ground — a spin entry, and at pattern altitude there's usually no room to recover. In a slip, the raised wing tends to stall first, so the roll-off is toward wings-level — still a stall, but far more forgiving. That's why the skidding base-to-final turn is the classic killer: keep the ball centered, especially turning final.

Straight from the memory table:

Secondary controls: flaps, leading-edge devices, spoilers, and trim systems (PHAK ch 6).

The wings' shallow V shape means that in a sideslip the lower wing meets the relative wind at a higher angle of attack than the raised wing, so it produces more lift and rolls the airplane back toward level. Fuel management plays into this too: an imbalanced fuel load holds one wing low and fights the dihedral effect (PHAK ch 5).

Longitudinal (pitch) stability depends above all on the CG staying inside the envelope — the tail-down-force geometry only works within limits. Directional (yaw) stability comes from the vertical stabilizer plus the fuselage side area behind the CG: the larger the fin and the farther aft it sits, the stronger the weathervane tendency back to coordinated flight (PHAK ch 5).

Plot total drag (power required) against airspeed and you get a U. Induced drag falls as speed builds while parasite drag rises, and where they cross — the bottom of the U — is L/D max, which is also best-glide speed. To the right, parasite drag dominates: that's the region of normal command, where more power means more speed. To the left of L/D max is the region of reversed command: induced drag dominates, so flying slower takes more power. Slow flight lives on that back side, and so does a dragged-in short final — if I get slow behind the curve and just pull, I sink harder. The fix is to lower the AoA and add power (PHAK ch 11).

Because L/D max is an angle of attack, not an airspeed. The wing's best lift-to-drag ratio always occurs at the same AoA; the airspeed just has to be whatever puts the wing at that AoA. A lighter airplane needs less lift, so it reaches that AoA at a lower speed — the glide angle and ratio stay the same, but the target number on the airspeed indicator drops (PHAK ch 11).

Ailerons control roll about the longitudinal axis; an up aileron decreases that wing's camber and lift (wing drops), a down aileron increases camber and lift (wing rises). The stabilator controls pitch about the lateral axis. The rudder controls yaw about the vertical axis.

The down-going aileron makes more lift and more drag, yawing the nose toward the raised wing — opposite the intended turn. Rudder counters it to stay coordinated.

Differential ailerons — the up aileron deflects more than the down aileron, balancing the drag. Frise-type ailerons — the leading edge of the up aileron projects into the airflow on the descending wing, adding offsetting drag. Some designs use coupled aileron-rudder linkages or flaperons.

A stabilator is a one-piece all-moving horizontal tail; it generally reduces drag and weight and increases authority, and uses an anti-servo tab to add control feel and act as trim. A conventional elevator hinges off a fixed horizontal stabilizer; a T-tail places it above the wing downwash but is more prone to a deep stall.

Control stops limit travel; elevator down-springs help lower the nose to prevent an aft-CG stall; stick pushers (mostly transport jets) push the stick forward to avoid a critical AoA.

High-lift devices on the trailing edge that increase lift and drag, allowing shorter takeoff/landing, steeper approaches, and slower speeds. Types: plain, split, slotted, and Fowler (slides aft to add wing area). The Warrior uses manual Johnson-bar flaps with detents at 10°, 25°, 40°; the retracted right flap doubles as a step.

Relieves control pressure so you don't hold force. The Warrior's anti-servo tab on the stabilator moves with the control to add feel and serve as trim. Set attitude/power/configuration first, then trim off the pressure, and re-trim for every change.

Lycoming O-320-E3D: 150 HP at 2,700 RPM, horizontally opposed, 4-cylinder, air-cooled, carbureted, normally aspirated, direct-drive (AFM §2). A horizontally opposed layout keeps frontal area and drag low with a good power-to-weight ratio.

Ambient air enters the intake — no turbocharger or supercharger — so power decreases as density altitude increases.

Intake (piston down, mixture in), compression (valves closed, piston up), power (spark ignites, piston driven down, turning the crankshaft), exhaust (valve open, piston up, gases out).

Two magnetos, two spark plugs per cylinder, leads, and an ignition switch. The dual system improves combustion and provides redundancy. Once running, the magnetos are self-sustaining and independent of the electrical system — the engine runs with the master OFF, which is why the prop is always treated as hot. Losing one magneto gives a slight RPM drop, not a stoppage.

Brings in air, mixes it with fuel, and delivers the mixture to the cylinders. Air enters through a filter; an alternate air source is used if the filter clogs. The Warrior is carbureted (float-type carburetor).

Fuel vaporization and the venturi pressure drop cool the carburetor 60–70°F, which can condense and freeze water vapor. It typically forms between ~20°F and 70°F with humidity above 80%, but can occur up to ~100°F and at lower humidity — especially at low/glide power. In a fixed-pitch airplane the first sign is an RPM drop, then roughness. Carb heat preheats the air to clear it (and can cost up to ~15% power); expect an initial further RPM drop, then a rise as ice clears (PHAK ch 7; AC 20-113).

Sets the fuel-to-air ratio. Lean as you climb because air density drops while fuel flow would otherwise stay constant, giving an over-rich mixture that fouls plugs and costs power (PHAK ch 7).

Lubricate, cool, seal, clean (carry contaminants to the filter), protect against corrosion, and cushion. The Warrior uses a wet-sump system; capacity 8 quarts; ashless-dispersant oil per Lycoming SI 1014 — heavier weight in summer, lighter in winter (not the Archer's 15W-50).

Oil pressure gauge (direct indication of operation) and oil temperature gauge. High oil temp can mean a plugged line, low quantity, a blocked cooler, or a bad gauge; low oil temp usually means improper cold-weather viscosity.

Primarily ram air directed around the cylinders by baffles, supplemented by an oil cooler. Overheating causes power loss, excessive oil consumption, detonation, and engine damage. To cool: enrich the mixture, reduce power, increase airspeed (and open cowl flaps if equipped).

Exhaust gases exit through the manifold; cabin heat is outside air ducted through a shroud around the heated muffler. The exhaust must be crack-free — a cracked muffler can leak carbon monoxide (odorless, colorless) into the cabin, a form of hypemic hypoxia.

Fixed-pitch Sensenich 74DM6, aluminum alloy — 74-inch diameter, 60-inch pitch, measured at 75% of the diameter (AFM §7). A propeller is a rotating airfoil, twisted (higher pitch at the hub, lower at the tip) so each section meets the relative wind at an efficient angle. On a fixed-pitch prop the tachometer is a direct indication of engine/prop RPM and the throttle sets it. (Not the 76" Archer prop.)

Two 25-gallon wing tanks = 50 gal total, 48 usable. Selector LEFT–RIGHT–OFF (no BOTH). An engine-driven fuel pump plus an electric auxiliary/boost pump (on for takeoff, landing, and tank switches) feeds the float-type carburetor; each tank has a drain plus a firewall gascolator (AFM §7).

100LL = blue; 100 = green; UL94 = unleaded; Jet A = clear/straw. Mixing avgas with Jet A or using the wrong grade causes detonation, power loss, and engine failure. Mixed grades — and Jet A — turn clear, so treat any clear sample with suspicion.

To check for water, sediment, and proper grade/color before the first flight of the day and after every fueling. Water is heavier than fuel and sinks to the low points, which is where the sumps drain (AFM §8).

Small leading-edge strips near the wing root that force the root to stall first, preserving aileron authority and giving stall warning. The Warrior's tapered wing also promotes root-first stall.

Cleveland single-disc hydraulic brakes on the mains, toe-actuated, with a parking brake (AFM §2).

Fixed tricycle gear — two mains and a nosewheel. Fixed gear is simple and low-maintenance (at the cost of some drag); the tricycle layout gives better forward visibility and ground handling than a tailwheel.

12-volt battery, 14-volt system, 60-amp alternator, voltage regulator/overvoltage relay, split master (BAT/ALT). The ammeter shows alternator load, not battery discharge. Push-to-reset breakers power radios, lights, fuel pump, and pitot heat (AFM §2).

An engine-driven dry vacuum pump pulls filtered air through the attitude and heading gyros, spinning them at rated RPM; normal vacuum is 4.8–5.2 in Hg. Higher damages the gyros; lower makes them unreliable. The turn coordinator is electric, so it survives a vacuum-pump failure.

The airspeed indicator is the only one using both ports — it reads the difference between ram (pitot) and static pressure. The altimeter (aneroid wafers) and VSI use static only.

• Pitot ram blocked, drain open: ASI reads low / drops toward zero.
• Pitot + drain blocked: ASI acts like an altimeter — reads high in a climb, low in a descent.
• Static blocked: altimeter freezes, VSI reads zero, ASI inaccurate — use the alternate static source.
• Both blocked: all three unreliable.

Attitude indicator, heading indicator, turn coordinator. Two principles: rigidity in space (the gyro holds its plane — attitude and heading) and precession (an applied force is felt 90° around in the direction of spin — turn coordinator). Reset the heading indicator to the compass about every 15 minutes for precession drift.

Variation (true vs. magnetic north — East is least, West is best), deviation (onboard fields, corrected by the compass card), and dip. Turning error: UNOS (Undershoot North, Overshoot South). Acceleration error: ANDS (Accelerate North, Decelerate South). Plus oscillation in turbulence.

Recognize the indication (gauge, sound, smell, control feel), fly the airplane first, run the appropriate checklist, and manage the failure (e.g., switch tanks, apply carb heat, shed electrical load for an alternator failure). Know which instruments you lose with a vacuum, pitot-static, or electrical failure.

• Airspeed indicator — the only instrument plumbed to both sources. Ram ("impact") air from the pitot tube pushes on a diaphragm, while the sealed case around it is filled with static air. The needle displays the difference between the two — dynamic pressure, i.e. airspeed.
• Altimeter — static air fills the instrument case around an aneroid wafer that has standard pressure (29.92 in Hg) sealed inside as a constant reference. Climb, and falling ambient pressure lets the wafer expand and drive the needles. It's a sensitive altimeter because I can calibrate it to the local barometric setting with the Kollsman window.
• VSI — the diaphragm gets static pressure instantly, while the case only catches up through a calibrated leak over roughly 6–9 seconds. That deliberate lag is what gets displayed as rate of climb or descent (PHAK ch 8).

The dangerous one is the trapped-pressure case: a pitot tube blocked at both ends turns the ASI into an altimeter, which can seduce you into pitching up as "airspeed" builds in a climb.

The attitude indicator stays erect because pendulous vanes at the base of the gyro duct the vacuum air through gravity-operated doors, constantly re-centering it. The turn coordinator's gyro is canted about 30° upward so it senses rate of roll as well as rate of turn — a rapid roll shows a steeper initial bank, then it settles to indicate the actual turn rate.

Small precession errors from maneuvering: a quick acceleration or deceleration can show a momentary false climb or descent, and on rollout from a steep turn it may briefly indicate a turn in the opposite direction. They self-correct once the pendulous vanes re-erect the gyro. The heading indicator's version of this is drift — reset it to the magnetic compass about every 15 minutes.

3° per second — a full 360° in 2 minutes, shown by the turn coordinator's index marks. It's a rate, not a specific bank angle (bank required grows with true airspeed). The inclinometer ball underneath shows slip or skid — coordination. Using standard-rate turns during maneuvers keeps them predictable.

Think of north as the compass's home. Sitting at home on a north heading, it doesn't want to leave — it lags the turn, reluctantly catching up (undershoot). Far from home on a south heading, it's eager to get back — it races ahead of the turn (overshoot).

Build it as a ladder — horsepower, maker, induction and cylinders, then the H-A-N-D qualities:

Say it the same way every time and it comes out as one smooth sentence.

Preventive maintenance under 14 CFR Part 43, Appendix A — things like oil changes and other fluids, servicing some batteries, cleaning fuel strainers, replacing spark plugs, and servicing landing gear wheel bearings. Anything beyond that list needs an appropriately rated mechanic, and any major alteration or repair requires an FAA Form 337 (an STC would reference it). Worn cylinders matter here too — as cylinders lose compression, the engine loses power.

It's dual-purpose: it lets air in so fuel can flow out of the tank without creating a vacuum, and it lets pressure (and expanding fuel) escape if the tank is over-full or heats up. A blocked vent can starve the engine even with fuel in the tank.

Almost certainly hydraulic fluid, which is dyed red. On this airplane hydraulic fluid serves the brakes, the oleo struts, and the nose-wheel shimmy dampener. (Don't confuse it with old 80-octane avgas, which was also red.) A clear puddle is the suspicious one — could be water or Jet A.

Vestibular (inner-ear motion sensing), somatosensory ("seat of the pants"), and visual — the visual system is the most reliable; the others mislead in IMC.

Trapped air expands and contracts with altitude; clear it by swallowing, yawning, or the Valsalva maneuver (gently exhale against a pinched nose and closed mouth). Don't fly with congestion — descents are the painful part.

Hypoxic (insufficient O₂ at altitude), hypemic (blood can't carry O₂ — CO poisoning, anemia), histotoxic (cells can't use O₂ — alcohol/drugs), stagnant (poor circulation — G-forces). Symptoms: euphoria, impaired judgment, cyanosis, tunnel vision, headache.

Over-breathing blows off CO₂; symptoms mimic hypoxia. Slow the breathing rate, talk aloud, or breathe into a bag.

Odorless exhaust gas, often from a cracked heater muff. Headache, dizziness, drowsiness. Turn off the heater, open fresh-air vents, use 100% O₂ if available, and land.

Narrow runway → feel too high (fly low); wide runway → feel too low (fly high); upsloping runway/terrain → feel too high; plus featureless-terrain / black-hole approaches and autokinesis (a static light appears to move).

At least 12 hours after a no-decompression dive before flying to cabin altitudes up to 8,000 ft; at least 24 hours after a dive requiring a controlled ascent; and at least 24 hours after any dive before flying above 8,000 ft.

No flying within 8 hours of "bottle to throttle," while under the influence, or with a BAC of 0.04 or greater. Alcohol/drug convictions must be reported.

Above 12,500 ft cabin altitude for more than 30 minutes — required minimum flight crew must use O₂; above 14,000 ft — crew uses O₂ continuously; above 15,000 ft — each occupant must be provided O₂.

A systematic, structured approach to consistently determining the best course of action for a given set of circumstances. Its two defining elements are hazard and risk.

• Anti-authority ("Don't tell me") → Follow the rules; they're usually right.
• Impulsivity ("Do something quickly") → Not so fast — think first.
• Invulnerability ("It won't happen to me") → It could happen to me.
• Macho ("I can do it") → Taking chances is foolish.
• Resignation ("What's the use?") → I'm not helpless; I can make a difference.

Managing all available resources — onboard (instruments, avionics, autopilot, checklists, passengers) and outside (ATC, flight service, flight following) — to reduce workload and maintain safety. SRM is the umbrella over the tools below.

Prioritize and sequence tasks so you're never saturated: aviate, navigate, communicate, in that order. Offload low-priority items, use checklists, and plan high-workload phases in advance.

An accurate, continuous picture of the aircraft, environment, and your own state. Lost SA shows up as fixation, confusion, or falling behind the airplane; rebuild it by stepping back to aviate-navigate-communicate.

Controlled flight into terrain — a flyable airplane flown into the ground, usually from lost SA, low visibility, or night/terrain. Mitigate with terrain awareness, proper altitudes, and not descending below safe minimums without positive position knowledge.

Know what the avionics/autopilot are doing and stay ahead of them; don't let heads-down programming erode your scan or SA. Be ready to drop to a lower level of automation and hand-fly.

Notify the nearest NTSB office immediately for an aircraft accident (death, serious injury, or substantial damage) or any of these serious incidents: flight control system malfunction or failure; a required crewmember unable to perform duties from injury/illness; in-flight fire; mid-air collision; certain turbine-engine failures; or property damage (other than the aircraft) over $25,000. A written report (Form 6120) is due within 10 days for an accident; within 7 days if an overdue aircraft is still missing (49 CFR 830).

Carbon monoxide (CO — not CO₂) bonds to the hemoglobin in red blood cells roughly 200 times more readily than oxygen does, so even a trace of exhaust in the cabin progressively crowds oxygen off the blood cells and causes hypemic hypoxia. That's why a small crack in the heater muff matters, and why smoking (which loads CO into the blood) raises susceptibility before you ever take off (PHAK ch 16).

Cones, concentrated at the center of the retina, give color and detail in good light; rods, out in the periphery, are far more sensitive in dim light. At night the center of your vision is effectively a blind spot, so scan by looking slightly off-center from what you want to see (PHAK ch 16).

Under the pressure of a dive, nitrogen dissolves into body tissues. As pressure drops it comes back out of solution and takes the path of least resistance — the joints, for example. Climbing to altitude after a dive is essentially a second ascent with even lower pressure, which is why the 12/24-hour wait times in the Quick Review exist (AIM 8-1-2).

Read the surface: wind streaks and foam lines run with the wind (foam spills off the downwind side of ripples); smoke, flags, and moored boats point it out on shore. Swells persist from distant or old winds and may not match the local wind — evaluate wind, swell direction, and water state separately. Glassy water hides height cues; rough water sets a structural limit.

Surface state (glassy, light chop — the ideal, rough), swell systems (land parallel to big swells, not through them), current in rivers and tidal areas, water depth and floating debris, and traffic wakes — a boat wake can be usable chop or a hazard depending on angle and size.

The Chart Supplement lists seaplane bases (identifiers with an anchor symbol on sectionals); the Water Aerodrome/seaplane base entries give operating restrictions, docking, and fuel. Local NOTAMs and the base operator fill in hazards charts can't — cables, sandbars, seasonal debris (FAA-H-8083-23; Chart Supplement).

On the water you are a vessel under the Inland/COLREGS navigation rules: give way to vessels you're overtaking, vessels constrained by draft, and generally anything less maneuverable; cross behind, not ahead. A seaplane on the water is among the least privileged vessels — stay clear of everything you can (14 CFR 91.115: on water, keep clear of all vessels and avoid impeding navigation).

Lateral buoys: red-right-returning — red nun buoys mark the right side of a channel returning from sea; green cans mark the left. Junction, danger/isolated-hazard, and regulatory/informational buoys (white with orange bands) mark exclusion zones, speed limits, and hazards. Treat marked swim and mooring areas as no-go (USCG Navigation Rules; FAA-H-8083-23).

Boat traffic and wakes, swimmers near shore, submerged obstacles (rocks, pilings, cables — often uncharted), debris after storms, current setting you into obstructions while taxiing or sailing, and noise-sensitive shorelines. A recon pass over an unfamiliar water area before committing is standard practice.

I run the IMSAFE self-check before every flight. If any item is questionable, I don't fly. Beyond the checklist, I honestly ask whether external pressures (a schedule, passengers waiting, get-there-itis) are pushing me to fly when I otherwise wouldn't (PHAK ch 2).

Two parts. Legally airworthy: required documents on board (ARROW), required inspections current (annual, 100-hour if for hire, transponder/altimeter as applicable, ELT), ADs complied with, and any inoperative equipment handled per 91.213. Practically appropriate: the preflight inspection shows it conforms to type design and is in condition for safe operation — and it has the performance and equipment for this mission (runway lengths, terrain, night, weather).

The POH checklist exists because memory fails under distraction — the classic missed items (fuel caps, tow bar, pitot cover, baggage door) happen when a flow gets interrupted. I use the manufacturer's sequence so nothing depends on my memory, and if I'm interrupted I back up several steps or restart the section.

I sump each drain point into a clear tester and check for water (bubbles or a distinct layer at the bottom), sediment, and correct color/smell. If I find water, I keep sumping until I get clean samples — and if it won't clear, or I suspect a larger problem (bad fuel batch, cap seal leak after rain), the airplane doesn't fly until a mechanic looks at it. I also verify quantity visually, never trusting gauges alone.

Weather along the whole route (not just departure), terrain and obstructions relative to my climb performance, density altitude, runway conditions and lengths, airspace, and NOTAMs/TFRs. I keep assessing after engine start — preflight assessment doesn't end at the hangar (PA.II.A.S4).

I use PAVE to structure it: Pilot (IMSAFE, currency vs. proficiency), Aircraft (airworthiness, performance, fuel), enVironment (weather, airport, terrain, airspace), External pressures (passengers, schedules). For each category I identify hazards, mitigate what I can, and set personal minimums in advance so the go/no-go decision isn't made under pressure (PHAK ch 2).

Lock the aircraft, verify no tampering during preflight, challenge unfamiliar people around aircraft, know the airport's security procedures, and report suspicious activity (AOPA's Airport Watch line, 866-GA-SECURE). I also stay aware of TFRs — a security violation is one of the easiest ways to meet an F-16.

By regulation: how to fasten and unfasten their seatbelt and shoulder harness, and that belts must be on for taxi, takeoff, and landing (91.107). As PIC I must ensure everyone is briefed and belted before I move the airplane. A good briefing goes well beyond the minimum — I use SAFETY.

No non-essential conversation or activity during critical phases — taxi, takeoff, approach, landing, and anything abnormal. I brief passengers on it up front so asking for quiet isn't awkward in the moment. Airlines are required to do it; I adopt it voluntarily because distraction during critical phases is a leading accident factor (AC 120-71).

Anything loose becomes a projectile in turbulence or a sudden stop, can jam the flight controls (the classic water bottle under the rudder pedals), and heavy items shift my weight and balance. Baggage gets strapped down or stowed within placard limits, and I confirm the baggage door is latched as part of my flow.

No part 91 rule mandates current charts for VFR, but 91.103 requires familiarity with all available information, and stale data undermines that. My practice: current sectional/EFB data and Chart Supplement info, and if I use GPS I check the database cycle — expired data gets treated with suspicion, especially for airspace and frequencies.

The autopilot and EFB are workload tools, not substitutes for flying. My rules: program before taxi, not while moving; always know what mode the automation is in; if it does something unexpected, disconnect and hand-fly first, troubleshoot second. For the EFB I carry a backup, manage battery and overheating, and mount it where it doesn't block view or controls.

Give them a real job: watching for traffic, holding checklists. That channels curiosity into usefulness. The briefing already set the rule — during sterile phases, speak up immediately for traffic or smoke, hold everything else until cruise. If a distraction happens anyway: fly the airplane first, then deal with the cabin.

Same 91.213 process as preflight: is it required by the type design/equipment list, by 91.205 for this kind of flight, or by an AD? If not required, deactivate and placard it INOP and I can go. If required, no flight until it's fixed or properly deferred. Beyond legality, I ask whether it's smart for this mission — legal to go isn't always safe to go.

Position and people. Airplane pointed so prop blast doesn't hit open hangars, people, or loose gravel; nothing and nobody behind me; brakes set or wheels chocked; and a loud 'CLEAR PROP' with a pause and a look before cranking — the pause matters, because someone may be moving toward the airplane the moment I yell (AFH ch 2).

Cold: the fuel doesn't vaporize well, so it needs priming — a few strokes of primer (or pumping the throttle per POH), then crank. Hot: the engine usually needs little or no prime; over-priming a hot engine is the classic way to flood it. Either way I follow the POH sequence, not habit.

Flooded means too much fuel, so I lean it out: mixture to idle cutoff, throttle full open, crank. The engine clears the excess fuel and fires — then immediately mixture rich and throttle back to idle. Full throttle with the mixture in is why flooded-start attempts sometimes end in a runaway RPM surprise; the mixture stays at cutoff until it fires.

The starter duty cycle in the POH — typically crank for a limited time, then a mandated cooling period before the next attempt, because starters overheat and fail quickly. Also oil pressure: it must come up within the POH time limit (commonly about 30 seconds, longer in cold weather) or I shut down. And minimum oil temperature/viscosity considerations for very cold starts, including preheat when it's cold enough.

No oil pressure within the POH limit, abnormal noises or smoke, an engine fire indication, RPM surging uncontrollably, a person or vehicle appearing near the prop, or the airplane starting to roll. For an engine fire during start, the POH memory item is generally: keep cranking to pull the fire into the engine, mixture to cutoff, fuel off, and get the extinguisher if it doesn't go out.

Follow the POH exactly — polarity and voltage must match, connection/disconnection order matters, and the avionics stay off during the jump to protect them from spikes. Bigger question: why is the battery dead? A battery too weak to start may also be too weak to be a reliable electrical backup in flight, so I want the cause understood before I go flying, especially at night or into IMC-adjacent conditions.

Treat every prop as if the mags are hot — a broken P-lead means the engine can fire from a small blade movement even with the key out. I never let anyone stand in or walk through the prop arc, I brief passengers on it, and when I move the prop for any reason (which I avoid), it's with mags confirmed off, mixture at cutoff, and the same respect as hand-propping.

'Climb into a headwind, dive away from a tailwind.' Quartering headwind: aileron into the wind (up-aileron on the windward side), elevator neutral. Quartering tailwind: aileron away from the wind (dive away), elevator down. The goal is to keep the wind from lifting a wing or the tail (AFH ch 2).

A brake check — immediately, while there's still room to stop with something else (mixture, or steering clear) if the brakes fail. Then taxi at a walking-pace speed near obstacles, controlling speed with throttle first and brakes second; riding the brakes overheats them and masks a developing failure.

Plan before moving: airport diagram out, expected taxi route drawn, Hot Spots identified (they're marked on the diagram and in the Chart Supplement). Write down the taxi clearance, read it back with my callsign, and never cross any runway without an explicit crossing clearance — ATC must issue one for each runway, and 'taxi to' a runway never authorizes crossing the assigned runway or entering it. Sterile flight deck while taxiing, heads-up, and if I'm ever unsure of position: stop (off the runway), and ask. Request progressive taxi if unfamiliar (AC 91-73, AIM 4-3).

Four yellow lines across the taxiway: two solid, two dashed. Solid side toward you means hold — you need a clearance (towered) or a self-clear (nontowered) to proceed. Dashed side toward you means you're exiting the runway; cross without stopping and clear the marking entirely. The runway isn't 'cleared' until the whole airplane is past the hold short lines. Also know the ILS critical area marking (the ladder) and the red-and-white runway signs versus yellow-on-black location signs (AIM 2-3).

No clearances — I self-announce on CTAF ('Warrior 123AB taxiing from the ramp to runway 16'), listen to build a picture of who's where, and visually clear every runway in both directions before crossing, even if the radio is quiet. NORDO aircraft exist. Expectation bias is the trap: hearing what I expect instead of what was actually said, or assuming the runway in use.

Stop the mental autopilot. If needed, physically stop the airplane clear of taxiway intersections, pull up the diagram, rebrief the new route and any new hot spots, and reload takeoff data if the runway changed (numbers, intersection distance, wind). A runway change is a classic setup for both incursions and wrong-runway departures — the old plan has to be consciously discarded.

Slower, more deliberate, and diagram-in-hand. Use the taxiway lighting/marking system: blue edge lights, green centerline lights at some airports, and know that geographic position markings (pink spots) exist for low-vis routes. Aircraft lights per AIM 4-3-23: nav lights on from sunset, beacon whenever the engine runs, taxi/landing light while moving (courtesy: don't blind others while holding), and strobes off around other aircraft on the ground. It's easy to get lost at a big airport at night — if unsure, stop and ask ground.

Idle (displacement) taxi: low RPM, nose-up, floats deep in the water — the normal mode for maneuvering, and the only sensible one near docks and traffic. Water rudders down. Plow taxi: nose-high with substantial power, the hull pushing a big bow wave — poor visibility, poor cooling, heavy spray. It's a transition state, not a destination; I avoid staying in it except momentarily (e.g., turning downwind in strong wind where its nose-high attitude helps). Step taxi: on the step at planing speed, water rudders up, steering with air rudder — used to cover distance quickly when the area ahead is confirmed clear. High energy, long stopping distance, and porpoise/skip risk if the pitch attitude is wrong (Seaplane Handbook FAA-H-8083-23 ch 4).

Down for displacement taxiing and most slow maneuvering; up for takeoff, landing, step taxi, and sailing (usually). They're small and can be damaged or ineffective at speed, and during sailing you often want the tail free to weathervane. It's a flow item every transition: 'water rudders — position.'

Sailing is maneuvering with the engine at idle or shut down, using the wind (and current) to move — typically backward or backward-and-sideways, since a seaplane weathervanes nose into wind. To sail toward a spot behind me: raise the water rudders, and use the air controls and doors as sails. Ailerons and rudder deflect to swing the tail; opening a door on one side adds drag/area to pull that side back; flaps down increase the surface area catching wind to drift back faster. The counterintuitive part: with the airplane drifting backward, I position controls opposite to my taxi instincts — I'm steering the tail, not the nose (FAA-H-8083-23 ch 4).

On the water I follow the nautical rules of the road (and 91.115 for water operations): the less maneuverable vessel has the right of way — and a seaplane on the water is usually more maneuverable-restricted than it looks but is still expected to keep clear of vessels it's overtaking. Crossing: the vessel to my right has right of way. Approaching head-on: alter course to the right, pass port-to-port. Overtaking: the overtaken vessel has right of way. Practical rule: seaplanes stay well clear of everything — swimmers, kayaks, wakes — regardless of who technically has the right of way.

Both are pitch-attitude problems. Porpoising (rhythmic bow-up/bow-down oscillation) means the attitude is outside the sweet spot — correct by re-establishing the proper planing attitude with firm, smooth elevator, and if it's diverging, close the throttle and let the airplane settle off the step. Skipping (bouncing off wave tops) usually comes from excess speed or striking swells at the wrong attitude — again, fix the attitude or come off the step. The wrong answer is chasing the oscillation with out-of-phase elevator inputs, which amplifies it.

The water tells you: wind streaks and ripples run with the wind (streaks align with it; the glassy band on the lee shore means calm), waves build with fetch toward the downwind shore, and moored boats and birds point into the wind. My own airplane weathervanes nose-to-wind at idle, which is a constant live wind indicator. Current can differ from wind — flags and streaks show wind, drifting debris shows current — and near a dock I have to plan for both.

First decide how the wind will move me the second the lines come off — a seaplane at idle drifts immediately. Ideally the wind pushes me away from the dock: cast off, let it drift clear, then start up. If the wind pins me to the dock, I may need to hand-turn the airplane, walk it to the end of the dock, or sail off. I plan the whole path before untying: where I'll start the engine, my taxi route, hazards (buoys, swimmers, shallow water), and an escape option if the engine doesn't start while drifting (FAA-H-8083-23 ch 4, 6).

Same structure as land airports: seaplane bases are listed in the Chart Supplement (with an anchor symbol on the sectional), and many share a CTAF for self-announcing taxi, takeoff, and landing intentions. At a towered field with a water landing area, I follow ATC instructions like any other operation, and an amphib complies with all the land taxi rules of Task II.D. Water lanes may be marked with buoys — know the local scheme before arriving.

The preflight inspected the airframe cold; the runup verifies the systems under power right before I bet a takeoff on them: ignition redundancy, carb heat, engine instruments in the green, flight instruments set, controls free and correct, and configuration (flaps, trim) matching the takeoff I briefed. It's the last chance to catch a malfunction while stopping is free (AFH ch 2, POH).

Two things. The RPM drop on each mag confirms that mag is actually being tested and the timing is roughly right — no drop at all suggests a broken P-lead (a hot mag). An excessive drop or rough running points to a fouled plug or failing mag. The difference between the two mags matters too, since a big split means one system is unhealthy. A fouled plug can often be cleared by leaning aggressively at moderate RPM for a bit, then rechecking — if it won't clear, taxi back.

Pointed as close to into the wind as practical (cooling for the engine), on a surface that won't sandblast the prop or throw stones into whatever's behind me, not aimed at other aircraft or people with my prop blast, and where I can still watch for traffic. I also make sure the nosewheel is straight and the area ahead is clear in case the airplane creeps.

Runway and expected performance (rotation speed, distance versus available), initial heading/altitude, and the emergency plan by phase: abort on the runway for anything abnormal before rotation; engine failure below my turnaround decision altitude means land ahead within roughly 30 degrees either side; above it, the options open up. Saying it out loud pre-loads the decision so an actual failure gets action, not deliberation. I also confirm the takeoff performance numbers I calculated still match reality — wind, runway, weight.

Anything abnormal before rotation: engine roughness, RPM not reaching the expected static value, airspeed not alive by my callout point, a door popping open, a warning light, an animal or aircraft on the runway. The decision is pre-made — abnormal equals abort — because inventing a decision at 50 knots wastes the runway I need to stop.

Re-run the numbers mentally: new runway length and surface, new wind components (is it now a tailwind or a bigger crosswind?), obstacle picture, and my emergency plan (the land-ahead options are different off a different runway). If the new runway doesn't work for my performance or comfort, the answer to ATC is 'unable.' A runway change also resets my wake-turbulence and taxi-route thinking.

Wingtip vortices sink and drift with the wind, and are worst behind heavy, slow, clean airplanes. Departing behind a large departing aircraft: rotate before its rotation point and climb upwind of its path. Behind a landing large aircraft: lift off beyond its touchdown point. If timing is tight, waiting two to three minutes costs nothing — I can tell tower I'll hold for wake turbulence (AIM 7-4).

The checklist gets done thoroughly but I keep a scan outside — traffic on final, aircraft taxiing behind me, and my hold-short position. If ATC interrupts mid-checklist, I answer, then back up several items rather than trusting that I remember where I was. Rushing the runup because someone's waiting behind me is exactly the external pressure the ACS wants me to recognize and reject.

Sectional chart (tower, CTAF, ATIS boxes), the Chart Supplement (the complete listing — ground, clearance, approach, FSS), the airport diagram, and NOTAMs for temporary changes. In the air: 121.5 is always the emergency frequency, and FSS is available on 122.2 and charted remote frequencies (AIM 4-1).

Nontowered (CTAF): self-announce position and intentions — who I am, where I am, what I'm doing, at which airport, with the airport name at both ends of the call ('Chino traffic, Warrior 123AB, ten miles south, inbound for forty-five to left downwind runway two-six, Chino'). Nobody clears me; the radio builds a shared picture, and my eyes do the separating. Towered: listen to ATIS first, then initial contact with who they are, who I am, where I am, what I want, and the ATIS code. I read back all clearances and instructions — verbatim for hold-short and runway assignments — with my callsign (AIM 4-2, 4-3).

FAA table (AIM 4-3-13):

Memory hook: green means go (land/takeoff/taxi), steady beats flashing in urgency, and red/green together means 'be careful.' Acknowledge in daylight by rocking wings; at night by flashing the landing light.

Squawk 7600, stay VFR. First troubleshoot: volume, frequency, headset jacks, hand mic, second radio, second comm's flip-flop — most 'failures' are a knob. If it's really dead, I can transmit blind in case only the receiver failed, then follow AIM 4-2-13: remain outside or above Class D, determine the flow, enter the pattern, and watch the tower for light gun signals, acknowledging with wing rock or landing light. At night I'd also consider going somewhere nontowered instead.

7500 hijacking, 7600 lost comm, 7700 emergency ('seventy-five, taken alive; seventy-six, radio fix; seventy-seven, going to heaven'). Squawk 1200 for normal VFR, with altitude reporting on — Mode C is required in Class A/B/C, above 10,000 feet MSL, and within the 30 nm Mode C veil of Class B airports (91.215). Never cycle through the emergency codes while changing a squawk. Related: radar can do a lot for a VFR pilot — flight following gives traffic advisories and safety alerts workload permitting, and if I'm lost or in trouble, saying so gets vectors and the full toolkit. Declaring an emergency is a decision I make early, not after options run out.

RWSL is automatic, ATC-independent: red in-pavement Runway Entrance Lights (RELs) at taxiway/runway crossings mean the runway is unsafe to enter; red Takeoff Hold Lights (THLs) on the runway mean unsafe to depart. Red lights, don't move — even with a clearance; query ATC (AIM 2-1-6). PAPI: four lights in a row — two white two red is on the roughly 3-degree path; more white, high; more red, low ('all red, you're dead'). VASI: two bars — red over white is on path; white over white high; red over red low. VASI guarantees obstacle clearance within plus/minus 10 degrees of extended centerline out to 4 nm (AIM 2-1-2).

Runway edge lights white (HIRL/MIRL/LIRL by intensity), turning amber in the caution zone on instrument runways; threshold lights green from the approach side and red from the runway side (end lights); REILs are flashing strobes marking the threshold. Taxiways: blue edge lights, green centerline at bigger airports. The rotating beacon flashes white-green for a lighted land airport — and a beacon on during the day suggests IFR weather in Class B/C/D/E surface areas. Pilot-controlled lighting: key the mic 7, 5, or 3 times on the designated frequency for high, medium, or low intensity (AIM 2-1).

An accident involves death or serious injury, or substantial damage to the aircraft — NTSB notification is immediate, and a report on Form 6120.1 is due within 10 days. Certain incidents also require immediate notification (NTSB 830.5): flight control system failure, crew incapacitation, propeller blade release, in-flight fire, mid-air collision damage, and an overdue aircraft believed in an accident, among others. Substantial damage excludes things like bent fairings, small skin dents, and ground-only prop damage.

Maintain within ±100 ft of traffic pattern altitude, with correct entry and spacing from other traffic.

Climb at Vy +10/−5 kt. Know your numbers before the roll — rotation speed, Vy, and abort criteria.

Touch down within 400 ft beyond the specified aim point, on centerline, with proper crosswind correction.

Keep weight off the nosewheel throughout; lift off at the lowest safe speed and accelerate in ground effect before climbing.

Touch down softly with no side drift, nosewheel held off as long as practical.

Best obstacle-clearance technique: full length, recommended flap setting, rotate at the recommended speed, climb at Vx until the obstacle is cleared, then Vy.

Touch down within +200/−0 ft of the specified point — never short — using the recommended approach speed and configuration.

Anything that limits the usable takeoff run or the climb-out: a small lake, a river bend, surrounding trees or terrain, shoreline obstacles. Before committing I evaluate from the air or the water: total usable distance for the wind that exists, obstacle heights on the climb path, water condition (glassy adds distance, light chop helps), density altitude, and my weight. The honest math question: does distance available comfortably exceed distance required to clear the obstacles — with margin? If not, offload, wait for wind, or don't go (Seaplane Handbook FAA-H-8083-23 ch 5).

Use all of it: start from the very edge, taxi back into the last usable corner. Use a curved takeoff path — start crosswind along the shore and arc into the wind so the total run exceeds the straight-line dimension of the area. Take off into the wind whenever possible, use the recommended flap setting, get on the step promptly and hold the sweet-spot planing attitude (minimum water drag), and lift off at the recommended speed rather than forcing it early into a mush. On glassy days, breaking one float free first reduces drag for liftoff.

Vx, best angle — most altitude per unit of horizontal distance — until the obstacle is cleared (ACS: Vx or the POH obstacle speed, +10/−5 knots, until clear or 50 feet). Then lower the nose to Vy, best rate — most altitude per unit of time — and hold Vy +10/−5 to a safe maneuvering altitude, retracting flaps once a positive rate is verified. Climbing at Vx longer than necessary costs engine cooling and leaves me slow near the ground.

Checklist complete, radio call, verify the takeoff path and wind (streaks, moored boats, drift). Clear the area — including a look for boats that may cross my path mid-run. Taxi to maximize the run, water rudders up, controls set for the wind. Throttle smoothly to full, check engine instruments and airspeed alive, establish the planing attitude, correct any porpoise or skip immediately, minimize spray through the prop, rotate at the recommended speed, then Vx (+10/−5) over the obstacle, transition to Vy, flaps up with positive rate, wind-drift correction throughout.

Decision point chosen before the run: a landmark by which I must be on the step and accelerating, or I chop the power. Water gives me an advantage over a runway — closing the throttle means I can usually just settle back on and stop. What kills people is pressing on past the point where neither flying over the obstacle nor stopping short of it works. Engine failure after liftoff: land ahead on whatever water remains, wings level, at minimum speed — not a turn-back from low altitude.

Boats and jet-skis that don't know a takeoff run is happening and have every right to be there, swimmers near shorelines, floating debris and deadheads (semi-submerged logs), birds lifting off the water ahead of me, and wires spanning river narrows — wires are nearly invisible and charted inconsistently. A high-speed step run into an unswept area is the classic setup, which is why I inspect the full path first, not just the first half.

Light chop is the friendly surface — it breaks the suction on the floats and shortens the run. Glassy water adds significant distance because the floats stay stuck to the surface tension. Rough water and swell slow acceleration and can throw the airplane airborne prematurely at below flying speed. Current matters on rivers: taking off downstream adds groundspeed 'free,' but the wind usually dominates the decision (FAA-H-8083-23 ch 5).

A deliberate reconnaissance before descending: circle at a safe altitude and check the usable landing distance for today's wind, obstacles on the approach and go-around paths, water condition (glassy? chop? swell?), water depth and color changes (shoals), boats, swimmers, debris, and wires across approaches. I pick the touchdown point, the go-around path, and an 'if the engine quits here' option before starting down. If the area doesn't work with margin, I find another spot — that's the whole risk-management point of this task (Seaplane Handbook FAA-H-8083-23 ch 6).

Configuration set, on speed, on the intended glidepath, trimmed, with only small corrections needed — established early and continuously. In a confined area the approach is often steeper (over obstacles) and the touchdown window is small; an unstable approach converts directly into floating past my point or arriving fast. My rule matches the ACS logic: if it's not stabilized, go around — early, while the go-around path still works.

The manufacturer's published approach speed, or if none is published, no more than 1.3 Vso, +10/−5 knots with gust factor applied (the ACS skill standard). Excess speed is the enemy: every extra knot becomes float, and float eats a confined area's margin fast. Energy management means arriving over the obstacle with just enough — steep, slow (but safe), and configured.

Full flaps (or POH recommendation), speed nailed, and a steeper-than-normal descent path aimed to clear the obstacle with minimum excess altitude — power controls the descent path, pitch holds the speed. Once past the obstacle, I can release the extra altitude and land on the selected point: touchdown in the proper pitch attitude, within the ACS's 200 feet beyond the point, no side drift, longitudinal axis aligned. After touchdown, elevator back as needed to stay off the step quickly and stop in the shortest safe distance.

Immediately when the approach falls outside tolerances, the touchdown point won't work, or anything enters the area — and the how was planned during the recon: full power, positive climb attitude, flaps retracted per POH, following the pre-identified path over the lowest obstacles or along the terrain's escape route. The trap is the late go-around: in a confined area, past a certain point the go-around path no longer outclimbs the terrain, so my decision point is early and briefed.

Wind: land into it whenever the geometry allows — groundspeed at touchdown drives stopping distance. Crosswind: wing-low sideslip through touchdown, and know when the crosswind plus the geometry equals 'no.' Tailwind landings in a confined area are a last resort. Water: light chop is ideal; glassy water in a confined area is a double threat because glassy technique wants a long, shallow, power-on descent that a small area may not accommodate — that combination may simply be a no-go (FAA-H-8083-23 ch 6, 8).

Committing without a real recon; letting the approach get fast ('just a few knots'); fixating on the touchdown point while a boat enters the area (task fixation versus situational awareness); the late go-around; and low-altitude maneuvering to salvage geometry — steep low turns to the point are how stall/spin accidents happen. The ACS answer is always the same: stabilized or go around, and go around early.

A mirror-smooth surface with no wind and no ripples. Two problems on takeoff: the smooth surface creates strong adhesion — the floats stick to the water and drag is higher than on light chop, stretching the takeoff run considerably — and the lack of surface texture makes height and attitude judgment unreliable once airborne (the bigger issue on landing, but it matters in the climb-out too). No wind also means no headwind help (Seaplane Handbook FAA-H-8083-23 ch 5, 8).

Normal start of the run: water rudders up, full power, establish the planing attitude on the step. Because the water won't let go, the standard technique is to break one float free first: once on the step at speed, apply aileron to lift one float out of the water — that halves the wetted surface and drag, the airplane accelerates, and the second float releases. Lift off, then immediately level the wings and lower the nose slightly to accelerate in ground effect before climbing, because liftoff happens at minimum speed. Then establish Vy +10/−5 to a safe altitude (FAA-H-8083-23 ch 5).

The airplane breaks free at a speed barely above stall. Ground effect reduces induced drag near the surface, so it can accelerate there when it couldn't climb cleanly yet. Pulling up out of ground effect at that speed risks settling back onto the water — or a stall — with no surface texture to judge the sink. Level acceleration to a healthy climb speed first, then up.

Carefully, because glassy water hides everything: floating debris, deadheads, and swimmers are harder to spot without ripples to break the reflections, and the mirrored surface can camouflage boats' wakes. I inspect the full takeoff path at slow taxi first if there's any doubt, use shoreline references to hold a straight track (there's no wind streak to follow), and confirm the run available is generous — glassy adds distance, so a marginal area on a choppy day may be a no-go on a glassy one.

Same discipline as any water takeoff, with more margin required: a pre-picked landmark where I must be accelerating on the step or I close the throttle and settle back on. Engine failure after liftoff over glassy water is nasty because I can't judge height — the answer is the glassy-landing attitude: establish a nose-up landing attitude, accept the descent, and let the airplane fly onto the water rather than trying to judge a flare. Land ahead, wings level; no low turn-backs.

Gear up for any water operation — a wheels-down water touchdown flips the airplane. The glassy tie-in: this task's risk list calls it out because glassy days are exactly when a distracted pilot mis-sets the gear, and there's no visual surface cue to trigger a late catch. Verbal confirmation every time: 'this is a water takeoff/landing — gear is up.'

The planing attitude sweet spot still rules: too nose-low digs the float bows and invites porpoising; too nose-high plows and kills acceleration — worse on glassy water because the drag is already elevated. Corrections are smooth and immediate; if an oscillation grows, throttle closed, settle, and start over. Also keep the spray out of the prop during the acceleration — spray erosion is real, and the nose attitude controls it.

Because your eyes lie. A mirror surface gives no texture for depth perception — pilots flare 20 feet in the air or fly straight into the water at speed, and the accident record shows experienced pilots doing both. The surface may also reflect sky and clouds so convincingly that there's no visible surface at all. The fix is a complete change of method: stop judging height visually and fly a known attitude with a known descent rate all the way to touchdown (Seaplane Handbook FAA-H-8083-23 ch 8).

Any time I can't reliably judge height above the surface: true glassy calm, but also night water landings where permitted and practical, hazy sun-glare conditions, and big open water without shoreline references. The cost is a longer, shallower, power-on approach that uses more distance — so the decision also depends on having enough room.

Fly a normal pattern to the last visual reference — typically the shoreline or an object at the water's edge, since height judgment is still trustworthy over textured terrain. Crossing that final reference at a couple hundred feet, I set the airplane up completely: landing configuration, the POH-recommended nose-up landing attitude, and power adjusted for roughly a 150 fpm descent (no more than about 200). Then I hold that attitude and descent rate with the instruments and trim and simply wait — no flare, no visual height judgment — until the airplane flies onto the water. On touchdown: throttle idle, stick back as the airplane comes off the step (FAA-H-8083-23 ch 8).

A flare requires knowing your height, and over glass you don't. The constant nose-up attitude guarantees the floats contact water at the correct pitch no matter when touchdown comes, and the shallow 150 fpm rate makes the arrival gentle whether it happens now or ten seconds from now. Power is what makes the descent rate controllable and shallow — a power-off glassy approach arrives too fast and too steep to survive an unjudged touchdown.

Manufacturer's published approach speed, or absent one, no more than 1.3 Vso, +10/−5 knots (ACS skill standard), with the approach stabilized early — configuration, attitude, descent rate, and trim locked in by the final visual reference. Trim matters more than usual: the technique is attitude-holding for an extended period, and a well-trimmed airplane holds it almost hands-off.

Distance: the shallow approach consumes a lot of water — verify the area is long enough, since glassy technique and a confined area may be incompatible. Hidden hazards: glass hides deadheads, debris, and shallow water; recon first. Impatience: the classic error is 'it's taking too long, I'll just ease it down' — abandoning the attitude is how the technique fails; fly it until it touches. Amphibian gear: gear up for water, verbally confirmed — glassy landings are the highest-consequence moment for a gear mistake. Go-around: power is already in, so committing to a go-around is quick — attitude, full power, climb, and re-plan.

Same as any go-around, with one wrinkle: I may not know exactly how high I am. Full power, establish a positive climb attitude by instruments and feel, verify a positive rate before reconfiguring, and don't push the nose down for airspeed near the surface. Triggers include drift off the planned path, anything appearing in the touchdown zone, an unstable descent rate, or reaching my pre-planned abort point along the shore reference without touching down.

Waves and swell big enough to pound the floats and disturb the takeoff run — as a practical matter, anything beyond light chop for a small floatplane. The rough water technique applies whenever wave impacts could damage the airplane or throw it airborne below flying speed. There's also an upper limit: every seaplane has a sea state it simply can't operate in safely, and knowing when to stay tied up is part of this task (Seaplane Handbook FAA-H-8083-23 ch 5).

Flaps per POH, water rudders up, controls set for the wind. The core idea is to spend minimum time in the water-impact zone: get on the step promptly, hold a slightly more nose-up planing attitude than normal so the float bows ride over the wave crests instead of digging in, and lift off at minimum airspeed — often helped off a wave crest — then stay in ground effect to accelerate to Vy before climbing (that's the ACS skill: lift off at minimum airspeed and accelerate to Vy +10/−5 before leaving ground effect). Once airborne, don't settle back into a crest (FAA-H-8083-23 ch 5).

Wind and swell don't always align — swell persists from old winds or distant weather. Ideal is into the wind and parallel to (or along) the swell; when they conflict, taking the swell at an angle usually beats pounding straight into wave faces, even at the cost of some crosswind. The ACS wants me to determine wind with or without indicators (streaks, spray blowing off crests, moored boats) and choose a path considering wind, swells, hazards, and vessels — then verify the whole run is clear, because a rough surface hides floating debris.

Elevated on both counts: wave impacts continually disturb the pitch attitude, and a bounce off a crest at the wrong attitude starts a skip; the wrong recovery input turns it into a porpoise. Corrections: re-establish the correct planing attitude smoothly and firmly — don't chase the oscillation — and if it's diverging, close the throttle and let the airplane settle. Spray management matters too: nose attitude keeps solid water out of the prop arc, and rough water throws a lot of it.

Pre-picked decision point: on the step and accelerating by a chosen landmark, or throttle closed. Aborting in rough water needs care — coming off the step fast into big waves pounds the airplane, so I decelerate as smoothly as the surface allows. Engine failure after liftoff: land ahead, wings level, at minimum speed, in the rough-water landing attitude — touchdown attitude matters even more when the surface is hostile. No turn-backs from low altitude.

Flaps as the POH recommends for rough/shortest-run takeoffs (they lower the liftoff speed, which is the whole game here), water rudders up before the run, and in an amphibian: gear up, verbally confirmed — the risk list calls out gear position because rough-water workload is exactly when the check gets skipped. After liftoff: positive rate verified in ground effect and climb established before reconfiguring, then Vy +10/−5 to a safe altitude with wind-drift correction.

It moves personal minimums to the front. Factors: wave height versus float size and POH guidance, wind strength and gust spread, fetch (waves grow with distance across open water), traffic and rescue proximity, and my own recency in rough conditions. A takeoff that's legal can still exceed the airplane's structure or my skill — and unlike a runway, the surface can get worse while I'm out there, so the return-landing conditions are part of the departure decision.

Whenever waves or swell are big enough to pound the floats on touchdown — beyond light chop. The goal is to arrive at the lowest safe touchdown speed in a nose-up attitude so the float bows stay above the wave crests and the impact energy is minimized. Speed is the enemy: impact loads grow with the square of speed, so every knot shaved off touchdown matters more here than anywhere (Seaplane Handbook FAA-H-8083-23 ch 6).

A stabilized, slightly power-on final at the published approach speed (or at most 1.3 Vso, +10/−5 knots, gust factor applied). Touchdown: a slightly more nose-up attitude than normal, at minimum speed, timed where possible to contact a crest or the back side of a swell rather than flying into a wave face. At contact, close the throttle and hold the attitude with elevator — don't let the nose pitch down into the next wave — and let the airplane decelerate off the step with back pressure, accepting the pounding at ever-lower energy. Keep flying it until it's at displacement speed (FAA-H-8083-23 ch 6).

Swell usually wins. Landing into a big swell face can stop the airplane violently or throw it back into the air; landing parallel to the swell (in the trough or along the crest line) with a crosswind correction is generally the better trade, up to my crosswind limit. Small wind-driven chop aligned with the wind is the easy case — straight into it. The decision comes from a proper recon circle: read the swell direction and spacing, the wind (spray off crests, streaks), and pick the compromise heading before descending.

Configured early, on speed, trimmed, with a touch of power retained to control the descent rate to a gentle arrival. Carrying extra speed 'for safety' is exactly backwards on rough water — the ACS stabilized-approach knowledge element is about arriving with minimum excess energy. Gusty conditions: apply the gust factor to approach speed, but the touchdown itself still targets minimum speed and the nose-up attitude.

Unstable approach, drift I can't kill before touchdown, a boat or debris in the zone, or the surface looking worse than the recon suggested (it happens — spray and shadows read differently up close). Rough-water go-arounds are flown positively: full power, climb attitude, reconfigure with a positive rate. A firm early bounce off a wave is also a go-around cue: if the airplane skips back into the air with flying speed, adding power and going around beats riding an uncontrolled second touchdown.

Wing-low sideslip through touchdown, same as land — but the water adds weathervaning as soon as the floats dig in, so I'm ready with rudder as the airplane decelerates. In swell-parallel landings the crosswind is by choice, so I've already confirmed it's within my and the airplane's limits. Wake turbulence from vessels is a real item on busy water: a large boat's wake is effectively a moving swell system across my touchdown zone.

Gear up for water, verbally confirmed on final — the ACS risk element exists because high-workload approaches are where gear mistakes happen, and a wheels-down water touchdown is usually a capsize. After landing in rough water, the workload continues: taxi attitude and speed matter to keep spray out of the prop and waves off the nose, and the docking/beaching plan should already account for the surface conditions.

Same control inputs — bank one way, opposite rudder — different purpose and geometry. Forward slip: the longitudinal axis is yawed well off the flightpath; the airplane presents its side to the wind for maximum drag, so it descends steeply without gaining airspeed. The ground track continues straight toward the runway. Side slip: the longitudinal axis stays aligned with the runway; the bank kills crosswind drift. That's the crosswind landing tool. On a slipped approach in a crosswind, I fly the forward slip and then transition to a side slip before touchdown so the wheels meet the runway aligned (AFH ch 9).

When I'm high and need to lose altitude without gaining speed: flap failure, a power-off approach (engine-out practice or the real thing), obstacle-clearance approaches, or salvaging a high final when a go-around isn't the better answer. It's energy management — the slip converts altitude into drag heat instead of airspeed. Into which wind? Slip into the crosswind (low wing upwind) so the transition to the sideslip for touchdown is seamless.

Reduce power to idle (typical), lower the upwind wing with aileron, and apply opposite rudder — enough to yaw the nose away from the bank so the track stays on the extended centerline. Pitch controls airspeed, and the attitude will look unusually nose-low; hold the approach speed. Steepness is controlled by bank angle, with rudder to match — up to full rudder deflection as the limit. Recover by leveling the wings and releasing the rudder simultaneously, then re-trim and re-establish the normal approach or transition to the sideslip for touchdown (AFH ch 9).

Not necessarily. With the fuselage yawed to the relative wind, the static ports (and pitot) sit in disturbed flow, so the ASI can misread — commonly reading low or fluctuating, direction depends on the airplane and which side the ports are on. The answer is attitude flying: set a known pitch attitude for approach speed before entering, hold it, and treat the ASI with suspicion until the slip is out. Stall awareness stays high, though a properly flown forward slip at approach speed has healthy margin.

Some aircraft prohibit or advise against slips with full flaps — disturbed airflow over the tail can cause pitch oscillations or, in the extreme, reduced elevator authority (tail-stall territory in some types). Check the POH and placards for your airplane; many, including most PA-28s, have no prohibition. Fuel: in a prolonged slip with low fuel, the fuel can slosh away from the tank outlet and unport it, starving the engine — the reason slips are held only as long as needed, and why I'd favor the tank on the low wing being the feeding tank if selectable (the ACS calls out fuel flowage explicitly, PA.IV.M.R7).

Touch down at a proper pitch attitude within 400 feet beyond or on the specified point, no side drift, longitudinal axis aligned with and over the runway center or landing path — which means the forward slip must transition to a side slip (or wings-level in calm wind) before touchdown. Ground track stays on centerline throughout. And the standing rule behind all landing tasks: go around if the approach can't be completed within tolerances.

Touching down misaligned (the slip held too long — side loads on the gear), the unstable approach dressed up as a slip (a slip is a controlled tool, not a dive at the runway), airspeed control given the unreliable ASI, LAHSO implications if accepting land-and-hold-short, and the low-altitude maneuvering/stall-spin picture: cross-controlled flight close to the ground demands that the airspeed and attitude discipline be non-negotiable. The forward slip is cross-controlled by design but flown at approach speed with the nose down — the deadly cousin is the skidding base-to-final turn, which is the opposite input set.

A timely decision is the maneuver: takeoff power promptly, pitch for Vy, retract flaps incrementally per POH.

45° bank ±5°; altitude ±100 ft; airspeed ±10 kt; roll out within ±10° of the entry heading.

Altitude ±100 ft while holding a constant ground track with proper wind correction throughout.

Pilotage is navigating by what I can see — matching landmarks and visual references on the ground to the sectional. Dead reckoning is navigating by the numbers: pre-computed headings, groundspeeds, and elapsed times worked out from the airplane's performance and the winds aloft. In practice they work together — dead reckoning gets me between checkpoints, pilotage confirms each one.

The angular difference between true north and magnetic north at my location. Sectionals show it as isogonic lines (dashed magenta, e.g. 12°E); I apply it to convert true course to magnetic course. "East is least, west is best" — subtract easterly variation, add westerly.

The Chart Supplement — runways, frequencies, lighting, fuel, services, and remarks for every public airport. It's republished on a 56-day cycle.

Two big ones. First, range: each station's power output sets its class, and the standard service volumes run from 25 nm up to 130 nm depending on the class of the VOR and my altitude. Second, line of sight: VHF signals don't bend over terrain, so a ridge between me and the station can block reception entirely — the lower I am, the shorter the usable range.

Receiver Autonomous Integrity Monitoring — the GPS receiver cross-checks extra satellites to verify its own solution is trustworthy. It needs at least five satellites in view (or four plus a baro input) to detect a bad signal. If RAIM is unavailable or flags a fault, the position can't be trusted for navigation.

VFR flight following from approach/center: traffic advisories and safety alerts on a workload-permitting basis. I stay responsible for navigation, terrain, and see-and-avoid — radar advisories help, they don't replace looking outside. A Mode C (or S) transponder with ADS-B Out is what makes me visible to those services in the airspace that requires it (91.215 / 91.225).

Weather deteriorating ahead or at the destination, fuel running lower than planned, a mechanical or electrical problem, a sick passenger, an unexpected airport or runway closure, or approaching darkness when I'm not prepared for it. The common thread: the original plan no longer fits the situation, and continuing to force it is the classic accident setup.

Nearest suitable, not just nearest: runway length and surface versus the winds, weather at the field, fuel and services if I need them, airspace and terrain between here and there, and my remaining fuel and daylight. A towered field with services 10 minutes farther can beat a short strip 5 minutes away.

Divert first, refine second — turn toward the airport immediately, then tighten up the numbers while established:

• Course: eyeball it from the sectional, using a nearby VOR compass rose or a straightedge for the rough magnetic course.
• Distance: measure with the plotter, or use known chart references (latitude ticks: one minute is one nautical mile).
• Time: distance divided by groundspeed — at 120 kt groundspeed that's 2 nm a minute, so 24 nm is about 12 minutes.
• Fuel: time en route times the known burn rate, checked against what's actually in the tanks.

Then hold the ACS numbers: altitude ±200 ft, heading ±15°, and keep updating weather and position along the way.

Work the 5 Cs — and the order makes sense: get a better view, stop making it worse, buy time, then get help.

Establish and maintain an airspeed just above stall-warning activation with no stall horn sounding; +10/−0 kt, ±100 ft, ±10° heading/bank. If the warning activates, recover promptly — that isn't disqualifying; ignoring it is.

Acknowledge the cues (buffet, horn, sight picture) and recover promptly after the full stall. Complete the recovery no lower than 1,500 ft AGL.

Acknowledge the cues and recover promptly after the full stall; complete no lower than 1,500 ft AGL. Expect stronger left-turning tendencies at high power and AoA — stay coordinated.

Altitude ±200 ft, heading ±10°, airspeed ±10 kt — and prompt recovery from unusual attitudes. These tolerances apply across the basic instrument tasks.

Two ways to think about it. Control and performance: set attitude on the AI and power on the tach, then confirm the result on the performance instruments (ASI, altimeter, VSI, HI, TC). Primary and supporting: for each maneuver, one instrument gives the most direct answer for pitch, bank, and power. In straight-and-level: altimeter primary for pitch, heading indicator primary for bank, ASI primary for power (IFH ch 6).

The radial (hub-and-spoke) scan: eyes return to the attitude indicator between glances at each performance instrument — AI, altimeter, AI, HI, AI, ASI, and so on. The AI is the only instrument showing pitch and bank at once, so it anchors the scan (IFH ch 6).

Fixation — staring at one instrument (usually whichever is misbehaving); omission — dropping an instrument from the scan; emphasis — trusting one instrument instead of the combination. The fix for all three is a disciplined return to the AI and small, patient corrections (IFH ch 6).

Gyro instruments (AI, HI) suffer precession — the HI drifts and needs resetting against the compass every 10–15 minutes in level flight; the VSI lags 6–9 seconds; the ASI is sluggish to pitch changes; and the magnetic compass is only reliable in straight, level, unaccelerated flight (IFH ch 5).

An out-of-trim airplane demands constant control pressure, which destroys the light touch small corrections require and eats attention that belongs to the scan. Trim off the pressure after every attitude or power change — attitude, power, trim, then scan (IFH ch 7).

Continued VFR into IMC is consistently one of the deadliest accident categories — spatial disorientation can take an untrained pilot from wings-level to a graveyard spiral in under three minutes. The basic instrument tasks exist so I can keep the airplane upright, turn around, and get help (climb, communicate, confess, comply) if I ever blunder into cloud (PHAK ch 17, AIM 6-1-2).

Simultaneously: raise the nose to the approximate climb attitude on the attitude indicator, add climb power, and trim off the control pressure. I hold that attitude and let the airspeed stabilize, then make small pitch corrections (a half-bar to one-bar width at a time) to nail the target speed (IFH ch 7).

Once established: airspeed indicator is primary for pitch (pitch attitude controls airspeed at a fixed power setting), heading indicator is primary for bank in a straight climb, and the tachometer is primary for power. The attitude indicator is the control instrument I actually fly; the others confirm performance (IFH ch 7).

Lead the level-off by about 10% of my vertical speed — climbing at 500 fpm, I start the push-over 50 feet before the target altitude. Lower the nose to level attitude, let the airspeed accelerate toward cruise, then set cruise power and trim. Standard: level off ±200 ft, heading ±20°, airspeed ±10 kt.

The VSI lags 6–9 seconds behind actual pitch changes (trend is instant, rate takes time), the attitude indicator can show small precession errors after sustained maneuvers, and the airspeed indicator responds slowly to pitch changes in a climb — which is why I fly attitude first and wait, instead of chasing the airspeed needle (IFH ch 5).

Fixation (staring at one instrument), omission (skipping one from the cross-check), and emphasis (relying on one instrument over the combination). In a climb, the classic trap is fixating on the airspeed indicator and chasing it with big pitch inputs (IFH ch 6).

Confess early. Admit the situation to ATC, ask for help (vectors, weather, nearest VFR), and declare an emergency if needed — no paperwork penalty for using the word, and priority handling can save my life (AIM 6-1-2).

To descend at cruise airspeed: reduce power to the descent setting and simultaneously lower the nose just enough to hold the airspeed, then trim. To descend at a slower speed: reduce power first, hold altitude while the airplane decelerates to the target speed, then lower the nose to maintain that speed as the descent begins (IFH ch 7).

Same logic as the climb: airspeed indicator primary for pitch, heading indicator primary for bank, tachometer primary for power. I set attitude and power on the control instruments (AI plus tach), then confirm performance on the rest of the panel (IFH ch 7).

Lead by roughly 10% of the vertical speed (500 fpm down means starting 50 ft above the target), and add power to the cruise setting as I raise the nose — power and pitch together, so the airspeed doesn't decay while the nose comes up. Then trim. Standard: ±200 ft, heading ±20°, airspeed ±10 kt.

Chasing the airspeed with large pitch changes instead of making small attitude corrections and waiting; forgetting to re-trim after the power change; letting the scan collapse onto one instrument (fixation); and blowing through the level-off altitude because I didn't lead it (IFH ch 7).

It lags 6–9 seconds before showing an accurate rate. The initial needle movement is a useful trend, but if I chase the rate itself I'll over-control. Fly the attitude indicator, cross-check the VSI once things stabilize (IFH ch 5).

Spatial disorientation (a descending turn is the graveyard-spiral setup), collision risk while heads-down under the hood, and task prioritization — aviate first, and if the situation deteriorates in real IMC, get ATC help early or declare an emergency (PHAK ch 17, AIM 6-1-2).

3° per second — a full 360° in two minutes. Rule of thumb for the required bank: TAS divided by 10, plus half that result. At 100 knots that's 10 + 5 = 15° of bank. The turn coordinator's index marks show standard rate (IFH ch 7).

The attitude indicator is the control instrument for setting bank; once established, the turn coordinator is primary for bank (it confirms the rate), the altimeter is primary for pitch, and the ASI is primary for power. The ball keeps me honest on coordination (IFH ch 7).

Lead the rollout by about half the bank angle — with 15° of bank, start rolling out 7–8° before the target heading. Standards: altitude ±200 ft, standard rate maintained, rollout heading ±10°, airspeed ±10 kt.

Banking tilts the lift vector, so the vertical component of lift decreases. I add a touch of back pressure (and accept a slight airspeed loss) as I roll in, and release it as I roll out — small corrections off the altimeter, not big pitch swings (PHAK ch 5, IFH ch 7).

On north/south headings the compass leads or lags in turns: UNOS — Undershoot North, Overshoot South (northern hemisphere). Acceleration errors on east/west headings: ANDS — Accelerate North, Decelerate South. That's why I turn to headings using the gyro heading indicator, set from the compass in steady, level, unaccelerated flight (IFH ch 5).

Timed turns: at standard rate I'm turning 3° per second, so a 90° heading change takes 30 seconds. Roll in, time it, roll out, then verify on the magnetic compass once wings-level and stable (IFH ch 7).

Fixating on the heading indicator and letting altitude wander, using too much bank (past standard rate it's easy to overshoot and it aggravates disorientation), uncoordinated rudder, and forgetting the rollout lead (IFH ch 6–7).

Airspeed decreasing, altimeter increasing, VSI showing a climb, and the attitude indicator showing a nose-up picture. The airspeed trend is the key confirmation — if the AI has tumbled or looks wrong, decreasing airspeed plus increasing altitude means nose-high (IFH ch 7).

In order: power — pitch — roll. Add full power, apply forward pressure to lower the nose and break the approach to a stall, then level the wings, and return to level flight on the instruments. The threat is a stall, so reducing angle of attack comes before finesse (AFH ch 4, IFH ch 7).

Power — roll — pitch: reduce power to idle, level the wings first, then smoothly raise the nose. Pulling while banked tightens the spiral and adds load factor — a rolling pullout at high airspeed risks an accelerated stall or overstress. Wings level, then a gentle pull (AFH ch 4, IFH ch 7).

The vestibular system is unreliable without visual reference — the leans, somatogravic illusion (acceleration feels like pitch-up), Coriolis illusion, and the graveyard spiral all produce compelling false sensations. Recovery means reading the instruments, believing them, and applying smooth control inputs against what my body says (PHAK ch 17).

An inadequate scan or interrupted cross-check, distraction and task saturation, spatial disorientation after losing outside reference, turbulence or wake, and system failures (a failed attitude indicator that I keep following). Prevention is a disciplined scan and staying out of IMC in the first place (IFH ch 7).

Control first: level wings on the instruments, trim, and commit to the gauges. Then a coordinated standard-rate 180° turn back toward the VMC I just left (time it — one minute), or climb if terrain demands it. Use the autopilot if I have one, confess to ATC, and take vectors — declaring an emergency is free (AIM 6-1-2, PHAK ch 17).

Older vacuum attitude indicators can tumble past their pitch/bank limits and mislead. The airspeed indicator, altimeter, VSI trend, and turn coordinator don't tumble — that combination identifies the attitude and confirms the recovery is working (IFH ch 5, 7).

Aviate, navigate, communicate — in that order. I keep the scan going while tuning: set the frequency in the standby side, glance, verify, swap. Never let a radio task steal the scan for more than a couple of seconds at a time (IFH ch 7).

Tune, identify, twist: tune the frequency, positively identify the station by its Morse code ident (no ident means the station may be undergoing maintenance and is unusable), then twist the OBS to the desired course and fly to center the needle. For GPS, verify the correct waypoint and CDI scaling (IFH ch 9, AIM 1-1-3).

Radar traffic advisories for VFR aircraft — ATC calls out traffic and can provide safety alerts, workload permitting. I request it from approach or center with callsign, type, position, altitude, and destination. It doesn't relieve me of see-and-avoid, and ATC can terminate it when busy (AIM 4-1-15).

FSS (briefings, flight plans, inflight advisories), clearance delivery/ground/tower at towered fields, TRACON (approach/departure) for terminal radar service, ARTCC (center) for en route, plus UNICOM/CTAF at nontowered fields. Radar services for VFR range from basic (advisories) to TRSA, Class C, and Class B services with sequencing and separation (AIM ch 4-1).

Squawk 7600, troubleshoot (volume, frequency, headset jacks, other radio, cell phone as backup), and continue to land at the planned airport watching for light gun signals from the tower. Steady green means cleared to land; I acknowledge with rocking wings by day or a flash of lights at night (AIM 4-2-13, 6-4-1).

The moment the outcome is in doubt — deteriorating weather, disorientation, fuel, failures. Squawk 7700, call on the current frequency or 121.5, and remember the C's: climb (for radar/radio coverage and terrain), communicate, confess, comply, conserve. Priority handling costs nothing and there's no automatic enforcement action (AIM 6-1-2, 6-2-2).

Automation (autopilot heading/altitude hold to shed workload), GPS nearest-airport and frequency pages, EFB planning aids, and ATC itself — vectors, weather, and no-gyro turns if instruments fail. Using them early is the risk-management answer the ACS wants (PHAK ch 2).

Per POH: power idle, published configuration, 30–45° bank, airspeed +0/−10 kt of the recommended speed.

Situations where altitude itself is the threat: cabin fire or smoke, an engine fire, or (in pressurized aircraft) rapid decompression. The goal is maximum practical descent rate to get on the ground — or to breathable air — as fast as the airframe safely allows (AFH ch 18).

Three reasons: the bank keeps a positive load on the wings while the nose drops (avoiding a zero-G pushover), it increases drag so the airplane can descend steeply without overspeeding, and the turning descent lets me clear the airspace and ground below before committing down through it (AFH ch 18).

Follow the POH — some procedures use gear/flaps extended at their limit speeds for drag, others use a clean high-speed descent. In smooth air I can descend up to VNE if the emergency truly demands it, but in turbulence the ceiling is VNO or VA. The ACS standard is the POH-recommended airspeed at +0/−10 kt (AFH ch 18, POH).

In a carbureted trainer I use carburetor heat, and I clear the engine periodically with a short application of power (and avoid shock-cooling considerations on prolonged idle descents) so power is available at the bottom — unless the descent is for an engine fire, in which case the POH may call for keeping it shut down (AFH ch 18, POH).

Level off with enough altitude margin to recover smoothly (the examiner will specify an altitude), or continue to a landing if the emergency is real — a cabin fire is a land-immediately event, possibly off-airport. Plan the rollout point during the descent, not at the bottom (AFH ch 18).

Clearing for traffic before and during the descent (this is a fast trip through a lot of airspace), avoiding excessive load factor and airspeed during the entry, task prioritization while running the associated emergency checklist, and altitude awareness so the recovery isn't rushed (ACS IX.A R1–R4).

Establish best glide immediately, pick a suitable field into the wind, run the restart/emergency checklist, declare and squawk 7700, and fly a planned approach to the field.

The ABCDE flow: Airspeed — pitch and trim for best glide immediately; Best field — pick it early and fly toward it; Checklist — restart attempt, then cause check; Declare — 121.5 or current frequency, squawk 7700; Execute — secure the airplane and fly the approach. Airspeed comes first because every second off best glide is altitude thrown away (AFH ch 18).

Fuel, air, spark, from memory: fuel selector to the fullest tank (or switch tanks), electric boost pump on, mixture rich, carb heat on, magnetos checked on both (try each), primer in and locked. If it doesn't relight, commit to the landing and stop troubleshooting in time to fly the approach (AFH ch 18, POH).

Rule of thumb for a typical trainer at roughly a 10:1 glide ratio: about 1.5 nm per 1,000 ft of altitude, before wind. Headwind shrinks it, tailwind stretches it, and a windmilling prop and poor speed control both cost real distance. Gliding toward somewhere landable at all times is the cross-country habit this feeds (PHAK ch 11).

The classic scan: wind, surface (firm, dry, smooth), size and shape (long into the wind), slope (land uphill if forced to choose), and surroundings (wires, fences, ditches, obstacles on the approach path). A road can work but wires and traffic make open fields usually safer. Decide once, then stop shopping — late field changes are a killer (AFH ch 18).

Once landing is assured and off-field: fuel selector off, mixture idle cutoff, magnetos off, flaps as needed, then master off after final flap selection, doors unlatched so they can't jam shut, and seatbelts tight. Brief passengers: belts, brace position, exit plan (AFH ch 18, POH).

Raising the nose past best-glide attitude steepens the descent instead of extending it, and near the ground it invites a stall/spin — the fatal version of this emergency. If the field is short, arrive controlled: it's far better to touch down slow and wings-level in the trees before the field than to stall in from fifty feet (AFH ch 18).

Prompt establishment of best glide (ACS: ±10 kt), a committed field selection with a planned key position, appropriate checklist use without sacrificing aircraft control, and sound energy management on the simulated approach — arriving at the field neither dangerously short nor ballooning long (ACS IX.B).

Fly the airplane first, then troubleshoot the three things an engine needs — fuel, air, spark: carb heat on (carb ice is the top suspect in a carbureted engine), adjust mixture, switch fuel tanks and boost pump on, check mags on both (then test each individually — if it smooths out on one mag, leave it there and land), check primer in and locked, scan the engine gauges. Then the POH checklist (AFH ch 18, POH).

Ammeter shows discharge (or a low-voltage light illuminates). I verify by cycling the master/ALT switch and checking the alternator field breaker. If it won't reset, everything is running on battery — typically 30–45 minutes, less with a heavy load — so I shed nonessential electrical load, save power for flaps/lights/one radio, and land before the battery dies. In a Warrior the engine keeps running fine on magnetos; this is an electrical problem, not an engine problem (PHAK ch 7).

The attitude indicator and heading indicator spin down slowly over several minutes and start lying gradually — that's the trap. I detect it with the suction gauge and by cross-checking: AI disagrees with turn coordinator, altimeter, and ASI. Response: cover the failed instruments, fly the electric turn coordinator plus compass/GPS track, and stay strictly VMC (IFH ch 5, PHAK ch 8).

Pitot ram opening blocked with the drain open: ASI drops toward zero. Both pitot openings blocked: the ASI acts like an altimeter, reading higher as I climb. Static blocked: altimeter freezes, VSI reads zero, and the ASI reads slow above the blockage altitude and fast below it. Fixes: pitot heat, and alternate static air (or breaking the VSI glass as a last resort) (PHAK ch 8).

The distinctive acrid smell comes first. Master off, avionics off — killing power usually kills the fire. Fire extinguisher if there are flames, and only after the fire is out, open vents to clear smoke. I don't restore power unless it's essential for a safe landing (then breakers in one at a time, watching for recurrence), and I land as soon as possible (AFH ch 18, POH).

Flap failure: plan a no-flap landing — flatter, faster approach (POH speed), longer float and rollout, so pick a longer runway. Asymmetric split flaps: stop moving them immediately and counter the roll. Inop trim: expect to hold sustained control pressure; land as soon as practical before fatigue builds (AFH ch 18).

It's noisy and startling but the airplane flies essentially normally. Fly the airplane — climb out, pattern, land, then close it. Trying to shut a door while hand-flying at low altitude has caused far more accidents than open doors ever have. This is the ACS's startle-response item (PHAK ch 2, POH).

Checklist discipline (memory items, then the printed checklist to verify), resisting the startle response for a few seconds before acting, and not letting the malfunction steal the scan — a distracted pilot in an undesired aircraft state is more dangerous than most system failures (ACS IX.C R1–R4).

Per 91.207: inspected every 12 calendar months (proper installation, battery corrosion, operation of controls, sufficient signal). Batteries must be replaced (or recharged) after 1 hour of cumulative use or when 50% of their useful life has expired. Most units transmit on 121.5 MHz plus modern 406 MHz — 406 units are satellite-monitored and registered to the owner; satellites no longer monitor 121.5 (AIM 6-2-4).

Analog 121.5 testing only during the first 5 minutes after the hour, maximum three audio sweeps; 406 MHz units use their built-in self-test. After any hard landing — and as a habit before shutdown — monitor 121.5 to make sure the ELT isn't transmitting (AIM 6-2-4).

Know its location and mount, and brief passengers on it. Technique is PASS: pull the pin, aim at the base of the fire, squeeze, sweep. Halon works well in a cockpit without leaving residue, but any discharge in a closed cabin calls for ventilation afterward. Check the gauge/seal during preflight (AFH ch 18, POH).

Enough water, clothing, shelter, signaling, and first-aid supplies for 48–72 hours — rescue can easily take that long. Core kit: water, space blanket or shelter, fire starter, signal mirror/whistle, flashlight, knife, first aid, and a PLB or charged phone. Dress to walk home, not for the cabin temperature (ACS IX.D R1, PHAK ch 2).

Hot/desert: water is everything — carry more than seems reasonable, plus sun protection and shade material. Cold/winter: insulation layers, sleeping bag, fire starting, and stay-with-the-aircraft discipline. Mountains: warm gear even in summer (temperature drops with altitude), signaling that works in terrain shadows. Overwater: flotation for each occupant when beyond gliding distance of shore, ideally a raft and PLB (ACS IX.D K3).

Where things are and how they work before we need them: door and seatbelt operation, ELT location and manual activation, fire extinguisher location, survival kit location, and brace position. If the aircraft had a ballistic parachute or auto-land, I'd brief the activation criteria and handle location too (ACS IX.D S2).

Close both throttles smoothly and promptly, maintain directional control with rudder (and brakes as needed in a landplane; flight controls in a seaplane), and stop on the remaining surface. I never attempt to continue the takeoff — below VMC there isn't enough rudder authority to counter the asymmetric thrust (AFH ch 13).

VMC is the minimum airspeed at which directional control can be maintained with the critical engine suddenly inoperative and the other at takeoff power. Airborne below that speed with one engine out, full rudder cannot stop the yaw/roll toward the dead engine — the airplane departs controlled flight at an altitude where recovery is impossible (AFH ch 13, 14 CFR 23.2135 heritage 23.149).

Red radial line: VMC, the sea-level minimum control speed demonstrated under certification conditions. Blue radial line: VYSE, best single-engine rate-of-climb speed — the speed that delivers the best climb (or slowest sink) on one engine. Rotation should never be planned below VMC plus a margin (AFH ch 13).

The distance to accelerate to liftoff/decision speed, lose an engine at that instant, and brake to a full stop. If the runway is shorter than the accelerate-stop distance, a rejected takeoff means going off the end — so I compute it from the POH for the actual weight, wind, temperature, and runway before every multiengine takeoff (AFH ch 13, POH).

The commit points, decided before the throttles go up: any failure before rotation or below VMC/liftoff — close both throttles and stop; failure after liftoff with gear down and runway remaining — land straight ahead; failure after liftoff, gear up, no runway — fly it as an engine failure after liftoff at VYSE. Briefing it beforehand is the antidote to the startle response (AFH ch 13).

Anything that changes rudder authority or asymmetric thrust: density altitude (VMC decreases as the good engine makes less power), CG position (aft CG shortens the rudder arm and raises VMC), bank angle toward the operating engine (each degree up to 5° lowers VMC), and whether the dead prop is windmilling or feathered. Full treatment lives in the VMC demo task (X.B) (AFH ch 13).

Control first — rudder against the yaw, pitch for airspeed. Then: mixtures, props, throttles full forward; flaps up; gear up (drag flow). Identify — dead foot, dead engine. Verify — retard the suspect throttle and confirm nothing changes. Feather the correct prop. Then climb at VYSE and run the securing checklist when time permits (AFH ch 13, POH).

If the gear is still down and there's runway (or suitable surface) remaining — close both throttles and land. Continuing is only justified when the airplane is cleaned up, at or above VMC with a margin, and actually capable of climbing. Many light twins can barely climb on one engine on a warm day; forcing a climb that isn't there is how VMC rollovers happen (AFH ch 13).

VYSE (blue line) for best single-engine climb. With obstructions ahead: VXSE, or VMC plus 5 knots, whichever is greater, until clear — then back to VYSE. ACS tolerance: heading ±10°, airspeed ±5 kt. VSSE is the manufacturer's minimum speed for intentionally failing an engine in training — the evaluator won't pull one below it (ACS IX.F, AFH ch 13).

Losing one of two engines cuts power in half but kills roughly 80–90% of climb performance, because climb rate lives on excess power. A windmilling propeller is the single largest drag item — feathering it can be the difference between a climb and a descent. Gear, flaps, and even the wrong ball position all bleed away what little excess remains (AFH ch 13).

Wings-level with the ball centered actually puts the twin in a slip that costs climb performance. Best performance comes from banking 2–5° into the operating engine with the ball about half out of center toward the good engine — that aligns the fuselage with the relative wind. "Raise the dead" — dead engine side slightly high (AFH ch 13).

The evaluator fails an engine only at a safe altitude and airspeed (per VSSE and the ACS safety appendix). I simulate feathering by calling it out; the evaluator then sets zero thrust — a power setting that mimics a feathered prop's drag — so we get realistic performance without an actually-dead engine (ACS IX.F K6).

Accept it: maintain VYSE for minimum sink, and turn back to the departure airport or the most suitable landing area. Pulling the nose up for a climb that isn't available just decays airspeed toward VMC. Deciding early to land is the correct ACS answer, not a failure (ACS IX.F S7, AFH ch 13).

Maintain control, set engine controls (mixtures/props/throttles), reduce drag, identify (dead foot), verify (retard the suspect throttle), simulate feathering — evaluator sets zero thrust — then trim for zero sideslip, run the securing checklist, and plan the approach (AFH ch 13, POH).

Slightly higher or tighter than normal, never lower — altitude is the bank account. Maintain VYSE until landing is assured, then slow to the POH-recommended approach speed. ACS tolerance on final: recommended approach speed +10/−5 kt, stabilized, touching down in the first third with centerline alignment (ACS IX.G, AFH ch 13).

Later than normal — each adds drag the remaining engine must overcome. Typical technique: gear down when landing is reasonably assured (abeam or on final within power of the field), approach flaps on final, and full flaps only when landing is certain. Until then I keep the airplane in a configuration that could still climb (AFH ch 13).

Treat it as a hard commitment problem: once I'm below roughly 500 ft AGL with gear down and full flaps, a single-engine go-around may be aerodynamically impossible in a light twin — the drag exceeds the climb capability while I retract everything. So I decide early, fly a stabilized approach, and if it's not working, break it off high, not low (AFH ch 13, ACS IX.G R6).

Two floors below me: VMC (directional control) and stall. Low, slow, high power on one side is exactly the VMC-rollover setup, and there's no altitude to recover. Blue line until landing assured protects both margins (AFH ch 13).

I perform the identify/verify steps and simulate the feather by stating it; the evaluator sets zero thrust to mimic the feathered drag. I still run the real checklist flow, monitor the operating engine (temps, fuel flow), and complete the appropriate checklists through touchdown and rollout (ACS IX.G K5, S10).

Identify: dead foot, dead engine — the leg doing no rudder work points at the failed engine. Verify: retard that engine's throttle; no change confirms it. Feather: pull the correct prop control fully aft into feather (past the detent). Secure: for the dead engine — mixture cutoff, fuel selector off, boost pump off, magnetos off, alternator off, cowl flap closed — per the POH checklist (AFH ch 13, POH).

The reason it quit — fuel, air, spark: switch tanks, boost pump on, mixture adjust, carb heat/alternate air, check mags. Many "failures" are fuel starvation and come right back. The ACS specifically wants me to attempt to determine and resolve the cause when altitude and time allow (ACS X.A S4).

A windmilling propeller is a huge flat-plate drag source that also drives the dead engine, and it can cost most of the remaining climb performance. Feathering aligns the blades with the airflow, stopping rotation and cutting drag dramatically — it's the highest-value drag reduction available (AFH ch 13).

Zero sideslip: bank 2–5° into the operating engine, ball roughly half-deflected toward the good engine, and trim it. Fly VYSE (blue line) for best climb or minimum sink. ACS tolerances here: altitude ±100 ft (or minimum sink if unable), airspeed ±10 kt, heading ±10° (AFH ch 13, ACS X.A S7).

Manufacturer's procedure — typically: fuel selector on, boost pump on, mixture set, prop control forward out of feather, then crank with the starter or use the unfeathering accumulator if equipped; the prop windmills, the engine fires, and I warm it at low power before bringing it back into service. Airspeed helps the prop come out of feather (AFH ch 13, POH).

Doing it at altitude with a recovery floor, honoring VSSE as the minimum speed for intentionally failed engines, monitoring the operating engine's temperatures and pressures (it's working hard), and maintaining situational awareness for traffic and terrain while heads-down in checklists (ACS X.A R2–R5, ACS Appendix 2).

The minimum airspeed at which directional control can be maintained after a sudden failure of the critical engine, with the remaining engine at takeoff power and not more than 5° of bank toward the operating engine. It's marked as the red radial line, determined under specific certification conditions — real-world VMC changes with conditions (AFH ch 13, 14 CFR 23.149 heritage).

Higher density altitude: the good engine makes less asymmetric thrust, so VMC decreases. Aft CG: shorter arm for the rudder, VMC increases. Windmilling prop: more asymmetry, VMC increases (feathering lowers it). Bank toward the good engine: each degree up to 5° lowers VMC substantially; wings level or banked toward the dead engine raises it sharply. Gear down tends to lower it (keel effect) (AFH ch 13).

VMC decreases with altitude but indicated stall speed stays essentially constant — so as I climb, the two speeds converge, and up high the airplane can stall before losing directional control. A stall with full asymmetric power is a spin entry. That's why the demo is recovered at the first sign of either, and why it's flown at a safe altitude (AFH ch 13).

The engine whose failure hurts most — on conventional twins (both props clockwise from the cockpit), the left. The PAST factors: P-factor (right engine's descending blade has a longer arm), Accelerated slipstream (asymmetric lift from prop wash), Spiraling slipstream (left engine's slipstream helps the rudder; the right one's doesn't), Torque (left-rolling tendency adds to the left-engine-out problem) (AFH ch 13).

Configure per the manufacturer (or gear up, takeoff flaps/trim/cowl flaps, props high rpm): critical engine to idle and windmilling, operating engine at takeoff power. From about 10 knots above VSSE, establish a single-engine climb attitude and up to 5° bank into the good engine, then raise the pitch slowly to decelerate about 1 knot per second, feeding in rudder to hold heading (ACS X.B S1–S4).

The first indication of any of: loss of directional control (heading starts walking with full rudder in), stall warning, or buffet. Recover by simultaneously reducing power on the operating engine and lowering the angle of attack to regain airspeed and control — never add power on the simulated-failed engine. Standards: recover within 20° of entry heading, then smoothly power up and accelerate to VSSE/VYSE +10/−5 kt (ACS X.B S5–S8).

Because asymmetric thrust is the whole problem. Cutting the operating engine's power removes the yawing moment instantly, while lowering the nose restores rudder effectiveness. Adding power on the dead side isn't available in a real failure, and pulling harder on the yoke only deepens the loss of control (AFH ch 13).

Control first: stop the yaw with rudder, keep the wings near level on the attitude indicator, and hold heading. Then the standard flow — engine controls set, drag reduced, identify (dead foot), verify (retard throttle), simulate feather (evaluator sets zero thrust) — followed by best engine-inoperative airspeed, zero-sideslip trim, and the securing checklist (AFH ch 13, IFH).

Same as visual: the yaw tells me — dead foot, dead engine. On instruments the heading indicator and turn coordinator show the yaw immediately, and engine gauges (fuel flow, EGT, MP) support the diagnosis. Verification by retarding the suspect throttle is non-negotiable before feathering anything (AFH ch 13, ACS X.C R1).

Hand-flying an untrimmed, slipping twin while scanning gauges is a workload trap. Setting 2–5° bank into the good engine, half-ball, and trimming the rudder pressure off frees attention for the scan and the checklist — and the performance gained may be what lets me hold altitude at all (AFH ch 13).

Accept the drift-down: hold VYSE for minimum sink rather than dragging the nose up and decaying toward VMC. Then make the performance-based decision the ACS asks for — divert to the nearest suitable airport, tell ATC, and plan the descent so it ends at a runway. Tolerances: altitude ±100 ft or minimum sink if applicable, airspeed ±10 kt, heading ±10° (ACS X.C S8–S9).

The operating engine is now doing all the work at high power — fuel burn on that side is high, and I may have usable fuel trapped on the dead-engine side. Know the POH crossfeed procedure and plan reserves accordingly; fuel starvation of the good engine is an unforgivable second emergency (ACS X.C R5, POH).

Declare the emergency and use ATC: vectors to the nearest suitable approach, terrain and weather info, priority handling. Use the autopilot if appropriate to shed workload, brief passengers, and keep the operating engine's gauges in the scan. Single-pilot resource management is a graded element here (ACS X.C S11, PHAK ch 2).

Run the engine-out flow (set controls, reduce drag, identify, verify, simulate feather — evaluator sets zero thrust), trim for zero sideslip, complete the checklist, then request an ATC clearance for the approach — a straight-in with a long final if I can get it. Fly at or above VYSE until landing is assured (ACS X.D, AFH ch 13).

Late and deliberately. Typical technique: stay clean until glideslope intercept or the final approach fix, gear down there to start down, approach flaps only if performance allows, and full flaps when landing is certain. Every drag item narrows my options if anything goes wrong (AFH ch 13).

Altitude ±100 ft (or minimum sink if applicable), airspeed ±10 kt, heading ±10°; on the final approach segment, lateral and vertical guidance within three-quarter-scale deflection; arrive at MDA or DA positioned to land straight-in or circling; comply with circling category criteria if circling; and execute a landing (ACS X.D S7–S12).

Plan not to. A single-engine missed approach in a light twin, configured and low, may be beyond the airplane's performance — so the approach briefing includes a commitment point after which I'm landing. If a miss is unavoidable, it happens as early and as clean as possible: power up, pitch for VYSE, drag up, one item at a time (AFH ch 13, ACS X.D R6).

Declare it. Priority handling gets me the straight-in approach, a longer final, the current weather, and equipment standing by. I state souls and fuel when asked, and I don't accept a clearance (like a tight circling approach) that the airplane can't safely fly on one engine (AIM 6-1-2).

The operating engine — temperatures, pressures, fuel flow, and the fuel selector/crossfeed situation — plus the approach needles and the airspeed floor at blue line. The classic failure mode on this task is shedding the scan to fuss with the dead engine and blowing through three-quarter-scale deflection (ACS X.D S5, S9).

Cones are concentrated in the center of the retina — sharp detail and color, but they need light. Rods surround them in the periphery — far more light-sensitive but no color and poor detail. At night the fovea becomes a central blind spot, so I use off-center viewing: look about 5–10° to the side of an object and scan slowly rather than staring (PHAK ch 17, AIM 8-1-6).

Rods take roughly 30 minutes to fully adapt to darkness (cones adapt in about 10). One blast of bright white light resets the clock, so I use low-intensity cockpit lighting, avoid bright lights before and during flight, and close one eye if exposure is unavoidable. Red light preserves night vision but washes out red chart markings; oxygen helps too — night vision degrades noticeably above about 5,000 ft cabin altitude (AIM 8-1-6, AFH ch 11).

Everything for day VFR plus the night items — approved position lights, an approved anticollision light system, a landing light if operated for hire, an adequate source of electrical energy, and spare fuses (one spare set or three of each kind) if the airplane uses fuses. Position lights must be on from sunset to sunrise (91.209).

To carry passengers between 1 hour after sunset and 1 hour before sunrise, I need 3 takeoffs and landings to a full stop in that same window, in the same category and class, within the preceding 90 days (61.57(b)). Three "nights" to keep straight: position lights on sunset-to-sunrise (91.209); logging night time from the end of evening civil twilight to the beginning of morning civil twilight (1.1, 61.51); and the 1-hour-after/1-hour-before window for passenger currency. Currency is the legal floor — proficiency is the real standard.

Rotating beacon: white/green for a lighted civilian land airport (beacon on during the day suggests IFR weather in Class B/C/D/E surface areas). Runway edge lights white (yellow on the last 2,000 ft of an instrument runway), green threshold/red runway end, REIL for identification, VASI/PAPI for glidepath. Taxiways: blue edge lights, green centerline. Pilot-controlled lighting: key the mike 7 times for high intensity, then 5 or 3 to adjust — I always key 7 first (AIM 2-1).

Red is on its left wingtip, green on its right, white on the tail. Red and green together with no white: it's coming at me — alter course right. White only: I'm overtaking it or it's moving away. Green only: it's crossing left to right. Red only: crossing right to left — and likely has the right-of-way (91.113, AIM 4-3).

Black-hole approach (no terrain lighting on final — tendency to fly a dangerously low approach; use the VASI/PAPI), false horizon (sloping cloud decks or ground lights mistaken for the horizon), autokinesis (a stared-at static light appears to move — keep the scan moving), featureless terrain illusion, and flicker vertigo from strobes in cloud or the prop in low sun/landing light. Bright runway lighting can make the runway seem closer than it is (PHAK ch 17, AIM 8-1-6).

Same flow — best glide, checklist, declare, squawk 7700 — but field selection is the hard part. Head for dark areas near lighted roads and towns (dark usually means open land), use the landing light on final to see the surface, and keep the airplane under control all the way through touchdown at the slowest safe speed. Planning night routes over lighted corridors and within glide of airports is the risk-management answer (AFH ch 11).

Fly the airplane until it's stopped or at taxi speed, exit at the first safe taxiway, and — the key discipline — clear the runway completely (past the hold-short lines) and stop before reconfiguring anything. Flaps, trim, transponder, lights, and the after-landing checklist all wait until I'm clear and stationary or slowly rolling on a straightaway. Heads-down cleanup while rolling out is how people take wrong turns onto runways; and touching the wrong lever while moving is how retractable pilots collapse gear (AFH ch 8).

Park with thought — prop blast pointed away from people, doors, and other aircraft; nosewheel straight; brakes as the POH directs. Shutdown per checklist: typically avionics off, then mixture to idle cutoff (the engine stops by fuel starvation, confirming the mixture control works), mags off and key out, master off. Then securing: control lock in, pitot cover on, tie-downs or chocks, doors locked. The key-out habit matters — a keyed mag left on plus a bumped prop is a fatal combination.

It's the pre-preflight for the next flight — mine or someone else's. I'm looking for anything the flight caused or revealed: new leaks under the cowl, brake and tire condition after that firm landing, bird strikes or stone damage, and oil quantity while trends are fresh in mind. It's also when servicing needs get flagged: fuel order, oil to add, oxygen, a squawk to the shop. Catching it now means it's fixed before the 6 a.m. departure, not discovered during it (PA.XII.A.S4).

Document it — in whatever discrepancy system the operator uses (squawk sheet, maintenance log, a call to the shop) with enough detail to be useful: what, when, conditions. Under 91.405 the owner/operator must have defects repaired between required inspections, and the maintenance record entry matters. The unwritten half: an undocumented squawk becomes the next renter's in-flight surprise. If the airplane's now unairworthy, it gets grounded visibly, not just mentioned.

Three-point tie-down with proper knots (or the ramp's chains), chocks, control lock installed — or controls secured with the belt if there's no lock — pitot cover on, and cowl plugs if equipped. Doors and windows latched and locked. In gusty forecasts, tie-downs snug (a little slack invites shock loads, too tight loads the structure — follow local practice), and I position flaps and trim per POH. A flying club airplane that blows into its neighbor is an entirely preventable accident (AFH ch 2).

Nobody moves until the propeller has stopped and I say so. I brief the exit path before opening doors — away from the prop arc, watching for other aircraft moving on the ramp, and no wandering. I escort passengers, and children get a hand held. The ramp is the least controlled environment in the whole operation: spinning props on neighboring aircraft don't announce themselves, and a ramp is not a place for photos next to a running airplane (PA.XII.A.R4).

Lock the airplane and remove the keys, follow the field's gate and access procedures (don't hold gates open for strangers), and know that ramp access rules exist for a reason. If something looks off — someone photographing N-numbers and door locks, an unfamiliar person around aircraft at night — report it (airport management, or AOPA Airport Watch, 866-GA-SECURE). Security is a listed risk element on this task, and the practical answer is simple vigilance plus locked doors.

Slowly, into the wind or current — whichever is dominating my drift — because a seaplane has no brakes and no reverse. The standard technique is to plan the approach so the engine can be shut down early and the airplane coasts the last distance, arriving with just enough momentum to touch gently; if I misjudge, an idling engine and a dock full of people is a bad combination. Approach at a shallow angle, protect the wing and float from contact, and have lines and fenders ready. If wind is pushing me onto the dock, I aim short and let the drift carry me on; if it's pushing me off, I come in a bit steeper (Seaplane Handbook FAA-H-8083-23 ch 6).

Mooring buoy: a permanent anchor point — I approach it into the wind at idle, shut down and coast the last stretch, and secure the bow line to the buoy (approaching slightly to one side so the buoy stays visible past the nose). Safer than my own anchor because the tackle is (presumably) engineered for the load. Anchoring: I supply the ground tackle. Pick a spot with the right depth, good holding bottom, and enough swing room for the airplane to weathervane through a full circle as wind shifts; lower the anchor and pay out generous scope — several times the water depth of line — so the pull on the anchor stays horizontal. Then confirm it's actually holding with shore references before shutting everything down (PA.XII.B.S1, FAA-H-8083-23 ch 6).

Adequate scope is the whole game — short scope lets the anchor break out. Use line and anchors sized for the airplane and expected weather, consider a second anchor for overnight or shifting winds, and think about what changes while I'm gone: tide (depth and swing radius change), forecast wind, and boat traffic and wakes. The ACS language is explicit: enough anchors and lines, of sufficient strength and length, considering movement, depth, tide, wind, and weather changes.

First, know the bottom — walk it, ask, or read the water color; sand and smooth gravel are friendly, rocks and shells eat float bottoms. Approach nose-in at bare steerageway, shutting down before the water gets shallow enough to strike the water rudders or prop, and let momentum slide the float bows gently onto the shore. In wind blowing offshore, or with a rising or falling water level, I often prefer to turn and back in tail-first (sailing backward onto the beach) so the airplane can be walked off easily and waves don't slap the tail. Then secure to something solid above the waterline — and account for water level changes so I don't return to a floating (or stranded) airplane (FAA-H-8083-23 ch 6).

A ramp approach is nose-first with enough momentum (or a touch of power) to slide the floats or hull up the ramp surface, then immediate shutdown per local procedure. For an amphibian using a land ramp: gear per the ramp type and POH, and the second I'm on pavement, all the land after-landing rules of Task XII.A apply — parking with prop blast in mind, checklists, securing. The gear-position discipline runs both directions: wheels for pavement, wheels up for water, verbally confirmed every time.

Everything from XII.A plus the water-specific items: pump the floats — each compartment gets checked and pumped because slow leaks are normal and an unnoticed flooded compartment can sink or flip the airplane at its mooring; inspect float bottoms and spreader bars for damage from debris or the beach; rinse with fresh water after salt operations (corrosion is relentless); check the water rudder cables and hinges; and document any discrepancies just like on land. If the airplane stays on the water, the securing checklist assumes weather will change — because it will (FAA-H-8083-23 ch 6).

Propeller stopped before anyone unbuckles — briefed in advance. Docks are slippery and floats more so; I direct the exit path, one person at a time, stepping where I say (float decks have walk areas; the wrong step goes through a hatch cover or into the water). Life vests stay on until everyone's on solid footing if that's the operation's rule. At a beach, passengers exit on the shore side, away from the prop even though it's stopped — habits transfer. Then I monitor them on the dock or ramp; a seaplane base has boats, props, and water as simultaneous hazards (PA.XII.B.R4).