sensors Mode-S transponder
A2A3AF
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N26960 · BOEING 787-9 Dreamliner · operated by UNITED AIRLINES INC
- Hex
- A2A3AF
- Octal
- 50521657
- Decimal
- 10,658,735
- Country
- US
- Tail
- N26960
- Type
- B789
- Flights observed
- 180
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A2A3AF 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 | United Airlines | 12 | 2026-05-11 |
| UAL820 | United Airlines | 11 | 2026-05-10 |
| UAL152 | United Airlines | 8 | 2026-07-05 |
| UAL870 | - | 7 | 2026-07-09 |
| UAL82 | - | 7 | 2026-04-13 |
| UAL892 | - | 6 | 2026-06-28 |
| UAL153 | United Airlines | 6 | 2026-07-06 |
| UAL114 | - | 6 | 2026-07-10 |
| UAL893 | - | 5 | 2026-06-27 |
| UAL863 | - | 5 | 2026-07-13 |
| UAL805 | - | 5 | 2026-06-22 |
| UAL29 | - | 5 | 2026-07-11 |
| UAL28 | - | 5 | 2026-07-12 |
| UAL115 | - | 5 | 2026-07-09 |
| UAL98 | United Airlines | 4 | 2026-05-12 |
| UAL83 | United Airlines | 4 | 2026-04-14 |
| UAL806 | - | 4 | 2026-06-23 |
| UAL2692 | United Airlines | 4 | 2026-04-16 |
| UAL1849 | - | 4 | 2026-07-12 |
| UAL935 | - | 3 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAL842 | SYD → LAX | Jul 14, 00:00 UTC | Jul 14, 13:20 UTC | 13h 20m |
| 2026-07-13 | UAL863 | SFO → SYD | Jul 13, 06:45 UTC | Jul 13, 20:39 UTC | 13h 54m |
| 2026-07-13 | UAL863 | SFO → SYD | Jul 13, 06:45 UTC | Jul 13, 20:45 UTC | 14h 0m |
| 2026-07-12 | UAL1757 | - | Jul 12, 22:25 UTC | Jul 13, 03:05 UTC | 4h 40m |
| 2026-07-12 | UAL1849 | SFO → IAD | Jul 12, 15:34 UTC | Jul 12, 19:55 UTC | 4h 21m |
| 2026-07-12 | UAL1849 | SFO → IAD | Jul 12, 15:25 UTC | Jul 12, 20:01 UTC | 4h 35m |
| 2026-07-12 | UAL28 | - | Jul 12, 04:25 UTC | Jul 12, 05:10 UTC | 45m |
| 2026-07-11 | UAL29 | - | Jul 11, 10:15 UTC | Jul 11, 10:25 UTC | 10m |
| 2026-07-10 | UAL29 | - | Jul 10, 18:40 UTC | Jul 11, 06:35 UTC | 11h 55m |
| 2026-07-10 | UAL114 | PPT → SFO | Jul 10, 07:53 UTC | Jul 10, 14:54 UTC | 7h 1m |
| 2026-07-10 | UAL114 | - | Jul 10, 07:30 UTC | Jul 10, 14:55 UTC | 7h 25m |
| 2026-07-09 | UAL115 | SFO → PPT | Jul 9, 22:00 UTC | Jul 10, 05:40 UTC | 7h 40m |
| 2026-07-09 | UAL870 | SYD → SFO | Jul 9, 00:45 UTC | Jul 9, 14:01 UTC | 13h 16m |
| 2026-07-09 | UAL870 | - | Jul 9, 00:55 UTC | Jul 9, 13:50 UTC | 12h 55m |
| 2026-07-08 | UAL863 | SFO → SYD | Jul 8, 06:49 UTC | Jul 8, 20:51 UTC | 14h 2m |
| 2026-07-08 | UAL863 | - | Jul 8, 06:45 UTC | Jul 8, 07:15 UTC | 30m |
| 2026-07-07 | UAL949 | - | Jul 7, 12:15 UTC | Jul 7, 22:40 UTC | 10h 25m |
| 2026-07-06 | UAL923 | - | Jul 6, 22:50 UTC | Jul 7, 09:05 UTC | 10h 15m |
| 2026-07-06 | UAL153 | HKG → LAX | Jul 6, 05:08 UTC | Jul 6, 17:44 UTC | 12h 36m |
| 2026-07-06 | UAL153 | HKG → LAX | Jul 6, 04:55 UTC | Jul 6, 17:50 UTC | 12h 55m |
| 2026-07-06 | UAL153 | HKG → LAX | Jul 6, 00:19 UTC | Jul 6, 02:24 UTC | 2h 5m |
| 2026-07-05 | UAL152 | LAX → HKG | Jul 5, 12:55 UTC | Jul 5, 13:10 UTC | 15m |
| 2026-07-04 | UAL152 | LAX → HKG | Jul 4, 20:18 UTC | Jul 5, 10:23 UTC | 14h 5m |
| 2026-07-04 | UAL152 | LAX → HKG | Jul 4, 20:30 UTC | Jul 5, 10:05 UTC | 13h 35m |
| 2026-07-04 | UAL33 | - | Jul 4, 08:10 UTC | Jul 4, 17:40 UTC | 9h 30m |
| 2026-07-04 | UAL33 | NRT → LAX | Jul 4, 08:05 UTC | Jul 4, 17:33 UTC | 9h 28m |
| 2026-07-03 | UAL7 | - | Jul 3, 15:50 UTC | Jul 4, 04:50 UTC | 13h 0m |
| 2026-07-03 | UAL63 | - | Jul 3, 01:20 UTC | Jul 3, 10:50 UTC | 9h 30m |
| 2026-07-02 | UAL62 | - | Jul 2, 01:15 UTC | Jul 2, 10:10 UTC | 8h 55m |
| 2026-07-02 | UAL62 | IAH → GRU | Jul 2, 01:13 UTC | Jul 2, 10:07 UTC | 8h 54m |
| 2026-07-01 | UAL6 | - | Jul 1, 08:15 UTC | Jul 1, 19:35 UTC | 11h 20m |
| 2026-06-30 | UAL32 | - | Jun 30, 18:25 UTC | Jul 1, 05:15 UTC | 10h 50m |
| 2026-06-29 | UAL935 | - | Jun 29, 12:20 UTC | Jun 29, 22:30 UTC | 10h 10m |
| 2026-06-29 | UAL948 | SFO → LHR | Jun 29, 00:14 UTC | Jun 29, 09:46 UTC | 9h 32m |
| 2026-06-29 | UAL948 | SFO → LHR | Jun 29, 00:14 UTC | Jun 29, 09:50 UTC | 9h 35m |
| 2026-06-28 | UAL892 | ICN → SFO | Jun 28, 08:21 UTC | Jun 28, 18:00 UTC | 9h 39m |
| 2026-06-28 | UAL892 | ICN → SFO | Jun 28, 08:14 UTC | Jun 28, 18:05 UTC | 9h 50m |
| 2026-06-27 | UAL893 | - | Jun 27, 18:20 UTC | Jun 28, 05:45 UTC | 11h 25m |
| 2026-06-27 | UAL893 | SFO → ICN | Jun 27, 18:10 UTC | Jun 28, 06:03 UTC | 11h 53m |
| 2026-06-26 | UAL28 | - | Jun 26, 14:35 UTC | Jun 27, 04:39 UTC | 14h 5m |
| 2026-06-26 | UAL28 | SIN → SFO | Jun 26, 13:06 UTC | Jun 27, 04:33 UTC | 15h 27m |
| 2026-06-26 | UAL29 | - | Jun 26, 10:05 UTC | Jun 26, 10:15 UTC | 10m |
| 2026-06-25 | UAL29 | - | Jun 25, 19:05 UTC | Jun 26, 08:54 UTC | 13h 50m |
| 2026-06-24 | UAL28 | - | Jun 24, 14:55 UTC | Jun 25, 04:25 UTC | 13h 30m |
| 2026-06-24 | UAL28 | - | Jun 24, 13:40 UTC | Jun 24, 13:50 UTC | 10m |
| 2026-06-23 | UAL29 | - | Jun 23, 18:39 UTC | Jun 24, 09:00 UTC | 14h 20m |
| 2026-06-23 | UAL806 | - | Jun 23, 02:55 UTC | Jun 23, 13:09 UTC | 10h 15m |
| 2026-06-22 | UAL805 | SFO → ICN | Jun 22, 07:32 UTC | Jun 22, 19:01 UTC | 11h 29m |
| 2026-06-22 | UAL805 | SFO → ICN | Jun 22, 07:45 UTC | Jun 22, 19:05 UTC | 11h 20m |
| 2026-06-21 | UAL1757 | - | Jun 21, 22:54 UTC | Jun 22, 04:00 UTC | 5h 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 N26960 page for operator, model, and routing details .