sensors Mode-S transponder
AD6B16
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N964AV · AIRBUS A-320neo · operated by BANK OF UTAH TRUSTEE
- Hex
- AD6B16
- Octal
- 53265426
- Decimal
- 11,365,142
- Country
- US
- Tail
- N964AV
- Type
- A20N
- Flights observed
- 273
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address AD6B16 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 |
|---|---|---|---|
| GLG8396 | - | 14 | 2026-07-04 |
| GLG8395 | - | 14 | 2026-07-02 |
| LRC655 | LACSA | 8 | 2026-04-17 |
| LRC654 | LACSA | 8 | 2026-04-17 |
| LRC652 | LACSA | 7 | 2026-05-04 |
| GLG7396 | - | 7 | 2026-07-11 |
| LRC641 | LACSA | 5 | 2026-05-27 |
| AVA255 | - | 5 | 2026-06-29 |
| AVA254 | - | 5 | 2026-06-29 |
| AVA205 | - | 5 | 2026-06-27 |
| AVA204 | - | 5 | 2026-06-27 |
| AVA021 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-07-07 |
| LRC640 | LACSA | 4 | 2026-05-26 |
| GLG7392 | - | 4 | 2026-07-09 |
| AVA211 | - | 4 | 2026-07-06 |
| AVA210 | - | 4 | 2026-07-06 |
| AVA189 | Avianca - Aerovias Nacionales de Colombia, S.A. | 4 | 2026-06-06 |
| AVA020 | - | 4 | 2026-07-07 |
| TAI444 | - | 3 | 2026-06-30 |
| LRC671 | LACSA | 3 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | GLG7395 | JFK → JFK | Jul 13, 09:20 UTC | Jul 14, 03:15 UTC | 17h 55m |
| 2026-07-12 | GLG7394 | BOG → JFK | Jul 12, 18:01 UTC | Jul 13, 07:01 UTC | 13h 0m |
| 2026-07-12 | GLG7393 | JFK → BOG | Jul 12, 06:40 UTC | Jul 12, 15:35 UTC | 8h 55m |
| 2026-07-11 | GLG7396 | - | Jul 11, 10:05 UTC | Jul 12, 04:30 UTC | 18h 25m |
| 2026-07-11 | GLG7396 | - | Jul 11, 07:35 UTC | Jul 12, 04:30 UTC | 20h 55m |
| 2026-07-11 | GLG7393 | JFK → JFK | Jul 11, 06:35 UTC | Jul 12, 04:30 UTC | 21h 55m |
| 2026-07-11 | GLG7396 | - | Jul 11, 02:10 UTC | Jul 11, 04:25 UTC | 2h 15m |
| 2026-07-10 | GLG7396 | - | Jul 10, 07:35 UTC | Jul 11, 04:25 UTC | 20h 50m |
| 2026-07-10 | GLG7397 | JFK → JFK | Jul 10, 05:40 UTC | Jul 11, 04:25 UTC | 22h 45m |
| 2026-07-09 | GLG7392 | BOG → JFK | Jul 9, 18:10 UTC | Jul 10, 03:30 UTC | 9h 20m |
| 2026-07-09 | AVA058 | BOG → BOG | Jul 9, 13:15 UTC | Jul 9, 16:45 UTC | 3h 30m |
| 2026-07-09 | AVA224 | - | Jul 9, 04:05 UTC | Jul 9, 10:05 UTC | 6h 0m |
| 2026-07-08 | AVA116 | - | Jul 8, 23:25 UTC | Jul 9, 01:00 UTC | 1h 35m |
| 2026-07-08 | AVA116 | - | Jul 8, 19:45 UTC | Jul 8, 19:55 UTC | 10m |
| 2026-07-08 | AVA115 | - | Jul 8, 14:00 UTC | Jul 8, 14:30 UTC | 30m |
| 2026-07-07 | AVA259 | - | Jul 7, 22:55 UTC | Jul 8, 01:20 UTC | 2h 25m |
| 2026-07-07 | AVA258 | BOG → SJU | Jul 7, 18:40 UTC | Jul 7, 21:05 UTC | 2h 25m |
| 2026-07-07 | AVA021 | JFK → BOG | Jul 7, 16:35 UTC | Jul 7, 16:55 UTC | 20m |
| 2026-07-07 | AVA021 | JFK → BOG | Jul 7, 11:45 UTC | Jul 7, 14:15 UTC | 2h 30m |
| 2026-07-07 | AVA020 | - | Jul 7, 07:50 UTC | Jul 7, 09:45 UTC | 1h 55m |
| 2026-07-06 | AVA211 | - | Jul 6, 21:10 UTC | Jul 6, 23:45 UTC | 2h 35m |
| 2026-07-06 | AVA210 | - | Jul 6, 15:20 UTC | Jul 6, 18:55 UTC | 3h 35m |
| 2026-07-06 | AVA198 | - | Jul 6, 04:55 UTC | Jul 6, 09:40 UTC | 4h 45m |
| 2026-07-05 | AVA197 | - | Jul 5, 11:30 UTC | Jul 6, 03:25 UTC | 15h 55m |
| 2026-07-05 | AVA087 | - | Jul 5, 05:05 UTC | Jul 5, 09:45 UTC | 4h 40m |
| 2026-07-04 | GLG8396 | - | Jul 4, 20:05 UTC | Jul 5, 01:00 UTC | 4h 55m |
| 2026-07-04 | AVA263 | ORD → EZE | Jul 4, 05:00 UTC | Jul 4, 18:30 UTC | 13h 30m |
| 2026-07-03 | AVA262 | - | Jul 3, 22:55 UTC | Jul 4, 01:45 UTC | 2h 50m |
| 2026-07-03 | AVA021 | JFK → BOG | Jul 3, 12:00 UTC | Jul 3, 14:25 UTC | 2h 25m |
| 2026-07-03 | AVA020 | - | Jul 3, 07:20 UTC | Jul 3, 09:35 UTC | 2h 15m |
| 2026-07-02 | GLG8396 | - | Jul 2, 20:10 UTC | Jul 3, 01:15 UTC | 5h 5m |
| 2026-07-02 | GLG8395 | - | Jul 2, 13:50 UTC | Jul 2, 18:30 UTC | 4h 40m |
| 2026-07-01 | AVA233 | - | Jul 1, 21:25 UTC | Jul 1, 21:35 UTC | 10m |
| 2026-07-01 | AVA232 | BOG → AUA | Jul 1, 19:25 UTC | Jul 1, 19:35 UTC | 10m |
| 2026-06-30 | TAI445 | - | Jun 30, 21:10 UTC | Jul 1, 01:45 UTC | 4h 35m |
| 2026-06-30 | TAI444 | - | Jun 30, 14:10 UTC | Jun 30, 18:55 UTC | 4h 45m |
| 2026-06-29 | TAI444 | - | Jun 29, 15:34 UTC | Jun 30, 15:30 UTC | 23h 56m |
| 2026-06-29 | AVA255 | - | Jun 29, 13:09 UTC | Jun 29, 16:00 UTC | 2h 50m |
| 2026-06-29 | AVA254 | - | Jun 29, 08:04 UTC | Jun 29, 10:59 UTC | 2h 55m |
| 2026-06-28 | AVA247 | IAD → BOG | Jun 28, 20:25 UTC | Jun 28, 22:39 UTC | 2h 15m |
| 2026-06-28 | AVA246 | - | Jun 28, 16:25 UTC | Jun 28, 18:25 UTC | 2h 0m |
| 2026-06-27 | AVA211 | - | Jun 27, 21:19 UTC | Jun 28, 00:04 UTC | 2h 45m |
| 2026-06-27 | AVA210 | - | Jun 27, 15:30 UTC | Jun 27, 18:09 UTC | 2h 40m |
| 2026-06-27 | AVA205 | - | Jun 27, 05:19 UTC | Jun 27, 08:10 UTC | 2h 50m |
| 2026-06-27 | AVA204 | - | Jun 27, 00:14 UTC | Jun 27, 03:04 UTC | 2h 50m |
| 2026-06-26 | AVA088 | - | Jun 26, 10:20 UTC | Jun 26, 15:15 UTC | 4h 55m |
| 2026-06-25 | AVA211 | - | Jun 25, 20:05 UTC | Jun 26, 09:05 UTC | 13h 0m |
| 2026-06-25 | AVA210 | - | Jun 25, 15:24 UTC | Jun 25, 17:54 UTC | 2h 30m |
| 2026-06-25 | AVA205 | - | Jun 25, 05:15 UTC | Jun 25, 07:59 UTC | 2h 45m |
| 2026-06-25 | AVA204 | - | Jun 25, 00:24 UTC | Jun 25, 03:15 UTC | 2h 50m |
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 N964AV page for operator, model, and routing details .