sensors Mode-S transponder
A68AD4
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N520VL · AIRBUS A-320 · operated by BANK OF UTAH TRUSTEE
- Hex
- A68AD4
- Octal
- 51505324
- Decimal
- 10,914,516
- Country
- US
- Tail
- N520VL
- Type
- A320
- Flights observed
- 323
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- Jul 26, 22:50 UTC
Last known position
Country allocation
The ICAO 24-bit address A68AD4 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 |
|---|---|---|---|
| VOI713 | - | 9 | 2026-07-11 |
| VOI381 | - | 8 | 2026-07-05 |
| VOI380 | - | 6 | 2026-06-30 |
| VOI712 | - | 5 | 2026-07-10 |
| VOI248 | Volaris | 5 | 2026-07-21 |
| VOI247 | - | 5 | 2026-07-01 |
| VOI246 | - | 5 | 2026-07-01 |
| VOI5616 | Volaris | 4 | 2026-06-16 |
| VOI3257 | Volaris | 4 | 2026-07-19 |
| VOI3183 | - | 4 | 2026-06-30 |
| VOI3182 | - | 4 | 2026-07-04 |
| VOI249 | - | 4 | 2026-06-22 |
| VOI751 | - | 3 | 2026-07-07 |
| VOI5609 | - | 3 | 2026-07-21 |
| VOI5608 | Volaris | 3 | 2026-07-21 |
| VOI5584 | - | 3 | 2026-06-21 |
| VOI5567 | - | 3 | 2026-06-21 |
| VOI5566 | - | 3 | 2026-06-21 |
| VOI3931 | Volaris | 3 | 2026-04-28 |
| VOI3930 | Volaris | 3 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | VOI3519 | QRO → CUN | Jul 26, 16:50 UTC | Jul 26, 22:45 UTC | 5h 55m |
| 2026-07-26 | VOI817 | DFW → QRO | Jul 26, 01:25 UTC | Jul 26, 15:15 UTC | 13h 51m |
| 2026-07-25 | VOI816 | QRO → DFW | Jul 25, 21:35 UTC | Jul 25, 23:15 UTC | 1h 40m |
| 2026-07-25 | VOI533 | OAX → QRO | Jul 25, 18:40 UTC | Jul 25, 19:10 UTC | 30m |
| 2026-07-25 | VOI537 | VER → QRO | Jul 25, 15:05 UTC | Jul 25, 17:30 UTC | 2h 25m |
| 2026-07-25 | VOI5554 | MTY → QRO | Jul 25, 02:20 UTC | Jul 25, 13:40 UTC | 11h 20m |
| 2026-07-24 | VOI3514 | CUN → MTY | Jul 24, 17:20 UTC | Jul 25, 01:25 UTC | 8h 5m |
| 2026-07-24 | VOI3515 | - | Jul 24, 04:40 UTC | Jul 24, 16:05 UTC | 11h 25m |
| 2026-07-23 | VOI5853 | SEA → GDL | Jul 23, 20:20 UTC | Jul 24, 03:30 UTC | 7h 10m |
| 2026-07-23 | VOI5852 | GDL → SEA | Jul 23, 08:00 UTC | Jul 23, 18:10 UTC | 10h 10m |
| 2026-07-22 | VOI1720 | GDL → LAX | Jul 22, 23:15 UTC | Jul 23, 05:55 UTC | 6h 40m |
| 2026-07-22 | VOI1083 | MTY → GDL | Jul 22, 18:35 UTC | Jul 22, 21:50 UTC | 3h 15m |
| 2026-07-22 | VOI1081 | MTY → MTY | Jul 22, 14:15 UTC | Jul 22, 17:35 UTC | 3h 20m |
| 2026-07-22 | VOI5575 | MXL → MTY | Jul 22, 02:45 UTC | Jul 22, 04:50 UTC | 2h 5m |
| 2026-07-21 | VOI5574 | MTY → MXL | Jul 21, 23:25 UTC | Jul 22, 01:25 UTC | 2h 0m |
| 2026-07-21 | VOI5609 | - | Jul 21, 19:55 UTC | Jul 21, 22:20 UTC | 2h 25m |
| 2026-07-21 | VOI5608 | MTY → TIJ | Jul 21, 16:20 UTC | Jul 21, 18:40 UTC | 2h 20m |
| 2026-07-21 | VOI1091 | MTY → MTY | Jul 21, 12:00 UTC | Jul 21, 15:10 UTC | 3h 10m |
| 2026-07-21 | VOI248 | MEX → MTY | Jul 21, 03:55 UTC | Jul 21, 05:00 UTC | 1h 5m |
| 2026-07-20 | VOI183 | TIJ → MEX | Jul 20, 02:35 UTC | Jul 20, 02:40 UTC | 5m |
| 2026-07-19 | VOI183 | TIJ → MEX | Jul 19, 23:35 UTC | Jul 20, 00:50 UTC | 1h 15m |
| 2026-07-19 | VOI3257 | LMM → TIJ | Jul 19, 17:50 UTC | Jul 19, 21:55 UTC | 4h 5m |
| 2026-07-19 | VOI3045 | - | Jul 19, 03:00 UTC | Jul 19, 15:45 UTC | 12h 45m |
| 2026-07-18 | VOI3502 | CUN → BJX | Jul 18, 20:10 UTC | Jul 19, 01:55 UTC | 5h 45m |
| 2026-07-18 | VOI3503 | - | Jul 18, 17:05 UTC | Jul 18, 18:45 UTC | 1h 40m |
| 2026-07-17 | VOI3503 | - | Jul 17, 21:10 UTC | Jul 18, 18:45 UTC | 21h 36m |
| 2026-07-17 | VOI3502 | CUN → CUN | Jul 17, 20:10 UTC | Jul 18, 18:45 UTC | 22h 36m |
| 2026-07-17 | VOI3503 | - | Jul 17, 15:00 UTC | Jul 17, 19:00 UTC | 4h 0m |
| 2026-07-17 | VOI3046 | - | Jul 17, 03:14 UTC | Jul 17, 14:00 UTC | 10h 45m |
| 2026-07-16 | VOI3008 | - | Jul 16, 21:50 UTC | Jul 17, 02:10 UTC | 4h 20m |
| 2026-07-16 | VOI3230 | - | Jul 16, 16:25 UTC | Jul 16, 20:35 UTC | 4h 10m |
| 2026-07-16 | VOI7841 | - | Jul 16, 08:10 UTC | Jul 16, 15:00 UTC | 6h 50m |
| 2026-07-16 | VOI7840 | - | Jul 16, 04:10 UTC | Jul 16, 05:30 UTC | 1h 20m |
| 2026-07-14 | VOI5723 | - | Jul 14, 17:30 UTC | Jul 14, 19:00 UTC | 1h 30m |
| 2026-07-14 | VOI5722 | - | Jul 14, 04:25 UTC | Jul 14, 14:55 UTC | 10h 30m |
| 2026-07-13 | VOI1101 | - | Jul 13, 22:35 UTC | Jul 14, 03:35 UTC | 5h 0m |
| 2026-07-13 | VOI1771 | - | Jul 13, 03:20 UTC | Jul 13, 21:15 UTC | 17h 55m |
| 2026-07-12 | VOI1770 | - | Jul 12, 18:15 UTC | Jul 13, 01:45 UTC | 7h 30m |
| 2026-07-12 | VOI5045 | - | Jul 12, 03:05 UTC | Jul 12, 14:50 UTC | 11h 45m |
| 2026-07-11 | VOI5044 | - | Jul 11, 12:20 UTC | Jul 12, 01:10 UTC | 12h 50m |
| 2026-07-11 | VOI713 | - | Jul 11, 05:25 UTC | Jul 11, 05:40 UTC | 15m |
| 2026-07-11 | VOI713 | - | Jul 11, 02:20 UTC | Jul 11, 03:45 UTC | 1h 25m |
| 2026-07-10 | VOI7965 | - | Jul 10, 17:55 UTC | Jul 11, 00:05 UTC | 6h 10m |
| 2026-07-10 | VOI712 | - | Jul 10, 12:20 UTC | Jul 10, 15:40 UTC | 3h 20m |
| 2026-07-10 | VOI741 | - | Jul 10, 03:05 UTC | Jul 10, 03:15 UTC | 10m |
| 2026-07-10 | VOI741 | - | Jul 10, 00:00 UTC | Jul 10, 01:10 UTC | 1h 10m |
| 2026-07-09 | VOI740 | - | Jul 9, 18:25 UTC | Jul 9, 21:45 UTC | 3h 20m |
| 2026-07-09 | VOI901 | GUA → MEX | Jul 9, 14:35 UTC | Jul 9, 16:15 UTC | 1h 40m |
| 2026-07-09 | VOI900 | - | Jul 9, 03:15 UTC | Jul 9, 03:25 UTC | 10m |
| 2026-07-09 | VOI900 | - | Jul 9, 01:50 UTC | Jul 9, 02:35 UTC | 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 N520VL page for operator, model, and routing details .