What is an encoding altimeter and how does it work with a Mode C transponder?

An encoding altimeter converts the aircraft's barometric altitude into a digital Gray code signal, which is then transmitted to the Mode C transponder. The transponder includes this pressure altitude data in its reply to ATC radar interrogations, allowing controllers to see the aircraft's altitude displayed alongside its radar return. This information is also used by Traffic Alert and Collision Avoidance Systems (TCAS) on other aircraft for separation and conflict alerts. The PHAK explains that the encoding altimeter and transponder together form a critical link in the ATC altitude-reporting system.

What's the difference between indicated altitude and the pressure altitude transmitted by a Mode C transponder?

Indicated altitude is what the pilot reads on the altimeter after setting the local altimeter setting (QNH) in the Kollsman window, and it approximates true altitude above mean sea level under standard conditions. Pressure altitude, however, is the altitude referenced to the standard datum plane of 29.92 inches of mercury, and this is what the encoding altimeter sends to the Mode C transponder regardless of the pilot's altimeter setting. ATC computers then automatically correct for the local altimeter setting to display a meaningful altitude readout to the controller. This is why 14 CFR Part 91 requires the transponder's altitude reporting to be based on pressure altitude, not the pilot-adjusted indicated altitude.

Why does ATC require Mode C transponder equipment in certain airspace?

14 CFR Section 91.215 mandates Mode C transponder equipment in Class A, B, and C airspace, as well as above 10,000 feet MSL in the contiguous United States (excluding airspace at or below 2,500 feet AGL), because altitude readouts are essential for controllers to provide safe traffic separation. Without altitude data, a radar return appears only as a two-dimensional blip, leaving controllers unable to determine vertical separation between aircraft. The automatic altitude reporting provided by the encoding altimeter and Mode C transponder also feeds ground-based TCAS processing, enhancing collision avoidance for equipped aircraft. The Aeronautical Information Manual further notes that pilots should operate their transponder on the appropriate code and with altitude reporting enabled at all times unless otherwise instructed by ATC.

Encoding Altimeter and Mode C Transponder Interface

Every time an aircraft with a Mode C transponder replies to an ATC radar interrogation, the controller's screen automatically displays the aircraft's altitude alongside its radar return. That altitude readout is not typed in by the pilot — it is generated automatically by a device called the encoding altimeter, which converts barometric pressure data into a digital code and sends it to the transponder. Understanding how these two instruments work together is fundamental for any airframe technician responsible for inspecting, testing, or troubleshooting aircraft instrument systems.

This article walks through the mechanical and electrical principles of the encoding altimeter, the Gray code scheme it uses, how the transponder packages and transmits that data, and the regulatory requirements that govern inspection and testing of the combined system.

The Encoding Altimeter: How It Works

A standard pressure altimeter uses an evacuated aneroid capsule that expands or contracts as ambient pressure changes through the static port system. In a conventional non-encoding instrument, the capsule's movement is mechanically linked to pointer gears and a Kollsman window where the pilot sets the local altimeter setting (QNH). The encoding altimeter does all of that — it still presents a readable dial for the pilot — but it adds an internal mechanism that translates capsule position into an electrical output representing pressure altitude.

The key distinction is pressure altitude versus indicated altitude. The encoding altimeter always outputs pressure altitude — altitude referenced to a standard datum of 29.92 in Hg (1013.25 hPa) — regardless of what Kollsman setting the pilot has dialed in. This is intentional. ATC needs a common reference for all aircraft so that separation can be computed consistently. The controller's system knows every aircraft's Mode C readout is referenced to 29.92, so it can calculate vertical separation without worrying about each crew's local altimeter setting.

The Rotary Encoder Mechanism

Inside the encoding altimeter, a series of electrically conductive and non-conductive segments are arranged on a rotating disc or drum that is mechanically coupled to the aneroid capsule stack. As the capsule moves with altitude changes, the disc rotates, and a set of electrical brushes or optical sensors read the pattern of active and inactive segments. Each unique angular position of the disc produces a specific combination of on/off signals across multiple output lines. Those combinations, taken together, form the Gray code output.

Some installations use a separate blind encoder (also called a digitizer) rather than a combined encoding altimeter. A blind encoder has no pilot-readable display; it is a standalone pressure transducer mounted in the aircraft and connected to the static system, used solely to generate the altitude code for the transponder. Either approach — integrated encoding altimeter or separate blind encoder — must meet the same performance and testing standards.

Gray Code: Why Not Binary?

The encoding altimeter outputs altitude data in Gillham code, a specific application of Gray code (also called reflected binary code). In standard binary, incrementing from one number to the next can require multiple bits to change simultaneously. For example, going from 7 (0111) to 8 (1000) flips all four bits at once. At the instant of transition, intermediate states can appear where the wrong altitude is briefly read. In a safety-critical system, even a momentary erroneous altitude report is unacceptable.

Gray code solves this by ensuring that only one bit changes at a time between consecutive values. At any transition, if one brush or sensor is momentarily ambiguous, the worst-case error is one altitude increment — far safer than a wild jump of thousands of feet. The Gillham code used by Mode C transponders encodes altitude in 100-foot increments, using eleven output lines (designated C1, A1, C2, A2, C4, A4, B1, B2, B4, D2, D4) to cover a reporting range from approximately −1,200 feet up through the mid-100,000-foot range in pressure altitude, though many installations and test sets are practically limited to lower service ceilings.

The Transponder's Role: Packaging and Transmitting

The transponder operates in the 1030/1090 MHz frequency band. ATC's Secondary Surveillance Radar (SSR) transmits interrogations at 1030 MHz, and the transponder replies at 1090 MHz. For Mode A interrogations, the transponder replies with the 4096-code squawk set by the pilot. For Mode C interrogations, it reads the Gray code from the encoding altimeter and formats it into a pulse-position reply containing the altitude information.

