sensors Mode-S transponder

A7F28D

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N611AZ · BOMBARDIER CL-600 Challenger · operated by PALOMA & JOAN LLC

Hex
A7F28D
Octal
51771215
Decimal
11,006,605
Country
US
Tail
N611AZ
Type
CL60
No current signal · last broadcast 2d ago
Flights observed
69
Distinct callsigns
2
Country
US
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S A7F28D.

Country allocation

The ICAO 24-bit address A7F28D 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

Callsign Airline Flights Last seen
JTL611 Jetall Holdings 63 2026-07-26
N611AZ - 6 2026-07-19

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 JTL611 SUA → ILG Jul 26, 19:00 UTCJul 26, 21:15 UTC2h 15m
2026-07-25 JTL611 SUA → ILG Jul 25, 22:10 UTCJul 25, 23:55 UTC1h 45m
2026-07-25 JTL611 SUA → ILG Jul 25, 15:50 UTCJul 25, 21:10 UTC5h 20m
2026-07-25 JTL611 - Jul 25, 13:00 UTCJul 25, 13:40 UTC40m
2026-07-19 JTL611 BGR → ILG Jul 19, 16:10 UTCJul 19, 17:35 UTC1h 25m
2026-07-19 N611AZ - Jul 19, 08:50 UTCJul 19, 15:50 UTC7h 0m
2026-07-17 N611AZ VLC → MAD Jul 17, 10:15 UTCJul 17, 11:00 UTC45m
2026-07-16 N611AZ - Jul 16, 13:25 UTCJul 16, 13:49 UTC25m
2026-07-16 N611AZ - Jul 16, 10:55 UTCJul 16, 12:05 UTC1h 10m
2026-07-11 N611AZ DUB → TLS Jul 11, 11:00 UTCJul 11, 12:45 UTC1h 45m
2026-07-10 N611AZ - Jul 10, 11:15 UTCJul 10, 17:30 UTC6h 15m
2026-07-06 JTL611 - Jul 6, 22:00 UTCJul 6, 23:45 UTC1h 45m
2026-07-06 JTL611 - Jul 6, 18:25 UTCJul 6, 21:25 UTC3h 0m
2026-07-06 JTL611 - Jul 6, 16:05 UTCJul 6, 16:25 UTC20m
2026-07-05 JTL611 TEB → PVU Jul 5, 21:25 UTCJul 6, 01:50 UTC4h 25m
2026-07-05 JTL611 - Jul 5, 17:05 UTCJul 5, 18:30 UTC1h 25m
2026-07-05 JTL611 - Jul 5, 14:40 UTCJul 5, 16:00 UTC1h 20m
2026-07-01 JTL611 - Jul 1, 22:15 UTCJul 1, 23:25 UTC1h 10m
2026-07-01 JTL611 - Jul 1, 19:15 UTCJul 1, 21:40 UTC2h 25m
2026-07-01 JTL611 - Jul 1, 16:45 UTCJul 1, 17:00 UTC15m
2026-07-01 JTL611 - Jul 1, 13:55 UTCJul 1, 16:05 UTC2h 10m
2026-06-30 JTL611 - Jun 30, 18:35 UTCJun 30, 19:30 UTC55m
2026-06-29 JTL611 - Jun 29, 16:00 UTCJun 29, 19:24 UTC3h 25m
2026-06-28 JTL611 - Jun 28, 20:39 UTCJun 28, 22:20 UTC1h 40m
2026-06-28 JTL611 - Jun 28, 16:25 UTCJun 28, 19:40 UTC3h 15m
2026-06-28 JTL611 - Jun 28, 13:45 UTCJun 28, 14:09 UTC25m
2026-06-22 JTL611 SUA → ILG Jun 22, 17:25 UTCJun 22, 19:19 UTC1h 55m
2026-06-22 JTL611 SUA → ILG Jun 22, 13:49 UTCJun 22, 16:50 UTC3h 0m
2026-06-22 JTL611 SUA → ILG Jun 22, 12:00 UTCJun 22, 12:40 UTC40m
2026-06-21 JTL611 SUA → ILG Jun 21, 18:10 UTCJun 21, 20:40 UTC2h 30m
2026-06-21 JTL611 SUA → ILG Jun 21, 14:05 UTCJun 21, 15:19 UTC1h 15m
2026-06-21 JTL611 SUA → ILG Jun 21, 11:49 UTCJun 21, 12:24 UTC35m
2026-06-19 JTL611 SUA → ILG Jun 19, 16:34 UTCJun 19, 20:24 UTC3h 50m
2026-06-18 JTL611 SUA → ILG Jun 18, 11:55 UTCJun 18, 16:05 UTC4h 10m
2026-06-17 JTL611 SUA → ILG Jun 17, 20:50 UTCJun 17, 22:55 UTC2h 5m
2026-06-17 JTL611 SUA → ILG Jun 17, 17:05 UTCJun 17, 19:40 UTC2h 35m
2026-06-17 JTL611 SUA → ILG Jun 17, 15:10 UTCJun 17, 15:46 UTC35m
2026-06-15 JTL611 SUA → ILG Jun 15, 14:15 UTCJun 15, 15:15 UTC1h 0m
2026-06-14 JTL611 SUA → ILG Jun 14, 19:25 UTCJun 14, 21:10 UTC1h 45m
2026-06-14 JTL611 SUA → ILG Jun 14, 14:10 UTCJun 14, 18:50 UTC4h 40m
2026-06-14 JTL611 SUA → ILG Jun 14, 12:25 UTCJun 14, 13:05 UTC40m
2026-06-12 JTL611 SUA → ILG Jun 12, 18:01 UTCJun 12, 18:55 UTC55m
2026-06-11 JTL611 SUA → ILG Jun 11, 12:55 UTCJun 11, 14:00 UTC1h 5m
2026-05-22 JTL611 SUA → ILG May 22, 23:35 UTCMay 23, 00:30 UTC55m
2026-05-22 JTL611 SUA → ILG May 22, 21:25 UTCMay 22, 23:00 UTC1h 35m
2026-05-22 JTL611 SUA → ILG May 22, 17:35 UTCMay 22, 19:20 UTC1h 45m
2026-05-21 JTL611 SUA → ILG May 21, 23:40 UTCMay 22, 01:00 UTC1h 20m
2026-05-21 JTL611 SUA → ILG May 21, 20:45 UTCMay 21, 23:10 UTC2h 25m
2026-05-21 JTL611 SUA → ILG May 21, 17:40 UTCMay 21, 18:25 UTC45m
2026-05-20 JTL611 SUA → ILG May 20, 22:05 UTCMay 21, 01:15 UTC3h 10m

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

Mode-S A7F28D frequently asked

What is Mode-S code A7F28D?
A7F28D is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N611AZ.
Where is Mode-S A7F28D registered?
Mode-S code A7F28D 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 A7F28D broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A7F28D, octal 51771215, decimal 11,006,605.
What flights does A7F28D operate?
Mode-S A7F28D has broadcast 2 distinct callsigns, including JTL611, N611AZ.