Why it matters
Most apps require the pilot to remember to start a tracker. CloudAhoy, ForeFlight, and Garmin Pilot all rely on the pilot triggering the recording. Marathon Rank 9 starts the track when the engine RPM and GPS-derived movement cross taxi thresholds — and stops when the engine quiets. The logbook entry writes itself, signed §61.59-style at landing.
Under the hood
- GPS movement + engine-state heuristic auto-start
Track begins when both GPS speed > 5kt and engine RPM is detected.
- Live in-cockpit track for debrief feed
Marathon Rank 2 debrief consumes the live track, not just imports.
- §61.59 wet-click logbook entry on landing
Entry includes route, time, landings, day/night split, instrument time.
- LAANC auto-close on landing detection
Marathon Rank 1 LAANC authorization releases when track ends.
- Currency window auto-update
90-day passenger, night currency, instrument currency all update automatically.
Regulatory and safety context
14 CFR §61.59 governs logbook record-keeping and explicitly requires the entry to be made by the airman. AeroCopilot stages the entry but requires the pilot to confirm — the "wet click" — preserving the §61.59 attestation chain while removing the transcription burden.