A student pilot's pre-checkride question about wingtip fire emergency procedures surfaces a foundational tension that extends well beyond the private pilot certificate: the relationship between POH/AFM-published emergency checklists and supplemental techniques passed down through instructor communities. In this case, the Cessna 172M POH directs the pilot to deenergize electrical loads associated with the wing — nav lights, anti-collision lights, pitot heat — and land as soon as possible. A cohort of CFIs has layered onto that a non-published technique: execute a steep emergency descent at Vno to generate sufficient airflow over the wing to extinguish the fire. The student is correctly sensing the tension and asking the right question before the practical test.
The answer, particularly for a checkride context, is unambiguous: the POH governs. The FAA's Airman Certification Standards (ACS) for the Private Pilot certificate evaluate the applicant's ability to identify and execute procedures per the manufacturer's documentation. A DPE observing a non-POH maneuver — however well-intentioned — has legitimate grounds to flag it as a deviation from approved procedures. More substantively, the C172M POH emergency section represents the manufacturer's analyzed, validated response to that emergency condition. The "steep descent at Vno to blow out the fire" technique carries no FAA or Cessna engineering backing, introduces additional energy management and structural considerations at a moment of already elevated workload, and may actually increase oxygen supply to a combustion event on an aluminum structure. The logic of the technique is appealing but untested against the actual physics of an in-flight electrical or fuel-fed fire at a wingtip.
For professional pilots operating under Parts 121, 135, or 91K, this dynamic is codified into regulatory and operational requirements. The AFM/POH is a legal instrument; deviation from its emergency procedures in flight must be justified under 14 CFR 91.3(b) — the pilot-in-command emergency authority provision — and documented accordingly. Airlines and charter operators formalize this further through Operations Specifications and Flight Operations Manuals, which either mirror or supplement AFM content with FAA-approved additions. No such approval exists for an informal descent technique originating in ground-school oral tradition. When a crew encounters an abnormal or emergency not covered by the QRH, the trained response is to apply first principles — aviate, navigate, communicate — not to reach for an ad-hoc maneuver that a previous instructor once mentioned.
The broader pattern here is well-known to aviation safety researchers: informal technique drift, sometimes called "normalization of deviance," occurs when pilots operationalize habits that feel logical but are disconnected from type-specific engineering analysis. In the training environment, CFIs who supplement the POH with unvalidated techniques may genuinely believe they are improving pilot capability, but the downstream effect is the creation of procedural ambiguity at exactly the moments when procedural clarity matters most. The FAA's continued emphasis on checklist discipline and manufacturer-sourced emergency procedures in ACS and ATP certification standards reflects an industry-wide effort to counteract this drift. For the student preparing for this checkride — and for any pilot reviewing their own emergency procedure habits — the correct frame is simple: the POH is the floor and the ceiling for published emergency response; anything added to it requires a demonstrably higher standard of validation than instructor consensus.