sensors Mode-S transponder

AD260E

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N94618 · CESSNA 172 Skyhawk · operated by FLIGHT TRAINER LLC

Hex
AD260E
Octal
53223016
Decimal
11,347,470
Country
US
Tail
N94618
Type
C172
No current signal · last broadcast 3d ago
Flights observed
156
Distinct callsigns
1
Country
US
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S AD260E.

Country allocation

The ICAO 24-bit address AD260E 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
CXK253 - 156 2026-07-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-11 CXK253 HWD → HWD Jul 11, 18:05 UTCJul 11, 18:55 UTC50m
2026-07-11 CXK253 BFL → HWD Jul 11, 00:40 UTCJul 11, 02:55 UTC2h 15m
2026-07-10 CXK253 - Jul 10, 21:20 UTCJul 10, 23:35 UTC2h 15m
2026-07-10 CXK253 - Jul 10, 18:45 UTCJul 10, 19:55 UTC1h 10m
2026-07-09 CXK253 - Jul 9, 23:35 UTCJul 10, 00:10 UTC35m
2026-07-09 CXK253 - Jul 9, 20:45 UTCJul 9, 21:25 UTC40m
2026-07-09 CXK253 - Jul 9, 19:50 UTCJul 9, 20:30 UTC40m
2026-07-09 CXK253 HWD → HWD Jul 9, 19:25 UTCJul 9, 19:35 UTC10m
2026-07-08 CXK253 HWD → HWD Jul 8, 18:40 UTCJul 8, 20:35 UTC1h 55m
2026-07-07 CXK253 HWD → HWD Jul 7, 20:00 UTCJul 7, 22:10 UTC2h 10m
2026-07-07 CXK253 HWD → HWD Jul 7, 00:25 UTCJul 7, 02:00 UTC1h 35m
2026-07-06 CXK253 HWD → HWD Jul 6, 18:25 UTCJul 6, 19:05 UTC40m
2026-07-06 CXK253 HWD → HWD Jul 6, 15:20 UTCJul 6, 17:00 UTC1h 40m
2026-07-03 CXK253 HWD → HWD Jul 3, 23:15 UTCJul 3, 23:25 UTC10m
2026-07-03 CXK253 HWD → HWD Jul 3, 22:50 UTCJul 3, 22:55 UTC5m
2026-07-03 CXK253 HWD → HWD Jul 3, 22:35 UTCJul 3, 22:40 UTC5m
2026-07-03 CXK253 HWD → HWD Jul 3, 22:20 UTCJul 3, 22:30 UTC10m
2026-07-03 CXK253 HWD → HWD Jul 3, 21:55 UTCJul 3, 22:00 UTC5m
2026-07-03 CXK253 HWD → HWD Jul 3, 19:35 UTCJul 3, 19:40 UTC5m
2026-07-03 CXK253 - Jul 3, 18:50 UTCJul 3, 19:00 UTC10m
2026-07-03 CXK253 HWD → HWD Jul 3, 18:35 UTCJul 3, 18:40 UTC5m
2026-07-03 CXK253 HWD → HWD Jul 3, 18:25 UTCJul 3, 18:30 UTC5m
2026-07-02 CXK253 HWD → HWD Jul 2, 22:10 UTCJul 3, 00:10 UTC2h 0m
2026-07-02 CXK253 HWD → HWD Jul 2, 20:30 UTCJul 2, 21:10 UTC40m
2026-07-01 CXK253 - Jul 1, 22:55 UTCJul 2, 00:30 UTC1h 35m
2026-07-01 CXK253 - Jul 1, 21:25 UTCJul 1, 22:00 UTC35m
2026-07-01 CXK253 HWD → LVK Jul 1, 20:30 UTCJul 1, 20:40 UTC10m
2026-07-01 CXK253 HWD → HWD Jul 1, 17:45 UTCJul 1, 19:30 UTC1h 45m
2026-07-01 CXK253 HWD → HWD Jul 1, 14:40 UTCJul 1, 16:30 UTC1h 50m
2026-07-01 CXK253 HWD → HWD Jul 1, 03:05 UTCJul 1, 03:10 UTC5m
2026-06-30 CXK253 HWD → HWD Jun 30, 19:00 UTCJun 30, 19:45 UTC45m
2026-06-30 CXK253 HWD → HWD Jun 30, 15:55 UTCJun 30, 16:05 UTC10m
2026-06-19 CXK253 HWD → HWD Jun 19, 18:05 UTCJun 19, 18:20 UTC15m
2026-06-19 CXK253 HWD → HWD Jun 19, 03:44 UTCJun 19, 03:55 UTC10m
2026-06-19 CXK253 HWD → HWD Jun 19, 03:15 UTCJun 19, 03:20 UTC5m
2026-06-18 CXK253 HWD → HWD Jun 18, 18:05 UTCJun 18, 18:45 UTC40m
2026-06-18 CXK253 HWD → HWD Jun 18, 04:05 UTCJun 18, 04:10 UTC5m
2026-06-18 CXK253 HWD → HWD Jun 18, 03:25 UTCJun 18, 03:40 UTC15m
2026-06-18 CXK253 HWD → HWD Jun 18, 03:10 UTCJun 18, 03:15 UTC5m
2026-06-17 CXK253 HWD → HWD Jun 17, 22:15 UTCJun 17, 23:05 UTC50m
2026-06-17 CXK253 HWD → HWD Jun 17, 20:40 UTCJun 17, 20:45 UTC5m
2026-06-17 CXK253 HWD → HWD Jun 17, 19:25 UTCJun 17, 19:40 UTC15m
2026-06-17 CXK253 HWD → HWD Jun 17, 19:05 UTCJun 17, 19:10 UTC5m
2026-06-17 CXK253 HWD → HWD Jun 17, 03:25 UTCJun 17, 03:35 UTC10m
2026-06-17 CXK253 HWD → HWD Jun 17, 03:00 UTCJun 17, 03:20 UTC20m
2026-06-16 CXK253 HWD → HWD Jun 16, 21:30 UTCJun 16, 22:00 UTC30m
2026-06-16 CXK253 HWD → HWD Jun 16, 19:35 UTCJun 16, 20:15 UTC41m
2026-06-16 CXK253 HWD → HWD Jun 16, 01:04 UTCJun 16, 01:50 UTC45m
2026-06-15 CXK253 HWD → HWD Jun 15, 21:30 UTCJun 15, 22:10 UTC40m
2026-06-15 CXK253 HWD → HWD Jun 15, 19:10 UTCJun 15, 20:15 UTC1h 5m

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

Mode-S AD260E frequently asked

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