Flight Currency Requirements: What 14 CFR 61.57 Means for Flight School Operations

Student pilots and instructors go non-current more often than most flight schools realize. A student who takes a three-month break between lessons, an instructor who focuses on ground instruction for a season, or anyone who skips night flying for two months can quietly fall outside the legal limits for carrying passengers. Understanding exactly what 14 CFR 61.57 requires is as much an operations problem as a regulatory one.

This article covers the three currency requirements that affect day-to-day flight school operations: passenger-carrying currency, night currency, and instrument currency. It also covers what happens when someone goes non-current in a training environment and how to build tracking into the dispatch workflow before the problem surfaces at the flight line.

What Passenger-Carrying Currency Requires

Under 14 CFR 61.57(a), a pilot must have made at least three takeoffs and three landings within the preceding 90 days to carry passengers. The requirement applies within the same category and class of aircraft. A certificated private pilot who primarily flies a Cessna 172 cannot carry passengers in a Piper Archer without first logging three takeoffs and three landings in a single-engine land aircraft. The aircraft do not have to be the same model, but they must be in the same category and class.

The 90-day window is calculated backward from the intended flight. If today is May 20 and the last qualifying landings were on February 19, the pilot is non-current. The math is simple. Keeping track of it across a fleet of students, part-time renters, and rotating instructors is where the process breaks down.

Night Currency

Night passenger-carrying currency imposes one additional layer: the three takeoffs and three landings must occur between one hour after sunset and one hour before sunrise. A pilot who is fully current for daytime passenger flights may not be current to carry passengers at night. For tailwheel aircraft, full-stop landings are required; for all other aircraft, touch-and-goes count toward the night requirement.

For flight schools that operate into the evening or run discovery flights around sunset, night currency tracking adds a real operational complication. Instructors who fly predominantly during the day can fall out of night currency without realizing it, which matters when a student books an evening lesson and arrives expecting to bring a family member along. The FAA's pilot certification resources provide the full breakdown of currency requirements by aircraft type and operation category.

Instrument Currency

Instrument currency under 61.57(c) requires six instrument approaches, holding procedures, and intercepting and tracking courses within the preceding six calendar months. This does not require actual IMC: approaches in an approved aviation training device count. The window is measured by calendar month, not a rolling 180-day period.

After the initial six-month window expires, there is an additional six-month grace period during which the pilot can fly with a safety pilot or in an authorized training device to restore currency without an IPC. Beyond that 12-month point, an Instrument Proficiency Check with a CFII or designated pilot examiner is required. Schools with active instrument rating programs need to track this separately from basic passenger-carrying currency, since students preparing for their instrument checkride often push close to these limits.

How Non-Currency Shows Up at the Dispatch Desk

Currency lapses rarely announce themselves in a busy training environment. A student calls to book a Saturday evening lesson and mentions that a parent wants to come along for the ride. The dispatcher approves the booking without checking whether the student has flown in the past 90 days or whether their night landings are current. The flight has to be restructured when the student arrives, the parent cannot come, and the lesson time is partly wasted. This scenario is more common than most schools acknowledge.

The same issue surfaces with instructors. A CFI who has spent several weeks on ground instruction and simulator sessions may have let passenger-carrying currency lapse without noticing. The regulatory burden falls on the pilot-in-command, but a dispatch system that catches the issue before a lesson is confirmed prevents the problem from becoming an operational one. Tracking currency reactively, after someone asks, means the answer is sometimes no when the student is already at the aircraft.

Building Currency Tracking Into Your Operations

The most reliable approach is to log the three most recent qualifying flights with takeoff count, landing count, and time-of-day for every pilot on your roster. Scheduling software that captures Hobbs time and booking history can generate this data automatically. This is one of the core operational benefits covered in our aircraft booking and fleet management guide: a booking system that understands the flight record is more useful than one that only manages calendar slots.

For schools that already track solo endorsements and checkout requirements, currency is a natural extension of the same data layer. If you know when a student last flew, which aircraft they used, and whether the flight included landings after sunset, the currency calculation is straightforward. If that data is not in a queryable form, building the tracking system starts with the booking and dispatch workflow. The broader strategies in our flight school operations guide cover where to begin.

Chief instructors and dispatchers should confirm that any student returning from a multi-week break is current before approving a booking with a passenger on board. Missed currency checks create liability for the school as well as the individual pilot.

When Currency Expires Mid-Schedule

The most operationally disruptive situation is discovering a lapse mid-schedule: a student has already booked an aircraft and an instructor, and the dispatcher catches the issue hours before the flight. A currency check at the booking approval step, rather than a retrospective audit, is the simplest prevention.

The path to restoring passenger-carrying currency is clear: complete the required three takeoffs and three landings in the relevant category before the passenger or night flight. For student pilots returning from a long absence, an instructor review may also be warranted depending on the scope of the break. The instructor scheduling best practices guide covers how to coordinate these situations across a team of CFIs without creating scheduling gaps.

HangarOS captures Hobbs time and landing data through the booking record, which means the information needed for currency checks is already available if flights are being logged correctly. The goal is to surface that data as a proactive flag in the dispatch workflow rather than a reactive lookup after someone asks.

Currency as Operational Information

Flight currency is not a compliance checkbox reviewed once a year. It is a live operational constraint that affects which students can do what on any given day. When schools track it as such and build verification into the booking workflow, currency problems are rare and manageable. When it is handled informally, the issues surface at the worst possible moment: at the aircraft, with a student and a passenger waiting, and a dispatcher who did not know to check. The regulation is simple. Maintaining currency awareness across an active training fleet requires intentional process.