A recurring debate on r/flying highlights a growing tension in primary flight training: how much manual flight-planning proficiency should applicants demonstrate on a private pilot checkride when apps like ForeFlight can generate a complete navigation log, fuel burn calculation, and wind-corrected headings in seconds. The original poster, a CFI who stepped away from active instructing roughly a decade ago, described giving a mock checkride to a friend who could not explain wind correction angles or magnetic variation deviation because "it's all in ForeFlight." The poster noted seeing multiple recent reports of applicants failing checkrides specifically on flight-planning knowledge, prompting the question of what Designated Pilot Examiners (DPEs) actually expect in 2026's app-saturated training environment.
The core issue for working pilots and flight instructors is that the Airman Certification Standards (ACS) have never been rewritten to exempt applicants from understanding the underlying principles of navigation, even as the tools used to execute that navigation have evolved. DPEs are testing airman knowledge, not app proficiency — an applicant who can operate ForeFlight but cannot explain why a computed heading differs from a magnetic course, or cannot manually true up a heading using an E6B (electronic or manual), is missing required knowledge under the ACS Task PA.III.A elements, which explicitly cover pilotage, dead reckoning, magnetic compass, and wind triangle computations. Examiners have discretion in how deeply they probe, but the consistent pattern of failures reported industry-wide suggests many CFIs are signing off students who can push buttons but cannot reason through the "why" behind the numbers — a gap that becomes dangerous the moment avionics fail, GPS is jammed or spoofed, or an alternate airport requires manual replanning in flight.
This matters beyond the private pilot level because the habits formed early persist throughout a career. Airline and corporate pilots routinely encounter scenarios — FMS database errors, RNAV outages, diversions to non-programmed airports — where genuine understanding of dead reckoning, magnetic variation, and mental math for fuel and time enroute becomes a real backup skill rather than an academic exercise. The FAA and NTSB have flagged automation dependency and eroding manual flying and navigation skills as a persistent contributor to loss-of-control and navigation-related incidents across GA and commercial operations alike, which is part of why the agency has resisted simplifying the ACS to match app-based workflows. The broader push toward Upset Prevention and Recovery Training (UPRT) integration and continued emphasis on stick-and-rudder fundamentals in ACS revisions reflects the same underlying philosophy: technology should augment airmanship, not replace the pilot's ability to independently verify and reason through a flight plan.
For CFIs and DPEs, the practical takeaway is that ForeFlight-generated nav logs are acceptable as a planning tool, but applicants must still be able to explain and manually reconstruct the key computations — true course to magnetic heading conversions, wind correction angle derivation, and fuel/time calculations — without the app doing the reasoning for them. Examiners increasingly probe this by asking applicants to explain a discrepancy between what the app produced and what a quick manual check would show, or by asking conceptual "why" questions rather than requiring a fully hand-built nav log from scratch. Instructors preparing students for checkrides in 2026 would be well served treating the E6B (or its electronic equivalent) not as a relic but as a diagnostic teaching tool, ensuring students internalize the math well enough to sanity-check any automated output — a skill set that scales directly into instrument, commercial, and eventually airline transport training where automation failures carry far higher stakes.