sensors Mode-S transponder
A31A34
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N29968 · BOEING 787-9 Dreamliner · operated by UNITED AIRLINES INC
- Hex
- A31A34
- Octal
- 50615064
- Decimal
- 10,689,076
- Country
- US
- Tail
- N29968
- Type
- B789
- Flights observed
- 204
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A31A34 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 |
|---|---|---|---|
| UAL61 | - | 12 | 2026-07-10 |
| UAL60 | - | 9 | 2026-07-09 |
| UAL29 | - | 8 | 2026-07-12 |
| UAL893 | - | 6 | 2026-07-06 |
| UAL892 | - | 5 | 2026-07-07 |
| UAL839 | - | 5 | 2026-06-18 |
| UAL806 | United Airlines | 5 | 2026-06-09 |
| UAL28 | - | 5 | 2026-07-12 |
| UAL2023 | United Airlines | 5 | 2026-05-22 |
| UAL199 | United Airlines | 5 | 2026-06-06 |
| UAL1849 | - | 5 | 2026-07-13 |
| UAL115 | - | 5 | 2026-07-10 |
| UAL969 | - | 4 | 2026-07-08 |
| UAL870 | - | 4 | 2026-06-26 |
| UAL863 | - | 4 | 2026-06-25 |
| UAL842 | - | 4 | 2026-06-18 |
| UAL821 | United Airlines | 4 | 2026-05-29 |
| UAL820 | United Airlines | 4 | 2026-05-29 |
| UAL82 | United Airlines | 4 | 2026-06-10 |
| UAL805 | United Airlines | 4 | 2026-06-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAL1757 | IAD → SFO | Jul 13, 22:25 UTC | Jul 14, 03:00 UTC | 4h 35m |
| 2026-07-13 | UAL1849 | SFO → IAD | Jul 13, 15:25 UTC | Jul 13, 20:00 UTC | 4h 35m |
| 2026-07-12 | UAL28 | - | Jul 12, 15:15 UTC | Jul 13, 05:20 UTC | 14h 5m |
| 2026-07-12 | UAL29 | - | Jul 12, 11:05 UTC | Jul 12, 11:15 UTC | 10m |
| 2026-07-11 | UAL29 | - | Jul 11, 19:05 UTC | Jul 12, 07:10 UTC | 12h 5m |
| 2026-07-11 | UAL114 | - | Jul 11, 07:25 UTC | Jul 11, 14:55 UTC | 7h 30m |
| 2026-07-10 | UAL115 | SFO → PPT | Jul 10, 21:27 UTC | Jul 11, 05:13 UTC | 7h 46m |
| 2026-07-10 | UAL115 | - | Jul 10, 21:20 UTC | Jul 11, 05:01 UTC | 7h 40m |
| 2026-07-10 | UAL61 | - | Jul 10, 01:05 UTC | Jul 10, 15:05 UTC | 14h 0m |
| 2026-07-09 | UAL60 | SFO → MEL | Jul 9, 06:51 UTC | Jul 9, 21:56 UTC | 15h 5m |
| 2026-07-09 | UAL60 | - | Jul 9, 07:00 UTC | Jul 9, 07:30 UTC | 30m |
| 2026-07-08 | UAL969 | - | Jul 8, 13:30 UTC | Jul 8, 23:50 UTC | 10h 20m |
| 2026-07-07 | UAL968 | - | Jul 7, 22:30 UTC | Jul 8, 08:15 UTC | 9h 45m |
| 2026-07-07 | UAL892 | - | Jul 7, 08:40 UTC | Jul 7, 10:20 UTC | 1h 40m |
| 2026-07-07 | UAL892 | ICN → SFO | Jul 7, 08:41 UTC | Jul 7, 18:42 UTC | 10h 1m |
| 2026-07-06 | UAL893 | SFO → ICN | Jul 6, 19:05 UTC | Jul 7, 06:35 UTC | 11h 30m |
| 2026-07-06 | UAL61 | MEL → SFO | Jul 6, 01:05 UTC | Jul 6, 14:35 UTC | 13h 30m |
| 2026-07-05 | UAL60 | SFO → MEL | Jul 5, 06:51 UTC | Jul 5, 22:22 UTC | 15h 31m |
| 2026-07-05 | UAL60 | SFO → MEL | Jul 5, 06:55 UTC | Jul 5, 22:25 UTC | 15h 30m |
| 2026-07-04 | UAL969 | - | Jul 4, 13:25 UTC | Jul 4, 23:55 UTC | 10h 30m |
| 2026-07-03 | UAL968 | - | Jul 3, 22:20 UTC | Jul 4, 08:05 UTC | 9h 45m |
| 2026-07-03 | UAL892 | - | Jul 3, 08:05 UTC | Jul 3, 18:10 UTC | 10h 5m |
| 2026-07-02 | UAL893 | SFO → ICN | Jul 2, 18:10 UTC | Jul 3, 05:45 UTC | 11h 35m |
| 2026-07-02 | UAL114 | - | Jul 2, 07:15 UTC | Jul 2, 14:55 UTC | 7h 40m |
| 2026-07-01 | UAL115 | SFO → PPT | Jul 1, 21:05 UTC | Jul 2, 04:55 UTC | 7h 50m |
| 2026-07-01 | UAL61 | MEL → SFO | Jul 1, 01:24 UTC | Jul 1, 15:03 UTC | 13h 39m |
| 2026-07-01 | UAL61 | MEL → SFO | Jul 1, 01:24 UTC | Jul 1, 14:45 UTC | 13h 21m |
| 2026-07-01 | UAL61 | - | Jul 1, 01:20 UTC | Jul 1, 14:55 UTC | 13h 35m |
| 2026-06-30 | UAL60 | SFO → MEL | Jun 30, 07:15 UTC | Jun 30, 22:25 UTC | 15h 10m |
| 2026-06-29 | UAL969 | AMS → SFO | Jun 29, 13:31 UTC | Jun 29, 23:28 UTC | 9h 57m |
| 2026-06-29 | UAL969 | - | Jun 29, 13:30 UTC | Jun 29, 23:29 UTC | 10h 0m |
| 2026-06-28 | UAL968 | SFO → AMS | Jun 28, 22:15 UTC | Jun 29, 07:50 UTC | 9h 35m |
| 2026-06-27 | UAL28 | - | Jun 27, 15:45 UTC | Jun 28, 04:10 UTC | 12h 25m |
| 2026-06-27 | UAL28 | - | Jun 27, 13:09 UTC | Jun 27, 13:20 UTC | 10m |
| 2026-06-27 | UAL29 | - | Jun 27, 10:29 UTC | Jun 27, 10:40 UTC | 10m |
| 2026-06-26 | UAL29 | - | Jun 26, 19:09 UTC | Jun 27, 09:19 UTC | 14h 10m |
| 2026-06-26 | UAL870 | - | Jun 26, 01:05 UTC | Jun 26, 14:05 UTC | 13h 0m |
| 2026-06-26 | UAL870 | SYD → SFO | Jun 26, 00:50 UTC | Jun 26, 14:01 UTC | 13h 11m |
| 2026-06-25 | UAL863 | SFO → SYD | Jun 25, 06:51 UTC | Jun 25, 21:25 UTC | 14h 34m |
| 2026-06-25 | UAL863 | - | Jun 25, 07:09 UTC | Jun 25, 07:34 UTC | 25m |
| 2026-06-24 | UAL1227 | - | Jun 24, 17:59 UTC | Jun 24, 23:24 UTC | 5h 25m |
| 2026-06-24 | UAL123 | - | Jun 24, 07:10 UTC | Jun 24, 14:20 UTC | 7h 10m |
| 2026-06-23 | UAL122 | EWR → LHR | Jun 23, 14:10 UTC | Jun 23, 20:10 UTC | 6h 0m |
| 2026-06-22 | UAL2222 | CPT → EWR | Jun 22, 18:12 UTC | Jun 23, 08:33 UTC | 14h 21m |
| 2026-06-22 | UAL2222 | CPT → EWR | Jun 22, 17:55 UTC | Jun 23, 08:30 UTC | 14h 35m |
| 2026-06-22 | UAL1122 | - | Jun 22, 00:44 UTC | Jun 22, 01:05 UTC | 20m |
| 2026-06-20 | UAL2222 | CPT → EWR | Jun 20, 19:19 UTC | Jun 21, 10:04 UTC | 14h 45m |
| 2026-06-20 | UAL1122 | - | Jun 20, 14:29 UTC | Jun 20, 14:50 UTC | 20m |
| 2026-06-20 | UAL1122 | - | Jun 20, 00:54 UTC | Jun 20, 01:19 UTC | 25m |
| 2026-06-19 | UAL2096 | LAX → EWR | Jun 19, 16:29 UTC | Jun 19, 20:55 UTC | 4h 25m |
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 N29968 page for operator, model, and routing details .