sensors Mode-S transponder
A2061E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N22992 · BOEING 787-9 Dreamliner · operated by UNITED AIRLINES INC
- Hex
- A2061E
- Octal
- 50403036
- Decimal
- 10,618,398
- Country
- US
- Tail
- N22992
- Type
- B789
- Flights observed
- 196
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A2061E 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 |
|---|---|---|---|
| UAL821 | - | 14 | 2026-07-07 |
| UAL820 | - | 13 | 2026-07-07 |
| UAL806 | United Airlines | 10 | 2026-05-14 |
| UAL842 | - | 8 | 2026-07-09 |
| UAL805 | United Airlines | 7 | 2026-05-13 |
| UAL28 | United Airlines | 7 | 2026-04-18 |
| UAL863 | - | 6 | 2026-07-02 |
| UAL29 | United Airlines | 6 | 2026-04-17 |
| UAL839 | - | 5 | 2026-07-08 |
| UAL7 | - | 5 | 2026-07-12 |
| UAL2222 | - | 5 | 2026-06-18 |
| UAL2096 | United Airlines | 5 | 2026-07-03 |
| UAL188 | United Airlines | 5 | 2026-07-04 |
| UAL63 | - | 4 | 2026-07-12 |
| UAL6 | - | 4 | 2026-07-10 |
| UAL2 | United Airlines | 4 | 2026-04-23 |
| UAL187 | - | 4 | 2026-07-04 |
| UAL182 | - | 4 | 2026-07-13 |
| UAL142 | - | 4 | 2026-07-13 |
| UAL1122 | - | 4 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAL182 | DEN → FRA | Jul 13, 22:10 UTC | Jul 14, 07:15 UTC | 9h 5m |
| 2026-07-13 | UAL142 | - | Jul 13, 08:05 UTC | Jul 13, 18:15 UTC | 10h 10m |
| 2026-07-12 | UAL7 | IAH → NRT | Jul 12, 16:02 UTC | Jul 13, 04:20 UTC | 12h 18m |
| 2026-07-12 | UAL7 | - | Jul 12, 15:50 UTC | Jul 13, 04:20 UTC | 12h 30m |
| 2026-07-12 | UAL63 | - | Jul 12, 01:05 UTC | Jul 12, 10:35 UTC | 9h 30m |
| 2026-07-10 | UAL62 | - | Jul 10, 23:55 UTC | Jul 11, 09:05 UTC | 9h 10m |
| 2026-07-10 | UAL6 | - | Jul 10, 08:20 UTC | Jul 10, 20:20 UTC | 12h 0m |
| 2026-07-09 | UAL32 | - | Jul 9, 18:25 UTC | Jul 10, 05:00 UTC | 10h 35m |
| 2026-07-09 | UAL842 | - | Jul 9, 00:05 UTC | Jul 9, 13:15 UTC | 13h 10m |
| 2026-07-08 | UAL839 | - | Jul 8, 06:45 UTC | Jul 8, 21:10 UTC | 14h 25m |
| 2026-07-07 | UAL821 | - | Jul 7, 14:40 UTC | Jul 8, 03:00 UTC | 12h 20m |
| 2026-07-07 | UAL821 | - | Jul 7, 12:00 UTC | Jul 7, 12:15 UTC | 15m |
| 2026-07-07 | UAL821 | - | Jul 7, 09:50 UTC | Jul 7, 11:15 UTC | 1h 25m |
| 2026-07-07 | UAL820 | - | Jul 7, 01:50 UTC | Jul 7, 02:30 UTC | 40m |
| 2026-07-07 | UAL820 | - | Jul 7, 00:15 UTC | Jul 7, 00:25 UTC | 10m |
| 2026-07-06 | UAL820 | - | Jul 6, 07:15 UTC | Jul 6, 21:25 UTC | 14h 10m |
| 2026-07-05 | UAL353 | - | Jul 5, 23:35 UTC | Jul 6, 04:45 UTC | 5h 10m |
| 2026-07-04 | UAL187 | - | Jul 4, 20:10 UTC | Jul 5, 11:25 UTC | 15h 15m |
| 2026-07-04 | UAL188 | EWR → JNB | Jul 4, 03:55 UTC | Jul 4, 17:35 UTC | 13h 40m |
| 2026-07-03 | UAL2096 | LAX → EWR | Jul 3, 16:55 UTC | Jul 3, 22:15 UTC | 5h 20m |
| 2026-07-03 | UAL842 | - | Jul 3, 00:00 UTC | Jul 3, 13:15 UTC | 13h 15m |
| 2026-07-02 | UAL842 | SYD → LAX | Jul 2, 23:51 UTC | Jul 3, 13:11 UTC | 13h 20m |
| 2026-07-02 | UAL863 | SFO → SYD | Jul 2, 06:31 UTC | Jul 2, 20:34 UTC | 14h 3m |
| 2026-07-02 | UAL863 | - | Jul 2, 06:25 UTC | Jul 2, 06:55 UTC | 30m |
| 2026-07-01 | UAL969 | - | Jul 1, 13:45 UTC | Jul 1, 23:55 UTC | 10h 10m |
| 2026-06-30 | UAL968 | - | Jun 30, 22:30 UTC | Jul 1, 08:05 UTC | 9h 35m |
| 2026-06-30 | UAL892 | ICN → SFO | Jun 30, 08:00 UTC | Jun 30, 18:05 UTC | 10h 5m |
| 2026-06-29 | UAL893 | SFO → ICN | Jun 29, 18:10 UTC | Jun 30, 05:51 UTC | 11h 41m |
| 2026-06-29 | UAL893 | SFO → ICN | Jun 29, 18:14 UTC | Jun 30, 05:55 UTC | 11h 40m |
| 2026-06-29 | UAL870 | - | Jun 29, 00:39 UTC | Jun 29, 13:34 UTC | 12h 55m |
| 2026-06-28 | UAL863 | SFO → SYD | Jun 28, 06:30 UTC | Jun 28, 20:54 UTC | 14h 25m |
| 2026-06-27 | UAL949 | - | Jun 27, 13:04 UTC | Jun 27, 23:14 UTC | 10h 10m |
| 2026-06-27 | UAL948 | SFO → LHR | Jun 27, 00:54 UTC | Jun 27, 10:40 UTC | 9h 46m |
| 2026-06-27 | UAL948 | SFO → LHR | Jun 27, 00:50 UTC | Jun 27, 10:45 UTC | 9h 55m |
| 2026-06-26 | UAL949 | - | Jun 26, 12:24 UTC | Jun 26, 22:40 UTC | 10h 15m |
| 2026-06-26 | UAL948 | SFO → LHR | Jun 26, 00:24 UTC | Jun 26, 10:15 UTC | 9h 50m |
| 2026-06-25 | UAL3908 | DEN → SFO | Jun 25, 19:49 UTC | Jun 25, 21:59 UTC | 2h 10m |
| 2026-06-25 | UAL142 | NRT → DEN | Jun 25, 07:45 UTC | Jun 25, 17:14 UTC | 9h 30m |
| 2026-06-24 | UAL32 | - | Jun 24, 18:09 UTC | Jun 25, 05:00 UTC | 10h 50m |
| 2026-06-23 | UAL353 | EWR → LAX | Jun 23, 23:50 UTC | Jun 24, 04:50 UTC | 5h 0m |
| 2026-06-23 | UAL8111 | LAX → EWR | Jun 23, 16:09 UTC | Jun 23, 20:40 UTC | 4h 30m |
| 2026-06-23 | UAL842 | - | Jun 23, 00:00 UTC | Jun 23, 00:30 UTC | 30m |
| 2026-06-22 | UAL842 | SYD → LAX | Jun 22, 23:56 UTC | Jun 23, 12:44 UTC | 12h 48m |
| 2026-06-22 | UAL839 | - | Jun 22, 06:29 UTC | Jun 22, 20:55 UTC | 14h 25m |
| 2026-06-22 | UAL839 | LAX → SYD | Jun 22, 06:09 UTC | Jun 22, 20:51 UTC | 14h 42m |
| 2026-06-21 | UAL821 | - | Jun 21, 14:15 UTC | Jun 22, 03:24 UTC | 13h 10m |
| 2026-06-21 | UAL821 | - | Jun 21, 11:05 UTC | Jun 21, 11:24 UTC | 20m |
| 2026-06-21 | UAL821 | - | Jun 21, 08:54 UTC | Jun 21, 10:14 UTC | 1h 20m |
| 2026-06-21 | UAL820 | HKG → BKK | Jun 21, 00:04 UTC | Jun 21, 02:15 UTC | 2h 10m |
| 2026-06-20 | UAL820 | - | Jun 20, 07:29 UTC | Jun 20, 21:25 UTC | 13h 55m |
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 N22992 page for operator, model, and routing details .