sensors Mode-S transponder

A657AA

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N508AB · LEARJET 60 · operated by LJ60-273 LLC

Hex
A657AA
Octal
51453652
Decimal
10,901,418
Country
US
Tail
N508AB
Type
LJ60
No current signal · last broadcast 11d ago
Flights observed
135
Distinct callsigns
1
Country
US
Last broadcast
11d ago

Last known position

Most recent position reported by Mode-S A657AA.

Country allocation

The ICAO 24-bit address A657AA 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
FTD508 - 135 2026-07-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 FTD508 TPA → BNA Jul 25, 10:45 UTCJul 25, 12:15 UTC1h 30m
2026-07-25 FTD508 BNA → TPA Jul 25, 00:20 UTCJul 25, 01:45 UTC1h 25m
2026-07-24 FTD508 LUK → BNA Jul 24, 07:15 UTCJul 24, 08:00 UTC45m
2026-07-23 FTD508 - Jul 23, 23:30 UTCJul 24, 00:05 UTC35m
2026-07-23 FTD508 - Jul 23, 00:50 UTCJul 23, 02:00 UTC1h 10m
2026-07-22 FTD508 BNA → YIP Jul 22, 21:50 UTCJul 22, 22:55 UTC1h 5m
2026-07-22 FTD508 - Jul 22, 18:50 UTCJul 22, 20:00 UTC1h 10m
2026-07-22 FTD508 - Jul 22, 11:35 UTCJul 22, 12:50 UTC1h 15m
2026-07-21 FTD508 - Jul 21, 03:25 UTCJul 21, 04:35 UTC1h 10m
2026-07-21 FTD508 - Jul 21, 01:20 UTCJul 21, 01:35 UTC15m
2026-07-20 FTD508 BNA → MSY Jul 20, 23:05 UTCJul 21, 00:15 UTC1h 9m
2026-07-18 FTD508 DAL → BNA Jul 18, 07:50 UTCJul 18, 09:20 UTC1h 30m
2026-07-18 FTD508 BNA → DAL Jul 18, 02:40 UTCJul 18, 04:00 UTC1h 21m
2026-07-16 FTD508 PAH → BNA Jul 16, 22:55 UTCJul 16, 23:20 UTC25m
2026-07-16 FTD508 BNA → PAH Jul 16, 15:45 UTCJul 16, 16:09 UTC25m
2026-07-16 FTD508 - Jul 16, 00:30 UTCJul 16, 01:55 UTC1h 25m
2026-07-15 FTD508 BNA → DAL Jul 15, 18:50 UTCJul 15, 20:15 UTC1h 25m
2026-07-15 FTD508 ROA → BNA Jul 15, 00:05 UTCJul 15, 01:05 UTC1h 0m
2026-07-14 FTD508 - Jul 14, 19:20 UTCJul 14, 20:20 UTC1h 0m
2026-07-13 FTD508 - Jul 13, 19:20 UTCJul 13, 20:35 UTC1h 15m
2026-07-13 FTD508 - Jul 13, 13:40 UTCJul 13, 14:50 UTC1h 10m
2026-07-12 FTD508 - Jul 12, 20:30 UTCJul 12, 21:55 UTC1h 25m
2026-07-12 FTD508 - Jul 12, 14:35 UTCJul 12, 15:50 UTC1h 15m
2026-07-11 FTD508 PIE → BNA Jul 11, 21:00 UTCJul 11, 22:35 UTC1h 35m
2026-07-11 FTD508 - Jul 11, 05:01 UTCJul 11, 06:05 UTC1h 5m
2026-07-10 FTD508 - Jul 10, 20:55 UTCJul 10, 22:00 UTC1h 5m
2026-07-10 FTD508 RDU → PIE Jul 10, 18:20 UTCJul 10, 19:50 UTC1h 30m
2026-07-09 FTD508 SRQ → RDU Jul 9, 17:35 UTCJul 9, 19:05 UTC1h 30m
2026-07-09 FTD508 - Jul 9, 16:40 UTCJul 9, 16:55 UTC15m
2026-07-09 FTD508 - Jul 9, 14:25 UTCJul 9, 16:00 UTC1h 35m
2026-07-08 FTD508 - Jul 8, 22:00 UTCJul 8, 22:55 UTC55m
2026-07-08 FTD508 - Jul 8, 19:15 UTCJul 8, 21:10 UTC1h 55m
2026-07-08 FTD508 - Jul 8, 16:00 UTCJul 8, 16:55 UTC55m
2026-07-05 FTD508 - Jul 5, 23:20 UTCJul 5, 23:55 UTC35m
2026-07-04 FTD508 - Jul 4, 18:45 UTCJul 4, 19:50 UTC1h 5m
2026-07-04 FTD508 - Jul 4, 13:50 UTCJul 4, 14:50 UTC1h 0m
2026-07-02 FTD508 - Jul 2, 06:15 UTCJul 2, 09:00 UTC2h 45m
2026-07-01 FTD508 - Jul 1, 22:35 UTCJul 2, 01:45 UTC3h 10m
2026-06-30 FTD508 - Jun 30, 18:55 UTCJun 30, 20:00 UTC1h 5m
2026-06-30 FTD508 - Jun 30, 11:30 UTCJun 30, 12:40 UTC1h 10m
2026-06-29 FTD508 - Jun 29, 22:24 UTCJun 29, 22:55 UTC30m
2026-06-29 FTD508 - Jun 29, 18:19 UTCJun 29, 18:49 UTC30m
2026-06-29 FTD508 - Jun 29, 15:24 UTCJun 29, 16:35 UTC1h 10m
2026-06-28 FTD508 - Jun 28, 17:19 UTCJun 28, 18:29 UTC1h 10m
2026-06-28 FTD508 - Jun 28, 15:14 UTCJun 28, 16:00 UTC45m
2026-06-27 FTD508 - Jun 27, 20:49 UTCJun 27, 22:15 UTC1h 25m
2026-06-27 FTD508 - Jun 27, 17:59 UTCJun 27, 19:05 UTC1h 5m
2026-06-26 FTD508 - Jun 26, 15:34 UTCJun 26, 18:15 UTC2h 40m
2026-06-26 FTD508 - Jun 26, 13:55 UTCJun 26, 14:19 UTC25m
2026-06-24 FTD508 - Jun 24, 22:14 UTCJun 25, 00:44 UTC2h 30m

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

Mode-S A657AA frequently asked

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