sensors Mode-S transponder
AA6BC0
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N77022 · BOEING 777-200 · operated by UNITED AIRLINES INC
- Hex
- AA6BC0
- Octal
- 52465700
- Decimal
- 11,168,704
- Country
- US
- Tail
- N77022
- Type
- B772
- Flights observed
- 203
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AA6BC0 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 |
|---|---|---|---|
| UAL888 | United Airlines | 11 | 2026-06-13 |
| UAL852 | - | 9 | 2026-07-05 |
| UAL853 | - | 8 | 2026-07-04 |
| UAL876 | - | 7 | 2026-06-27 |
| UAL926 | - | 6 | 2026-07-07 |
| UAL889 | United Airlines | 6 | 2026-06-14 |
| UAL45 | - | 6 | 2026-07-06 |
| UAL148 | - | 6 | 2026-06-26 |
| UAL927 | - | 5 | 2026-07-07 |
| UAL59 | United Airlines | 5 | 2026-05-26 |
| UAL149 | - | 5 | 2026-06-25 |
| UAL949 | United Airlines | 4 | 2026-05-19 |
| UAL948 | United Airlines | 4 | 2026-05-19 |
| UAL917 | - | 4 | 2026-07-08 |
| UAL880 | United Airlines | 4 | 2026-06-09 |
| UAL803 | United Airlines | 4 | 2026-06-23 |
| UAL672 | United Airlines | 4 | 2026-05-12 |
| UAL507 | - | 4 | 2026-06-15 |
| UAL506 | - | 4 | 2026-06-15 |
| UAL23 | United Airlines | 4 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAL818 | - | Jul 14, 00:20 UTC | Jul 14, 01:30 UTC | 1h 10m |
| 2026-07-14 | UAL818 | EZE → IAH | Jul 14, 00:16 UTC | Jul 14, 10:01 UTC | 9h 45m |
| 2026-07-13 | UAL819 | - | Jul 13, 01:40 UTC | Jul 13, 10:45 UTC | 9h 5m |
| 2026-07-12 | UAL47 | FRA → IAH | Jul 12, 12:26 UTC | Jul 12, 22:31 UTC | 10h 5m |
| 2026-07-12 | UAL47 | - | Jul 12, 12:35 UTC | Jul 12, 14:01 UTC | 1h 25m |
| 2026-07-12 | UAL46 | - | Jul 12, 00:05 UTC | Jul 12, 09:55 UTC | 9h 50m |
| 2026-07-10 | UAL160 | - | Jul 10, 11:05 UTC | Jul 10, 21:45 UTC | 10h 40m |
| 2026-07-09 | UAL194 | SFO → MUC | Jul 9, 22:13 UTC | Jul 10, 08:56 UTC | 10h 43m |
| 2026-07-09 | UAL194 | - | Jul 9, 22:30 UTC | Jul 10, 08:00 UTC | 9h 30m |
| 2026-07-09 | UAL916 | - | Jul 9, 02:15 UTC | Jul 9, 13:45 UTC | 11h 30m |
| 2026-07-08 | UAL917 | SFO → AKL | Jul 8, 06:36 UTC | Jul 8, 19:00 UTC | 12h 24m |
| 2026-07-08 | UAL917 | - | Jul 8, 06:40 UTC | Jul 8, 07:10 UTC | 30m |
| 2026-07-07 | UAL927 | - | Jul 7, 15:50 UTC | Jul 8, 02:50 UTC | 11h 0m |
| 2026-07-07 | UAL926 | SFO → FRA | Jul 7, 02:44 UTC | Jul 7, 12:53 UTC | 10h 9m |
| 2026-07-07 | UAL926 | - | Jul 7, 02:45 UTC | Jul 7, 05:40 UTC | 2h 55m |
| 2026-07-06 | UAL45 | ZRH → SFO | Jul 6, 12:22 UTC | Jul 6, 23:36 UTC | 11h 14m |
| 2026-07-06 | UAL45 | - | Jul 6, 12:10 UTC | Jul 6, 15:45 UTC | 3h 35m |
| 2026-07-05 | UAL44 | SFO → ZRH | Jul 5, 21:50 UTC | Jul 6, 08:10 UTC | 10h 20m |
| 2026-07-05 | UAL852 | - | Jul 5, 08:20 UTC | Jul 5, 09:30 UTC | 1h 10m |
| 2026-07-05 | UAL852 | TPE → SFO | Jul 5, 06:51 UTC | Jul 5, 17:55 UTC | 11h 4m |
| 2026-07-05 | UAL852 | - | Jul 5, 06:40 UTC | Jul 5, 06:55 UTC | 15m |
| 2026-07-04 | UAL853 | - | Jul 4, 19:50 UTC | Jul 4, 20:00 UTC | 10m |
| 2026-07-04 | UAL853 | - | Jul 4, 07:35 UTC | Jul 4, 19:05 UTC | 11h 30m |
| 2026-07-03 | UAL927 | FRA → SFO | Jul 3, 15:51 UTC | Jul 4, 02:38 UTC | 10h 47m |
| 2026-07-03 | UAL927 | - | Jul 3, 15:50 UTC | Jul 3, 21:20 UTC | 5h 30m |
| 2026-07-03 | UAL926 | SFO → FRA | Jul 3, 03:05 UTC | Jul 3, 13:00 UTC | 9h 55m |
| 2026-07-02 | UAL45 | ZRH → SFO | Jul 2, 12:27 UTC | Jul 2, 23:20 UTC | 10h 53m |
| 2026-07-02 | UAL45 | - | Jul 2, 12:15 UTC | Jul 2, 23:30 UTC | 11h 15m |
| 2026-07-01 | UAL44 | SFO → ZRH | Jul 1, 22:15 UTC | Jul 2, 08:40 UTC | 10h 25m |
| 2026-07-01 | UAL852 | - | Jul 1, 07:00 UTC | Jul 1, 07:20 UTC | 20m |
| 2026-07-01 | UAL852 | TPE → SFO | Jul 1, 06:51 UTC | Jul 1, 18:01 UTC | 11h 10m |
| 2026-06-30 | UAL853 | SFO → TPE | Jun 30, 07:43 UTC | Jun 30, 20:05 UTC | 12h 22m |
| 2026-06-30 | UAL853 | - | Jun 30, 07:45 UTC | Jun 30, 20:00 UTC | 12h 15m |
| 2026-06-29 | UAL927 | - | Jun 29, 16:10 UTC | Jun 30, 02:40 UTC | 10h 30m |
| 2026-06-29 | UAL926 | SFO → FRA | Jun 29, 02:44 UTC | Jun 29, 13:02 UTC | 10h 18m |
| 2026-06-29 | UAL926 | - | Jun 29, 02:45 UTC | Jun 29, 05:34 UTC | 2h 50m |
| 2026-06-28 | UAL45 | ZRH → SFO | Jun 28, 12:02 UTC | Jun 28, 23:45 UTC | 11h 43m |
| 2026-06-28 | UAL45 | ZRH → SFO | Jun 28, 13:00 UTC | Jun 28, 13:59 UTC | 1h 0m |
| 2026-06-27 | UAL44 | SFO → ZRH | Jun 27, 21:50 UTC | Jun 28, 08:29 UTC | 10h 40m |
| 2026-06-27 | UAL876 | HND → SFO | Jun 27, 07:15 UTC | Jun 27, 16:31 UTC | 9h 16m |
| 2026-06-27 | UAL876 | HND → SFO | Jun 27, 07:15 UTC | Jun 27, 16:42 UTC | 9h 27m |
| 2026-06-27 | UAL876 | - | Jun 27, 07:10 UTC | Jun 27, 07:49 UTC | 40m |
| 2026-06-26 | UAL131 | - | Jun 26, 15:05 UTC | Jun 27, 04:59 UTC | 13h 55m |
| 2026-06-26 | UAL148 | - | Jun 26, 00:24 UTC | Jun 26, 03:05 UTC | 2h 40m |
| 2026-06-26 | UAL148 | GRU → EWR | Jun 26, 00:21 UTC | Jun 26, 09:53 UTC | 9h 32m |
| 2026-06-25 | UAL149 | EWR → GRU | Jun 25, 01:11 UTC | Jun 25, 09:37 UTC | 8h 26m |
| 2026-06-25 | UAL149 | - | Jun 25, 00:59 UTC | Jun 25, 09:50 UTC | 8h 50m |
| 2026-06-24 | UAL130 | HND → EWR | Jun 24, 09:19 UTC | Jun 24, 21:40 UTC | 12h 20m |
| 2026-06-23 | UAL803 | IAD → HND | Jun 23, 17:20 UTC | Jun 24, 06:25 UTC | 13h 5m |
| 2026-06-23 | UAL803 | IAD → HND | Jun 23, 17:20 UTC | Jun 24, 06:25 UTC | 13h 5m |
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 N77022 page for operator, model, and routing details .