sensors Mode-S transponder
A0F428
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N16009 · BOEING 787-10 Dreamliner · operated by UNITED AIRLINES INC
- Hex
- A0F428
- Octal
- 50172050
- Decimal
- 10,548,264
- Country
- US
- Tail
- N16009
- Type
- B78X
- Flights observed
- 152
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A0F428 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 |
|---|---|---|---|
| UAL945 | - | 14 | 2026-06-25 |
| UAL944 | - | 12 | 2026-06-24 |
| UAL995 | - | 10 | 2026-07-06 |
| UAL994 | - | 9 | 2026-07-08 |
| UAL973 | - | 8 | 2026-07-09 |
| UAL986 | - | 7 | 2026-07-11 |
| UAL972 | - | 7 | 2026-07-06 |
| UAL65 | - | 7 | 2026-07-08 |
| UAL64 | - | 7 | 2026-07-08 |
| UAL2238 | - | 6 | 2026-07-06 |
| UAL125 | - | 6 | 2026-06-20 |
| UAL124 | - | 6 | 2026-06-19 |
| UAL987 | - | 5 | 2026-07-11 |
| UAL881 | - | 4 | 2026-07-03 |
| UAL2692 | - | 4 | 2026-06-18 |
| UAL2397 | - | 4 | 2026-06-17 |
| UAL1855 | - | 4 | 2026-06-18 |
| UAL121 | United Airlines | 4 | 2026-05-19 |
| UAL120 | United Airlines | 4 | 2026-05-19 |
| UAL882 | - | 3 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | UAL907 | - | Jul 12, 00:10 UTC | Jul 12, 07:50 UTC | 7h 40m |
| 2026-07-11 | UAL986 | - | Jul 11, 10:20 UTC | Jul 11, 18:10 UTC | 7h 50m |
| 2026-07-11 | UAL987 | - | Jul 11, 00:50 UTC | Jul 11, 08:01 UTC | 7h 10m |
| 2026-07-10 | UAL986 | - | Jul 10, 10:20 UTC | Jul 10, 18:25 UTC | 8h 5m |
| 2026-07-10 | UAL987 | - | Jul 10, 00:45 UTC | Jul 10, 07:55 UTC | 7h 10m |
| 2026-07-09 | UAL973 | BRU → ORD | Jul 9, 08:40 UTC | Jul 9, 16:40 UTC | 8h 0m |
| 2026-07-08 | UAL994 | EWR → BRU | Jul 8, 23:04 UTC | Jul 9, 05:24 UTC | 6h 20m |
| 2026-07-08 | UAL65 | LIS → EWR | Jul 8, 10:55 UTC | Jul 8, 17:35 UTC | 6h 40m |
| 2026-07-08 | UAL64 | EWR → LIS | Jul 8, 01:20 UTC | Jul 8, 07:10 UTC | 5h 50m |
| 2026-07-07 | UAL1981 | DEN → LGA | Jul 7, 18:30 UTC | Jul 7, 23:00 UTC | 4h 30m |
| 2026-07-06 | UAL2238 | - | Jul 6, 21:35 UTC | Jul 7, 02:25 UTC | 4h 50m |
| 2026-07-06 | UAL995 | - | Jul 6, 09:50 UTC | Jul 6, 11:25 UTC | 1h 35m |
| 2026-07-06 | UAL995 | BRU → EWR | Jul 6, 09:44 UTC | Jul 6, 17:15 UTC | 7h 31m |
| 2026-07-06 | UAL995 | BRU → EWR | Jul 6, 09:44 UTC | Jul 6, 17:15 UTC | 7h 31m |
| 2026-07-06 | UAL972 | - | Jul 6, 00:05 UTC | Jul 6, 07:15 UTC | 7h 10m |
| 2026-07-05 | UAL986 | - | Jul 5, 20:30 UTC | Jul 5, 20:35 UTC | 5m |
| 2026-07-05 | UAL986 | - | Jul 5, 12:20 UTC | Jul 5, 20:35 UTC | 8h 15m |
| 2026-07-05 | UAL986 | CDG → ORD | Jul 5, 12:24 UTC | Jul 5, 20:11 UTC | 7h 47m |
| 2026-07-05 | UAL987 | - | Jul 5, 02:35 UTC | Jul 5, 09:30 UTC | 6h 55m |
| 2026-07-04 | UAL882 | HND → ORD | Jul 4, 10:50 UTC | Jul 4, 23:00 UTC | 12h 10m |
| 2026-07-03 | UAL881 | ORD → HND | Jul 3, 19:30 UTC | Jul 4, 08:30 UTC | 13h 0m |
| 2026-07-03 | UAL881 | ORD → HND | Jul 3, 18:01 UTC | Jul 4, 08:36 UTC | 14h 35m |
| 2026-07-03 | UAL844 | - | Jul 3, 01:55 UTC | Jul 3, 11:25 UTC | 9h 30m |
| 2026-07-02 | UAL845 | ORD → GRU | Jul 2, 05:45 UTC | Jul 2, 15:10 UTC | 9h 25m |
| 2026-07-01 | UAL415 | - | Jul 1, 16:05 UTC | Jul 2, 01:25 UTC | 9h 20m |
| 2026-07-01 | UAL416 | ORD → MXP | Jul 1, 05:30 UTC | Jul 1, 13:25 UTC | 7h 55m |
| 2026-06-30 | UAL415 | MXP → ORD | Jun 30, 16:40 UTC | Jul 1, 01:35 UTC | 8h 55m |
| 2026-06-30 | UAL416 | - | Jun 30, 05:35 UTC | Jun 30, 13:30 UTC | 7h 55m |
| 2026-06-29 | UAL882 | HND → ORD | Jun 29, 14:05 UTC | Jun 30, 01:29 UTC | 11h 24m |
| 2026-06-29 | UAL882 | - | Jun 29, 14:14 UTC | Jun 30, 00:00 UTC | 9h 45m |
| 2026-06-29 | UAL39 | - | Jun 29, 00:54 UTC | Jun 29, 12:00 UTC | 11h 5m |
| 2026-06-29 | UAL39 | LAX → HND | Jun 29, 00:57 UTC | Jun 29, 11:53 UTC | 10h 56m |
| 2026-06-28 | UAL38 | - | Jun 28, 09:45 UTC | Jun 28, 19:04 UTC | 9h 20m |
| 2026-06-27 | UAL881 | - | Jun 27, 17:34 UTC | Jun 28, 05:55 UTC | 12h 20m |
| 2026-06-27 | UAL844 | - | Jun 27, 01:44 UTC | Jun 27, 11:30 UTC | 9h 45m |
| 2026-06-26 | UAL845 | ORD → GRU | Jun 26, 03:24 UTC | Jun 26, 12:34 UTC | 9h 10m |
| 2026-06-26 | UAL845 | ORD → GRU | Jun 26, 03:28 UTC | Jun 26, 12:35 UTC | 9h 7m |
| 2026-06-25 | UAL945 | - | Jun 25, 07:34 UTC | Jun 25, 15:54 UTC | 8h 20m |
| 2026-06-24 | UAL944 | - | Jun 24, 20:35 UTC | Jun 24, 21:50 UTC | 1h 15m |
| 2026-06-24 | UAL944 | ORD → FRA | Jun 24, 20:47 UTC | Jun 25, 04:04 UTC | 7h 17m |
| 2026-06-24 | UAL945 | FRA → ORD | Jun 24, 07:24 UTC | Jun 24, 15:35 UTC | 8h 10m |
| 2026-06-24 | UAL945 | FRA → ORD | Jun 24, 07:18 UTC | Jun 24, 15:23 UTC | 8h 5m |
| 2026-06-23 | UAL944 | - | Jun 23, 20:59 UTC | Jun 24, 04:24 UTC | 7h 25m |
| 2026-06-23 | UAL973 | BRU → ORD | Jun 23, 09:40 UTC | Jun 23, 17:44 UTC | 8h 5m |
| 2026-06-22 | UAL994 | PBI → ORD | Jun 22, 23:39 UTC | Jun 23, 05:49 UTC | 6h 10m |
| 2026-06-22 | UAL995 | BRU → EWR | Jun 22, 09:34 UTC | Jun 22, 17:15 UTC | 7h 40m |
| 2026-06-21 | UAL972 | - | Jun 21, 23:55 UTC | Jun 22, 07:04 UTC | 7h 10m |
| 2026-06-21 | UAL973 | BRU → ORD | Jun 21, 08:25 UTC | Jun 21, 16:34 UTC | 8h 10m |
| 2026-06-20 | UAL994 | PBI → ORD | Jun 20, 23:15 UTC | Jun 21, 05:29 UTC | 6h 14m |
| 2026-06-20 | UAL994 | PBI → ORD | Jun 20, 23:04 UTC | Jun 21, 05:35 UTC | 6h 30m |
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 N16009 page for operator, model, and routing details .