Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A8C0F0

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N663SB · GULFSTREAM G200 · operated by KKA ENTERPRISES LLC

Hex
A8C0F0
Octal
52140360
Decimal
11,059,440
Country
US
Tail
N663SB
Type
GALX
No current signal · last broadcast 1d ago
Flights observed
86
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S A8C0F0.

Country allocation

The ICAO 24-bit address A8C0F0 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
JTL663 - 86 2026-07-16

Recent flights last 50

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

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

Mode-S A8C0F0 frequently asked

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