Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A4ACE1

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N400CP · CESSNA 560XL Citation XLS · operated by CP AVIATION LLC

Hex
A4ACE1
Octal
51126341
Decimal
10,792,161
Country
US
Tail
N400CP
Type
C56X
No current signal · last broadcast 2d ago
Flights observed
73
Distinct callsigns
1
Country
US
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S A4ACE1.

Country allocation

The ICAO 24-bit address A4ACE1 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
JTL400 - 73 2026-06-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-22 JTL400 - Jun 22, 21:14 UTCJun 22, 21:59 UTC45m
2026-06-22 JTL400 - Jun 22, 19:54 UTCJun 22, 20:34 UTC40m
2026-06-21 JTL400 - Jun 21, 19:39 UTCJun 21, 22:15 UTC2h 35m
2026-06-20 JTL400 - Jun 20, 22:20 UTCJun 20, 23:14 UTC55m
2026-06-20 JTL400 BFI → APC Jun 20, 02:49 UTCJun 20, 04:29 UTC1h 40m
2026-06-19 JTL400 - Jun 19, 13:09 UTCJun 19, 14:39 UTC1h 30m
2026-06-18 JTL400 - Jun 18, 23:10 UTCJun 19, 00:10 UTC59m
2026-06-18 JTL400 - Jun 18, 18:30 UTCJun 18, 21:50 UTC3h 20m
2026-06-10 JTL400 OAK → LAX Jun 10, 21:00 UTCJun 10, 21:45 UTC45m
2026-06-10 JTL400 OAK → LAX Jun 10, 14:15 UTCJun 10, 15:00 UTC45m
2026-06-09 JTL400 OAK → LAX Jun 9, 18:10 UTCJun 9, 19:55 UTC1h 45m
2026-06-07 JTL400 OAK → LAX Jun 7, 19:55 UTCJun 7, 21:35 UTC1h 40m
2026-06-07 JTL400 OAK → LAX Jun 7, 02:19 UTCJun 7, 02:55 UTC35m
2026-06-06 JTL400 OAK → LAX Jun 6, 18:04 UTCJun 6, 18:45 UTC40m
2026-06-04 JTL400 OAK → LAX Jun 4, 21:50 UTCJun 4, 23:00 UTC1h 10m
2026-06-04 JTL400 OAK → LAX Jun 4, 18:00 UTCJun 4, 19:50 UTC1h 50m
2026-06-03 JTL400 OAK → LAX Jun 3, 22:40 UTCJun 3, 23:45 UTC1h 5m
2026-06-03 JTL400 OAK → LAX Jun 3, 20:05 UTCJun 3, 21:10 UTC1h 5m
2026-06-03 JTL400 OAK → LAX Jun 3, 18:10 UTCJun 3, 19:00 UTC50m
2026-06-03 JTL400 OAK → LAX Jun 3, 13:45 UTCJun 3, 15:30 UTC1h 45m
2026-06-02 JTL400 OAK → LAX Jun 2, 20:45 UTCJun 2, 21:25 UTC40m
2026-06-02 JTL400 OAK → LAX Jun 2, 15:15 UTCJun 2, 16:00 UTC45m
2026-06-02 JTL400 OAK → LAX Jun 2, 13:00 UTCJun 2, 13:45 UTC45m
2026-05-30 JTL400 OAK → LAX May 30, 17:05 UTCMay 30, 19:35 UTC2h 30m
2026-05-26 JTL400 OAK → LAX May 26, 15:20 UTCMay 26, 17:50 UTC2h 30m
2026-05-25 JTL400 OAK → LAX May 25, 19:00 UTCMay 25, 19:40 UTC39m
2026-05-25 JTL400 OAK → LAX May 25, 16:50 UTCMay 25, 17:40 UTC50m
2026-05-25 JTL400 OAK → LAX May 25, 13:50 UTCMay 25, 14:25 UTC35m
2026-05-24 JTL400 OAK → LAX May 24, 17:20 UTCMay 24, 19:05 UTC1h 45m
2026-05-23 JTL400 OAK → LAX May 23, 01:10 UTCMay 23, 02:00 UTC50m
2026-05-22 JTL400 OAK → LAX May 22, 22:00 UTCMay 22, 23:45 UTC1h 45m
2026-05-22 JTL400 OAK → LAX May 22, 18:10 UTCMay 22, 19:20 UTC1h 10m
2026-05-22 JTL400 OAK → LAX May 22, 15:05 UTCMay 22, 17:00 UTC1h 55m
2026-05-21 JTL400 OAK → LAX May 21, 18:55 UTCMay 21, 20:20 UTC1h 25m
2026-05-21 JTL400 OAK → LAX May 21, 15:25 UTCMay 21, 17:35 UTC2h 10m
2026-05-21 JTL400 OAK → LAX May 21, 11:55 UTCMay 21, 13:25 UTC1h 30m
2026-05-19 JTL400 OAK → LAX May 19, 15:10 UTCMay 19, 16:20 UTC1h 10m
2026-05-19 JTL400 OAK → LAX May 19, 12:30 UTCMay 19, 13:55 UTC1h 25m
2026-05-17 JTL400 OAK → LAX May 17, 18:01 UTCMay 17, 20:25 UTC2h 25m
2026-05-16 JTL400 OAK → LAX May 16, 23:55 UTCMay 17, 02:40 UTC2h 45m
2026-05-16 JTL400 OAK → LAX May 16, 19:25 UTCMay 16, 22:25 UTC3h 0m
2026-05-15 JTL400 OAK → LAX May 15, 22:25 UTCMay 16, 00:10 UTC1h 45m
2026-05-15 JTL400 OAK → LAX May 15, 16:20 UTCMay 15, 19:05 UTC2h 45m
2026-05-14 JTL400 OAK → LAX May 14, 18:40 UTCMay 14, 19:45 UTC1h 5m
2026-05-14 JTL400 OAK → LAX May 14, 17:10 UTCMay 14, 17:45 UTC35m
2026-05-13 JTL400 OAK → LAX May 13, 19:50 UTCMay 13, 22:30 UTC2h 40m
2026-05-11 JTL400 OAK → LAX May 11, 13:40 UTCMay 11, 14:20 UTC40m
2026-05-10 JTL400 OAK → LAX May 10, 18:15 UTCMay 10, 20:09 UTC1h 55m
2026-05-07 JTL400 OAK → LAX May 7, 17:45 UTCMay 7, 18:50 UTC1h 5m
2026-05-07 JTL400 OAK → LAX May 7, 14:45 UTCMay 7, 15:25 UTC40m

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

Mode-S A4ACE1 frequently asked

What is Mode-S code A4ACE1?
A4ACE1 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N400CP.
Where is Mode-S A4ACE1 registered?
Mode-S code A4ACE1 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 A4ACE1 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 A4ACE1, octal 51126341, decimal 10,792,161.
What flights does A4ACE1 operate?
Mode-S A4ACE1 has broadcast 1 distinct callsign, including JTL400.