Crosswind before taxi
Ask: Estimate the components and identify the side before touching the calculator.
Verify: Calculator math, then aircraft/personal limits and runway conditions.
Use PilotDesk to build a quick scenario, make the student explain the decision first, then open the calculator or source that checks the work. Calculators, guides, and Daily work without an account. Oral practice includes free sample subjects; full interactive checkride preparation requires Pro.
Estimate → explain → calculate → verify.
Change runway, wind direction, and wind speed to turn one airport into a quick teaching scenario.
Open crosswind → PERFORMANCECompare pressure altitude, temperature, and ISA deviation before going back to the aircraft POH or AFM.
Open density altitude → LOADINGPractice weight, arm, moment, and CG work with the student's own aircraft data.
Open weight & balance → FLIGHT COMPUTERKeep common wind, fuel, time, airspeed, altitude, and conversion work in one place.
Open E6B → 3 QUESTIONS · CHANGES DAILYA quick aviation challenge you can send to a student between lessons and talk through later.
Play today's challenge →Copy a prompt into a text, LMS, or preflight brief.
Ask: Estimate the components and identify the side before touching the calculator.
Verify: Calculator math, then aircraft/personal limits and runway conditions.
Ask: Predict the direction and magnitude before calculating.
Verify: Density altitude first, then the exact POH/AFM takeoff and climb data.
Ask: Predict CG movement and identify the limits that matter.
Verify: Current W&B data and the approved envelope for that airplane.
Ask: Use the GS × 5 rule first.
Verify: Exact math, then the actual procedure, restrictions, and aircraft situation.
Ask: Separate VMC, VYSE, control, and performance.
Verify: Certificate-level ACS plus the exact airplane POH/AFM.
Ask: Plain language, example, mistake, source.
Verify: The explanation should survive a follow-up “why?” question.
I'm working on my CFI right now and recently picked up coding as a hobby. I started building PilotDesk because I wanted my own place for the calculators and training tools I kept reaching for.
I'm still learning, and I've used ChatGPT to help code quite a bit of it. If something feels too AI, awkward, unnecessary, or just not how a pilot would actually use it, please tell me. If you like something, tell me that too. I'm looking for specific feedback on what works, what doesn't, what's missing, and what should probably be removed.
Give the student the scenario first. Have them estimate the answer and explain the decision. Then use the tool to check the math. If the result is aircraft-specific or operational, finish with the current POH/AFM, chart, weather source, or regulation that actually controls the decision.