sensors Mode-S transponder

A3FF0A

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N357CK · LEARJET 35 · operated by KALITTA CHARTERS LLC

Hex
A3FF0A
Octal
50777412
Decimal
10,747,658
Country
US
Tail
N357CK
Type
LJ35
No current signal · last broadcast 2d ago
Flights observed
66
Distinct callsigns
10
Country
US
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S A3FF0A.

Country allocation

The ICAO 24-bit address A3FF0A 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 10 distinct

Callsign Airline Flights Last seen
KFS69 Kalitta Charters 16 2026-05-03
KFS133 - 16 2026-07-11
KFS55 Kalitta Charters 7 2026-05-24
KFS150 - 7 2026-06-22
KFS77 Kalitta Charters 5 2026-04-15
KFS157 Kalitta Charters 5 2026-06-06
KFS57 Kalitta Charters 4 2026-05-26
KFS123 - 4 2026-06-28
KFS84 Kalitta Charters 1 2026-06-03
KFS34 Kalitta Charters 1 2026-04-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-11 KFS133 - Jul 11, 18:35 UTCJul 11, 21:25 UTC2h 50m
2026-07-11 KFS133 - Jul 11, 01:50 UTCJul 11, 04:01 UTC2h 10m
2026-07-10 KFS133 - Jul 10, 22:20 UTCJul 11, 00:40 UTC2h 20m
2026-07-10 KFS133 - Jul 10, 19:25 UTCJul 10, 20:35 UTC1h 10m
2026-07-08 KFS133 IND → YIP Jul 8, 19:15 UTCJul 8, 21:55 UTC2h 40m
2026-07-08 KFS133 IND → YIP Jul 8, 15:15 UTCJul 8, 17:05 UTC1h 50m
2026-07-02 KFS133 IND → YIP Jul 2, 22:45 UTCJul 3, 00:50 UTC2h 5m
2026-06-28 KFS123 - Jun 28, 23:50 UTCJun 29, 03:10 UTC3h 20m
2026-06-28 KFS123 - Jun 28, 21:10 UTCJun 28, 21:50 UTC40m
2026-06-27 KFS123 - Jun 27, 18:45 UTCJun 27, 19:24 UTC40m
2026-06-27 KFS123 - Jun 27, 13:30 UTCJun 27, 16:30 UTC3h 0m
2026-06-22 KFS150 - Jun 22, 22:34 UTCJun 23, 01:40 UTC3h 5m
2026-06-22 KFS150 - Jun 22, 20:14 UTCJun 22, 21:54 UTC1h 40m
2026-06-21 KFS150 - Jun 21, 16:39 UTCJun 21, 18:10 UTC1h 30m
2026-06-21 KFS150 - Jun 21, 13:34 UTCJun 21, 15:59 UTC2h 25m
2026-06-20 KFS150 - Jun 20, 18:14 UTCJun 20, 19:34 UTC1h 20m
2026-06-18 KFS150 - Jun 18, 20:10 UTCJun 18, 21:10 UTC1h 0m
2026-06-18 KFS150 LAS → BFI Jun 18, 15:20 UTCJun 18, 17:25 UTC2h 5m
2026-06-16 KFS133 IND → YIP Jun 16, 21:50 UTCJun 16, 23:55 UTC2h 5m
2026-06-16 KFS133 IND → YIP Jun 16, 16:25 UTCJun 16, 19:10 UTC2h 45m
2026-06-15 KFS133 IND → YIP Jun 15, 18:29 UTCJun 15, 22:00 UTC3h 30m
2026-06-15 KFS133 IND → YIP Jun 15, 16:15 UTCJun 15, 17:45 UTC1h 30m
2026-06-15 KFS133 IND → YIP Jun 15, 13:05 UTCJun 15, 14:50 UTC1h 45m
2026-06-11 KFS133 IND → YIP Jun 11, 15:55 UTCJun 11, 19:20 UTC3h 25m
2026-06-11 KFS133 IND → YIP Jun 11, 12:15 UTCJun 11, 13:10 UTC55m
2026-06-10 KFS133 IND → YIP Jun 10, 03:30 UTCJun 10, 05:20 UTC1h 50m
2026-06-09 KFS133 IND → YIP Jun 9, 23:20 UTCJun 10, 01:30 UTC2h 10m
2026-06-06 KFS157 PNS → ORL Jun 6, 20:55 UTCJun 6, 23:24 UTC2h 30m
2026-06-06 KFS157 PNS → ORL Jun 6, 17:49 UTCJun 6, 18:45 UTC55m
2026-06-06 KFS157 PNS → ORL Jun 6, 13:15 UTCJun 6, 14:54 UTC1h 40m
2026-06-04 KFS157 PNS → ORL Jun 4, 17:35 UTCJun 4, 18:45 UTC1h 10m
2026-06-04 KFS157 PNS → ORL Jun 4, 12:15 UTCJun 4, 14:55 UTC2h 40m
2026-06-03 KFS84 RST → YIP Jun 3, 02:45 UTCJun 3, 03:40 UTC55m
2026-05-26 KFS57 MDW → BKL May 26, 17:30 UTCMay 26, 17:55 UTC25m
2026-05-26 KFS57 MDW → BKL May 26, 15:29 UTCMay 26, 16:30 UTC1h 0m
2026-05-26 KFS57 MDW → BKL May 26, 13:40 UTCMay 26, 14:35 UTC55m
2026-05-26 KFS57 MDW → BKL May 26, 12:30 UTCMay 26, 12:54 UTC25m
2026-05-24 KFS55 CVG → YIP May 24, 02:40 UTCMay 24, 03:20 UTC40m
2026-05-24 KFS55 CVG → YIP May 24, 00:00 UTCMay 24, 01:55 UTC1h 55m
2026-05-23 KFS55 CVG → YIP May 23, 17:30 UTCMay 23, 19:15 UTC1h 45m
2026-05-23 KFS55 CVG → YIP May 23, 16:00 UTCMay 23, 16:45 UTC45m
2026-05-06 KFS55 CVG → YIP May 6, 01:50 UTCMay 6, 03:05 UTC1h 15m
2026-05-05 KFS55 CVG → YIP May 5, 23:50 UTCMay 6, 01:05 UTC1h 15m
2026-05-05 KFS55 CVG → YIP May 5, 20:05 UTCMay 5, 20:30 UTC25m
2026-05-03 KFS69 PHL → CMH May 3, 21:35 UTCMay 3, 22:45 UTC1h 10m
2026-05-03 KFS69 PHL → CMH May 3, 19:50 UTCMay 3, 20:20 UTC30m
2026-05-03 KFS69 PHL → CMH May 3, 17:10 UTCMay 3, 18:00 UTC50m
2026-05-02 KFS69 PHL → CMH May 2, 05:30 UTCMay 2, 07:25 UTC1h 55m
2026-05-01 KFS69 PHL → CMH May 1, 22:35 UTCMay 2, 01:05 UTC2h 30m
2026-05-01 KFS69 PHL → CMH May 1, 20:50 UTCMay 1, 21:25 UTC35m

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

Mode-S A3FF0A frequently asked

What is Mode-S code A3FF0A?
A3FF0A is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N357CK.
Where is Mode-S A3FF0A registered?
Mode-S code A3FF0A 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 A3FF0A broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A3FF0A, octal 50777412, decimal 10,747,658.
What flights does A3FF0A operate?
Mode-S A3FF0A has broadcast 10 distinct callsigns, including KFS69, KFS133, KFS55, KFS150, KFS77.