Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A375CC

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N322AP · BOMBARDIER CL-600 Challenger · operated by SKYLARK PARTNERS MANAGEMENT LLC

Hex
A375CC
Octal
50672714
Decimal
10,712,524
Country
US
Tail
N322AP
Type
CL60
No current signal · last broadcast 2d ago
Flights observed
51
Distinct callsigns
1
Country
US
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S A375CC.

Country allocation

The ICAO 24-bit address A375CC 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
JTL322 Jetall Holdings 51 2026-05-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-27 JTL322 OAK → LAS May 27, 19:40 UTCMay 27, 21:10 UTC1h 30m
2026-05-27 JTL322 OAK → LAS May 27, 17:35 UTCMay 27, 18:45 UTC1h 10m
2026-05-26 JTL322 OAK → LAS May 26, 16:50 UTCMay 26, 17:09 UTC20m
2026-05-25 JTL322 OAK → LAS May 25, 14:20 UTCMay 25, 16:30 UTC2h 10m
2026-05-23 JTL322 OAK → LAS May 23, 16:20 UTCMay 23, 18:25 UTC2h 6m
2026-05-22 JTL322 OAK → LAS May 22, 23:40 UTCMay 23, 01:50 UTC2h 10m
2026-05-22 JTL322 OAK → LAS May 22, 19:30 UTCMay 22, 20:40 UTC1h 10m
2026-05-22 JTL322 OAK → LAS May 22, 16:20 UTCMay 22, 18:25 UTC2h 5m
2026-05-22 JTL322 OAK → LAS May 22, 13:50 UTCMay 22, 14:10 UTC20m
2026-05-20 JTL322 OAK → LAS May 20, 01:00 UTCMay 20, 04:00 UTC3h 0m
2026-05-19 JTL322 OAK → LAS May 19, 17:20 UTCMay 19, 19:30 UTC2h 10m
2026-05-18 JTL322 OAK → LAS May 18, 15:25 UTCMay 19, 00:50 UTC9h 24m
2026-05-16 JTL322 OAK → LAS May 16, 17:10 UTCMay 16, 19:20 UTC2h 10m
2026-05-15 JTL322 OAK → LAS May 15, 21:20 UTCMay 15, 22:15 UTC55m
2026-05-15 JTL322 OAK → LAS May 15, 19:35 UTCMay 15, 20:15 UTC40m
2026-05-14 JTL322 OAK → LAS May 14, 21:15 UTCMay 14, 22:00 UTC45m
2026-05-14 JTL322 OAK → LAS May 14, 19:35 UTCMay 14, 20:30 UTC55m
2026-05-14 JTL322 OAK → LAS May 14, 17:55 UTCMay 14, 18:10 UTC15m
2026-05-14 JTL322 OAK → LAS May 14, 14:20 UTCMay 14, 17:15 UTC2h 55m
2026-05-13 JTL322 OAK → LAS May 13, 21:00 UTCMay 13, 21:50 UTC50m
2026-05-13 JTL322 OAK → LAS May 13, 19:20 UTCMay 13, 20:05 UTC45m
2026-05-13 JTL322 OAK → LAS May 13, 16:20 UTCMay 13, 17:05 UTC45m
2026-05-13 JTL322 OAK → LAS May 13, 13:40 UTCMay 13, 15:35 UTC1h 55m
2026-05-10 JTL322 OAK → LAS May 10, 18:20 UTCMay 10, 20:54 UTC2h 35m
2026-05-10 JTL322 OAK → LAS May 10, 16:34 UTCMay 10, 17:05 UTC30m
2026-05-10 JTL322 OAK → LAS May 10, 15:15 UTCMay 10, 15:29 UTC15m
2026-05-09 JTL322 OAK → LAS May 9, 17:25 UTCMay 9, 19:30 UTC2h 5m
2026-05-09 JTL322 OAK → LAS May 9, 14:00 UTCMay 9, 15:55 UTC1h 55m
2026-05-07 JTL322 OAK → LAS May 7, 18:15 UTCMay 7, 19:25 UTC1h 10m
2026-05-06 JTL322 OAK → LAS May 6, 00:40 UTCMay 6, 02:30 UTC1h 50m
2026-05-03 JTL322 OAK → LAS May 3, 14:30 UTCMay 3, 17:10 UTC2h 40m
2026-05-03 JTL322 OAK → LAS May 3, 11:40 UTCMay 3, 11:55 UTC15m
2026-04-28 JTL322 OAK → LAS Apr 28, 22:55 UTCApr 28, 23:20 UTC25m
2026-04-28 JTL322 OAK → LAS Apr 28, 20:05 UTCApr 28, 22:10 UTC2h 5m
2026-04-28 JTL322 OAK → LAS Apr 28, 14:30 UTCApr 28, 17:15 UTC2h 45m
2026-04-25 JTL322 OAK → LAS Apr 25, 13:20 UTCApr 25, 15:30 UTC2h 10m
2026-04-24 JTL322 OAK → LAS Apr 24, 17:05 UTCApr 24, 17:50 UTC45m
2026-04-24 JTL322 OAK → LAS Apr 24, 15:45 UTCApr 24, 16:30 UTC45m
2026-04-21 JTL322 OAK → LAS Apr 21, 23:45 UTCApr 22, 00:20 UTC35m
2026-04-21 JTL322 OAK → LAS Apr 21, 21:00 UTCApr 21, 23:10 UTC2h 10m
2026-04-19 JTL322 OAK → LAS Apr 19, 18:20 UTCApr 19, 20:15 UTC1h 55m
2026-04-19 JTL322 OAK → LAS Apr 19, 16:40 UTCApr 19, 17:20 UTC40m
2026-04-17 JTL322 OAK → LAS Apr 17, 19:25 UTCApr 17, 20:25 UTC1h 0m
2026-04-17 JTL322 OAK → LAS Apr 17, 11:45 UTCApr 17, 12:30 UTC45m
2026-04-17 JTL322 OAK → LAS Apr 17, 03:20 UTCApr 17, 04:35 UTC1h 16m
2026-04-17 JTL322 OAK → LAS Apr 17, 02:20 UTCApr 17, 03:15 UTC55m
2026-04-13 JTL322 OAK → LAS Apr 13, 16:15 UTCApr 13, 18:50 UTC2h 35m
2026-04-13 JTL322 OAK → LAS Apr 13, 16:00 UTCApr 13, 16:15 UTC15m
2026-04-13 JTL322 OAK → LAS Apr 13, 00:40 UTCApr 13, 02:50 UTC2h 10m
2026-04-12 JTL322 OAK → LAS Apr 12, 23:55 UTCApr 13, 02:50 UTC2h 55m

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

Mode-S A375CC frequently asked

What is Mode-S code A375CC?
A375CC is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N322AP.
Where is Mode-S A375CC registered?
Mode-S code A375CC 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 A375CC 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 A375CC, octal 50672714, decimal 10,712,524.
What flights does A375CC operate?
Mode-S A375CC has broadcast 1 distinct callsign, including JTL322.