sensors Mode-S transponder
AA92F8
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N78001 · BOEING 777-200 · operated by UNITED AIRLINES INC
- Hex
- AA92F8
- Octal
- 52511370
- Decimal
- 11,178,744
- Country
- US
- Tail
- N78001
- Type
- B772
- Flights observed
- 153
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AA92F8 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 |
|---|---|---|---|
| UAL97 | - | 11 | 2026-07-12 |
| UAL889 | - | 11 | 2026-07-13 |
| UAL888 | - | 10 | 2026-07-12 |
| UAL969 | United Airlines | 8 | 2026-05-07 |
| UAL949 | United Airlines | 7 | 2026-04-14 |
| UAL927 | - | 7 | 2026-07-05 |
| UAL968 | United Airlines | 6 | 2026-05-06 |
| UAL96 | - | 6 | 2026-07-11 |
| UAL926 | United Airlines | 5 | 2026-05-25 |
| UAL804 | - | 4 | 2026-07-04 |
| UAL673 | - | 4 | 2026-07-14 |
| UAL57 | United Airlines | 4 | 2026-06-28 |
| UAL506 | - | 4 | 2026-07-10 |
| UAL131 | - | 4 | 2026-07-03 |
| UAL984 | - | 3 | 2026-06-29 |
| UAL919 | United Airlines | 3 | 2026-06-02 |
| UAL918 | United Airlines | 3 | 2026-06-01 |
| UAL875 | United Airlines | 3 | 2026-05-30 |
| UAL803 | United Airlines | 3 | 2026-06-04 |
| UAL507 | - | 3 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UAL673 | - | Jul 14, 14:20 UTC | Jul 14, 16:00 UTC | 1h 40m |
| 2026-07-14 | UAL672 | SFO → BCN | Jul 14, 01:25 UTC | Jul 14, 11:50 UTC | 10h 25m |
| 2026-07-13 | UAL889 | - | Jul 13, 12:25 UTC | Jul 13, 23:05 UTC | 10h 40m |
| 2026-07-12 | UAL888 | - | Jul 12, 18:05 UTC | Jul 13, 05:31 UTC | 11h 25m |
| 2026-07-12 | UAL97 | BNE → SFO | Jul 12, 00:43 UTC | Jul 12, 13:02 UTC | 12h 19m |
| 2026-07-12 | UAL97 | - | Jul 12, 00:40 UTC | Jul 12, 13:05 UTC | 12h 25m |
| 2026-07-12 | UAL97 | BNE → SFO | Jul 12, 00:43 UTC | Jul 12, 13:01 UTC | 12h 18m |
| 2026-07-11 | UAL96 | SFO → BNE | Jul 11, 07:00 UTC | Jul 11, 21:00 UTC | 14h 0m |
| 2026-07-10 | UAL506 | - | Jul 10, 15:05 UTC | Jul 11, 03:25 UTC | 12h 20m |
| 2026-07-10 | UAL507 | SFO → FCO | Jul 10, 00:23 UTC | Jul 10, 11:47 UTC | 11h 24m |
| 2026-07-10 | UAL507 | - | Jul 10, 00:35 UTC | Jul 10, 03:20 UTC | 2h 45m |
| 2026-07-09 | UAL889 | - | Jul 9, 10:55 UTC | Jul 9, 12:50 UTC | 1h 55m |
| 2026-07-09 | UAL889 | PEK → SFO | Jul 9, 09:56 UTC | Jul 9, 21:11 UTC | 11h 15m |
| 2026-07-09 | UAL889 | - | Jul 9, 04:10 UTC | Jul 9, 21:15 UTC | 17h 5m |
| 2026-07-08 | UAL888 | SFO → PEK | Jul 8, 18:55 UTC | Jul 9, 07:36 UTC | 12h 41m |
| 2026-07-08 | UAL888 | - | Jul 8, 18:55 UTC | Jul 9, 06:00 UTC | 11h 5m |
| 2026-07-07 | UAL889 | PEK → SFO | Jul 7, 11:35 UTC | Jul 7, 21:50 UTC | 10h 15m |
| 2026-07-06 | UAL888 | SFO → PEK | Jul 6, 18:15 UTC | Jul 7, 07:02 UTC | 12h 47m |
| 2026-07-06 | UAL888 | SFO → PEK | Jul 6, 18:10 UTC | Jul 7, 04:00 UTC | 9h 50m |
| 2026-07-05 | UAL927 | - | Jul 5, 15:55 UTC | Jul 6, 03:10 UTC | 11h 15m |
| 2026-07-05 | UAL927 | FRA → SFO | Jul 5, 15:51 UTC | Jul 6, 03:03 UTC | 11h 12m |
| 2026-07-05 | UAL932 | IAD → FRA | Jul 5, 03:08 UTC | Jul 5, 10:29 UTC | 7h 21m |
| 2026-07-05 | UAL932 | - | Jul 5, 03:05 UTC | Jul 5, 05:05 UTC | 2h 0m |
| 2026-07-04 | UAL804 | HND → IAD | Jul 4, 08:15 UTC | Jul 4, 20:00 UTC | 11h 45m |
| 2026-07-03 | UAL131 | EWR → HND | Jul 3, 15:23 UTC | Jul 4, 05:45 UTC | 14h 22m |
| 2026-07-03 | UAL131 | - | Jul 3, 15:25 UTC | Jul 3, 23:20 UTC | 7h 55m |
| 2026-07-02 | UAL1333 | SFO → EWR | Jul 2, 21:20 UTC | Jul 3, 02:00 UTC | 4h 40m |
| 2026-07-02 | UAL673 | - | Jul 2, 06:45 UTC | Jul 2, 11:50 UTC | 5h 5m |
| 2026-07-01 | UAL673 | - | Jul 1, 18:25 UTC | Jul 1, 19:55 UTC | 1h 30m |
| 2026-07-01 | UAL673 | BCN → EWR | Jul 1, 17:36 UTC | Jul 2, 02:17 UTC | 8h 41m |
| 2026-07-01 | UAL672 | SFO → BCN | Jul 1, 01:20 UTC | Jul 1, 11:50 UTC | 10h 30m |
| 2026-06-30 | UAL59 | - | Jun 30, 11:35 UTC | Jun 30, 13:20 UTC | 1h 45m |
| 2026-06-30 | UAL59 | FRA → SFO | Jun 30, 11:44 UTC | Jun 30, 22:00 UTC | 10h 16m |
| 2026-06-29 | UAL58 | SFO → FRA | Jun 29, 21:22 UTC | Jun 30, 07:30 UTC | 10h 8m |
| 2026-06-29 | UAL58 | - | Jun 29, 21:19 UTC | Jun 30, 07:40 UTC | 10h 21m |
| 2026-06-29 | UAL984 | - | Jun 29, 07:55 UTC | Jun 29, 09:29 UTC | 1h 35m |
| 2026-06-29 | UAL984 | CDG → SFO | Jun 29, 07:48 UTC | Jun 29, 18:01 UTC | 10h 13m |
| 2026-06-28 | UAL57 | EWR → CDG | Jun 28, 22:58 UTC | Jun 29, 05:25 UTC | 6h 27m |
| 2026-06-28 | UAL57 | EWR → CDG | Jun 28, 22:59 UTC | Jun 29, 05:30 UTC | 6h 30m |
| 2026-06-07 | UAL148 | GRU → EWR | Jun 7, 00:19 UTC | Jun 7, 09:15 UTC | 8h 55m |
| 2026-06-06 | UAL149 | EWR → GRU | Jun 6, 01:31 UTC | Jun 6, 10:12 UTC | 8h 41m |
| 2026-06-06 | UAL149 | EWR → GRU | Jun 6, 01:25 UTC | Jun 6, 01:55 UTC | 30m |
| 2026-06-05 | UAL130 | HND → EWR | Jun 5, 09:30 UTC | Jun 5, 21:55 UTC | 12h 25m |
| 2026-06-04 | UAL803 | IAD → HND | Jun 4, 17:35 UTC | Jun 5, 06:36 UTC | 13h 1m |
| 2026-06-04 | UAL803 | IAD → HND | Jun 4, 17:30 UTC | Jun 5, 06:45 UTC | 13h 15m |
| 2026-06-03 | UAL943 | LIS → IAD | Jun 3, 11:51 UTC | Jun 3, 19:11 UTC | 7h 20m |
| 2026-06-03 | UAL943 | LIS → IAD | Jun 3, 11:40 UTC | Jun 3, 12:10 UTC | 30m |
| 2026-06-03 | UAL942 | IAD → LIS | Jun 3, 02:55 UTC | Jun 3, 09:00 UTC | 6h 5m |
| 2026-06-02 | UAL919 | LHR → IAD | Jun 2, 11:55 UTC | Jun 2, 18:50 UTC | 6h 55m |
| 2026-06-01 | UAL918 | IAD → LHR | Jun 1, 22:55 UTC | Jun 2, 05:40 UTC | 6h 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 N78001 page for operator, model, and routing details .