A Mode S transponder operates similarly but adds a unique 24-bit ICAO address for each aircraft, enabling selective interrogation and more sophisticated data exchange. Altitude is still encoded from the same Gray code source, but Mode S can also carry additional data used by ADS-B and TCAS. The encoding altimeter or blind encoder interfaces with the Mode S transponder through the same 11-wire Gillham code connection used by older Mode A/C transponders, maintaining backward compatibility.

TCAS Integration

The Traffic Alert and Collision Avoidance System (TCAS) relies heavily on Mode C altitude reports. When TCAS interrogates nearby aircraft, it reads their Mode C replies to determine vertical separation. The altitude data TCAS receives about its own aircraft also comes from the on-board encoding altimeter — fed directly to the TCAS computer. Errors in the encoding altimeter therefore affect not only ATC displays but also the integrity of TCAS resolution advisories. This underscores why the regulatory testing requirements for this system are strict and non-negotiable.

Regulatory Requirements and Inspection Standards

Under 14 CFR Part 91, Section 91.413, any transponder-equipped aircraft operated in airspace where a transponder is required under §91.215 or §99.12 must have that transponder tested and inspected within the preceding 24 calendar months — this requirement is tied to the equipment and the airspace in which it must be used, not merely to the aircraft's location at any given moment. The regulation requires that tests be performed by appropriately rated repair stations or holders of a certificate authorizing the work. The tests must meet the standards of 14 CFR Part 43, Appendix F, which specifies the testing procedures for transponders and altitude reporting systems.

Appendix F testing covers two separate but related areas. First, the transponder itself is bench- or ramp-tested for parameters including frequency accuracy, reply frequency, output power, suppression, decoder performance, and side-lobe suppression. Minimum output power requirements vary by transponder class under the applicable TSO and RTCA/DO-181 minimum performance standards — for example, some classes require 21 dBW minimum while others are held to 18.5 dBW — so technicians must check the specific class and installation rather than apply a single flat figure. Second, the altitude reporting system — the encoding altimeter or blind encoder along with its static plumbing — is tested for accuracy. The altitude encoding must be within ±125 feet of actual pressure altitude at each tested altitude throughout the operating range. Some installations require testing at multiple altitude increments, and any defect found must be corrected before the aircraft is returned to service.

Key Numbers and Rules

Altitude increment: Mode C reports altitude in 100-foot increments using Gillham (Gray) code.
Reporting range: approximately −1,200 feet and up in pressure altitude, with the exact upper limit depending on the specific equipment and code combinations used.
Output lines: 11 lines designated C1, A1, C2, A2, C4, A4, B1, B2, B4, D2, D4.
Encoding accuracy tolerance: ±125 feet of actual pressure altitude (per 14 CFR Part 43, Appendix F).
Inspection interval: every 24 calendar months per 14 CFR §91.413.
Transponder frequency: interrogation at 1030 MHz, reply at 1090 MHz.
Minimum transponder output power: varies by transponder class per the applicable TSO/RTCA DO-181 standards (e.g., 18.5 dBW to 21 dBW depending on class).
Altitude reference: always 29.92 in Hg (standard pressure datum), regardless of Kollsman window setting.

Common Test Traps

Indicated altitude vs. pressure altitude: A common mistake is believing the transponder reports the altitude shown on the altimeter face after the pilot dials in an altimeter setting. It always reports pressure altitude (29.92 in Hg reference), not the locally corrected indicated altitude. The controller's equipment applies corrections as needed.
Blind encoder vs. encoding altimeter: Some examinees assume every Mode C installation uses a combined encoding altimeter. A separate blind encoder with no display is equally valid and commonly found in GA aircraft. The airframe technician must know both configurations exist and trace the wiring accordingly.
Gray code vs. binary: Test questions sometimes probe why Gray code is used. The answer is not speed or range — it is reliability at transitions. Only one bit changes per step, preventing momentary false altitude reports.
Who can perform the 24-month test: The inspection under §91.413 must be performed by appropriately certificated persons per Part 43, Appendix F — it is not a routine preflight or owner-performed check. Confusing this with general avionics maintenance permissions is a frequent error.
Accuracy tolerance is for the encoder, not just the altimeter: The ±125-foot tolerance applies to the altitude encoding accuracy — the correlation between actual pressure altitude and what is transmitted. A separate altimeter accuracy check per Part 43, Appendix E applies to the instrument's indicated readings. They are related but distinct tests.

Practical Maintenance Considerations

When troubleshooting a Mode C altitude discrepancy reported by ATC, the airframe technician should begin by verifying the integrity of the static system. Leaks, moisture contamination, or blocked ports will affect both the indicated altimeter reading and the encoding output simultaneously. If the static system is clean, the next step is to connect an altitude encoder tester — sometimes called a transponder test set — to the encoder output and compare the Gray code against known pressure altitudes. The tester decodes the Gillham output and displays it in feet, making it straightforward to identify stuck bits, which typically appear as altitude errors that repeat in a pattern corresponding to a specific output line being permanently open or grounded.

Wiring between the encoding altimeter and the transponder is another failure area. The 11-wire Gillham harness uses logic-level signals, often referenced to aircraft ground, and any intermittent connection can produce erratic altitude readouts on ATC displays. Technicians should inspect connector pins for corrosion, proper crimp integrity, and correct pin assignments per the aircraft's wiring diagram before condemning either the encoder or the transponder. After any repair to the encoding altimeter, blind encoder, static system, or transponder, a fresh compliance test per 14 CFR Part 43, Appendix F is required before the aircraft returns to service in controlled airspace.