sensors Mode-S transponder
A09FC4
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N13954 · BOEING 787-9 Dreamliner · operated by UNITED AIRLINES INC
- Hex
- A09FC4
- Octal
- 50117704
- Decimal
- 10,526,660
- Country
- US
- Tail
- N13954
- Type
- B789
- Flights observed
- 196
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address A09FC4 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 | - | 10 | 2026-07-02 |
| UAL820 | - | 9 | 2026-07-02 |
| UAL805 | - | 9 | 2026-07-05 |
| UAL806 | - | 8 | 2026-07-06 |
| UAL79 | United Airlines | 8 | 2026-05-03 |
| UAL199 | - | 7 | 2026-07-13 |
| UAL83 | United Airlines | 6 | 2026-06-28 |
| UAL198 | - | 6 | 2026-07-12 |
| UAL187 | United Airlines | 6 | 2026-06-04 |
| UAL1849 | United Airlines | 6 | 2026-06-24 |
| UAL7 | United Airlines | 5 | 2026-05-06 |
| UAL2023 | - | 5 | 2026-06-19 |
| UAL1855 | United Airlines | 5 | 2026-05-14 |
| UAL1011 | - | 5 | 2026-06-19 |
| UAL863 | - | 4 | 2026-07-11 |
| UAL82 | - | 4 | 2026-06-28 |
| UAL78 | United Airlines | 4 | 2026-04-16 |
| UAL63 | United Airlines | 4 | 2026-05-06 |
| UAL33 | United Airlines | 4 | 2026-05-07 |
| UAL29 | - | 4 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAL199 | - | Jul 13, 13:10 UTC | Jul 13, 14:50 UTC | 1h 40m |
| 2026-07-13 | UAL199 | - | Jul 13, 06:40 UTC | Jul 14, 00:10 UTC | 17h 30m |
| 2026-07-13 | UAL199 | - | Jul 13, 01:05 UTC | Jul 14, 00:10 UTC | 23h 5m |
| 2026-07-12 | UAL198 | - | Jul 12, 23:35 UTC | Jul 13, 23:00 UTC | 23h 25m |
| 2026-07-12 | UAL198 | - | Jul 12, 20:50 UTC | Jul 13, 07:01 UTC | 10h 10m |
| 2026-07-12 | UAL198 | LAX → PVG | Jul 12, 20:31 UTC | Jul 13, 09:23 UTC | 12h 52m |
| 2026-07-11 | UAL842 | SYD → LAX | Jul 11, 23:51 UTC | Jul 12, 12:42 UTC | 12h 51m |
| 2026-07-11 | UAL842 | - | Jul 11, 23:40 UTC | Jul 12, 12:35 UTC | 12h 55m |
| 2026-07-11 | UAL863 | SFO → SYD | Jul 11, 06:39 UTC | Jul 11, 21:01 UTC | 14h 22m |
| 2026-07-11 | UAL863 | SFO → SYD | Jul 11, 06:50 UTC | Jul 11, 21:05 UTC | 14h 15m |
| 2026-07-10 | UAL969 | AMS → SFO | Jul 10, 13:16 UTC | Jul 10, 23:44 UTC | 10h 28m |
| 2026-07-10 | UAL969 | - | Jul 10, 13:15 UTC | Jul 10, 23:45 UTC | 10h 30m |
| 2026-07-09 | UAL968 | SFO → AMS | Jul 9, 23:10 UTC | Jul 10, 09:00 UTC | 9h 50m |
| 2026-07-09 | UAL892 | - | Jul 9, 08:15 UTC | Jul 9, 18:35 UTC | 10h 20m |
| 2026-07-08 | UAL893 | SFO → ICN | Jul 8, 18:30 UTC | Jul 9, 06:05 UTC | 11h 35m |
| 2026-07-07 | UAL28 | - | Jul 7, 14:30 UTC | Jul 8, 03:45 UTC | 13h 15m |
| 2026-07-07 | UAL28 | - | Jul 7, 12:55 UTC | Jul 7, 13:05 UTC | 10m |
| 2026-07-07 | UAL28 | SIN → SFO | Jul 7, 13:06 UTC | Jul 8, 03:40 UTC | 14h 34m |
| 2026-07-07 | UAL29 | - | Jul 7, 10:15 UTC | Jul 7, 10:35 UTC | 20m |
| 2026-07-06 | UAL29 | - | Jul 6, 19:00 UTC | Jul 7, 08:10 UTC | 13h 10m |
| 2026-07-06 | UAL806 | - | Jul 6, 02:50 UTC | Jul 6, 12:45 UTC | 9h 55m |
| 2026-07-05 | UAL805 | SFO → ICN | Jul 5, 07:25 UTC | Jul 5, 18:55 UTC | 11h 30m |
| 2026-07-04 | UAL949 | - | Jul 4, 12:45 UTC | Jul 4, 13:00 UTC | 15m |
| 2026-07-04 | UAL949 | LHR → SFO | Jul 4, 12:25 UTC | Jul 4, 23:03 UTC | 10h 38m |
| 2026-07-03 | UAL923 | - | Jul 3, 23:10 UTC | Jul 4, 02:20 UTC | 3h 10m |
| 2026-07-03 | UAL923 | LAX → LHR | Jul 3, 23:08 UTC | Jul 4, 08:41 UTC | 9h 33m |
| 2026-07-02 | UAL821 | - | Jul 2, 15:25 UTC | Jul 3, 03:50 UTC | 12h 25m |
| 2026-07-02 | UAL821 | - | Jul 2, 12:50 UTC | Jul 2, 12:55 UTC | 5m |
| 2026-07-02 | UAL821 | - | Jul 2, 10:45 UTC | Jul 2, 12:00 UTC | 1h 15m |
| 2026-07-02 | UAL820 | - | Jul 2, 01:00 UTC | Jul 2, 01:15 UTC | 15m |
| 2026-07-02 | UAL820 | - | Jul 2, 00:20 UTC | Jul 2, 00:30 UTC | 10m |
| 2026-07-02 | UAL820 | HKG → BKK | Jul 2, 00:01 UTC | Jul 2, 02:28 UTC | 2h 27m |
| 2026-07-01 | UAL820 | - | Jul 1, 07:10 UTC | Jul 1, 21:00 UTC | 13h 50m |
| 2026-07-01 | UAL820 | LAX → HKG | Jul 1, 07:14 UTC | Jul 1, 21:03 UTC | 13h 49m |
| 2026-06-30 | UAL353 | - | Jun 30, 23:20 UTC | Jul 1, 04:20 UTC | 5h 0m |
| 2026-06-30 | UAL123 | LHR → EWR | Jun 30, 07:05 UTC | Jun 30, 14:05 UTC | 7h 0m |
| 2026-06-29 | UAL122 | EWR → LHR | Jun 29, 14:19 UTC | Jun 29, 20:00 UTC | 5h 41m |
| 2026-06-29 | UAL122 | EWR → TEB | Jun 29, 13:54 UTC | Jun 29, 13:59 UTC | 5m |
| 2026-06-28 | UAL83 | DEL → EWR | Jun 28, 19:29 UTC | Jun 28, 20:04 UTC | 35m |
| 2026-06-28 | UAL83 | DEL → EWR | Jun 28, 19:22 UTC | Jun 29, 10:41 UTC | 15h 19m |
| 2026-06-28 | UAL83 | DEL → EWR | Jun 28, 19:22 UTC | Jun 29, 11:06 UTC | 15h 44m |
| 2026-06-28 | UAL82 | EWR → DEL | Jun 28, 01:44 UTC | Jun 28, 15:15 UTC | 13h 31m |
| 2026-06-28 | UAL82 | - | Jun 28, 01:40 UTC | Jun 28, 11:39 UTC | 10h 0m |
| 2026-06-27 | UAL713 | - | Jun 27, 17:55 UTC | Jun 27, 22:15 UTC | 4h 20m |
| 2026-06-27 | UAL806 | ICN → SFO | Jun 27, 02:56 UTC | Jun 27, 12:55 UTC | 9h 59m |
| 2026-06-27 | UAL806 | - | Jun 27, 02:39 UTC | Jun 27, 02:59 UTC | 20m |
| 2026-06-26 | UAL805 | - | Jun 26, 07:45 UTC | Jun 26, 19:55 UTC | 12h 10m |
| 2026-06-25 | UAL1757 | - | Jun 25, 23:14 UTC | Jun 26, 04:39 UTC | 5h 25m |
| 2026-06-24 | UAL1849 | MCO → EWR | Jun 24, 15:59 UTC | Jun 24, 20:09 UTC | 4h 10m |
| 2026-06-23 | UAL28 | - | Jun 23, 15:55 UTC | Jun 24, 03:19 UTC | 11h 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 N13954 page for operator, model, and routing details .