sensors Mode-S transponder
A2A41E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N26996 · BOEING 787-9 Dreamliner · operated by BOEING CO
- Hex
- A2A41E
- Octal
- 50522036
- Decimal
- 10,658,846
- Country
- US
- Tail
- N26996
- Type
- B789
- Flights observed
- 219
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 16m ago
Last known position
Country allocation
The ICAO 24-bit address A2A41E 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 | - | 19 | 2026-07-10 |
| UAL820 | - | 14 | 2026-07-10 |
| UAL152 | - | 9 | 2026-07-13 |
| UAL892 | United Airlines | 8 | 2026-06-11 |
| UAL63 | - | 8 | 2026-06-27 |
| UAL6 | - | 8 | 2026-06-25 |
| UAL153 | United Airlines | 8 | 2026-07-07 |
| UAL62 | - | 7 | 2026-06-26 |
| UAL29 | - | 7 | 2026-06-21 |
| UAL28 | - | 7 | 2026-06-22 |
| UAL761 | United Airlines | 6 | 2026-04-14 |
| UAL143D | United Airlines | 6 | 2026-04-16 |
| UAL99 | - | 5 | 2026-07-11 |
| UAL83 | United Airlines | 5 | 2026-05-28 |
| UAL82 | United Airlines | 5 | 2026-05-28 |
| UAL1227 | United Airlines | 5 | 2026-05-24 |
| UAL98 | - | 4 | 2026-07-11 |
| UAL893 | United Airlines | 4 | 2026-06-10 |
| UAL870 | - | 4 | 2026-06-16 |
| UAL61 | - | 4 | 2026-06-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAL152 | - | Jul 13, 20:15 UTC | Jul 14, 07:20 UTC | 11h 5m |
| 2026-07-13 | UAL33 | - | Jul 13, 08:10 UTC | Jul 13, 17:50 UTC | 9h 40m |
| 2026-07-12 | UAL32 | - | Jul 12, 18:35 UTC | Jul 13, 05:10 UTC | 10h 35m |
| 2026-07-11 | UAL99 | - | Jul 11, 23:50 UTC | Jul 12, 13:35 UTC | 13h 45m |
| 2026-07-11 | UAL98 | - | Jul 11, 06:35 UTC | Jul 11, 21:40 UTC | 15h 5m |
| 2026-07-10 | UAL821 | - | Jul 10, 14:20 UTC | Jul 10, 14:40 UTC | 20m |
| 2026-07-10 | UAL821 | HKG → LAX | Jul 10, 14:13 UTC | Jul 11, 03:25 UTC | 13h 12m |
| 2026-07-10 | UAL821 | - | Jul 10, 11:30 UTC | Jul 10, 11:50 UTC | 20m |
| 2026-07-10 | UAL821 | - | Jul 10, 09:30 UTC | Jul 10, 10:00 UTC | 30m |
| 2026-07-10 | UAL820 | - | Jul 10, 00:10 UTC | Jul 10, 02:25 UTC | 2h 15m |
| 2026-07-09 | UAL820 | - | Jul 9, 07:30 UTC | Jul 9, 18:50 UTC | 11h 20m |
| 2026-07-09 | UAL820 | LAX → HKG | Jul 9, 07:14 UTC | Jul 9, 21:18 UTC | 14h 4m |
| 2026-07-08 | UAL935 | - | Jul 8, 12:20 UTC | Jul 8, 22:30 UTC | 10h 10m |
| 2026-07-07 | UAL923 | - | Jul 7, 22:40 UTC | Jul 8, 09:05 UTC | 10h 25m |
| 2026-07-07 | UAL153 | HKG → LAX | Jul 7, 05:30 UTC | Jul 7, 18:30 UTC | 13h 0m |
| 2026-07-07 | UAL153 | HKG → LAX | Jul 7, 02:10 UTC | Jul 7, 02:30 UTC | 20m |
| 2026-07-06 | UAL152 | LAX → HKG | Jul 6, 13:00 UTC | Jul 6, 13:15 UTC | 15m |
| 2026-07-06 | UAL152 | LAX → HKG | Jul 6, 10:15 UTC | Jul 6, 10:30 UTC | 15m |
| 2026-07-05 | UAL152 | LAX → HKG | Jul 5, 20:10 UTC | Jul 6, 09:40 UTC | 13h 30m |
| 2026-07-04 | UAL99 | MEL → LAX | Jul 4, 23:50 UTC | Jul 5, 13:35 UTC | 13h 45m |
| 2026-07-04 | UAL98 | LAX → MEL | Jul 4, 06:10 UTC | Jul 4, 21:40 UTC | 15h 30m |
| 2026-07-03 | UAL821 | - | Jul 3, 15:10 UTC | Jul 4, 03:05 UTC | 11h 55m |
| 2026-07-03 | UAL821 | - | Jul 3, 14:25 UTC | Jul 3, 14:40 UTC | 15m |
| 2026-07-03 | UAL821 | - | Jul 3, 09:15 UTC | Jul 3, 09:30 UTC | 15m |
| 2026-07-03 | UAL821 | BKK → HKG | Jul 3, 09:05 UTC | Jul 3, 11:25 UTC | 2h 20m |
| 2026-07-03 | UAL820 | - | Jul 3, 01:10 UTC | Jul 3, 02:35 UTC | 1h 25m |
| 2026-07-03 | UAL820 | HKG → BKK | Jul 3, 00:01 UTC | Jul 3, 02:29 UTC | 2h 28m |
| 2026-07-03 | UAL820 | - | Jul 3, 00:05 UTC | Jul 3, 00:20 UTC | 15m |
| 2026-07-02 | UAL820 | - | Jul 2, 07:45 UTC | Jul 2, 21:35 UTC | 13h 50m |
| 2026-07-02 | UAL353 | - | Jul 2, 00:05 UTC | Jul 2, 05:00 UTC | 4h 55m |
| 2026-06-30 | UAL1855 | - | Jun 30, 21:20 UTC | Jul 1, 01:45 UTC | 4h 25m |
| 2026-06-30 | UAL153 | HKG → LAX | Jun 30, 05:08 UTC | Jun 30, 17:23 UTC | 12h 15m |
| 2026-06-30 | UAL153 | HKG → LAX | Jun 30, 04:50 UTC | Jun 30, 17:25 UTC | 12h 35m |
| 2026-06-30 | UAL153 | HKG → LAX | Jun 30, 02:30 UTC | Jun 30, 02:35 UTC | 5m |
| 2026-06-29 | UAL152 | LAX → HKG | Jun 29, 12:39 UTC | Jun 29, 12:49 UTC | 10m |
| 2026-06-28 | UAL152 | LAX → HKG | Jun 28, 20:14 UTC | Jun 29, 09:29 UTC | 13h 15m |
| 2026-06-28 | UAL152 | LAX → HKG | Jun 28, 20:08 UTC | Jun 29, 10:23 UTC | 14h 15m |
| 2026-06-28 | UAL33 | - | Jun 28, 08:00 UTC | Jun 28, 17:10 UTC | 9h 10m |
| 2026-06-27 | UAL7 | - | Jun 27, 15:49 UTC | Jun 28, 04:29 UTC | 12h 40m |
| 2026-06-27 | UAL63 | - | Jun 27, 01:24 UTC | Jun 27, 11:00 UTC | 9h 35m |
| 2026-06-26 | UAL62 | - | Jun 26, 00:10 UTC | Jun 26, 08:54 UTC | 8h 45m |
| 2026-06-25 | UAL6 | - | Jun 25, 09:29 UTC | Jun 25, 20:30 UTC | 11h 0m |
| 2026-06-24 | UAL143 | DEN → NRT | Jun 24, 19:59 UTC | Jun 25, 07:09 UTC | 11h 10m |
| 2026-06-24 | UAL3903 | OGG → SFO | Jun 24, 15:24 UTC | Jun 24, 17:20 UTC | 1h 55m |
| 2026-06-24 | UAL806 | - | Jun 24, 02:45 UTC | Jun 24, 12:20 UTC | 9h 35m |
| 2026-06-23 | UAL805 | SFO → ICN | Jun 23, 07:35 UTC | Jun 23, 19:10 UTC | 11h 35m |
| 2026-06-22 | UAL28 | SIN → SFO | Jun 22, 13:21 UTC | Jun 23, 03:59 UTC | 14h 38m |
| 2026-06-21 | UAL29 | SFO → SIN | Jun 21, 18:35 UTC | Jun 22, 10:37 UTC | 16h 2m |
| 2026-06-21 | UAL29 | - | Jun 21, 18:35 UTC | Jun 22, 07:30 UTC | 12h 55m |
| 2026-06-21 | UAL61 | - | Jun 21, 01:14 UTC | Jun 21, 14:59 UTC | 13h 45m |
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 N26996 page for operator, model, and routing details .