sensors Mode-S transponder
A2A3D2
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N26970 · BOEING 787-9 Dreamliner · operated by UNITED AIRLINES INC
- Hex
- A2A3D2
- Octal
- 50521722
- Decimal
- 10,658,770
- Country
- US
- Tail
- N26970
- Type
- B789
- Flights observed
- 199
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 30m ago
Current position
Country allocation
The ICAO 24-bit address A2A3D2 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 |
|---|---|---|---|
| UAL820 | - | 21 | 2026-07-13 |
| UAL821 | - | 20 | 2026-07-13 |
| UAL198 | - | 15 | 2026-07-02 |
| UAL199 | United Airlines | 12 | 2026-07-03 |
| UAL153 | United Airlines | 10 | 2026-06-28 |
| UAL761 | United Airlines | 8 | 2026-04-16 |
| UAL760 | United Airlines | 7 | 2026-04-16 |
| UAL2096 | United Airlines | 7 | 2026-07-07 |
| UAL152 | United Airlines | 7 | 2026-06-27 |
| UAL842 | - | 6 | 2026-06-25 |
| UAL188 | United Airlines | 5 | 2026-05-02 |
| UAL187 | United Airlines | 5 | 2026-05-02 |
| UAL177 | - | 5 | 2026-04-13 |
| UAL143 | United Airlines | 5 | 2026-04-18 |
| UAL839 | - | 4 | 2026-06-19 |
| UAL771 | - | 4 | 2026-07-10 |
| UAL353 | - | 4 | 2026-07-07 |
| UAL263 | United Airlines | 4 | 2026-04-14 |
| UAL78 | United Airlines | 3 | 2026-04-21 |
| UAL772 | - | 3 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAL821 | - | Jul 13, 14:05 UTC | Jul 14, 02:30 UTC | 12h 25m |
| 2026-07-13 | UAL821 | - | Jul 13, 11:15 UTC | Jul 13, 11:20 UTC | 5m |
| 2026-07-13 | UAL821 | - | Jul 13, 09:10 UTC | Jul 13, 09:20 UTC | 10m |
| 2026-07-13 | UAL821 | BKK → HKG | Jul 13, 09:05 UTC | Jul 13, 11:20 UTC | 2h 15m |
| 2026-07-13 | UAL820 | - | Jul 13, 02:15 UTC | Jul 13, 02:35 UTC | 20m |
| 2026-07-13 | UAL820 | - | Jul 13, 00:25 UTC | Jul 13, 00:35 UTC | 10m |
| 2026-07-12 | UAL820 | - | Jul 12, 21:50 UTC | Jul 12, 22:15 UTC | 25m |
| 2026-07-12 | UAL820 | - | Jul 12, 08:15 UTC | Jul 12, 21:15 UTC | 13h 0m |
| 2026-07-11 | UAL772 | - | Jul 11, 05:10 UTC | Jul 11, 16:00 UTC | 10h 50m |
| 2026-07-10 | UAL771 | - | Jul 10, 07:20 UTC | Jul 10, 19:25 UTC | 12h 5m |
| 2026-07-10 | UAL771 | LAX → PEK | Jul 10, 07:08 UTC | Jul 10, 20:32 UTC | 13h 24m |
| 2026-07-09 | UAL821 | HKG → LAX | Jul 9, 14:06 UTC | Jul 10, 03:02 UTC | 12h 56m |
| 2026-07-09 | UAL821 | HKG → LAX | Jul 9, 14:00 UTC | Jul 10, 03:05 UTC | 13h 5m |
| 2026-07-09 | UAL821 | - | Jul 9, 11:05 UTC | Jul 9, 11:25 UTC | 20m |
| 2026-07-09 | UAL821 | - | Jul 9, 09:00 UTC | Jul 9, 09:30 UTC | 30m |
| 2026-07-09 | UAL820 | HKG → BKK | Jul 9, 00:01 UTC | Jul 9, 02:08 UTC | 2h 7m |
| 2026-07-08 | UAL820 | HKG → BKK | Jul 8, 23:55 UTC | Jul 9, 02:10 UTC | 2h 15m |
| 2026-07-08 | UAL820 | - | Jul 8, 07:20 UTC | Jul 8, 21:15 UTC | 13h 55m |
| 2026-07-08 | UAL820 | LAX → HKG | Jul 8, 07:20 UTC | Jul 8, 21:09 UTC | 13h 49m |
| 2026-07-07 | UAL353 | - | Jul 7, 23:10 UTC | Jul 8, 04:00 UTC | 4h 50m |
| 2026-07-07 | UAL2096 | LAX → EWR | Jul 7, 15:50 UTC | Jul 7, 20:30 UTC | 4h 40m |
| 2026-07-06 | UAL353T | EWR → LAX | Jul 6, 23:19 UTC | Jul 7, 04:19 UTC | 5h 0m |
| 2026-07-06 | UAL353T | - | Jul 6, 23:25 UTC | Jul 7, 04:25 UTC | 5h 0m |
| 2026-07-06 | UAL2096 | LAX → EWR | Jul 6, 15:55 UTC | Jul 6, 20:50 UTC | 4h 55m |
| 2026-07-05 | UAL821 | - | Jul 5, 15:00 UTC | Jul 6, 02:55 UTC | 11h 55m |
| 2026-07-05 | UAL821 | - | Jul 5, 14:15 UTC | Jul 5, 14:30 UTC | 15m |
| 2026-07-05 | UAL821 | - | Jul 5, 11:15 UTC | Jul 5, 11:35 UTC | 20m |
| 2026-07-05 | UAL821 | - | Jul 5, 09:00 UTC | Jul 5, 09:40 UTC | 40m |
| 2026-07-05 | UAL820 | - | Jul 5, 01:25 UTC | Jul 5, 02:10 UTC | 45m |
| 2026-07-05 | UAL820 | HKG → BKK | Jul 5, 00:01 UTC | Jul 5, 02:07 UTC | 2h 6m |
| 2026-07-04 | UAL820 | - | Jul 4, 23:55 UTC | Jul 5, 00:10 UTC | 15m |
| 2026-07-04 | UAL820 | - | Jul 4, 07:15 UTC | Jul 4, 21:20 UTC | 14h 5m |
| 2026-07-04 | UAL820 | LAX → HKG | Jul 4, 07:14 UTC | Jul 4, 21:12 UTC | 13h 58m |
| 2026-07-03 | UAL199 | PVG → LAX | Jul 3, 15:40 UTC | Jul 3, 17:15 UTC | 1h 35m |
| 2026-07-03 | UAL199 | PVG → LAX | Jul 3, 07:00 UTC | Jul 4, 02:30 UTC | 19h 30m |
| 2026-07-02 | UAL198 | - | Jul 2, 20:55 UTC | Jul 2, 21:55 UTC | 1h 0m |
| 2026-07-02 | UAL198 | LAX → PVG | Jul 2, 20:46 UTC | Jul 3, 09:53 UTC | 13h 7m |
| 2026-07-02 | UAL772 | - | Jul 2, 05:25 UTC | Jul 2, 06:30 UTC | 1h 5m |
| 2026-07-02 | UAL772 | PEK → LAX | Jul 2, 04:34 UTC | Jul 2, 15:40 UTC | 11h 6m |
| 2026-07-01 | UAL771 | - | Jul 1, 06:55 UTC | Jul 1, 18:30 UTC | 11h 35m |
| 2026-07-01 | UAL771 | LAX → PEK | Jul 1, 06:54 UTC | Jul 1, 20:29 UTC | 13h 35m |
| 2026-06-30 | UAL199 | PVG → LAX | Jun 30, 13:20 UTC | Jun 30, 15:05 UTC | 1h 45m |
| 2026-06-30 | UAL199 | PVG → LAX | Jun 30, 12:31 UTC | Jun 30, 23:53 UTC | 11h 22m |
| 2026-06-30 | UAL199 | PVG → LAX | Jun 30, 07:00 UTC | Jul 1, 00:00 UTC | 17h 0m |
| 2026-06-29 | UAL198 | LAX → PVG | Jun 29, 20:31 UTC | Jun 30, 09:48 UTC | 13h 17m |
| 2026-06-29 | UAL198 | - | Jun 29, 20:35 UTC | Jun 30, 15:05 UTC | 18h 31m |
| 2026-06-28 | UAL153 | HKG → LAX | Jun 28, 06:00 UTC | Jun 28, 18:19 UTC | 12h 20m |
| 2026-06-28 | UAL153 | HKG → LAX | Jun 28, 00:19 UTC | Jun 28, 02:28 UTC | 2h 9m |
| 2026-06-27 | UAL152 | LAX → HKG | Jun 27, 12:50 UTC | Jun 27, 13:04 UTC | 15m |
| 2026-06-26 | UAL152 | LAX → HKG | Jun 26, 20:24 UTC | Jun 27, 10:40 UTC | 14h 15m |
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 N26970 page for operator, model, and routing details .