sensors Mode-S transponder
AA92F9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N78002 · BOEING 777-200 · operated by UNITED AIRLINES INC
- Hex
- AA92F9
- Octal
- 52511371
- Decimal
- 11,178,745
- Country
- US
- Tail
- N78002
- Type
- B772
- Flights observed
- 204
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address AA92F9 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 |
|---|---|---|---|
| UAL507 | - | 10 | 2026-07-09 |
| UAL131 | - | 10 | 2026-07-06 |
| UAL804 | United Airlines | 9 | 2026-06-05 |
| UAL506 | - | 9 | 2026-07-09 |
| UAL195 | United Airlines | 9 | 2026-06-15 |
| UAL130 | - | 8 | 2026-07-03 |
| UAL943 | United Airlines | 7 | 2026-07-01 |
| UAL888 | United Airlines | 7 | 2026-07-07 |
| UAL803 | United Airlines | 7 | 2026-07-02 |
| UAL916 | United Airlines | 6 | 2026-06-18 |
| UAL889 | - | 6 | 2026-07-08 |
| UAL819 | - | 6 | 2026-06-13 |
| UAL97 | - | 5 | 2026-06-28 |
| UAL942 | - | 5 | 2026-07-01 |
| UAL984 | United Airlines | 4 | 2026-06-11 |
| UAL968 | United Airlines | 4 | 2026-06-02 |
| UAL879 | United Airlines | 4 | 2026-05-26 |
| UAL876 | - | 4 | 2026-07-07 |
| UAL875 | United Airlines | 4 | 2026-06-04 |
| UAL818 | - | 4 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | UAL927 | - | Jul 13, 16:25 UTC | Jul 14, 03:35 UTC | 11h 10m |
| 2026-07-13 | UAL932 | IAD → FRA | Jul 13, 02:45 UTC | Jul 13, 10:05 UTC | 7h 20m |
| 2026-07-12 | UAL933 | FRA → IAD | Jul 12, 15:25 UTC | Jul 12, 23:25 UTC | 8h 0m |
| 2026-07-12 | UAL926 | SFO → FRA | Jul 12, 02:45 UTC | Jul 12, 12:50 UTC | 10h 5m |
| 2026-07-11 | UAL59 | - | Jul 11, 12:20 UTC | Jul 11, 13:55 UTC | 1h 35m |
| 2026-07-11 | UAL59 | FRA → SFO | Jul 11, 12:24 UTC | Jul 11, 23:19 UTC | 10h 55m |
| 2026-07-11 | UAL59 | FRA → SFO | Jul 11, 12:24 UTC | Jul 11, 23:22 UTC | 10h 58m |
| 2026-07-10 | UAL58 | SFO → FRA | Jul 10, 22:45 UTC | Jul 11, 08:45 UTC | 10h 0m |
| 2026-07-09 | UAL506 | - | Jul 9, 14:30 UTC | Jul 10, 02:20 UTC | 11h 50m |
| 2026-07-09 | UAL506 | FCO → SFO | Jul 9, 14:07 UTC | Jul 10, 02:18 UTC | 12h 11m |
| 2026-07-09 | UAL507 | - | Jul 9, 00:25 UTC | Jul 9, 11:40 UTC | 11h 15m |
| 2026-07-08 | UAL889 | PEK → SFO | Jul 8, 10:06 UTC | Jul 8, 21:23 UTC | 11h 17m |
| 2026-07-08 | UAL889 | PEK → SFO | Jul 8, 10:06 UTC | Jul 8, 21:30 UTC | 11h 24m |
| 2026-07-07 | UAL888 | SFO → PEK | Jul 7, 19:00 UTC | Jul 8, 13:15 UTC | 18h 15m |
| 2026-07-07 | UAL876 | HND → SFO | Jul 7, 07:15 UTC | Jul 7, 16:15 UTC | 9h 0m |
| 2026-07-07 | UAL876 | - | Jul 7, 07:15 UTC | Jul 7, 07:55 UTC | 40m |
| 2026-07-06 | UAL131 | EWR → HND | Jul 6, 14:53 UTC | Jul 7, 03:41 UTC | 12h 48m |
| 2026-07-06 | UAL131 | - | Jul 6, 14:45 UTC | Jul 6, 21:50 UTC | 7h 5m |
| 2026-07-05 | UAL1333 | SFO → EWR | Jul 5, 22:52 UTC | Jul 6, 04:37 UTC | 5h 45m |
| 2026-07-05 | UAL1333 | - | Jul 5, 22:40 UTC | Jul 6, 04:15 UTC | 5h 35m |
| 2026-07-05 | UAL1593 | - | Jul 5, 13:45 UTC | Jul 5, 18:50 UTC | 5h 5m |
| 2026-07-05 | UAL148 | - | Jul 5, 00:20 UTC | Jul 5, 09:00 UTC | 8h 40m |
| 2026-07-04 | UAL149 | - | Jul 4, 02:40 UTC | Jul 4, 11:30 UTC | 8h 50m |
| 2026-07-03 | UAL130 | HND → EWR | Jul 3, 09:45 UTC | Jul 3, 22:00 UTC | 12h 15m |
| 2026-07-02 | UAL803 | IAD → HND | Jul 2, 17:20 UTC | Jul 3, 06:20 UTC | 13h 0m |
| 2026-07-01 | UAL943 | LIS → IAD | Jul 1, 17:55 UTC | Jul 1, 19:20 UTC | 1h 25m |
| 2026-07-01 | UAL943 | LIS → IAD | Jul 1, 12:10 UTC | Jul 1, 12:45 UTC | 35m |
| 2026-07-01 | UAL942 | IAD → LIS | Jul 1, 03:20 UTC | Jul 1, 10:00 UTC | 6h 40m |
| 2026-06-30 | UAL943 | LIS → IAD | Jun 30, 12:28 UTC | Jun 30, 19:29 UTC | 7h 1m |
| 2026-06-30 | UAL943 | LIS → IAD | Jun 30, 12:15 UTC | Jun 30, 19:30 UTC | 7h 15m |
| 2026-06-30 | UAL942 | IAD → LIS | Jun 30, 03:05 UTC | Jun 30, 09:45 UTC | 6h 40m |
| 2026-06-29 | UAL914 | CDG → IAD | Jun 29, 10:44 UTC | Jun 29, 18:30 UTC | 7h 45m |
| 2026-06-28 | UAL990 | SFO → CDG | Jun 28, 22:08 UTC | Jun 29, 07:59 UTC | 9h 51m |
| 2026-06-28 | UAL990 | SFO → CDG | Jun 28, 22:10 UTC | Jun 29, 07:59 UTC | 9h 50m |
| 2026-06-28 | UAL97 | - | Jun 28, 00:55 UTC | Jun 28, 02:25 UTC | 1h 30m |
| 2026-06-28 | UAL97 | BNE → SFO | Jun 28, 00:53 UTC | Jun 28, 13:22 UTC | 12h 29m |
| 2026-06-27 | UAL96 | SFO → BNE | Jun 27, 07:10 UTC | Jun 27, 20:14 UTC | 13h 5m |
| 2026-06-26 | UAL506 | - | Jun 26, 14:25 UTC | Jun 27, 02:29 UTC | 12h 5m |
| 2026-06-26 | UAL506 | FCO → SFO | Jun 26, 14:07 UTC | Jun 27, 02:30 UTC | 12h 23m |
| 2026-06-26 | UAL507 | SFO → FCO | Jun 26, 00:19 UTC | Jun 26, 11:57 UTC | 11h 38m |
| 2026-06-26 | UAL507 | - | Jun 26, 00:39 UTC | Jun 26, 03:45 UTC | 3h 5m |
| 2026-06-25 | UAL889 | PEK → SFO | Jun 25, 10:50 UTC | Jun 25, 12:15 UTC | 1h 25m |
| 2026-06-25 | UAL889 | PEK → SFO | Jun 25, 09:51 UTC | Jun 25, 20:36 UTC | 10h 45m |
| 2026-06-24 | UAL888 | SFO → PEK | Jun 24, 18:15 UTC | Jun 25, 07:16 UTC | 13h 1m |
| 2026-06-24 | UAL888 | SFO → PEK | Jun 24, 18:09 UTC | Jun 25, 05:55 UTC | 11h 45m |
| 2026-06-24 | UAL97 | - | Jun 24, 00:44 UTC | Jun 24, 13:10 UTC | 12h 25m |
| 2026-06-23 | UAL96 | SFO → BNE | Jun 23, 06:59 UTC | Jun 23, 20:29 UTC | 13h 30m |
| 2026-06-22 | UAL889 | PEK → SFO | Jun 22, 03:40 UTC | Jun 22, 21:14 UTC | 17h 35m |
| 2026-06-21 | UAL888 | SFO → PEK | Jun 21, 22:20 UTC | Jun 22, 21:14 UTC | 22h 55m |
| 2026-06-21 | UAL888 | SFO → PEK | Jun 21, 18:25 UTC | Jun 22, 12:19 UTC | 17h 55m |
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 N78002 page for operator, model, and routing details .