Pitot-Static, Altimeter, and Transponder Inspections: The 24-Month Cycle Flight Schools Miss

An IFR cross-country trainer gets a ramp check on a Wednesday afternoon and the inspector asks for the pitot-static log entry. The chief mechanic pulls the binder, finds the entry, and the date on it is twenty-five months and four days old. The airplane has flown twelve IFR legs in the last week. Nothing in that morning's preflight surfaced the lapse, because the 100-hour was fresh, the annual was fresh, and the airframe and engine records all looked clean. The thing that grounded the airplane was an inspection cycle running on a clock nobody on the operating side was watching.

That failure mode is more common in a flight school fleet than the ramp-check story suggests. A school running six trainers and an IFR cross-country airplane has the 100-hour and annual schedules tracked tightly because they recur often. The 24-month inspections under 14 CFR 91.411 and 91.413 recur rarely, get done quietly when an airplane is already in the shop for something else, and are exactly the kind of due date that lapses unnoticed.

Two Regulations, Three Inspections

14 CFR 91.411 governs the altimeter and the static pressure system. Before any aircraft can be operated under IFR in controlled airspace, both must have been tested and inspected in the preceding 24 calendar months under the procedures listed in Appendix E to Part 43. The work covers the static system for leaks, the altimeter for calibration against a known reference at multiple altitudes, and the automatic altitude reporting equipment for correspondence with the indicated altitude.

14 CFR 91.413 covers the transponder. The transponder and its installation must be tested and inspected every 24 calendar months for any aircraft on which a transponder is required for the operation being conducted. A trainer flying VFR in airspace that requires Mode C reporting falls inside that requirement, which means the rule is not an IFR-only obligation in practice. Most schools operating anywhere near a Class B or Class C airport are flying transponder-required airspace on every cross-country.

The third inspection lives quietly inside the first. The altitude encoder feeding the transponder has to correspond with the altitude indicated to the pilot, and that correspondence is verified as part of the 91.411 work. A new encoder installed in isolation between cycles is one of the ways a school discovers, on the next cycle, that the system as a whole was not within tolerance for months.

What VFR-Only Buys You, and What It Does Not

A school operating a primary trainer used exclusively for VFR day instruction in airspace that does not require a transponder does not have to do either inspection. That is the narrow case, and very few real fleets sit inside it. A school that operates the same trainer for any IFR training, any actual IFR flight, or even repositions it home in IFR conditions has triggered 91.411 and is on the 24-month clock until the airplane permanently leaves IFR operation.

The transponder inspection under 91.413 is harder to escape. The rule attaches to any aircraft operated in airspace where a transponder is required, which includes Class A, Class B, the Mode C veil around Class B, Class C, above 10,000 feet MSL outside specific exceptions, and several other configurations. A trainer that does cross-country work to almost any reasonable city is a trainer that needs current transponder certification, regardless of whether it is flown VFR or IFR.

A school that documents its fleet's intended operating envelope and the inspections each tail number actually needs is a school whose 24-month tracking is grounded in something other than a default assumption.

Why the 24-Month Cycle Is the One That Lapses

The 100-hour and the annual inspection recur often enough that everyone in dispatch has them in working memory. A 100-hour airplane is past its inspection inside a few weeks of routine use. The annual is back on the calendar inside a year. The 24-month cycle has none of that pressure. An airplane finishes a 91.411 inspection in March of one year and the next due date sits eighteen months past the chief instructor's window of attention.

The standard failure pattern is that the airplane gets pulled in for an annual at month twenty-three, the shop does not have the pitot-static work scheduled because nobody asked for it, the annual finishes and the airplane returns to service, and four weeks later the 91.411 cycle has lapsed. The maintenance department has done nothing wrong. The school's tracking system never surfaced that the two cycles were almost coincident, and a sortable due date never made it to the dispatcher.

This is the same failure mode that runs flight schools into trouble on recurring airworthiness directives. Anything that recurs on a clock the operating staff does not see is something the school is one calendar slip away from missing.

What the Inspection Actually Covers

The pitot-static work under Appendix E to Part 43 is a static system leak check at a defined rate, an altimeter calibration at multiple test altitudes against a known reference, and a correspondence test between the altimeter and any automatic altitude reporting source. The inspection is invasive enough that the work order will list the lines opened, the test equipment used, and the result at each altitude.

The transponder inspection under Appendix F to Part 43 includes a frequency test, a power output test, a reply test, a Mode C correspondence test, and a sensitivity check. The shop closes the work with a logbook entry that names the equipment used, the result at each test point, and the date.

Both entries belong in the aircraft records the school inspects when an airplane goes back on the dispatch line. A return-to-service after a 24-month cycle is a moment where the squawk that opened the work and the inspection that closed it both need to land in the same status picture the dispatcher reads in the morning.

What Happens When the Date Slips

A school that discovers a lapsed 91.411 or 91.413 has an inoperative-equipment problem before it has a compliance problem. The airplane cannot be operated for the affected category of flight until the inspection is current. That is the 14 CFR 91.213 machinery. The equipment is not actually broken, but it is not legally usable for the operation, and the dispatcher has to treat it the same way as a broken altimeter or a failed transponder.

The remediation is to ground the airplane for the affected operations, schedule the inspection, and document the lapse in the aircraft records. None of that is hard. The expensive part is the cancellations between the discovery and the fix, and those cancellations only happen because the due date was not surfaced before it passed.

Putting the 24-Month Cycle on the Dispatch Screen

The mechanical answer is the same one that already exists for the 100-hour and the annual. Every recurring inspection on the airplane needs a due date in the same record the booking system reads. A 91.411 inspection due in sixty days is a soft flag on the dispatch screen. A 91.413 inspection past due is a hard block that prevents the airplane from being released for any operation that requires it.

A flight school scheduling platform that treats every recurring maintenance event as a first-class field on the aircraft record surfaces the next-due value against the booking calendar and refuses to dispatch an airplane whose status will lapse during the booked block. HangarOS holds the 24-month cycles in the same airworthiness picture as the 100-hour, the annual, and the recurring AD list, because the rule that grounds the airplane on a Wednesday afternoon does not care which clock it ran on.

The Inspection That Recurs Slowly Is the One You Have to Engineer Around

Anything that recurs on a 90-day cycle surfaces itself through routine use. Anything that recurs on a 24-month cycle surfaces itself only through deliberate tracking. The flight schools that never get caught are the ones that treat the 91.411 and 91.413 cycles as scheduled work, written into the aircraft record with the next-due value visible on every booking, and not as a thing the maintenance shop reminds them about when an airplane happens to be in the hangar.