sensors Mode-S transponder
A03387
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N1119K · RAYTHEON 4000 Hawker Horizon · operated by BANK OF UTAH TRUSTEE
- Hex
- A03387
- Octal
- 50031607
- Decimal
- 10,498,951
- Country
- US
- Tail
- N1119K
- Type
- HA4T
- Flights observed
- 88
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address A03387 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | VYR19 | - | Jul 25, 20:20 UTC | Jul 25, 22:35 UTC | 2h 15m |
| 2026-07-25 | VYR19 | - | Jul 25, 16:05 UTC | Jul 25, 18:15 UTC | 2h 10m |
| 2026-07-20 | VYR19 | - | Jul 20, 01:20 UTC | Jul 20, 02:30 UTC | 1h 10m |
| 2026-07-19 | VYR19 | - | Jul 19, 22:35 UTC | Jul 19, 23:45 UTC | 1h 10m |
| 2026-07-19 | VYR19 | - | Jul 19, 20:35 UTC | Jul 19, 21:50 UTC | 1h 15m |
| 2026-07-19 | VYR19 | - | Jul 19, 14:00 UTC | Jul 19, 19:50 UTC | 5h 50m |
| 2026-07-16 | VYR19 | - | Jul 16, 00:55 UTC | Jul 16, 02:05 UTC | 1h 10m |
| 2026-07-15 | VYR19 | - | Jul 15, 22:25 UTC | Jul 16, 00:30 UTC | 2h 5m |
| 2026-07-15 | VYR19 | - | Jul 15, 20:20 UTC | Jul 15, 21:25 UTC | 1h 5m |
| 2026-07-15 | VYR19 | - | Jul 15, 01:30 UTC | Jul 15, 02:55 UTC | 1h 25m |
| 2026-07-14 | VYR19 | - | Jul 14, 22:55 UTC | Jul 15, 00:25 UTC | 1h 30m |
| 2026-07-14 | VYR19 | - | Jul 14, 00:25 UTC | Jul 14, 02:40 UTC | 2h 15m |
| 2026-07-10 | VYR19 | - | Jul 10, 19:50 UTC | Jul 10, 22:15 UTC | 2h 25m |
| 2026-07-08 | VYR19 | - | Jul 8, 21:10 UTC | Jul 8, 21:40 UTC | 30m |
| 2026-07-08 | VYR19 | - | Jul 8, 13:55 UTC | Jul 8, 14:30 UTC | 35m |
| 2026-07-08 | VYR19 | - | Jul 8, 02:50 UTC | Jul 8, 04:15 UTC | 1h 25m |
| 2026-07-07 | VYR19 | - | Jul 7, 03:50 UTC | Jul 8, 03:45 UTC | 23h 55m |
| 2026-07-07 | VYR19 | - | Jul 7, 02:55 UTC | Jul 7, 04:35 UTC | 1h 40m |
| 2026-07-06 | VYR19 | - | Jul 6, 20:10 UTC | Jul 6, 22:40 UTC | 2h 30m |
| 2026-07-06 | VYR19 | - | Jul 6, 16:30 UTC | Jul 6, 18:00 UTC | 1h 30m |
| 2026-07-06 | VYR19 | - | Jul 6, 05:05 UTC | Jul 6, 05:45 UTC | 40m |
| 2026-07-06 | VYR19 | - | Jul 6, 03:00 UTC | Jul 6, 04:20 UTC | 1h 20m |
| 2026-07-06 | VYR19 | - | Jul 6, 00:20 UTC | Jul 6, 02:30 UTC | 2h 10m |
| 2026-07-05 | VYR19 | YYC → YEG | Jul 5, 23:35 UTC | Jul 6, 00:05 UTC | 30m |
| 2026-07-02 | VYR19 | - | Jul 2, 23:10 UTC | Jul 3, 01:10 UTC | 2h 0m |
| 2026-07-02 | VYR19 | - | Jul 2, 07:00 UTC | Jul 2, 08:40 UTC | 1h 40m |
| 2026-07-02 | VYR19 | - | Jul 2, 03:50 UTC | Jul 2, 05:55 UTC | 2h 5m |
| 2026-07-01 | VYR19 | - | Jul 1, 21:00 UTC | Jul 1, 21:40 UTC | 40m |
| 2026-07-01 | VYR19 | - | Jul 1, 16:40 UTC | Jul 1, 20:05 UTC | 3h 25m |
| 2026-07-01 | VYR19 | - | Jul 1, 04:30 UTC | Jul 1, 05:35 UTC | 1h 5m |
| 2026-07-01 | VYR19 | - | Jul 1, 03:15 UTC | Jul 1, 03:45 UTC | 30m |
| 2026-06-30 | VYR19 | - | Jun 30, 23:30 UTC | Jul 1, 02:15 UTC | 2h 45m |
| 2026-06-30 | VYR19 | - | Jun 30, 16:10 UTC | Jun 30, 16:50 UTC | 40m |
| 2026-06-08 | VYR19 | - | Jun 8, 03:05 UTC | Jun 8, 04:10 UTC | 1h 5m |
| 2026-06-08 | N1119K | - | Jun 8, 01:05 UTC | Jun 8, 02:30 UTC | 1h 25m |
| 2026-06-04 | N1119K | - | Jun 4, 19:05 UTC | Jun 4, 20:40 UTC | 1h 35m |
| 2026-06-04 | VYR19 | - | Jun 4, 16:30 UTC | Jun 4, 18:00 UTC | 1h 30m |
| 2026-06-03 | VYR19 | SBD → SPZ | Jun 3, 19:05 UTC | Jun 3, 21:45 UTC | 2h 40m |
| 2026-06-03 | VYR19 | - | Jun 3, 15:25 UTC | Jun 3, 18:15 UTC | 2h 50m |
| 2026-06-03 | VYR19 | - | Jun 3, 13:50 UTC | Jun 3, 14:10 UTC | 20m |
| 2026-05-30 | VYR19 | - | May 30, 22:40 UTC | May 30, 23:05 UTC | 25m |
| 2026-05-30 | VYR19 | - | May 30, 21:00 UTC | May 30, 21:40 UTC | 40m |
| 2026-05-30 | N1119K | - | May 30, 12:00 UTC | May 30, 20:30 UTC | 8h 30m |
| 2026-05-27 | VYR19 | - | May 27, 21:10 UTC | May 27, 23:45 UTC | 2h 35m |
| 2026-05-26 | VYR19 | - | May 26, 19:55 UTC | May 26, 22:50 UTC | 2h 55m |
| 2026-05-24 | VYR19 | - | May 24, 04:05 UTC | May 24, 04:35 UTC | 30m |
| 2026-05-23 | VYR19 | OPF → ICT | May 23, 17:00 UTC | May 23, 19:50 UTC | 2h 50m |
| 2026-05-22 | VYR19 | - | May 22, 20:55 UTC | May 23, 00:15 UTC | 3h 20m |
| 2026-05-22 | VYR19 | - | May 22, 02:05 UTC | May 22, 03:10 UTC | 1h 5m |
| 2026-05-22 | VYR19 | - | May 22, 00:00 UTC | May 22, 01:00 UTC | 1h 0m |
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 N1119K page for operator, model, and routing details .