Pitot-Static and Transponder Checks: How 14 CFR 91.411 and 91.413 Become a Flight School Dispatch Item

A school's instrument trainer launched on a 1300 stage check with two hours of forecast IMC on the route. It came back at 1400 because the CFII opened the maintenance summary on the ramp and saw the static system check had expired three weeks earlier. The dispatcher had released the airplane. The binder showed the date. The two never met until the student was strapped in with the IFR clearance copied. Nothing about the airframe was unsafe. The flight was illegal anyway, the lesson had to be rescheduled, and the chief instructor spent the afternoon writing up a process that should have existed before the airplane was added to the IFR pool.

14 CFR 91.411 and 91.413 are the two recurring inspections most likely to ground a flight school's IFR trainer in a way the dispatcher cannot see coming. They live on a calendar clock, they have nothing to do with the 100-hour or the annual, and they tend to expire mid-month on a date nobody is watching unless the school made watching it someone's job.

What 91.411 Covers

14 CFR 91.411 requires that no person operate an airplane in controlled airspace under IFR unless the static pressure system, each altimeter, and each automatic pressure-altitude reporting system have been tested and inspected within the preceding 24 calendar months. The work has to follow Appendix E of Part 43 and be entered in the aircraft maintenance records. The testing has to be done by the manufacturer, by a properly equipped certificated repair station, or, for static system tests that do not involve disassembling the altimeter, by a certificated mechanic with an airframe rating.

91.411 takes the IFR-capable airplane and adds a recurring inspection condition on top of the equipment baseline in 91.205: the altimeter and the static system have to have been bench-tested to the tolerances Appendix E names, and the result has to be inside the limits.

The pressure-altitude reporting system, the encoder that feeds the Mode C signal, falls under 91.411 because what gets reported to ATC has to match what the pilot reads off the altimeter. A drifted encoder and a tight altimeter can fail traffic separation in a way neither one surfaces on a VFR ramp. The 24-month bench check catches the drift before a controller does.

What 91.413 Covers

14 CFR 91.413 is the transponder rule. No person may use an ATC transponder unless, within the preceding 24 calendar months, it has been tested and inspected and the test has been entered in the aircraft maintenance records under Appendix F of Part 43.

91.413 is the rule the school's VFR-only trainers do not get to ignore. A 172 that never sees an IFR lesson still operates the transponder when crossing a Mode C veil, when getting flight following, or when entering Class C or D airspace with a working transponder installed. The 24-month check is the precondition to using the box at all, and most flight school airplanes use the box on most flights.

91.411 and 91.413 cover overlapping equipment but they are different tests. The altimeter and static check live under 91.411 and Appendix E. The transponder bench check lives under 91.413 and Appendix F. The encoder gets caught by both. A shop knocks them out together because the airplane is already on the bench, but the maintenance entries are separate and the next-due dates are separate. A school treating them as one inspection has set itself up to misread the cycle the first time the shop does one without the other.

The 24-Calendar-Month Clock

The clock in both rules is calendar months, not hours. A trainer that flew 1,400 hours in 24 months and a trainer that flew 200 hours in 24 months are equally due. That makes the 91.411 and 91.413 checks different from the 100-hour inspection, which counts time in service, and different from the annual, which is calendar but easier to remember because most schools already plan around it.

"Within the preceding 24 calendar months" means the test is good through the last day of the 24th month after the month it was performed. A static check signed off on 12 March 2024 is good through 31 March 2026. The airplane can be operated IFR on 31 March 2026 and cannot be operated IFR on 1 April 2026 unless a new check is in the records. The reason schools get caught is that the last-day-of-month boundary makes the deadline feel like the end of the next month, and the schedule books a stage check on the 2nd that should have come a week earlier.

Where the Check Belongs at Dispatch

A pitot-static or transponder check that expires inside a booked block of IFR lessons is the same failure pattern as a recurring AD coming due mid-week. The discipline is the same as the one covered in the AD tracking guide: the next-due date lives on the aircraft record where the dispatcher sees it, with a soft flag at a comfortable lead time before the deadline and a hard block on the day the inspection lapses.

The interaction with 91.213(d) inoperative equipment is worth being precise about. An expired 91.411 check does not give the school a 91.213(d) deferral. The static system itself is not broken, but the airplane is not legal for IFR until the inspection is current. That removes the airplane from IFR operations the same way a placarded vacuum pump would, with the same kinds-of-operation flag on the booking. A VFR dual the next day is fine. An IFR cross-country two hours later is not, and the dispatch system has to know which lesson is which.

The Transponder Side Catches the VFR-Only Schools

A school that flies exclusively VFR sometimes treats 91.411 and 91.413 as IFR-only paperwork and lets both lapse together. The 91.413 check then catches them on the next flight to a Mode C veil airport or the next request for flight following, because the rule does not care whether the airplane is IFR or VFR. It applies to the use of the transponder.

The fix is to track 91.413 as a recurring item against every airframe with a transponder installed and any plausible operation involving Class C or D airspace, Mode C veils, or ATC services. That is most flight school airplanes, and the cost of the bench check is a small fraction of the lost revenue from a grounded trainer on a Saturday morning.

Pair the Bench Visit With the Avionics AD Sweep

The bench visit is also the natural moment to run the AD sweep on the transponder and the encoder. Avionics products carry their own airworthiness directives, and the airplane is already on the bench with the boxes pulled. A school that uses the 91.411 and 91.413 visit as the scheduled checkpoint for transponder-related ADs spends fewer non-revenue days at the avionics shop across the year, and the aircraft booking system sees one block of unavailability instead of two.

A modern flight school management platform like HangarOS holds the 91.411 next-due and the 91.413 next-due as structured fields on each aircraft, ties them to the dispatch decision the same way it ties the annual and the 100-hour, and blocks IFR bookings the day the static check lapses. The check stops being something the chief instructor has to remember and becomes a property of the airplane the schedule reads.

Plan the Inspection Inside the Window

The schools that never get caught book the 91.411 and 91.413 work three to four weeks before the deadline, not the week of. An avionics shop with a full bench can run a week or two long, and a check that has to be redone because something failed the first pass adds another. A school that walked in expecting to leave the same day and is told to come back on Tuesday has lost the booked stage check and every IFR lesson that would have flown in the interim.

The cleanest pattern is to set the dispatch flag at a fixed lead time, schedule the bench visit when the flag fires, and treat the 91.411 and 91.413 cycle as a routine maintenance event the same way the next 100-hour is. The trainer that comes back with both certificates in order and a comfortable next-due date is the one the IFR schedule can be built around for the next 23 months.