sensors Mode-S transponder

A8BF72

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N663AV · operated by CIRRUS DESIGN CORP

Hex
A8BF72
Octal
52137562
Decimal
11,059,058
Country
US
Tail
N663AV
Type
SR20
No current signal · last broadcast 1h ago
Flights observed
144
Distinct callsigns
1
Country
US
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S A8BF72.

Country allocation

The ICAO 24-bit address A8BF72 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 1 distinct

Callsign Airline Flights Last seen
VAR663 - 144 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 VAR663 - Jul 14, 17:45 UTCJul 14, 18:30 UTC45m
2026-07-12 VAR663 GYR → GYR Jul 12, 21:10 UTCJul 12, 21:25 UTC15m
2026-07-11 VAR663 GYR → GYR Jul 11, 21:10 UTCJul 11, 22:30 UTC1h 20m
2026-07-11 VAR663 GYR → GYR Jul 11, 00:50 UTCJul 11, 03:15 UTC2h 25m
2026-07-10 VAR663 GYR → GYR Jul 10, 16:45 UTCJul 10, 18:05 UTC1h 20m
2026-07-09 VAR663 VGT → GYR Jul 9, 05:35 UTCJul 9, 07:20 UTC1h 45m
2026-07-09 VAR663 - Jul 9, 04:05 UTCJul 9, 04:45 UTC40m
2026-07-09 VAR663 - Jul 9, 02:40 UTCJul 9, 03:20 UTC40m
2026-07-08 VAR663 GYR → GYR Jul 8, 21:55 UTCJul 9, 00:15 UTC2h 20m
2026-07-08 VAR663 GYR → GYR Jul 8, 17:50 UTCJul 8, 19:00 UTC1h 10m
2026-07-08 VAR663 GYR → GYR Jul 8, 14:10 UTCJul 8, 16:10 UTC2h 0m
2026-07-07 VAR663 GYR → GYR Jul 7, 23:05 UTCJul 8, 00:55 UTC1h 50m
2026-07-07 VAR663 GYR → GYR Jul 7, 19:40 UTCJul 7, 20:50 UTC1h 10m
2026-07-07 VAR663 HII → GYR Jul 7, 16:35 UTCJul 7, 17:55 UTC1h 20m
2026-07-07 VAR663 GYR → HII Jul 7, 15:20 UTCJul 7, 16:30 UTC1h 10m
2026-07-07 VAR663 GYR → GYR Jul 7, 01:05 UTCJul 7, 02:05 UTC1h 0m
2026-07-06 VAR663 - Jul 6, 20:35 UTCJul 6, 22:10 UTC1h 35m
2026-07-03 VAR663 GYR → GYR Jul 3, 15:30 UTCJul 3, 17:20 UTC1h 50m
2026-07-03 VAR663 GYR → GYR Jul 3, 01:15 UTCJul 3, 03:15 UTC2h 0m
2026-07-02 VAR663 GYR → GYR Jul 2, 16:10 UTCJul 2, 17:50 UTC1h 40m
2026-07-01 VAR663 GYR → GYR Jul 1, 23:00 UTCJul 2, 00:20 UTC1h 20m
2026-07-01 VAR663 GYR → GYR Jul 1, 19:20 UTCJul 1, 20:30 UTC1h 10m
2026-07-01 VAR663 GYR → GYR Jul 1, 15:35 UTCJul 1, 17:00 UTC1h 25m
2026-06-30 VAR663 GYR → GYR Jun 30, 16:50 UTCJun 30, 18:50 UTC2h 0m
2026-06-29 VAR663 GYR → GYR Jun 29, 19:05 UTCJun 29, 20:54 UTC1h 50m
2026-06-29 VAR663 GYR → GYR Jun 29, 14:50 UTCJun 29, 17:10 UTC2h 20m
2026-06-27 VAR663 - Jun 27, 00:10 UTCJun 27, 00:20 UTC10m
2026-06-26 VAR663 GYR → BXK Jun 26, 17:19 UTCJun 26, 18:04 UTC45m
2026-06-26 VAR663 GYR → GYR Jun 26, 00:35 UTCJun 26, 02:40 UTC2h 5m
2026-06-25 VAR663 GYR → GYR Jun 25, 21:35 UTCJun 25, 23:19 UTC1h 45m
2026-06-25 VAR663 GYR → GYR Jun 25, 17:09 UTCJun 25, 18:50 UTC1h 40m
2026-06-24 VAR663 GYR → GYR Jun 24, 21:54 UTCJun 24, 23:45 UTC1h 50m
2026-06-24 VAR663 GYR → GYR Jun 24, 16:24 UTCJun 24, 17:55 UTC1h 30m
2026-06-23 VAR663 GYR → GYR Jun 23, 14:19 UTCJun 23, 15:09 UTC50m
2026-06-23 VAR663 - Jun 23, 04:19 UTCJun 23, 05:39 UTC1h 20m
2026-06-23 VAR663 - Jun 23, 03:25 UTCJun 23, 03:39 UTC15m
2026-06-23 VAR663 - Jun 23, 02:09 UTCJun 23, 02:55 UTC45m
2026-06-22 VAR663 - Jun 22, 22:44 UTCJun 23, 00:24 UTC1h 40m
2026-06-22 VAR663 GYR → GYR Jun 22, 17:50 UTCJun 22, 19:34 UTC1h 45m
2026-06-22 VAR663 GYR → GYR Jun 22, 14:34 UTCJun 22, 16:10 UTC1h 35m
2026-06-20 VAR663 GYR → GYR Jun 20, 14:35 UTCJun 20, 16:05 UTC1h 30m
2026-06-19 VAR663 GYR → GYR Jun 19, 23:29 UTCJun 20, 01:09 UTC1h 40m
2026-06-19 VAR663 GYR → GYR Jun 19, 18:05 UTCJun 19, 19:09 UTC1h 5m
2026-06-19 VAR663 GYR → GYR Jun 19, 15:14 UTCJun 19, 16:14 UTC1h 0m
2026-06-19 VAR663 GYR → GYR Jun 19, 12:49 UTCJun 19, 14:15 UTC1h 25m
2026-06-19 VAR663 GYR → GYR Jun 19, 03:55 UTCJun 19, 05:59 UTC2h 5m
2026-06-18 VAR663 GYR → GYR Jun 18, 22:55 UTCJun 19, 01:10 UTC2h 14m
2026-06-18 VAR663 GYR → GYR Jun 18, 19:55 UTCJun 18, 21:05 UTC1h 10m
2026-06-18 VAR663 GYR → GYR Jun 18, 16:55 UTCJun 18, 17:55 UTC1h 0m
2026-06-18 VAR663 GYR → GYR Jun 18, 14:10 UTCJun 18, 15:35 UTC1h 25m

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

Mode-S A8BF72 frequently asked

What is Mode-S code A8BF72?
A8BF72 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N663AV.
Where is Mode-S A8BF72 registered?
Mode-S code A8BF72 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 A8BF72 broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A8BF72, octal 52137562, decimal 11,059,058.
What flights does A8BF72 operate?
Mode-S A8BF72 has broadcast 1 distinct callsign, including VAR663.