Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A6583B

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N508FX · BOMBARDIER BD-100 Challenger 350 · operated by FLEXJET LLC, TREVISO LLC, LEDIC LLC, KOENIGSBAUER KIRK, BOB TOMES FORD INC, DFI TRAVEL LLC

Hex
A6583B
Octal
51454073
Decimal
10,901,563
Country
US
Tail
N508FX
Type
CL35
No current signal · last broadcast Jul 26, 22:45 UTC
Flights observed
165
Distinct callsigns
1
Country
US
Last broadcast
Jul 26, 22:45 UTC

Last known position

Most recent position reported by Mode-S A6583B.

Country allocation

The ICAO 24-bit address A6583B 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
LXJ508 - 165 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 LXJ508 - Jul 26, 22:15 UTCJul 26, 22:45 UTC30m
2026-07-26 LXJ508 - Jul 26, 15:50 UTCJul 26, 21:20 UTC5h 30m
2026-07-26 LXJ508 LUK → TEB Jul 26, 13:35 UTCJul 26, 15:05 UTC1h 30m
2026-07-25 LXJ508 BLM → LUK Jul 25, 22:20 UTCJul 25, 23:50 UTC1h 30m
2026-07-25 LXJ508 - Jul 25, 20:05 UTCJul 25, 20:50 UTC45m
2026-07-25 LXJ508 - Jul 25, 15:20 UTCJul 25, 18:30 UTC3h 10m
2026-07-25 LXJ508 SDM → DAL Jul 25, 00:10 UTCJul 25, 02:50 UTC2h 40m
2026-07-24 LXJ508 RST → SDM Jul 24, 20:00 UTCJul 24, 23:15 UTC3h 15m
2026-07-24 LXJ508 - Jul 24, 16:25 UTCJul 24, 18:25 UTC2h 0m
2026-07-20 LXJ508 - Jul 20, 19:20 UTCJul 20, 20:25 UTC1h 5m
2026-07-20 LXJ508 OAK → SJC Jul 20, 18:15 UTCJul 20, 18:35 UTC20m
2026-07-20 LXJ508 - Jul 20, 15:30 UTCJul 20, 17:00 UTC1h 30m
2026-07-20 LXJ508 - Jul 20, 11:45 UTCJul 20, 13:40 UTC1h 55m
2026-07-19 LXJ508 - Jul 19, 20:30 UTCJul 19, 21:40 UTC1h 10m
2026-07-19 LXJ508 - Jul 19, 19:30 UTCJul 19, 19:50 UTC20m
2026-07-19 LXJ508 - Jul 19, 16:15 UTCJul 19, 18:30 UTC2h 15m
2026-07-19 LXJ508 - Jul 19, 13:30 UTCJul 19, 14:10 UTC40m
2026-07-18 LXJ508 - Jul 18, 21:20 UTCJul 19, 00:45 UTC3h 25m
2026-07-18 LXJ508 - Jul 18, 13:35 UTCJul 18, 14:55 UTC1h 20m
2026-07-17 LXJ508 - Jul 17, 19:30 UTCJul 17, 21:55 UTC2h 25m
2026-07-17 LXJ508 - Jul 17, 16:59 UTCJul 17, 17:35 UTC35m
2026-07-17 LXJ508 - Jul 17, 14:24 UTCJul 17, 15:00 UTC35m
2026-07-17 LXJ508 - Jul 17, 12:04 UTCJul 17, 13:20 UTC1h 15m
2026-07-16 LXJ508 - Jul 16, 21:55 UTCJul 16, 22:45 UTC50m
2026-07-16 LXJ508 - Jul 16, 16:55 UTCJul 16, 18:59 UTC2h 5m
2026-07-15 LXJ508 - Jul 15, 20:50 UTCJul 16, 18:59 UTC22h 10m
2026-07-15 LXJ508 - Jul 15, 18:50 UTCJul 16, 18:44 UTC23h 55m
2026-07-15 LXJ508 - Jul 15, 16:55 UTCJul 15, 21:00 UTC4h 5m
2026-07-15 LXJ508 - Jul 15, 13:40 UTCJul 15, 15:00 UTC1h 20m
2026-07-15 LXJ508 - Jul 15, 11:10 UTCJul 15, 12:10 UTC1h 0m
2026-07-14 LXJ508 - Jul 14, 21:10 UTCJul 14, 22:05 UTC55m
2026-07-14 LXJ508 BOS → YYZ Jul 14, 01:10 UTCJul 14, 02:20 UTC1h 10m
2026-07-13 LXJ508 PHL → BOS Jul 13, 22:15 UTCJul 13, 23:25 UTC1h 10m
2026-07-13 LXJ508 - Jul 13, 20:10 UTCJul 13, 21:05 UTC55m
2026-07-13 LXJ508 PIE → CLE Jul 13, 01:50 UTCJul 13, 03:55 UTC2h 5m
2026-07-12 LXJ508 ADS → PIE Jul 12, 23:00 UTCJul 13, 01:01 UTC2h 0m
2026-07-12 LXJ508 - Jul 12, 18:25 UTCJul 12, 21:30 UTC3h 5m
2026-07-11 LXJ508 - Jul 11, 18:50 UTCJul 12, 18:45 UTC23h 55m
2026-07-11 LXJ508 - Jul 11, 16:25 UTCJul 11, 19:05 UTC2h 40m
2026-07-11 LXJ508 - Jul 11, 13:55 UTCJul 11, 15:15 UTC1h 20m
2026-07-10 LXJ508 - Jul 10, 15:30 UTCJul 10, 18:05 UTC2h 35m
2026-07-10 LXJ508 SUS → DFW Jul 10, 13:15 UTCJul 10, 14:35 UTC1h 20m
2026-07-09 LXJ508 LAS → SUS Jul 9, 21:50 UTCJul 10, 00:35 UTC2h 45m
2026-07-08 LXJ508 - Jul 8, 18:50 UTCJul 8, 19:35 UTC45m
2026-07-07 LXJ508 - Jul 7, 23:30 UTCJul 7, 23:55 UTC25m
2026-07-07 LXJ508 - Jul 7, 19:35 UTCJul 7, 21:45 UTC2h 10m
2026-07-07 LXJ508 - Jul 7, 16:55 UTCJul 7, 18:20 UTC1h 25m
2026-07-06 LXJ508 - Jul 6, 23:55 UTCJul 7, 02:40 UTC2h 45m
2026-07-06 LXJ508 - Jul 6, 22:35 UTCJul 6, 23:15 UTC40m
2026-07-06 LXJ508 - Jul 6, 14:10 UTCJul 6, 20:00 UTC5h 50m

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

Mode-S A6583B frequently asked

What is Mode-S code A6583B?
A6583B is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N508FX.
Where is Mode-S A6583B registered?
Mode-S code A6583B 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 A6583B broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 22:45 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A6583B, octal 51454073, decimal 10,901,563.
What flights does A6583B operate?
Mode-S A6583B has broadcast 1 distinct callsign, including LXJ508.