Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AAF724

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N8052X · CESSNA 172 Skyhawk · operated by LAFAYETTE AERO CLUB INC

Hex
AAF724
Octal
52573444
Decimal
11,204,388
Country
US
Tail
N8052X
Type
C172
No current signal · last broadcast 23d ago
Flights observed
90
Distinct callsigns
1
Country
US
Last broadcast
23d ago

Last known position

Most recent position reported by Mode-S AAF724.

Country allocation

The ICAO 24-bit address AAF724 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
N8052X - 90 2026-07-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-22 N8052X - Jul 22, 00:45 UTCJul 22, 01:25 UTC40m
2026-07-21 N8052X LAF → LAF Jul 21, 15:35 UTCJul 21, 15:55 UTC20m
2026-07-21 N8052X - Jul 21, 14:05 UTCJul 21, 14:45 UTC40m
2026-07-21 N8052X - Jul 21, 13:50 UTCJul 21, 14:00 UTC10m
2026-07-20 N8052X LAF → LAF Jul 20, 11:25 UTCJul 20, 12:15 UTC50m
2026-07-19 N8052X LAF → LAF Jul 19, 13:35 UTCJul 19, 14:50 UTC1h 15m
2026-07-16 N8052X - Jul 16, 20:29 UTCJul 16, 22:00 UTC1h 30m
2026-07-16 N8052X - Jul 16, 17:54 UTCJul 16, 18:34 UTC40m
2026-07-16 N8052X - Jul 16, 15:45 UTCJul 16, 16:15 UTC30m
2026-07-16 N8052X - Jul 16, 14:40 UTCJul 16, 15:14 UTC35m
2026-07-15 N8052X LAF → LAF Jul 15, 20:20 UTCJul 15, 21:45 UTC1h 25m
2026-07-14 N8052X - Jul 14, 18:45 UTCJul 14, 19:20 UTC35m
2026-07-14 N8052X - Jul 14, 17:15 UTCJul 14, 18:10 UTC55m
2026-07-14 N8052X - Jul 14, 15:40 UTCJul 14, 16:20 UTC40m
2026-07-10 N8052X - Jul 10, 19:25 UTCJul 10, 20:20 UTC55m
2026-07-10 N8052X - Jul 10, 18:30 UTCJul 10, 18:50 UTC20m
2026-07-10 N8052X - Jul 10, 16:50 UTCJul 10, 17:25 UTC35m
2026-07-10 N8052X - Jul 10, 15:05 UTCJul 10, 16:05 UTC1h 0m
2026-07-10 N8052X - Jul 10, 13:45 UTCJul 10, 14:20 UTC35m
2026-07-08 N8052X LAF → LAF Jul 8, 00:20 UTCJul 8, 00:40 UTC20m
2026-07-07 N8052X LAF → LAF Jul 7, 23:45 UTCJul 8, 00:10 UTC25m
2026-07-01 N8052X - Jul 1, 14:20 UTCJul 1, 14:55 UTC35m
2026-07-01 N8052X - Jul 1, 13:30 UTCJul 1, 14:15 UTC45m
2026-06-30 N8052X - Jun 30, 18:35 UTCJun 30, 19:10 UTC35m
2026-06-30 N8052X - Jun 30, 16:45 UTCJun 30, 17:55 UTC1h 10m
2026-06-30 N8052X - Jun 30, 15:25 UTCJun 30, 16:00 UTC35m
2026-06-29 N8052X LAF → LAF Jun 29, 14:50 UTCJun 29, 16:10 UTC1h 20m
2026-06-25 N8052X LAF → LAF Jun 25, 19:49 UTCJun 25, 20:25 UTC35m
2026-06-25 N8052X LAF → LAF Jun 25, 19:15 UTCJun 25, 19:44 UTC30m
2026-06-25 N8052X - Jun 25, 15:10 UTCJun 25, 16:55 UTC1h 45m
2026-06-25 N8052X - Jun 25, 13:50 UTCJun 25, 14:29 UTC40m
2026-06-23 N8052X - Jun 23, 19:34 UTCJun 23, 20:15 UTC40m
2026-06-23 N8052X - Jun 23, 16:44 UTCJun 23, 19:04 UTC2h 20m
2026-06-23 N8052X - Jun 23, 13:50 UTCJun 23, 14:49 UTC1h 0m
2026-06-23 N8052X - Jun 23, 13:34 UTCJun 23, 13:45 UTC10m
2026-06-20 N8052X - Jun 20, 15:24 UTCJun 20, 17:14 UTC1h 50m
2026-06-19 N8052X - Jun 19, 22:04 UTCJun 20, 00:09 UTC2h 5m
2026-06-19 N8052X - Jun 19, 19:49 UTCJun 19, 20:19 UTC30m
2026-06-19 N8052X - Jun 19, 19:14 UTCJun 19, 19:45 UTC30m
2026-06-18 N8052X LAF → LAF Jun 18, 23:55 UTCJun 19, 00:05 UTC10m
2026-06-02 N8052X - Jun 2, 16:40 UTCJun 2, 17:15 UTC35m
2026-06-02 N8052X - Jun 2, 14:50 UTCJun 2, 15:05 UTC15m
2026-06-02 N8052X - Jun 2, 13:15 UTCJun 2, 14:40 UTC1h 25m
2026-06-02 N8052X - Jun 2, 12:40 UTCJun 2, 13:10 UTC30m
2026-05-26 N8052X LAF → LAF May 26, 14:09 UTCMay 26, 15:45 UTC1h 35m
2026-05-25 N8052X LAF → LAF May 25, 14:35 UTCMay 25, 15:00 UTC25m
2026-05-23 N8052X LAF → LAF May 23, 19:50 UTCMay 23, 20:35 UTC45m
2026-05-21 N8052X - May 21, 23:25 UTCMay 22, 00:15 UTC50m
2026-05-21 N8052X - May 21, 22:50 UTCMay 21, 23:20 UTC30m
2026-05-14 N8052X - May 14, 23:25 UTCMay 14, 23:35 UTC10m

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

Mode-S AAF724 frequently asked

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