Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A4B4CC

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N402HP · BOMBARDIER BD-100 Challenger 300 · operated by GOTTSCH BROTHERS OF ELKHORN LLC

Hex
A4B4CC
Octal
51132314
Decimal
10,794,188
Country
US
Tail
N402HP
Type
CL30
No current signal · last broadcast 3d ago
Flights observed
53
Distinct callsigns
1
Country
US
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S A4B4CC.

Country allocation

The ICAO 24-bit address A4B4CC 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
JTL402 - 53 2026-07-10

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-10 JTL402 YXE → YEG Jul 10, 22:15 UTCJul 11, 01:10 UTC2h 55m
2026-07-10 JTL402 - Jul 10, 19:20 UTCJul 10, 21:15 UTC1h 55m
2026-07-10 JTL402 - Jul 10, 16:40 UTCJul 10, 18:00 UTC1h 20m
2026-06-28 JTL402 - Jun 28, 18:14 UTCJun 28, 20:45 UTC2h 30m
2026-06-28 JTL402 - Jun 28, 16:00 UTCJun 28, 17:19 UTC1h 20m
2026-06-27 JTL402 - Jun 27, 23:39 UTCJun 28, 01:59 UTC2h 20m
2026-06-27 JTL402 - Jun 27, 21:44 UTCJun 27, 22:09 UTC25m
2026-06-27 JTL402 - Jun 27, 18:09 UTCJun 27, 20:59 UTC2h 50m
2026-06-27 JTL402 - Jun 27, 15:05 UTCJun 27, 15:55 UTC50m
2026-06-27 JTL402 - Jun 27, 00:00 UTCJun 27, 00:29 UTC30m
2026-06-26 JTL402 - Jun 26, 21:45 UTCJun 26, 22:34 UTC50m
2026-06-26 JTL402 - Jun 26, 17:19 UTCJun 26, 20:04 UTC2h 45m
2026-06-26 JTL402 - Jun 26, 13:10 UTCJun 26, 15:45 UTC2h 35m
2026-06-25 JTL402 - Jun 25, 18:39 UTCJun 25, 20:34 UTC1h 55m
2026-06-24 JTL402 - Jun 24, 13:44 UTCJun 24, 15:00 UTC1h 15m
2026-06-21 JTL402 - Jun 21, 21:29 UTCJun 21, 22:34 UTC1h 5m
2026-06-20 JTL402 - Jun 20, 14:14 UTCJun 20, 18:04 UTC3h 50m
2026-06-19 JTL402 MSP → FLL Jun 19, 21:34 UTCJun 20, 00:54 UTC3h 20m
2026-06-19 JTL402 - Jun 19, 18:25 UTCJun 19, 19:59 UTC1h 35m
2026-06-18 JTL402 APA → GXY Jun 18, 22:50 UTCJun 18, 23:05 UTC15m
2026-06-18 JTL402 - Jun 18, 20:40 UTCJun 18, 22:00 UTC1h 20m
2026-06-16 JTL402 - Jun 16, 19:50 UTCJun 16, 21:10 UTC1h 20m
2026-06-16 JTL402 - Jun 16, 16:20 UTCJun 16, 17:59 UTC1h 40m
2026-06-15 JTL402 SNA → APC Jun 15, 21:55 UTCJun 15, 23:45 UTC1h 50m
2026-06-15 JTL402 SNA → APC Jun 15, 17:34 UTCJun 15, 17:50 UTC15m
2026-06-15 JTL402 SNA → APC Jun 15, 15:15 UTCJun 15, 16:24 UTC1h 10m
2026-06-14 JTL402 SNA → APC Jun 14, 22:50 UTCJun 15, 01:00 UTC2h 10m
2026-06-12 JTL402 SNA → APC Jun 12, 14:50 UTCJun 12, 17:25 UTC2h 35m
2026-06-08 JTL402 SNA → APC Jun 8, 20:00 UTCJun 8, 20:25 UTC25m
2026-06-07 JTL402 SNA → APC Jun 7, 13:00 UTCJun 7, 13:25 UTC25m
2026-06-01 JTL402 SNA → APC Jun 1, 18:25 UTCJun 1, 18:55 UTC30m
2026-06-01 JTL402 SNA → APC Jun 1, 14:15 UTCJun 1, 14:45 UTC30m
2026-05-23 JTL402 SNA → APC May 23, 00:15 UTCMay 23, 01:20 UTC1h 5m
2026-05-20 JTL402 SNA → APC May 20, 19:30 UTCMay 20, 20:30 UTC1h 0m
2026-05-17 JTL402 SNA → APC May 17, 16:01 UTCMay 17, 17:25 UTC1h 25m
2026-05-15 JTL402 SNA → APC May 15, 18:10 UTCMay 15, 19:25 UTC1h 15m
2026-05-09 JTL402 SNA → APC May 9, 03:15 UTCMay 9, 03:30 UTC15m
2026-05-09 JTL402 SNA → APC May 9, 00:00 UTCMay 9, 02:45 UTC2h 45m
2026-05-07 JTL402 SNA → APC May 7, 13:55 UTCMay 7, 16:40 UTC2h 45m
2026-05-07 JTL402 SNA → APC May 7, 12:10 UTCMay 7, 12:25 UTC15m
2026-05-04 JTL402 SNA → APC May 4, 20:50 UTCMay 4, 21:20 UTC30m
2026-05-03 JTL402 SNA → APC May 3, 15:20 UTCMay 3, 15:50 UTC30m
2026-04-29 JTL402 SNA → APC Apr 29, 23:55 UTCApr 30, 01:20 UTC1h 25m
2026-04-29 JTL402 SNA → APC Apr 29, 21:25 UTCApr 29, 22:40 UTC1h 15m
2026-04-29 JTL402 SNA → APC Apr 29, 16:45 UTCApr 29, 17:40 UTC55m
2026-04-29 JTL402 SNA → APC Apr 29, 13:45 UTCApr 29, 15:35 UTC1h 50m
2026-04-26 JTL402 SNA → APC Apr 26, 18:15 UTCApr 26, 19:40 UTC1h 25m
2026-04-26 JTL402 SNA → APC Apr 26, 15:25 UTCApr 26, 16:15 UTC50m
2026-04-24 JTL402 SNA → APC Apr 24, 19:30 UTCApr 24, 21:45 UTC2h 15m
2026-04-23 JTL402 SNA → APC Apr 23, 15:00 UTCApr 23, 17:00 UTC2h 0m

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

Mode-S A4B4CC frequently asked

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