Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AAF502

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N805FW · CESSNA 172 Skyhawk · operated by MEDARY AVIATION LLC

Hex
AAF502
Octal
52572402
Decimal
11,203,842
Country
US
Tail
N805FW
Type
C172
No current signal · last broadcast 11h ago
Flights observed
81
Distinct callsigns
1
Country
US
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S AAF502.

Country allocation

The ICAO 24-bit address AAF502 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
N805FW - 81 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 N805FW BKX → BKX May 29, 22:35 UTCMay 29, 23:40 UTC1h 5m
2026-05-29 N805FW BKX → BKX May 29, 20:40 UTCMay 29, 21:35 UTC55m
2026-05-29 N805FW BKX → BKX May 29, 18:35 UTCMay 29, 19:45 UTC1h 10m
2026-05-29 N805FW BKX → BKX May 29, 16:40 UTCMay 29, 17:25 UTC45m
2026-05-29 N805FW BKX → BKX May 29, 13:00 UTCMay 29, 14:10 UTC1h 10m
2026-05-28 N805FW BKX → BKX May 28, 23:20 UTCMay 29, 01:10 UTC1h 50m
2026-05-28 N805FW BKX → BKX May 28, 22:25 UTCMay 28, 22:30 UTC5m
2026-05-28 N805FW - May 28, 21:30 UTCMay 28, 21:40 UTC10m
2026-05-28 N805FW - May 28, 19:30 UTCMay 28, 20:35 UTC1h 5m
2026-05-28 N805FW - May 28, 18:30 UTCMay 28, 18:40 UTC10m
2026-05-28 N805FW - May 28, 17:35 UTCMay 28, 17:55 UTC20m
2026-05-28 N805FW BKX → BKX May 28, 15:20 UTCMay 28, 16:25 UTC1h 5m
2026-05-28 N805FW BKX → BKX May 28, 00:45 UTCMay 28, 01:50 UTC1h 5m
2026-05-27 N805FW BKX → BKX May 27, 22:45 UTCMay 27, 23:50 UTC1h 5m
2026-05-27 N805FW - May 27, 20:30 UTCMay 27, 20:40 UTC10m
2026-05-27 N805FW BKX → BKX May 27, 18:30 UTCMay 27, 19:40 UTC1h 10m
2026-05-27 N805FW BKX → BKX May 27, 14:50 UTCMay 27, 16:05 UTC1h 15m
2026-05-27 N805FW - May 27, 02:49 UTCMay 27, 03:39 UTC50m
2026-05-27 N805FW BKX → BKX May 27, 00:10 UTCMay 27, 01:29 UTC1h 20m
2026-05-26 N805FW - May 26, 22:29 UTCMay 26, 23:25 UTC55m
2026-05-26 N805FW BKX → BKX May 26, 20:29 UTCMay 26, 21:55 UTC1h 25m
2026-05-26 N805FW BKX → BKX May 26, 19:05 UTCMay 26, 19:50 UTC45m
2026-05-26 N805FW BKX → BKX May 26, 15:45 UTCMay 26, 16:35 UTC50m
2026-05-25 N805FW BKX → BKX May 25, 22:34 UTCMay 25, 23:54 UTC1h 20m
2026-05-25 N805FW BKX → BKX May 25, 21:24 UTCMay 25, 21:35 UTC10m
2026-05-25 N805FW - May 25, 20:30 UTCMay 25, 20:34 UTC5m
2026-05-25 N805FW BKX → BKX May 25, 18:05 UTCMay 25, 18:45 UTC40m
2026-05-22 N805FW BKX → BKX May 22, 02:30 UTCMay 22, 04:45 UTC2h 15m
2026-05-22 N805FW - May 22, 00:35 UTCMay 22, 01:10 UTC35m
2026-05-21 N805FW BKX → BKX May 21, 22:40 UTCMay 21, 23:40 UTC1h 0m
2026-05-21 N805FW BKX → BKX May 21, 20:50 UTCMay 21, 21:40 UTC50m
2026-05-21 N805FW BKX → BKX May 21, 15:00 UTCMay 21, 16:20 UTC1h 20m
2026-05-21 N805FW - May 21, 03:20 UTCMay 21, 03:35 UTC15m
2026-05-21 N805FW - May 21, 01:05 UTCMay 21, 01:25 UTC20m
2026-05-21 N805FW - May 21, 00:05 UTCMay 21, 00:15 UTC10m
2026-05-20 N805FW - May 20, 22:30 UTCMay 20, 23:35 UTC1h 5m
2026-05-20 N805FW BKX → BKX May 20, 20:50 UTCMay 20, 21:40 UTC50m
2026-05-20 N805FW BKX → BKX May 20, 17:45 UTCMay 20, 19:40 UTC1h 55m
2026-05-20 N805FW BKX → BKX May 20, 14:45 UTCMay 20, 16:00 UTC1h 15m
2026-05-19 N805FW BKX → BKX May 19, 17:30 UTCMay 19, 18:15 UTC45m
2026-05-17 N805FW BKX → BKX May 17, 03:05 UTCMay 17, 03:30 UTC25m
2026-05-17 N805FW BKX → BKX May 17, 02:45 UTCMay 17, 03:00 UTC15m
2026-05-17 N805FW BKX → BKX May 17, 02:35 UTCMay 17, 02:40 UTC5m
2026-05-16 N805FW BKX → BKX May 16, 20:45 UTCMay 16, 21:15 UTC30m
2026-05-16 N805FW BKX → BKX May 16, 17:50 UTCMay 16, 18:45 UTC55m
2026-05-16 N805FW BKX → BKX May 16, 12:45 UTCMay 16, 13:35 UTC50m
2026-05-15 N805FW BKX → BKX May 15, 22:45 UTCMay 15, 23:50 UTC1h 5m
2026-05-15 N805FW BKX → BKX May 15, 21:25 UTCMay 15, 21:50 UTC25m
2026-05-15 N805FW - May 15, 18:45 UTCMay 15, 19:40 UTC55m
2026-05-14 N805FW BKX → BKX May 14, 02:40 UTCMay 14, 04:25 UTC1h 45m

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

Mode-S AAF502 frequently asked

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