Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A3A5FC

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N334PM · operated by RD1989 LEASING LLC

Hex
A3A5FC
Octal
50722774
Decimal
10,724,860
Country
US
Tail
N334PM
Type
C56X
No current signal · last broadcast Jul 26, 20:10 UTC
Flights observed
107
Distinct callsigns
1
Country
US
Last broadcast
Jul 26, 20:10 UTC

Last known position

Most recent position reported by Mode-S A3A5FC.

Country allocation

The ICAO 24-bit address A3A5FC 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
JTL334 Jetall Holdings 107 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 JTL334 BOS → MSN Jul 26, 19:10 UTCJul 26, 20:10 UTC1h 0m
2026-07-26 JTL334 BOS → MSN Jul 26, 16:15 UTCJul 26, 18:05 UTC1h 50m
2026-07-26 JTL334 BOS → MSN Jul 26, 12:40 UTCJul 26, 13:45 UTC1h 5m
2026-07-26 JTL334 BOS → MSN Jul 26, 10:30 UTCJul 26, 11:50 UTC1h 20m
2026-07-25 JTL334 BOS → MSN Jul 25, 20:40 UTCJul 25, 21:25 UTC45m
2026-07-24 JTL334 BOS → MSN Jul 24, 20:30 UTCJul 24, 21:35 UTC1h 5m
2026-07-24 JTL334 BOS → MSN Jul 24, 18:45 UTCJul 24, 19:45 UTC1h 0m
2026-07-24 JTL334 BOS → MSN Jul 24, 02:25 UTCJul 24, 03:25 UTC1h 0m
2026-07-23 JTL334 BOS → MSN Jul 23, 21:10 UTCJul 23, 23:10 UTC2h 0m
2026-07-22 JTL334 BOS → MSN Jul 22, 23:20 UTCJul 23, 00:15 UTC55m
2026-07-22 JTL334 BOS → MSN Jul 22, 18:35 UTCJul 22, 19:40 UTC1h 5m
2026-07-22 JTL334 BOS → MSN Jul 22, 16:55 UTCJul 22, 17:35 UTC40m
2026-07-21 JTL334 BOS → MSN Jul 21, 18:15 UTCJul 21, 20:10 UTC1h 55m
2026-07-21 JTL334 BOS → MSN Jul 21, 15:10 UTCJul 21, 15:40 UTC30m
2026-07-21 JTL334 BOS → MSN Jul 21, 13:35 UTCJul 21, 14:20 UTC45m
2026-07-20 JTL334 BOS → MSN Jul 20, 19:05 UTCJul 20, 19:35 UTC30m
2026-07-20 JTL334 BOS → MSN Jul 20, 16:05 UTCJul 20, 18:20 UTC2h 15m
2026-07-14 JTL334 - Jul 14, 21:55 UTCJul 14, 22:55 UTC59m
2026-07-14 JTL334 FCM → MKE Jul 14, 01:40 UTCJul 14, 02:35 UTC55m
2026-07-12 JTL334 RST → FCM Jul 12, 21:05 UTCJul 12, 21:25 UTC20m
2026-07-12 JTL334 - Jul 12, 18:20 UTCJul 12, 20:20 UTC2h 0m
2026-07-11 JTL334 - Jul 11, 22:05 UTCJul 11, 22:45 UTC40m
2026-07-11 JTL334 - Jul 11, 19:35 UTCJul 11, 21:25 UTC1h 50m
2026-07-10 JTL334 - Jul 10, 22:45 UTCJul 11, 00:25 UTC1h 40m
2026-07-05 JTL334 - Jul 5, 22:50 UTCJul 5, 23:30 UTC40m
2026-07-05 JTL334 - Jul 5, 21:00 UTCJul 5, 22:10 UTC1h 10m
2026-07-05 JTL334 OMA → ATW Jul 5, 18:05 UTCJul 5, 19:10 UTC1h 5m
2026-07-05 JTL334 - Jul 5, 16:00 UTCJul 5, 16:55 UTC55m
2026-07-05 JTL334 - Jul 5, 13:25 UTCJul 5, 13:50 UTC25m
2026-07-02 JTL334 - Jul 2, 15:50 UTCJul 2, 16:10 UTC20m
2026-07-02 JTL334 - Jul 2, 14:25 UTCJul 2, 15:10 UTC45m
2026-07-01 JTL334 - Jul 1, 16:15 UTCJul 1, 18:30 UTC2h 15m
2026-07-01 JTL334 - Jul 1, 13:50 UTCJul 1, 14:35 UTC45m
2026-06-27 JTL334 GRB → FCM Jun 27, 20:14 UTCJun 27, 21:04 UTC50m
2026-06-26 JTL334 - Jun 26, 15:45 UTCJun 26, 16:24 UTC40m
2026-06-24 JTL334 IND → MSP Jun 24, 19:15 UTCJun 24, 20:44 UTC1h 30m
2026-06-24 JTL334 - Jun 24, 16:09 UTCJun 24, 17:34 UTC1h 25m
2026-06-24 JTL334 BED → RDU Jun 24, 13:34 UTCJun 24, 15:29 UTC1h 55m
2026-06-23 JTL334 - Jun 23, 18:34 UTCJun 23, 19:04 UTC30m
2026-06-23 JTL334 - Jun 23, 14:19 UTCJun 23, 17:25 UTC3h 5m
2026-06-23 JTL334 - Jun 23, 11:35 UTCJun 23, 12:20 UTC45m
2026-06-21 JTL334 - Jun 21, 15:49 UTCJun 21, 16:25 UTC35m
2026-06-19 JTL334 - Jun 19, 15:44 UTCJun 19, 16:14 UTC30m
2026-06-19 JTL334 - Jun 19, 14:24 UTCJun 19, 15:04 UTC40m
2026-06-18 JTL334 APA → FCM Jun 18, 19:45 UTCJun 18, 21:20 UTC1h 35m
2026-06-11 JTL334 APA → APA Jun 11, 21:05 UTCJun 11, 21:20 UTC15m
2026-06-11 JTL334 - Jun 11, 15:50 UTCJun 11, 16:40 UTC50m
2026-06-11 JTL334 - Jun 11, 14:10 UTCJun 11, 14:50 UTC40m
2026-06-11 JTL334 - Jun 11, 12:05 UTCJun 11, 13:00 UTC55m
2026-06-08 JTL334 BOS → MSN Jun 8, 01:30 UTCJun 8, 03:15 UTC1h 45m

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

Mode-S A3A5FC frequently asked

What is Mode-S code A3A5FC?
A3A5FC is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N334PM.
Where is Mode-S A3A5FC registered?
Mode-S code A3A5FC 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 A3A5FC broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 20:10 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A3A5FC, octal 50722774, decimal 10,724,860.
What flights does A3A5FC operate?
Mode-S A3A5FC has broadcast 1 distinct callsign, including JTL334.