sensors Mode-S transponder

A64D16

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N505FX · BOMBARDIER BD-100 Challenger 350 · operated by CWIERNTNIA MATTHEW DOW, GRAVES SCOTT, CHALLENGER 350 2019 LLC, FORD KEVIN TRUSTEE, FORD CELESTE TRUSTEE, BLUE LAKE LLC

Hex
A64D16
Octal
51446426
Decimal
10,898,710
Country
US
Tail
N505FX
Type
CL35
No current signal · last broadcast 8h ago
Flights observed
109
Distinct callsigns
1
Country
US
Last broadcast
8h ago

Last known position

Most recent position reported by Mode-S A64D16.

Country allocation

The ICAO 24-bit address A64D16 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
LXJ505 - 109 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 LXJ505 - May 29, 20:55 UTCMay 29, 21:20 UTC25m
2026-05-29 LXJ505 - May 29, 15:10 UTCMay 29, 20:05 UTC4h 55m
2026-05-28 LXJ505 - May 28, 23:15 UTCMay 28, 23:40 UTC25m
2026-05-28 LXJ505 - May 28, 15:40 UTCMay 28, 22:25 UTC6h 45m
2026-05-27 LXJ505 - May 27, 20:30 UTCMay 27, 23:45 UTC3h 15m
2026-05-27 LXJ505 - May 27, 18:15 UTCMay 27, 18:35 UTC20m
2026-05-26 LXJ505 - May 26, 15:09 UTCMay 26, 15:45 UTC35m
2026-05-25 LXJ505 TEB → MDW May 25, 21:09 UTCMay 25, 23:10 UTC2h 0m
2026-05-25 LXJ505 - May 25, 17:05 UTCMay 25, 19:30 UTC2h 24m
2026-05-25 LXJ505 - May 25, 14:15 UTCMay 25, 14:50 UTC35m
2026-05-23 LXJ505 - May 23, 20:40 UTCMay 23, 21:35 UTC55m
2026-05-23 LXJ505 - May 23, 17:20 UTCMay 23, 18:00 UTC40m
2026-05-23 LXJ505 - May 23, 13:50 UTCMay 23, 14:40 UTC50m
2026-05-22 LXJ505 - May 22, 22:40 UTCMay 23, 00:30 UTC1h 50m
2026-05-22 LXJ505 - May 22, 19:55 UTCMay 22, 21:45 UTC1h 50m
2026-05-22 LXJ505 - May 22, 17:35 UTCMay 22, 18:30 UTC55m
2026-05-22 LXJ505 - May 22, 05:00 UTCMay 22, 05:30 UTC30m
2026-05-22 LXJ505 TEB → SRQ May 22, 01:25 UTCMay 22, 03:50 UTC2h 25m
2026-05-21 LXJ505 - May 21, 22:55 UTCMay 21, 23:30 UTC35m
2026-05-21 LXJ505 - May 21, 20:05 UTCMay 21, 21:50 UTC1h 45m
2026-05-20 LXJ505 - May 20, 18:55 UTCMay 20, 20:55 UTC2h 0m
2026-05-20 LXJ505 - May 20, 14:45 UTCMay 20, 17:50 UTC3h 5m
2026-05-20 LXJ505 - May 20, 13:15 UTCMay 20, 13:55 UTC40m
2026-05-19 LXJ505 - May 19, 21:10 UTCMay 19, 23:30 UTC2h 20m
2026-05-19 LXJ505 ORL → FMY May 19, 19:25 UTCMay 19, 20:00 UTC35m
2026-05-19 LXJ505 - May 19, 13:50 UTCMay 19, 15:45 UTC1h 55m
2026-05-19 LXJ505 - May 19, 01:15 UTCMay 19, 01:30 UTC15m
2026-05-18 LXJ505 SFO → STL May 18, 20:55 UTCMay 19, 00:20 UTC3h 25m
2026-05-18 LXJ505 - May 18, 17:30 UTCMay 18, 19:15 UTC1h 44m
2026-05-17 LXJ505 IND → BFI May 17, 15:10 UTCMay 18, 02:15 UTC11h 5m
2026-05-16 LXJ505 - May 16, 20:30 UTCMay 16, 22:45 UTC2h 15m
2026-05-16 LXJ505 - May 16, 17:01 UTCMay 16, 19:25 UTC2h 25m
2026-05-16 LXJ505 - May 16, 15:16 UTCMay 16, 16:05 UTC50m
2026-05-16 LXJ505 IAD → MDW May 16, 12:25 UTCMay 16, 13:51 UTC1h 25m
2026-05-15 LXJ505 - May 15, 18:20 UTCMay 15, 20:20 UTC2h 0m
2026-05-15 LXJ505 - May 15, 16:40 UTCMay 15, 17:10 UTC30m
2026-05-14 LXJ505 TEB → MIA May 14, 20:45 UTCMay 14, 23:15 UTC2h 30m
2026-05-14 LXJ505 - May 14, 14:10 UTCMay 14, 17:20 UTC3h 10m
2026-05-14 LXJ505 - May 14, 11:50 UTCMay 14, 12:20 UTC30m
2026-05-13 LXJ505 - May 13, 22:20 UTCMay 13, 22:50 UTC30m
2026-05-13 LXJ505 AUS → DAL May 13, 14:20 UTCMay 13, 21:10 UTC6h 50m
2026-05-13 LXJ505 - May 13, 12:05 UTCMay 13, 12:35 UTC30m
2026-05-12 LXJ505 AUS → DAL May 12, 20:30 UTCMay 12, 21:10 UTC40m
2026-05-12 LXJ505 LRD → AUS May 12, 18:55 UTCMay 12, 19:35 UTC40m
2026-05-11 LXJ505 - May 11, 20:45 UTCMay 11, 22:10 UTC1h 25m
2026-05-11 LXJ505 - May 11, 18:15 UTCMay 11, 18:50 UTC35m
2026-05-10 LXJ505 - May 10, 16:59 UTCMay 10, 18:35 UTC1h 35m
2026-05-09 LXJ505 - May 9, 03:30 UTCMay 9, 05:35 UTC2h 5m
2026-05-09 LXJ505 - May 9, 00:10 UTCMay 9, 01:30 UTC1h 20m
2026-05-08 LXJ505 - May 8, 02:44 UTCMay 8, 05:05 UTC2h 20m

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

Mode-S A64D16 frequently asked

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