Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A2DB5F

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N283Z · operated by ALPHA TANGO AIRCRAFT LLC

Hex
A2DB5F
Octal
50555537
Decimal
10,672,991
Country
US
Tail
N283Z
Type
P28A
No current signal · last broadcast 9h ago
Flights observed
107
Distinct callsigns
1
Country
US
Last broadcast
9h ago

Last known position

Most recent position reported by Mode-S A2DB5F.

Country allocation

The ICAO 24-bit address A2DB5F 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
CXK349 - 107 2026-07-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 CXK349 FRG → FRG Jul 17, 21:05 UTCJul 17, 23:05 UTC2h 0m
2026-07-17 CXK349 - Jul 17, 18:00 UTCJul 17, 19:49 UTC1h 50m
2026-07-17 CXK349 FRG → FRG Jul 17, 12:04 UTCJul 17, 13:10 UTC1h 5m
2026-07-16 CXK349 FRG → FRG Jul 16, 13:00 UTCJul 16, 14:35 UTC1h 35m
2026-07-14 CXK349 - Jul 14, 15:00 UTCJul 14, 17:05 UTC2h 5m
2026-07-13 CXK349 FRG → FRG Jul 13, 14:45 UTCJul 13, 16:25 UTC1h 40m
2026-07-13 CXK349 - Jul 13, 12:10 UTCJul 13, 12:45 UTC35m
2026-07-13 CXK349 - Jul 13, 09:15 UTCJul 13, 11:00 UTC1h 45m
2026-07-12 CXK349 - Jul 12, 11:50 UTCJul 12, 13:50 UTC2h 0m
2026-07-11 CXK349 FRG → FRG Jul 11, 18:30 UTCJul 11, 20:25 UTC1h 55m
2026-07-11 CXK349 FRG → FRG Jul 11, 16:05 UTCJul 11, 16:55 UTC50m
2026-07-11 CXK349 - Jul 11, 12:00 UTCJul 11, 13:45 UTC1h 45m
2026-07-11 CXK349 - Jul 11, 09:15 UTCJul 11, 10:40 UTC1h 25m
2026-07-10 CXK349 - Jul 10, 11:55 UTCJul 10, 13:10 UTC1h 15m
2026-07-09 CXK349 - Jul 9, 12:50 UTCJul 9, 14:05 UTC1h 15m
2026-07-08 CXK349 FRG → FRG Jul 8, 17:30 UTCJul 8, 19:35 UTC2h 5m
2026-07-08 CXK349 FRG → FRG Jul 8, 09:05 UTCJul 8, 10:20 UTC1h 15m
2026-07-07 CXK349 - Jul 7, 20:00 UTCJul 7, 21:30 UTC1h 30m
2026-07-07 CXK349 - Jul 7, 18:30 UTCJul 7, 19:30 UTC1h 0m
2026-07-04 CXK349 FRG → FRG Jul 4, 12:20 UTCJul 4, 13:30 UTC1h 10m
2026-07-04 CXK349 - Jul 4, 09:05 UTCJul 4, 10:40 UTC1h 35m
2026-07-03 CXK349 - Jul 3, 14:25 UTCJul 3, 15:45 UTC1h 20m
2026-07-03 CXK349 FRG → FRG Jul 3, 11:55 UTCJul 3, 12:55 UTC1h 0m
2026-07-02 CXK349 FRG → FRG Jul 2, 23:15 UTCJul 3, 00:30 UTC1h 15m
2026-07-02 CXK349 - Jul 2, 13:20 UTCJul 2, 16:00 UTC2h 40m
2026-07-01 CXK349 - Jul 1, 19:40 UTCJul 1, 20:55 UTC1h 15m
2026-07-01 CXK349 - Jul 1, 16:35 UTCJul 1, 18:30 UTC1h 55m
2026-06-26 CXK349 - Jun 26, 15:54 UTCJun 26, 17:35 UTC1h 40m
2026-06-25 CXK349 - Jun 25, 20:54 UTCJun 25, 21:20 UTC25m
2026-06-25 CXK349 - Jun 25, 18:04 UTCJun 25, 19:29 UTC1h 25m
2026-06-25 CXK349 - Jun 25, 15:04 UTCJun 25, 16:45 UTC1h 40m
2026-06-24 CXK349 - Jun 24, 22:14 UTCJun 24, 23:54 UTC1h 40m
2026-06-24 CXK349 PNE → PNE Jun 24, 17:59 UTCJun 24, 19:29 UTC1h 30m
2026-06-24 CXK349 - Jun 24, 15:00 UTCJun 24, 16:09 UTC1h 10m
2026-06-22 CXK349 - Jun 22, 14:55 UTCJun 22, 16:14 UTC1h 20m
2026-06-22 CXK349 PNE → PNE Jun 22, 12:00 UTCJun 22, 13:29 UTC1h 30m
2026-06-22 CXK349 - Jun 22, 10:00 UTCJun 22, 10:49 UTC50m
2026-06-21 CXK349 - Jun 21, 20:40 UTCJun 21, 22:15 UTC1h 35m
2026-06-21 CXK349 - Jun 21, 16:10 UTCJun 21, 16:54 UTC45m
2026-06-21 CXK349 PNE → PNE Jun 21, 12:55 UTCJun 21, 14:24 UTC1h 30m
2026-06-21 CXK349 - Jun 21, 10:09 UTCJun 21, 11:30 UTC1h 20m
2026-06-20 CXK349 - Jun 20, 18:24 UTCJun 20, 19:44 UTC1h 20m
2026-06-20 CXK349 - Jun 20, 15:14 UTCJun 20, 17:14 UTC2h 0m
2026-06-20 CXK349 PNE → PNE Jun 20, 10:04 UTCJun 20, 11:49 UTC1h 45m
2026-06-19 CXK349 PNE → PNE Jun 19, 23:44 UTCJun 20, 00:19 UTC35m
2026-06-19 CXK349 - Jun 19, 21:30 UTCJun 19, 22:30 UTC1h 0m
2026-06-19 CXK349 PNE → PNE Jun 19, 13:20 UTCJun 19, 14:44 UTC1h 25m
2026-06-19 CXK349 - Jun 19, 10:24 UTCJun 19, 11:39 UTC1h 15m
2026-06-17 CXK349 PNE → PNE Jun 17, 19:05 UTCJun 17, 19:30 UTC25m
2026-06-17 CXK349 - Jun 17, 13:20 UTCJun 17, 16:00 UTC2h 40m

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

Mode-S A2DB5F frequently asked

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