sensors Mode-S transponder

AD763B

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N976AV · AIRBUS A-320neo · operated by BANK OF UTAH TRUSTEE

Hex
AD763B
Octal
53273073
Decimal
11,367,995
Country
US
Tail
N976AV
Type
A20N
Broadcasting now · callsign TAI553 · 37,050 ft
Flights observed
269
Distinct callsigns
20
Country
US
Last broadcast
1h ago

Current position

AD763B is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address AD763B 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
TAI562 - 9 2026-07-03
TAI325 - 8 2026-07-13
TAI324 - 8 2026-07-13
TAI430 - 7 2026-07-04
TAI563 - 6 2026-07-03
LRC641 - 6 2026-07-09
LRC640 - 6 2026-07-08
LRC605 - 6 2026-07-09
LRC604 - 6 2026-07-09
TAI583 Avianca El Salvador 5 2026-04-20
TAI582 Avianca El Salvador 5 2026-04-20
TAI529 - 5 2026-06-21
TAI528 - 5 2026-06-21
LRC634 - 5 2026-07-05
AVA242 Avianca - Aerovias Nacionales de Colombia, S.A. 5 2026-05-24
TAI523 Avianca El Salvador 4 2026-06-21
TAI522 - 4 2026-06-21
TAI424 - 4 2026-06-16
LRC699 - 4 2026-07-09
LRC646 - 4 2026-06-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAI553 - Jul 14, 15:10 UTCJul 14, 16:45 UTC1h 35m
2026-07-14 TAI552 - Jul 14, 07:15 UTCJul 14, 12:25 UTC5h 10m
2026-07-14 TAI578 - Jul 14, 04:30 UTCJul 14, 04:50 UTC20m
2026-07-13 TAI325 - Jul 13, 21:35 UTCJul 14, 02:10 UTC4h 35m
2026-07-13 TAI324 - Jul 13, 14:35 UTCJul 13, 19:00 UTC4h 25m
2026-07-10 TAI329 - Jul 10, 20:45 UTCJul 11, 01:25 UTC4h 40m
2026-07-10 TAI328 BOG → YUL Jul 10, 04:05 UTCJul 10, 18:30 UTC14h 25m
2026-07-09 LRC699 - Jul 9, 23:25 UTCJul 9, 23:55 UTC30m
2026-07-09 LRC605 - Jul 9, 18:30 UTCJul 9, 20:35 UTC2h 5m
2026-07-09 LRC604 - Jul 9, 03:50 UTCJul 9, 16:10 UTC12h 20m
2026-07-09 LRC641 - Jul 9, 02:05 UTCJul 9, 02:20 UTC15m
2026-07-08 LRC641 - Jul 8, 21:55 UTCJul 9, 01:30 UTC3h 35m
2026-07-08 LRC640 GUA → LAX Jul 8, 15:00 UTCJul 8, 19:45 UTC4h 45m
2026-07-08 LRC650 - Jul 8, 12:05 UTCJul 8, 13:05 UTC1h 0m
2026-07-07 LRC699 - Jul 7, 23:35 UTCJul 8, 00:00 UTC25m
2026-07-07 LRC605 - Jul 7, 18:25 UTCJul 7, 18:55 UTC30m
2026-07-07 LRC604 - Jul 7, 14:00 UTCJul 7, 16:10 UTC2h 10m
2026-07-05 LRC634 - Jul 5, 09:30 UTCJul 5, 14:50 UTC5h 20m
2026-07-05 LRC635 - Jul 5, 03:00 UTCJul 5, 07:20 UTC4h 20m
2026-07-04 LRC633 - Jul 4, 19:15 UTCJul 4, 21:00 UTC1h 45m
2026-07-04 TAI430 - Jul 4, 15:00 UTCJul 4, 16:50 UTC1h 50m
2026-07-03 TAI563 - Jul 3, 21:40 UTCJul 4, 02:40 UTC5h 0m
2026-07-03 TAI562 - Jul 3, 14:05 UTCJul 3, 19:35 UTC5h 30m
2026-07-03 TAI561 - Jul 3, 07:15 UTCJul 3, 12:10 UTC4h 55m
2026-07-02 TAI560 - Jul 2, 23:50 UTCJul 3, 05:20 UTC5h 30m
2026-07-02 LRC651 - Jul 2, 03:35 UTCJul 2, 04:05 UTC30m
2026-07-01 LRC641 LAX → GUA Jul 1, 21:50 UTCJul 2, 02:15 UTC4h 25m
2026-07-01 LRC640 GUA → LAX Jul 1, 15:05 UTCJul 1, 19:55 UTC4h 50m
2026-07-01 LRC641 LAX → GUA Jul 1, 03:40 UTCJul 1, 13:15 UTC9h 35m
2026-06-30 LRC641 LAX → GUA Jun 30, 21:50 UTCJul 1, 02:10 UTC4h 20m
2026-06-30 LRC640 - Jun 30, 15:00 UTCJun 30, 19:35 UTC4h 35m
2026-06-30 LRC640 - Jun 30, 12:40 UTCJun 30, 13:05 UTC25m
2026-06-29 TAI563 - Jun 29, 22:00 UTCJun 30, 03:00 UTC5h 1m
2026-06-29 TAI562 - Jun 29, 14:14 UTCJun 29, 19:39 UTC5h 25m
2026-06-29 TAI561 - Jun 29, 07:34 UTCJun 29, 12:29 UTC4h 55m
2026-06-28 TAI560 - Jun 28, 23:44 UTCJun 29, 05:04 UTC5h 20m
2026-06-28 TAI557 LAX → GUA Jun 28, 20:39 UTCJun 28, 20:54 UTC15m
2026-06-28 TAI557 LAX → GUA Jun 28, 14:34 UTCJun 28, 18:59 UTC4h 25m
2026-06-28 TAI556 SAL → OAK Jun 28, 07:54 UTCJun 28, 12:35 UTC4h 40m
2026-06-28 TAI556 SAL → OAK Jun 28, 05:40 UTCJun 28, 06:00 UTC20m
2026-06-27 TAI527 LAS → SAL Jun 27, 22:20 UTCJun 28, 02:39 UTC4h 20m
2026-06-27 TAI526 SAL → LAS Jun 27, 15:14 UTCJun 27, 19:49 UTC4h 35m
2026-06-26 TAI369 - Jun 26, 16:05 UTCJun 26, 20:59 UTC4h 55m
2026-06-26 TAI531 - Jun 26, 07:14 UTCJun 26, 11:40 UTC4h 25m
2026-06-25 TAI530 - Jun 25, 23:59 UTCJun 26, 04:30 UTC4h 30m
2026-06-25 TAI311 - Jun 25, 20:05 UTCJun 25, 22:04 UTC2h 0m
2026-06-25 TAI396 - Jun 25, 15:34 UTCJun 25, 17:30 UTC1h 55m
2026-06-25 TAI591 - Jun 25, 08:14 UTCJun 25, 11:59 UTC3h 45m
2026-06-25 TAI590 - Jun 25, 02:35 UTCJun 25, 06:20 UTC3h 45m
2026-06-24 TAI431 - Jun 24, 23:04 UTCJun 25, 00:40 UTC1h 35m

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 N976AV page for operator, model, and routing details .

Mode-S AD763B frequently asked

What is Mode-S code AD763B?
AD763B is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N976AV.
Where is Mode-S AD763B registered?
Mode-S code AD763B is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is AD763B broadcasting right now?
Yes. Mode-S AD763B is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AD763B, octal 53273073, decimal 11,367,995.
What flights does AD763B operate?
Mode-S AD763B has broadcast 20 distinct callsigns, including TAI562, TAI325, TAI324, TAI430, TAI563.