sensors Mode-S transponder
AA6B7E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N77006 · BOEING 777-200 · operated by UNITED AIRLINES INC
- Hex
- AA6B7E
- Octal
- 52465576
- Decimal
- 11,168,638
- Country
- US
- Tail
- N77006
- Type
- B772
- Flights observed
- 195
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address AA6B7E falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UAL130 | - | 11 | 2026-07-09 |
| UAL889 | United Airlines | 10 | 2026-07-04 |
| UAL803 | - | 10 | 2026-07-08 |
| UAL932 | - | 9 | 2026-07-07 |
| UAL888 | United Airlines | 9 | 2026-07-03 |
| UAL131 | - | 8 | 2026-07-11 |
| UAL804 | - | 7 | 2026-07-06 |
| UAL939 | United Airlines | 6 | 2026-04-16 |
| UAL933 | - | 6 | 2026-07-07 |
| UAL70 | United Airlines | 6 | 2026-06-18 |
| UAL149 | - | 6 | 2026-07-10 |
| UAL926 | - | 5 | 2026-07-14 |
| UAL148 | - | 5 | 2026-07-11 |
| UAL97 | United Airlines | 4 | 2026-04-26 |
| UAL943 | United Airlines | 4 | 2026-06-15 |
| UAL942 | - | 4 | 2026-06-15 |
| UAL917 | - | 4 | 2026-06-28 |
| UAL905 | - | 4 | 2026-06-24 |
| UAL876 | - | 4 | 2026-07-12 |
| UAL875 | - | 4 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAL926 | - | Jul 14, 02:40 UTC | Jul 14, 03:30 UTC | 50m |
| 2026-07-13 | UAL45 | ZRH → SFO | Jul 13, 12:02 UTC | Jul 13, 23:42 UTC | 11h 40m |
| 2026-07-13 | UAL45 | - | Jul 13, 12:00 UTC | Jul 13, 23:45 UTC | 11h 45m |
| 2026-07-12 | UAL44 | SFO → ZRH | Jul 12, 21:45 UTC | Jul 13, 08:01 UTC | 10h 15m |
| 2026-07-12 | UAL876 | - | Jul 12, 07:25 UTC | Jul 12, 16:40 UTC | 9h 15m |
| 2026-07-11 | UAL131 | EWR → HND | Jul 11, 14:53 UTC | Jul 12, 03:55 UTC | 13h 2m |
| 2026-07-11 | UAL131 | EWR → HND | Jul 11, 14:45 UTC | Jul 12, 04:01 UTC | 13h 15m |
| 2026-07-11 | UAL148 | - | Jul 11, 00:15 UTC | Jul 11, 09:15 UTC | 9h 0m |
| 2026-07-10 | UAL149 | EWR → GRU | Jul 10, 01:21 UTC | Jul 10, 10:00 UTC | 8h 39m |
| 2026-07-10 | UAL149 | - | Jul 10, 01:30 UTC | Jul 10, 10:05 UTC | 8h 35m |
| 2026-07-09 | UAL130 | HND → EWR | Jul 9, 09:45 UTC | Jul 9, 22:10 UTC | 12h 25m |
| 2026-07-08 | UAL803 | IAD → HND | Jul 8, 17:10 UTC | Jul 9, 06:48 UTC | 13h 38m |
| 2026-07-08 | UAL803 | IAD → HND | Jul 8, 17:10 UTC | Jul 9, 06:50 UTC | 13h 40m |
| 2026-07-07 | UAL933 | - | Jul 7, 15:40 UTC | Jul 7, 23:45 UTC | 8h 5m |
| 2026-07-07 | UAL932 | IAD → FRA | Jul 7, 05:33 UTC | Jul 7, 12:50 UTC | 7h 17m |
| 2026-07-07 | UAL932 | - | Jul 7, 05:40 UTC | Jul 7, 12:45 UTC | 7h 5m |
| 2026-07-06 | UAL804 | HND → IAD | Jul 6, 11:40 UTC | Jul 6, 23:35 UTC | 11h 55m |
| 2026-07-05 | UAL875 | SFO → HND | Jul 5, 18:40 UTC | Jul 6, 04:50 UTC | 10h 10m |
| 2026-07-04 | UAL889 | PEK → SFO | Jul 4, 14:40 UTC | Jul 5, 01:05 UTC | 10h 25m |
| 2026-07-04 | UAL889 | PEK → SFO | Jul 4, 13:51 UTC | Jul 5, 01:05 UTC | 11h 14m |
| 2026-07-03 | UAL888 | SFO → PEK | Jul 3, 18:30 UTC | Jul 4, 07:34 UTC | 13h 4m |
| 2026-07-03 | UAL888 | SFO → PEK | Jul 3, 18:35 UTC | Jul 3, 19:05 UTC | 30m |
| 2026-07-02 | UAL927 | FRA → SFO | Jul 2, 18:25 UTC | Jul 3, 05:00 UTC | 10h 35m |
| 2026-07-02 | UAL926 | SFO → FRA | Jul 2, 06:30 UTC | Jul 2, 16:15 UTC | 9h 45m |
| 2026-07-01 | UAL506 | - | Jul 1, 15:50 UTC | Jul 2, 03:45 UTC | 11h 55m |
| 2026-07-01 | UAL506 | FCO → SFO | Jul 1, 14:27 UTC | Jul 2, 03:38 UTC | 13h 11m |
| 2026-07-01 | UAL507 | SFO → FCO | Jul 1, 00:54 UTC | Jul 1, 12:08 UTC | 11h 14m |
| 2026-07-01 | UAL507 | SFO → FCO | Jul 1, 01:05 UTC | Jul 1, 12:15 UTC | 11h 10m |
| 2026-06-30 | UAL889 | PEK → SFO | Jun 30, 10:40 UTC | Jun 30, 20:30 UTC | 9h 50m |
| 2026-06-29 | UAL888 | SFO → PEK | Jun 29, 18:25 UTC | Jun 30, 06:05 UTC | 11h 41m |
| 2026-06-29 | UAL916 | AKL → SFO | Jun 29, 02:14 UTC | Jun 29, 13:59 UTC | 11h 45m |
| 2026-06-28 | UAL917 | SFO → AKL | Jun 28, 06:41 UTC | Jun 28, 18:56 UTC | 12h 15m |
| 2026-06-28 | UAL917 | - | Jun 28, 06:44 UTC | Jun 28, 07:20 UTC | 35m |
| 2026-06-27 | UAL889 | PEK → SFO | Jun 27, 11:00 UTC | Jun 27, 12:39 UTC | 1h 40m |
| 2026-06-27 | UAL889 | PEK → SFO | Jun 27, 10:21 UTC | Jun 27, 21:02 UTC | 10h 41m |
| 2026-06-26 | UAL888 | SFO → PEK | Jun 26, 21:35 UTC | Jun 27, 20:59 UTC | 23h 25m |
| 2026-06-26 | UAL888 | SFO → PEK | Jun 26, 18:15 UTC | Jun 27, 08:01 UTC | 13h 46m |
| 2026-06-26 | UAL888 | SFO → PEK | Jun 26, 18:29 UTC | Jun 27, 06:44 UTC | 12h 15m |
| 2026-06-25 | UAL984 | - | Jun 25, 07:25 UTC | Jun 25, 17:49 UTC | 10h 25m |
| 2026-06-25 | UAL984 | CDG → SFO | Jun 25, 07:39 UTC | Jun 25, 17:48 UTC | 10h 9m |
| 2026-06-24 | UAL57 | EWR → CDG | Jun 24, 22:45 UTC | Jun 25, 04:54 UTC | 6h 10m |
| 2026-06-24 | UAL905 | - | Jun 24, 09:05 UTC | Jun 24, 09:29 UTC | 25m |
| 2026-06-24 | UAL905 | LHR → EWR | Jun 24, 08:55 UTC | Jun 24, 16:31 UTC | 7h 36m |
| 2026-06-24 | UAL905 | LHR → EWR | Jun 24, 08:55 UTC | Jun 24, 16:32 UTC | 7h 37m |
| 2026-06-24 | UAL14 | - | Jun 24, 00:09 UTC | Jun 24, 01:30 UTC | 1h 20m |
| 2026-06-23 | UAL14 | EWR → LHR | Jun 23, 23:45 UTC | Jun 24, 06:18 UTC | 6h 33m |
| 2026-06-23 | UAL22 | DUB → EWR | Jun 23, 09:40 UTC | Jun 23, 16:20 UTC | 6h 40m |
| 2026-06-23 | UAL23 | - | Jun 23, 01:50 UTC | Jun 23, 03:15 UTC | 1h 25m |
| 2026-06-23 | UAL23 | EWR → DUB | Jun 23, 00:55 UTC | Jun 23, 07:18 UTC | 6h 23m |
| 2026-06-22 | UAL22 | DUB → EWR | Jun 22, 08:40 UTC | Jun 22, 15:14 UTC | 6h 35m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the N77006 page for operator, model, and routing details .