What squawk 7700 means, and what it doesn't

Of all the things a flight tracker can tell you, the emergency squawk is the one that reliably raises a pulse. It is also the one most often misread. A 7700 on the map is not a crash, not a prediction of one, and frequently not even a particularly bad day. It is a request for priority. A very loud, very standardised one.

Worth understanding properly, then.

What a squawk actually is

Every transponder-equipped aircraft carries a four-digit code that it transmits when interrogated by secondary surveillance radar, and which modern ADS-B equipment also broadcasts as part of its regular messages. The digits are octal: each one runs 0 to 7, never 8 or 9, because the code is physically encoded as pulse pairs rather than decimal digits. Four octal digits gives 8 × 8 × 8 × 8 = 4,096 possible codes, which is why old transponders were sometimes advertised as "4096 code" units.

Almost all of those codes are administrative. A controller assigns one to a flight ("squawk four six two one"), the crew dials it in, and from then on the radar system can tie that particular blip to that particular flight plan. Codes get reused constantly and mean nothing on their own.

A handful are different. They are reserved worldwide, they mean the same thing in every country, and no controller will ever assign one to you.

Pilots learn them with a rhyme that has survived decades of ground school precisely because it is impossible to forget: seven five, man with a knife; seven six, radio needs a fix; seven seven, going to heaven. Crude, and effective.

The word "squawk" itself is a leftover from wartime identification-friend-or-foe equipment, whose systems were given bird-themed codenames; the usage stuck to transponders and never left.

What happens on the ground when 7700 appears

The code is not a message to a person. It is a message to the automation.

When a radar processing system sees 7700, it flags that target: visually on every affected controller's display, and in most systems audibly as well. The flight becomes an emergency in the system's own bookkeeping, and supervisors are alerted. From that moment the aircraft has priority over everything else in the sector: other traffic is turned or descended around it, a runway is cleared, approach sequences are rebuilt.

Crucially, the code works even if nobody can talk. That is the point of it. A crew dealing with a fire, a rapid depressurisation, or a total electrical problem may have no capacity to explain themselves on the radio for several minutes. Two twists of a knob tell every facility in radar range that this aircraft now comes first. Aviate, navigate, communicate. The transponder does a good deal of the communicating.

In practice a crew with time will do both: select 7700 and make a radio call prefixed MAYDAY (distress: grave and imminent danger) or PAN PAN (urgency: a serious situation that is not, yet, distress). Neither call requires the code, and the code does not require the call. They are independent ways of saying the same thing, and using both is belt and braces.

Why most 7700s are not what people assume

Here is the part that a push notification cannot convey. An emergency declaration is a request for priority handling, not a prediction of an accident. It is used for:

• A passenger or crew medical event, where the aircraft is fine and a person is not.
• A pressurisation problem, prompting an emergency descent to a breathable altitude. Dramatic on a tracker, routine in a simulator.
• A single engine shut down as a precaution on a twin, which is a certificated condition the aircraft is designed and tested to fly in.
• A smoke or fume indication, which crews treat as serious until proven otherwise precisely because the cost of being casual is unacceptable.
• Low fuel after extended holding, where declaring guarantees a direct routing rather than another orbit.
• A gear indication that will not go green, usually a light rather than a leg.

Good crews declare early and often, because declaring costs nothing and buying yourself priority is free. The overwhelming majority of flights that squawk 7700 land safely at an airport, are met by fire vehicles as a standard precaution, and taxi in. The interesting ones are interesting; they are not typical.

Codes that appear and vanish

Not every emergency squawk on a tracker is real. Codes are entered by hand, and hands slip. A crew changing from 4671 to 4677 can pass through neighbouring values, and older equipment happily transmits whatever is momentarily displayed; most modern transponders guard against this by holding the previous code until all four digits have been entered, but not all equipment is modern. Maintenance testing on the ground produces spurious codes too.

The signature is short duration. A 7700 that exists for eight seconds and is never followed by a diversion, a descent or a turn was almost certainly finger trouble. A 7700 accompanied by a descent, a heading change toward the nearest suitable airport, and a hold being abandoned is the real thing.

7500 deserves particular care. It does sometimes appear in error, and the standard response is a controller asking the crew to confirm it, a question with a very deliberate form. Given how rare actual hijackings are, a 7500 flashing briefly on a tracking app is far more likely to be a mis-set transponder than anything else. Treat it as noise unless and until something official says otherwise.

Other codes worth recognising

Once you start reading squawks, several non-emergency codes turn up constantly:

A screen full of 1200s around a small airfield on a Saturday morning is not a mystery formation. It is people going flying.

How the app handles emergencies

Airplanes.live can push you a notification the moment any aircraft in view of the network broadcasts 7700, whether or not the app is open. In ATC scope mode, the codes 7500, 7600 and 7700 are called out on the target itself, alongside the callsign, flight level and groundspeed in the data block. That is the same information, in roughly the same place, that a controller's display would put there.

There is also a small design decision worth explaining. Our servers keep a rolling 24-hour list of aircraft that have broadcast an emergency squawk, so that the app can show you recent events rather than only the ones it happened to be running for. Each entry is the aircraft's own broadcast and the time we saw it. It records nothing whatsoever about who was watching, and it would look identical if nobody had opened the app at all, which is the same standard the rest of the privacy policy holds to.

And the standing caveat, which matters more here than anywhere else in the app: this is a view of public radio traffic, not air traffic control information. It is not verified, it is not complete, and it is for interest and education only.