Flight Review Requirements Under 14 CFR 61.56: A Flight School Guide
A practical breakdown of the FAA flight review under 14 CFR 61.56, including what the review covers, how the 24 calendar-month interval works, what counts in place of a review, and how to track due dates in your dispatch workflow.
A club renter shows up for a Saturday booking, preflights the airplane, and mentions in passing that his last flight review was sometime in the spring two years ago. The dispatcher checks the logbook endorsement: April of the year before last, 25 calendar months back. He is not legal to act as pilot in command, and no amount of recent flying changes that. The booking gets handed to an instructor, the renter flies the next hour as dual, and what should have been a solo rental becomes a flight review nobody scheduled.
This is the quiet failure mode of 14 CFR 61.56. The rule is short and its consequences are absolute, but the tracking is easy to let slide until someone is already at the airplane.
What the Flight Review Requires
A flight review is a minimum of one hour of flight training and one hour of ground training given by an authorized instructor. The ground portion must cover the current general operating and flight rules of part 91. The flight portion covers whatever maneuvers and procedures the instructor judges necessary for the pilot to safely exercise the privileges of the certificate. That discretion is deliberate. A 200-hour private pilot who flies a 172 twice a month and a 5,000-hour commercial pilot returning after a long layoff need different reviews, and the regulation lets the instructor tailor both.
There is no pass or fail in the checkride sense. The review is complete when the instructor is satisfied and makes a logbook endorsement saying so. If the instructor is not satisfied, there is simply no endorsement and the pilot is not current for PIC. Nothing gets recorded as a failure, which is part of why the flight review functions as a teaching tool rather than a test.
No person may act as pilot in command unless, within the preceding 24 calendar months, they have completed a satisfactory flight review in an aircraft for which they are rated. The phrase biennial flight review, or BFR, is the old name. The regulation now just says flight review, but the 24-month interval is the same.
Calendar Months, Not a Rolling Date
The 24-month window is measured in calendar months, which trips up pilots who expect a rolling two-year date. A review completed on April 12 is good through the last day of April two years later, not through April 12. The endorsement effectively expires at the end of the 24th calendar month after the month it was given.
This matters for scheduling because a pilot who reviews in mid-month gets a small grace window to the end of that month, and a school that tracks the exact day rather than the calendar month will either ground a pilot early or, worse, let one fly a few days late. The same calendar-month logic governs instrument currency under 14 CFR 61.57, so a school that already tracks currency correctly has the date math it needs.
What Resets the Clock Besides a Standard Review
A standalone flight review is the common path, but it is not the only one. Passing a practical test for a new certificate or rating satisfies the requirement, which is why a pilot who earns an instrument rating does not also need a separate flight review that month. Completing one phase of the FAA's WINGS pilot proficiency program counts as well. So does a proficiency check or practical test administered by the FAA, an approved check airman, or a designated examiner.
The practical effect for a flight school is that students moving through training are usually covered by their checkrides, while the certificated renters, club members, and occasional instructors are the ones who drift past 24 months without noticing. The FAA's guidance for conducting and crediting reviews lives in Advisory Circular 61-98E, which is worth keeping on hand for the edge cases.
Flight Review Is Not Currency
The most common confusion is treating the flight review and recent-flight-experience currency as the same obligation. They are independent. A pilot can be perfectly current under 61.57 with three takeoffs and landings in the last 90 days and still be illegal to fly because the flight review lapsed at 24 months. The reverse is also true: a freshly reviewed pilot who has not flown in four months is legal as far as the flight review goes but cannot carry passengers until the takeoffs and landings are back in the window.
A dispatch desk has to check both, and they fail in different ways. Currency lapses quietly across a 90-day window that resets constantly. The flight review is a single hard date two years out. The operational habits that catch one will not automatically catch the other unless the system is built to track both.
Why This Belongs in the Dispatch Workflow
For a flight school or club, the flight review is an operations problem disguised as a regulatory one. The school is not the pilot in command and does not carry the legal duty, but it is the one renting the airplane, and a renter who flies PIC past their review window is a liability exposure and an insurance problem the school owns in practice if not in regulation.
The reactive version is what the opening scenario describes: the question gets asked at the airplane, the answer is no, and the schedule absorbs the disruption. Tracking it the same way you track instructor availability and aircraft inspections turns it into a non-event. Record the endorsement date when the review is completed, store it against the pilot, and surface a flag at the booking-approval step when the date is inside, say, 60 days of expiring.
Building the Check In
The data is not complicated. For each certificated pilot on the roster you need one date: the last satisfactory flight review. From that single field the booking system can compute the expiration, warn in advance, and block a PIC rental that would fall outside the window. A scheduling platform that already understands who is flying and which aircraft they are rated in has most of what it needs, and adding the review date is a small extension of the same record. This is the kind of proactive flag that separates a booking system that knows the flight record from a calendar that only holds time slots, and it is one of the operational details HangarOS keeps in the booking record rather than a spreadsheet someone updates by hand.
Flight reviews are predictable in a way currency is not. Every certificated pilot has exactly one date, it moves only when they fly a review, and it is knowable months ahead. A school that surfaces that date proactively never has the Saturday-morning conversation about a 25-month-old endorsement, and the renter who came to fly gets to fly.
