90 Day Landing Currency Calculator
Audit paired takeoffs and landings against category/class/type, sole-manipulator, full-stop and night requirements in the preceding 90 days. Inputs stay in your browser.
The tool counts paired takeoffs and landings only when the date, category/class/type, sole-manipulator and full-stop/night conditions match the selected 14 CFR 61.57 path. Review note: Complete the matching 90-day logbook review.
Context matters.
- Day passenger currency generally requires three takeoffs and three landings as sole manipulator in the same category, class and required type; tailwheel events must be to a full stop.
- Night passenger currency separately requires three takeoffs and three full-stop landings from one hour after sunset to one hour before sunrise.
- Approved simulator/training-center paths and listed operating-rule exceptions have additional conditions that must be verified outside this standard logbook check.
Sources & scope
The calculation guide and this source trail show what the result means, where the rule came from and when it was last reviewed. This is source-and-calculation QA, not a claim of medical, legal, tax or other professional review; time-sensitive decisions still belong with the linked authority.
A visible path from input to answer.
Audit paired takeoffs and landings against category/class/type, sole-manipulator, full-stop and night requirements in the preceding 90 days. The page keeps the calculation scope and its limits beside the result so the output can be checked, copied or revisited.
- Read the record. The calculator uses Planned passenger-carrying flight date, Passenger operation, Aircraft category / class / required type, Operating-rule screen and Session 1 · date and 33 additional fields supplied in the form.
- Apply the scope. It applies the United States standard passenger-currency logbook check — 14 CFR 61.57 category/class/type, sole-manipulator, full-stop and night conditions control reference and the explicit date, unit and counting conventions shown in the result.
- Expose the checkpoints. Intermediate rows, warnings and timeline events stay visible; the emphasized row identifies the primary checkpoint when one exists.
The tool counts paired takeoffs and landings only when the date, category/class/type, sole-manipulator and full-stop/night conditions match the selected 14 CFR 61.57 path. Review note: Complete the matching 90-day logbook review.
- Preceding 90-day review windowJun 1, 2026 – Aug 30, 2026
- Overall authority to carry passengersNot determined by this logbook check
Calculation purpose: Audit paired takeoffs and landings against category/class/type, sole-manipulator, full-stop and night requirements in the preceding 90 days. This is a high-sensitivity reference output; the linked authority or qualified professional controls the final decision.
Calendar inputs use plain year-month-day semantics. Leap days, month ends, date-pair order and unsupported dates are checked before the result is shown.
Rule set 1.1.0 · Last reviewed 2026-08-20 · Next review due 2027-02-20. The source panel below contains the linked evidence.
What to know before using the result.
What counts for ordinary day passenger currency?
Generally three takeoffs and three landings within the preceding 90 days as sole manipulator in the same category, class and required type. Tailwheel events must be to a full stop.
Why is night passenger currency separate?
Night currency requires three takeoffs and three full-stop landings during the period from one hour after sunset to one hour before sunrise.
Does a currency result prove I can legally carry passengers?
No. Certification, ratings, medical qualification, flight review, aircraft requirements and applicable operating rules remain separate.