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
- Flights observed
- 89
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 5h ago
Last known position
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 | - | 89 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JTL334 | FCM → MKE | Jul 14, 01:40 UTC | Jul 14, 02:35 UTC | 55m |
| 2026-07-12 | JTL334 | RST → FCM | Jul 12, 21:05 UTC | Jul 12, 21:25 UTC | 20m |
| 2026-07-12 | JTL334 | - | Jul 12, 18:20 UTC | Jul 12, 20:20 UTC | 2h 0m |
| 2026-07-11 | JTL334 | - | Jul 11, 22:05 UTC | Jul 11, 22:45 UTC | 40m |
| 2026-07-11 | JTL334 | - | Jul 11, 19:35 UTC | Jul 11, 21:25 UTC | 1h 50m |
| 2026-07-10 | JTL334 | - | Jul 10, 22:45 UTC | Jul 11, 00:25 UTC | 1h 40m |
| 2026-07-05 | JTL334 | - | Jul 5, 22:50 UTC | Jul 5, 23:30 UTC | 40m |
| 2026-07-05 | JTL334 | - | Jul 5, 21:00 UTC | Jul 5, 22:10 UTC | 1h 10m |
| 2026-07-05 | JTL334 | OMA → ATW | Jul 5, 18:05 UTC | Jul 5, 19:10 UTC | 1h 5m |
| 2026-07-05 | JTL334 | - | Jul 5, 16:00 UTC | Jul 5, 16:55 UTC | 55m |
| 2026-07-05 | JTL334 | - | Jul 5, 13:25 UTC | Jul 5, 13:50 UTC | 25m |
| 2026-07-02 | JTL334 | - | Jul 2, 15:50 UTC | Jul 2, 16:10 UTC | 20m |
| 2026-07-02 | JTL334 | - | Jul 2, 14:25 UTC | Jul 2, 15:10 UTC | 45m |
| 2026-07-01 | JTL334 | - | Jul 1, 16:15 UTC | Jul 1, 18:30 UTC | 2h 15m |
| 2026-07-01 | JTL334 | - | Jul 1, 13:50 UTC | Jul 1, 14:35 UTC | 45m |
| 2026-06-27 | JTL334 | GRB → FCM | Jun 27, 20:14 UTC | Jun 27, 21:04 UTC | 50m |
| 2026-06-26 | JTL334 | - | Jun 26, 15:45 UTC | Jun 26, 16:24 UTC | 40m |
| 2026-06-24 | JTL334 | IND → MSP | Jun 24, 19:15 UTC | Jun 24, 20:44 UTC | 1h 30m |
| 2026-06-24 | JTL334 | - | Jun 24, 16:09 UTC | Jun 24, 17:34 UTC | 1h 25m |
| 2026-06-24 | JTL334 | BED → RDU | Jun 24, 13:34 UTC | Jun 24, 15:29 UTC | 1h 55m |
| 2026-06-23 | JTL334 | - | Jun 23, 18:34 UTC | Jun 23, 19:04 UTC | 30m |
| 2026-06-23 | JTL334 | - | Jun 23, 14:19 UTC | Jun 23, 17:25 UTC | 3h 5m |
| 2026-06-23 | JTL334 | - | Jun 23, 11:35 UTC | Jun 23, 12:20 UTC | 45m |
| 2026-06-21 | JTL334 | - | Jun 21, 15:49 UTC | Jun 21, 16:25 UTC | 35m |
| 2026-06-19 | JTL334 | - | Jun 19, 15:44 UTC | Jun 19, 16:14 UTC | 30m |
| 2026-06-19 | JTL334 | - | Jun 19, 14:24 UTC | Jun 19, 15:04 UTC | 40m |
| 2026-06-18 | JTL334 | APA → FCM | Jun 18, 19:45 UTC | Jun 18, 21:20 UTC | 1h 35m |
| 2026-06-11 | JTL334 | APA → APA | Jun 11, 21:05 UTC | Jun 11, 21:20 UTC | 15m |
| 2026-06-11 | JTL334 | - | Jun 11, 15:50 UTC | Jun 11, 16:40 UTC | 50m |
| 2026-06-11 | JTL334 | - | Jun 11, 14:10 UTC | Jun 11, 14:50 UTC | 40m |
| 2026-06-11 | JTL334 | - | Jun 11, 12:05 UTC | Jun 11, 13:00 UTC | 55m |
| 2026-06-08 | JTL334 | BOS → MSN | Jun 8, 01:30 UTC | Jun 8, 03:15 UTC | 1h 45m |
| 2026-06-06 | JTL334 | BOS → MSN | Jun 6, 17:05 UTC | Jun 6, 17:34 UTC | 30m |
| 2026-06-06 | JTL334 | BOS → MSN | Jun 6, 14:20 UTC | Jun 6, 16:04 UTC | 1h 45m |
| 2026-06-05 | JTL334 | BOS → MSN | Jun 5, 18:25 UTC | Jun 5, 20:10 UTC | 1h 45m |
| 2026-06-05 | JTL334 | BOS → MSN | Jun 5, 15:55 UTC | Jun 5, 16:10 UTC | 15m |
| 2026-06-05 | JTL334 | BOS → MSN | Jun 5, 11:10 UTC | Jun 5, 13:10 UTC | 2h 0m |
| 2026-06-02 | JTL334 | BOS → MSN | Jun 2, 18:55 UTC | Jun 2, 20:50 UTC | 1h 55m |
| 2026-06-01 | JTL334 | BOS → MSN | Jun 1, 14:55 UTC | Jun 1, 16:35 UTC | 1h 40m |
| 2026-05-31 | JTL334 | BOS → MSN | May 31, 19:55 UTC | May 31, 20:50 UTC | 55m |
| 2026-05-31 | JTL334 | BOS → MSN | May 31, 19:00 UTC | May 31, 19:20 UTC | 20m |
| 2026-05-28 | JTL334 | BOS → MSN | May 28, 19:40 UTC | May 28, 19:55 UTC | 15m |
| 2026-05-28 | JTL334 | BOS → MSN | May 28, 18:20 UTC | May 28, 19:10 UTC | 50m |
| 2026-05-22 | JTL334 | BOS → MSN | May 22, 17:35 UTC | May 22, 20:05 UTC | 2h 30m |
| 2026-05-20 | JTL334 | BOS → MSN | May 20, 19:25 UTC | May 20, 21:00 UTC | 1h 35m |
| 2026-05-19 | JTL334 | BOS → MSN | May 19, 19:10 UTC | May 19, 20:45 UTC | 1h 35m |
| 2026-05-19 | JTL334 | BOS → MSN | May 19, 15:00 UTC | May 19, 17:15 UTC | 2h 15m |
| 2026-05-15 | JTL334 | BOS → MSN | May 15, 17:05 UTC | May 15, 20:10 UTC | 3h 5m |
| 2026-05-14 | JTL334 | BOS → MSN | May 14, 20:05 UTC | May 14, 23:40 UTC | 3h 35m |
| 2026-05-13 | JTL334 | BOS → MSN | May 13, 19:10 UTC | May 13, 19:35 UTC | 25m |
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 .