Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AAAF2A

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N788KL · SWEARINGEN Metro · operated by C B G LLC

Hex
AAAF2A
Octal
52527452
Decimal
11,185,962
Country
US
Tail
N788KL
Type
SW4
Broadcasting now · callsign LYM356 · 5,200 ft
Flights observed
95
Distinct callsigns
6
Country
US
Last broadcast
12h ago

Current position

AAAF2A is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address AAAF2A 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 6 distinct

Callsign Airline Flights Last seen
LYM356 Key Lime Air 84 2026-06-02
LYM717 Key Lime Air 5 2026-04-16
LYM536 Key Lime Air 2 2026-05-01
LYM137 - 2 2026-04-14
LYM404 Key Lime Air 1 2026-04-15
LYM117 Key Lime Air 1 2026-04-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-02 LYM356 LAR → DEN Jun 2, 12:55 UTCJun 2, 13:50 UTC55m
2026-06-02 LYM356 LAR → DEN Jun 2, 02:05 UTCJun 2, 02:30 UTC25m
2026-06-02 LYM356 LAR → DEN Jun 2, 00:35 UTCJun 2, 01:05 UTC30m
2026-05-30 LYM356 LAR → DEN May 30, 14:35 UTCMay 30, 15:00 UTC25m
2026-05-30 LYM356 LAR → DEN May 30, 13:30 UTCMay 30, 13:50 UTC20m
2026-05-30 LYM356 LAR → DEN May 30, 01:35 UTCMay 30, 02:06 UTC31m
2026-05-30 LYM356 LAR → DEN May 30, 00:30 UTCMay 30, 01:00 UTC30m
2026-05-29 LYM356 LAR → DEN May 29, 12:45 UTCMay 29, 13:35 UTC50m
2026-05-29 LYM356 LAR → DEN May 29, 01:35 UTCMay 29, 02:00 UTC25m
2026-05-29 LYM356 LAR → DEN May 29, 00:25 UTCMay 29, 01:00 UTC35m
2026-05-28 LYM356 LAR → DEN May 28, 13:15 UTCMay 28, 14:10 UTC55m
2026-05-28 LYM356 LAR → DEN May 28, 01:50 UTCMay 28, 02:15 UTC25m
2026-05-28 LYM356 LAR → DEN May 28, 00:25 UTCMay 28, 01:00 UTC35m
2026-05-27 LYM356 LAR → DEN May 27, 12:45 UTCMay 27, 13:30 UTC45m
2026-05-27 LYM356 LAR → DEN May 27, 02:04 UTCMay 27, 02:29 UTC25m
2026-05-27 LYM356 LAR → DEN May 27, 00:25 UTCMay 27, 01:05 UTC40m
2026-05-23 LYM356 LAR → DEN May 23, 14:20 UTCMay 23, 14:55 UTC35m
2026-05-23 LYM356 LAR → DEN May 23, 13:00 UTCMay 23, 13:25 UTC25m
2026-05-23 LYM356 LAR → DEN May 23, 01:35 UTCMay 23, 01:55 UTC20m
2026-05-23 LYM356 LAR → DEN May 23, 00:25 UTCMay 23, 01:00 UTC35m
2026-05-22 LYM356 LAR → DEN May 22, 13:05 UTCMay 22, 14:05 UTC1h 0m
2026-05-22 LYM356 LAR → DEN May 22, 01:40 UTCMay 22, 02:10 UTC30m
2026-05-22 LYM356 LAR → DEN May 22, 00:25 UTCMay 22, 01:00 UTC35m
2026-05-21 LYM356 LAR → DEN May 21, 13:05 UTCMay 21, 14:00 UTC55m
2026-05-21 LYM356 LAR → DEN May 21, 01:50 UTCMay 21, 02:20 UTC30m
2026-05-21 LYM356 LAR → DEN May 21, 00:25 UTCMay 21, 01:00 UTC35m
2026-05-20 LYM356 LAR → DEN May 20, 12:35 UTCMay 20, 13:25 UTC50m
2026-05-20 LYM356 LAR → DEN May 20, 01:35 UTCMay 20, 02:10 UTC35m
2026-05-20 LYM356 LAR → DEN May 20, 00:30 UTCMay 20, 01:00 UTC30m
2026-05-19 LYM356 LAR → DEN May 19, 12:50 UTCMay 19, 13:40 UTC50m
2026-05-19 LYM356 LAR → DEN May 19, 00:25 UTCMay 19, 02:10 UTC1h 45m
2026-05-16 LYM356 LAR → DEN May 16, 14:16 UTCMay 16, 14:51 UTC35m
2026-05-16 LYM356 LAR → DEN May 16, 13:05 UTCMay 16, 13:25 UTC20m
2026-05-16 LYM356 LAR → DEN May 16, 01:35 UTCMay 16, 02:00 UTC25m
2026-05-16 LYM356 LAR → DEN May 16, 00:25 UTCMay 16, 01:00 UTC35m
2026-05-15 LYM356 LAR → DEN May 15, 13:20 UTCMay 15, 14:15 UTC55m
2026-05-15 LYM356 LAR → DEN May 15, 00:25 UTCMay 15, 02:05 UTC1h 40m
2026-05-14 LYM356 LAR → DEN May 14, 12:45 UTCMay 14, 13:40 UTC55m
2026-05-14 LYM356 LAR → DEN May 14, 01:30 UTCMay 14, 01:55 UTC25m
2026-05-14 LYM356 LAR → DEN May 14, 00:25 UTCMay 14, 01:00 UTC35m
2026-05-13 LYM356 LAR → DEN May 13, 12:45 UTCMay 13, 13:40 UTC55m
2026-05-13 LYM356 LAR → DEN May 13, 01:30 UTCMay 13, 01:50 UTC20m
2026-05-13 LYM356 LAR → DEN May 13, 00:20 UTCMay 13, 00:55 UTC35m
2026-05-12 LYM356 LAR → DEN May 12, 12:55 UTCMay 12, 13:55 UTC1h 0m
2026-05-09 LYM356 LAR → DEN May 9, 14:20 UTCMay 9, 14:50 UTC30m
2026-05-09 LYM356 LAR → DEN May 9, 13:05 UTCMay 9, 13:30 UTC25m
2026-05-09 LYM356 LAR → DEN May 9, 01:35 UTCMay 9, 02:05 UTC30m
2026-05-09 LYM356 LAR → DEN May 9, 00:25 UTCMay 9, 01:00 UTC35m
2026-05-08 LYM356 LAR → DEN May 8, 13:30 UTCMay 8, 14:30 UTC1h 0m
2026-05-08 LYM356 LAR → DEN May 8, 01:40 UTCMay 8, 02:09 UTC30m

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

Mode-S AAAF2A frequently asked

What is Mode-S code AAAF2A?
AAAF2A is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N788KL.
Where is Mode-S AAAF2A registered?
Mode-S code AAAF2A 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 AAAF2A broadcasting right now?
Yes. Mode-S AAAF2A is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AAAF2A, octal 52527452, decimal 11,185,962.
What flights does AAAF2A operate?
Mode-S AAAF2A has broadcast 6 distinct callsigns, including LYM356, LYM717, LYM536, LYM137, LYM404.