Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A5F852

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N484JW · operated by AIMS COMMUNITY COLLEGE

Hex
A5F852
Octal
51374122
Decimal
10,877,010
Country
US
Tail
N484JW
Type
P28A
Broadcasting now · callsign RTY484 · 4,500 ft
Flights observed
197
Distinct callsigns
1
Country
US
Last broadcast
1h ago

Current position

A5F852 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address A5F852 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
RTY484 - 197 2026-07-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 RTY484 FNL → FNL Jul 18, 14:25 UTCJul 18, 15:40 UTC1h 15m
2026-07-18 RTY484 FNL → FNL Jul 18, 12:40 UTCJul 18, 13:25 UTC45m
2026-07-17 RTY484 FNL → FNL Jul 17, 18:00 UTCJul 17, 19:09 UTC1h 10m
2026-07-17 RTY484 FNL → FNL Jul 17, 15:40 UTCJul 17, 16:44 UTC1h 5m
2026-07-17 RTY484 FNL → FNL Jul 17, 13:29 UTCJul 17, 14:15 UTC45m
2026-07-16 RTY484 FNL → FNL Jul 16, 17:30 UTCJul 16, 18:50 UTC1h 20m
2026-07-16 RTY484 FNL → FNL Jul 16, 15:10 UTCJul 16, 16:05 UTC55m
2026-07-10 RTY484 FNL → FNL Jul 10, 14:55 UTCJul 10, 16:15 UTC1h 20m
2026-07-10 RTY484 FNL → FNL Jul 10, 12:20 UTCJul 10, 13:35 UTC1h 15m
2026-07-09 RTY484 FNL → FNL Jul 9, 15:20 UTCJul 9, 17:10 UTC1h 50m
2026-07-09 RTY484 FNL → FNL Jul 9, 12:55 UTCJul 9, 14:15 UTC1h 20m
2026-07-07 RTY484 FNL → FNL Jul 7, 19:35 UTCJul 7, 20:25 UTC50m
2026-07-07 RTY484 FNL → FNL Jul 7, 16:45 UTCJul 7, 18:10 UTC1h 25m
2026-07-07 RTY484 - Jul 7, 14:20 UTCJul 7, 14:55 UTC35m
2026-07-07 RTY484 - Jul 7, 13:00 UTCJul 7, 13:35 UTC35m
2026-07-06 RTY484 - Jul 6, 17:20 UTCJul 6, 18:05 UTC45m
2026-07-06 RTY484 - Jul 6, 13:55 UTCJul 6, 14:45 UTC50m
2026-07-01 RTY484 FNL → FNL Jul 1, 20:10 UTCJul 1, 21:50 UTC1h 40m
2026-07-01 RTY484 - Jul 1, 17:40 UTCJul 1, 19:15 UTC1h 35m
2026-07-01 RTY484 - Jul 1, 16:20 UTCJul 1, 16:50 UTC30m
2026-07-01 RTY484 - Jul 1, 13:20 UTCJul 1, 14:15 UTC55m
2026-06-30 RTY484 FNL → FNL Jun 30, 18:10 UTCJun 30, 18:55 UTC45m
2026-06-30 RTY484 FNL → FNL Jun 30, 15:30 UTCJun 30, 16:40 UTC1h 10m
2026-06-30 RTY484 FNL → FNL Jun 30, 13:10 UTCJun 30, 14:15 UTC1h 5m
2026-06-29 RTY484 FNL → FNL Jun 29, 17:59 UTCJun 29, 19:00 UTC1h 0m
2026-06-29 RTY484 FNL → FNL Jun 29, 15:34 UTCJun 29, 16:55 UTC1h 20m
2026-06-29 RTY484 FNL → FNL Jun 29, 12:49 UTCJun 29, 14:09 UTC1h 20m
2026-06-28 RTY484 FNL → FNL Jun 28, 16:39 UTCJun 28, 18:25 UTC1h 45m
2026-06-28 RTY484 FNL → FNL Jun 28, 14:54 UTCJun 28, 15:44 UTC50m
2026-06-27 RTY484 FNL → FNL Jun 27, 13:09 UTCJun 27, 14:25 UTC1h 15m
2026-06-26 RTY484 FNL → FNL Jun 26, 16:39 UTCJun 26, 17:29 UTC50m
2026-06-23 RTY484 FNL → FNL Jun 23, 17:50 UTCJun 23, 19:04 UTC1h 15m
2026-06-22 RTY484 FNL → FNL Jun 22, 16:50 UTCJun 22, 17:04 UTC15m
2026-06-22 RTY484 FNL → FNL Jun 22, 14:19 UTCJun 22, 15:29 UTC1h 10m
2026-06-21 RTY484 FNL → FNL Jun 21, 17:45 UTCJun 21, 18:44 UTC1h 0m
2026-06-21 RTY484 FNL → FNL Jun 21, 14:40 UTCJun 21, 15:30 UTC50m
2026-06-20 RTY484 FNL → FNL Jun 20, 17:34 UTCJun 20, 18:54 UTC1h 20m
2026-06-18 RTY484 - Jun 18, 22:05 UTCJun 18, 22:50 UTC45m
2026-06-18 RTY484 FNL → FNL Jun 18, 20:15 UTCJun 18, 21:30 UTC1h 15m
2026-06-18 RTY484 FNL → FNL Jun 18, 18:00 UTCJun 18, 18:50 UTC50m
2026-06-18 RTY484 - Jun 18, 15:10 UTCJun 18, 15:35 UTC25m
2026-06-18 RTY484 - Jun 18, 13:15 UTCJun 18, 13:45 UTC30m
2026-06-16 RTY484 FNL → FNL Jun 16, 20:20 UTCJun 16, 21:25 UTC1h 5m
2026-06-16 RTY484 FNL → FNL Jun 16, 17:49 UTCJun 16, 19:05 UTC1h 15m
2026-06-16 RTY484 - Jun 16, 16:00 UTCJun 16, 16:55 UTC55m
2026-06-16 RTY484 - Jun 16, 14:25 UTCJun 16, 14:55 UTC30m
2026-06-15 RTY484 FNL → FNL Jun 15, 21:55 UTCJun 15, 23:04 UTC1h 10m
2026-06-15 RTY484 FNL → FNL Jun 15, 19:39 UTCJun 15, 20:45 UTC1h 5m
2026-06-14 RTY484 FNL → FNL Jun 14, 19:50 UTCJun 14, 21:20 UTC1h 30m
2026-06-14 RTY484 FNL → FNL Jun 14, 17:10 UTCJun 14, 17:55 UTC45m

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

Mode-S A5F852 frequently asked

What is Mode-S code A5F852?
A5F852 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N484JW.
Where is Mode-S A5F852 registered?
Mode-S code A5F852 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 A5F852 broadcasting right now?
Yes. Mode-S A5F852 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A5F852, octal 51374122, decimal 10,877,010.
What flights does A5F852 operate?
Mode-S A5F852 has broadcast 1 distinct callsign, including RTY484.