What changes the moment the code changes
Our guide to squawk codes covers what the numbers are. This one is about what actually happens afterwards — because the interesting part of an emergency squawk is not the four digits, it is the sequence of events they set off on the ground.
The moment a transponder is set to 7700, the code is flagged automatically at every radar display receiving that aircraft. It is not something a controller has to notice. The target changes appearance and an alert is raised, typically across the whole sector rather than at one position.
This is why flight trackers frequently show an emergency before any news outlet does. You are seeing the same automatic flag the controller sees, at the same moment, because both come from the same transmission.
What a controller does next
The response is well rehearsed and follows a broadly consistent shape:
- Establish what is wrong. The controller asks the crew to say the nature of the emergency, souls on board and fuel remaining. Those last two are not curiosity — they determine the response the fire service prepares.
- Give them room. Other traffic is moved out of the way. The aircraft usually gets a direct routing and priority for descent and approach.
- Reduce the workload. A crew dealing with a failure does not want a busy frequency. They may be moved to a discrete frequency, and further instructions kept minimal.
- Alert the ground. The destination airport is warned, and the fire service positions for a full emergency or a local standby depending on severity.
The phrase controllers use is that the crew are given time and space. In practice the aircraft stops being one of forty in a sequence and becomes the thing everything else is arranged around.
What it looks like on a tracker
Several things usually happen at once, and they are recognisable if you know the pattern:
| What you see | What it usually means |
|---|---|
| Squawk changes to 7700 | The crew has declared an emergency. |
| An immediate turn | Turning back, or towards a suitable airport. |
| A steep descent | Often a pressurisation problem — a rapid descent to a level where the cabin does not need pressurising is the standard response. |
| Level flight in a holding pattern | Burning fuel down to landing weight, or working through checklists before an approach. |
| Speed reducing well out from the airport | A configuration or gear problem being assessed. |
Most emergencies are not dramatic
It is worth stating plainly, because a 7700 on a map invites the worst assumption. The large majority of declared emergencies are precautionary. Common causes include a passenger taken ill, a single system failure with plenty of redundancy remaining, a warning light the crew wants on the ground rather than in the air, and fuel reserves being approached after holding.
Crews are trained to declare early rather than late. Declaring costs nothing and unlocks priority; waiting narrows the options. An aircraft squawking 7700 is very often an aircraft whose crew is being appropriately cautious, and it will usually land normally and taxi to a stand.
The other two codes behave differently
7600, radio failure. The aircraft is flyable but cannot communicate. Because the crew cannot be told anything, the response is procedural: they follow published lost-communication rules, flying the route and levels they were last cleared for or that were filed. Controllers clear a path around a predicted track. On a tracker, a 7600 aircraft often looks unremarkable — it continues steadily, because predictability is the entire point.
7500, unlawful interference. Handled quite differently and largely invisibly. There is a deliberate protocol for confirming it that avoids alerting anyone aboard, and details are not made public. On flight trackers, a brief 7500 is far more often a mis-keyed transponder — 7500 is one digit away from several ordinary codes — than a real event.
Codes are set by hand on a keypad, and hands slip. A squawk that appears for a few seconds and then reverts is almost always a finger error during a routine change, caught immediately. Real emergencies persist, and are accompanied by a change in how the aircraft is flying.
What happens after landing
The squawk usually reverts once the aircraft is on the ground and the emergency is over, which on a tracker can look like the event simply evaporating. Behind that, a declared emergency generates paperwork: an ATC occurrence report, an operator report, and depending on severity a filing with the national investigation body.
Most produce no further action at all. That is the system working — the reporting threshold is set deliberately low so that patterns can be spotted long before they become accidents.
What not to do with it
Emergency squawks are visible because ADS-B is an open broadcast, not because the information is published for the public. Live speculation about an aircraft in difficulty reaches worried relatives surprisingly quickly, and is very often wrong — the squawk tells you an emergency was declared and nothing whatever about what it is.
Watch it, by all means. It is genuinely one of the more interesting things a tracker shows. Just resist the urge to narrate it as though you know what is happening on board, because you do not.