sensors Mode-S transponder

A4CF95

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N409RP · operated by MH2 CAPITAL LLC

Hex
A4CF95
Octal
51147625
Decimal
10,801,045
Country
US
Tail
N409RP
Type
C25B
No current signal · last broadcast 1d ago
Flights observed
78
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S A4CF95.

Country allocation

The ICAO 24-bit address A4CF95 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
JTL40 - 78 2026-07-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 JTL40 SCF → SCF Jul 13, 17:05 UTCJul 13, 17:55 UTC50m
2026-07-12 JTL40 - Jul 12, 17:30 UTCJul 12, 20:55 UTC3h 25m
2026-07-12 JTL40 FOK → DAL Jul 12, 15:20 UTCJul 12, 16:05 UTC45m
2026-07-05 JTL40 FOK → DAL Jul 5, 22:40 UTCJul 5, 23:35 UTC55m
2026-07-05 JTL40 FOK → DAL Jul 5, 20:55 UTCJul 5, 22:05 UTC1h 10m
2026-07-05 JTL40 FOK → DAL Jul 5, 17:10 UTCJul 5, 18:10 UTC1h 0m
2026-07-05 JTL40 FOK → DAL Jul 5, 15:00 UTCJul 5, 16:20 UTC1h 20m
2026-07-04 JTL40 FOK → DAL Jul 4, 19:30 UTCJul 4, 20:45 UTC1h 15m
2026-07-01 JTL40 FOK → DAL Jul 1, 23:45 UTCJul 2, 00:55 UTC1h 10m
2026-07-01 JTL40 FOK → DAL Jul 1, 21:25 UTCJul 1, 22:40 UTC1h 15m
2026-06-29 JTL40 FOK → DAL Jun 29, 20:44 UTCJun 29, 21:30 UTC45m
2026-06-29 JTL40 FOK → DAL Jun 29, 18:14 UTCJun 29, 20:09 UTC1h 55m
2026-06-28 JTL40 FOK → DAL Jun 28, 18:55 UTCJun 28, 20:45 UTC1h 50m
2026-06-28 JTL40 FOK → DAL Jun 28, 16:45 UTCJun 28, 17:25 UTC40m
2026-06-28 JTL40 FOK → DAL Jun 28, 14:45 UTCJun 28, 16:00 UTC1h 15m
2026-06-27 JTL40 FOK → DAL Jun 27, 19:34 UTCJun 27, 20:24 UTC50m
2026-06-27 JTL40 FOK → DAL Jun 27, 17:14 UTCJun 27, 18:49 UTC1h 35m
2026-06-27 JTL40 FOK → DAL Jun 27, 13:30 UTCJun 27, 15:10 UTC1h 40m
2026-06-26 JTL40 FOK → DAL Jun 26, 18:09 UTCJun 26, 20:10 UTC2h 0m
2026-06-26 JTL40 FOK → DAL Jun 26, 14:15 UTCJun 26, 15:39 UTC1h 25m
2026-06-17 JTL40 FOK → DAL Jun 17, 01:15 UTCJun 17, 01:40 UTC25m
2026-06-16 JTL40 FOK → DAL Jun 16, 23:55 UTCJun 17, 01:10 UTC1h 15m
2026-06-16 JTL40 FOK → DAL Jun 16, 21:50 UTCJun 16, 22:50 UTC1h 0m
2026-06-16 JTL40 FOK → DAL Jun 16, 18:35 UTCJun 16, 20:05 UTC1h 31m
2026-06-14 JTL40 FOK → DAL Jun 14, 22:45 UTCJun 15, 00:35 UTC1h 49m
2026-06-14 JTL40 FOK → DAL Jun 14, 20:30 UTCJun 14, 21:00 UTC30m
2026-06-13 JTL40 FOK → DAL Jun 13, 14:05 UTCJun 13, 14:50 UTC45m
2026-06-12 JTL40 FOK → DAL Jun 12, 19:55 UTCJun 12, 22:10 UTC2h 15m
2026-06-12 JTL40 FOK → DAL Jun 12, 15:25 UTCJun 12, 16:10 UTC45m
2026-06-12 JTL40 FOK → DAL Jun 12, 13:15 UTCJun 12, 14:01 UTC45m
2026-06-08 JTL40 FOK → DAL Jun 8, 19:55 UTCJun 8, 20:55 UTC1h 0m
2026-06-08 JTL40 FOK → DAL Jun 8, 17:55 UTCJun 8, 18:25 UTC30m
2026-05-03 JTL40 FOK → DAL May 3, 21:00 UTCMay 3, 21:24 UTC25m
2026-05-03 JTL40 FOK → DAL May 3, 19:34 UTCMay 3, 20:20 UTC45m
2026-05-03 JTL40 FOK → DAL May 3, 18:14 UTCMay 3, 18:25 UTC10m
2026-05-03 JTL40 FOK → DAL May 3, 16:15 UTCMay 3, 17:35 UTC1h 20m
2026-05-01 JTL40 FOK → DAL May 1, 18:00 UTCMay 1, 19:05 UTC1h 5m
2026-04-30 JTL40 FOK → DAL Apr 30, 21:50 UTCApr 30, 23:15 UTC1h 25m
2026-04-30 JTL40 FOK → DAL Apr 30, 19:15 UTCApr 30, 21:05 UTC1h 50m
2026-04-30 JTL40 FOK → DAL Apr 30, 17:05 UTCApr 30, 17:45 UTC40m
2026-04-30 JTL40 FOK → DAL Apr 30, 14:35 UTCApr 30, 15:50 UTC1h 15m
2026-04-29 JTL40 FOK → DAL Apr 29, 19:55 UTCApr 29, 22:00 UTC2h 5m
2026-04-29 JTL40 FOK → DAL Apr 29, 16:50 UTCApr 29, 18:50 UTC2h 0m
2026-04-29 JTL40 FOK → DAL Apr 29, 14:20 UTCApr 29, 15:00 UTC40m
2026-04-28 JTL40 FOK → DAL Apr 28, 21:30 UTCApr 28, 22:40 UTC1h 10m
2026-04-28 JTL40 FOK → DAL Apr 28, 15:30 UTCApr 28, 16:35 UTC1h 5m
2026-04-27 JTL40 FOK → DAL Apr 27, 14:25 UTCApr 27, 14:50 UTC25m
2026-04-26 JTL40 FOK → DAL Apr 26, 19:05 UTCApr 26, 19:40 UTC35m
2026-04-26 JTL40 FOK → DAL Apr 26, 16:10 UTCApr 26, 18:05 UTC1h 55m
2026-04-26 JTL40 FOK → DAL Apr 26, 14:25 UTCApr 26, 14:50 UTC25m

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

Mode-S A4CF95 frequently asked

What is Mode-S code A4CF95?
A4CF95 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N409RP.
Where is Mode-S A4CF95 registered?
Mode-S code A4CF95 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 A4CF95 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 A4CF95, octal 51147625, decimal 10,801,045.
What flights does A4CF95 operate?
Mode-S A4CF95 has broadcast 1 distinct callsign, including JTL40.