History & heritage

MIL-STD-1553 at fifty: why a 1973 data bus still flies

It runs at one megabit per second, carries 16-bit words and was written before the personal computer existed. Fifty years later, MIL-STD-1553 still links the computers of the International Space Station, the flight controls of a recent airliner and the avionics of tens of thousands of aircraft. Its longevity is no accident, and it says a lot about what an onboard bus is really for.

5 min read·Updated October 2026

Born from a wiring problem

In the late 1960s, aircraft electronics multiplied faster than the wiring could follow. Every unit was connected to every other by its own wires, and the harnesses grew heavy, complex and fragile. An SAE subcommittee began work in 1968 on a shared, time-multiplexed digital bus, and MIL-STD-1553 was published in the United States in 1973. Revision A followed in 1975, and revision B, dated 21 September 1978, closed the options that A had left open to designers. That is the version equipment is still built to.

scroll

Fifty years of MIL-STD-1553: one protocol, fixed in 1978, carried over new media and new documents.

Notices followed. Notice 2, in 1986, tightened the cable impedance to between 70 and 85 Ω and allowed broadcast again, for mode codes only; the later notices were administrative. SAE published a commercial equivalent, AS15531, in 1995, and the C edition of 2018 folded the notices into one text without changing any function.

How it works, in one paragraph

1553 is a command-and-response bus at 1 Mbit/s, Manchester-encoded, on a shielded twisted pair. One bus controller decides who speaks: it sends a command, and the addressed remote terminal answers within 4 to 12 µs. A word lasts 20 bit times — a sync pattern of three bit times, 16 data bits and a parity bit. Up to 31 remote terminals share a bus, address 31 being reserved for broadcast; a message carries at most 32 data words; and every bus is doubled, A and B. Units connect through short stubs, transformer-coupled up to 6.1 m from the bus.

The bus controller sends a transmit command to RT 12 on bus A.RT 12 answers on bus A within 4–12 µs: its status word, then 4 data words.The monitor records the message, time-stamped on reception: bus A, command and answer.Next minor frame, 20 ms later: the stub linking RT 12 to bus A is cut.The bus controller sends the same command on bus A……and RT 12 does not answer. The monitor records the missing response.The bus controller repeats the same transaction on bus B.RT 12 answers on bus B: status word, then 4 data words.Dual-redundant: every terminal is wired to bus A and to bus B. When a transaction fails on A, the controller can repeat it on B; the monitor hears both buses and records the failure and the retry.

Dual-redundant 1553, slowed down: every terminal is coupled to bus A and to bus B. When RT 12 falls silent on A, the bus controller repeats the same command on B, and a monitor listening to both buses records each attempt with its time.

Why it lasted

Determinism. Nothing speaks unless asked, so the timing of every message is known in advance: a property certification values, and that a switched network has to work hard to imitate.
Robustness. Transformer coupling isolates every unit, the bus is doubled, and a terminal that fails falls silent without taking the others with it. The isolation matters even more on composite airframes, which shield less than metal ones.
Simplicity. A short standard whose function has not changed since 1978, implemented by decades of chips and test equipment from many suppliers.
The installed base. Estimates speak of at least 30,000 aircraft equipped worldwide. Replacing the bus means rewiring and requalifying every unit on it, a cost the trade press puts at more than a million dollars per aircraft.

Far beyond its first use

The International Space Station. The computers of its US segment are linked by 1553B buses in three tiers, and the experiment racks get a 1553 payload bus. With two channels per bus and backup buses, NASA counted that it takes four failed channels to cut communication.
European space. ESA describes 1553 as used in virtually all European onboard data-handling systems — launchers, Earth-observation and navigation satellites, science missions — and the ECSS adapted it to spacecraft in 2008, in ECSS-E-ST-50-13C.
Airliners. Airbus chose 1553 for the flight control system of the A350 XWB, a choice made public in 2010.
Optical fibre. Its fibre variant, MIL-STD-1773, flew on NASA spacecraft from 1992.

What came after

Enhanced Bit Rate 1553, SAE AS5652 (2005): the same principles at 10 Mbit/s, in a star topology.
High-speed signals over the existing wires: flight-tested at 40 Mbit/s in 2005, with measurements showing the cables could carry far more. The revision that would have standardised it never appeared; edition C changed no function.
Ethernet. Switched networks such as AFDX, ARINC 664, developed for the A380, and Time-Triggered Ethernet, which on Ariane 6 replaces the 1553 bus of earlier launchers.

None of them has displaced 1553 on the platforms that already carry it. The bus will fly as long as the aircraft and spacecraft built around it do, and many of those have decades left.

What it teaches

Predictability outlives bandwidth. A bus whose timing is known in advance stays useful long after faster ones appear.
A short, stable standard is easier to keep than a rich, moving one: fifty years of compatible equipment came from not changing the protocol.
The cost of a bus is not its chips but its certification. Once a platform is qualified with it, the bus is part of the airframe.