sensors Mode-S transponder
A35F29
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N316XA · operated by REGISTRATION PENDING
- Hex
- A35F29
- Octal
- 50657451
- Decimal
- 10,706,729
- Country
- US
- Tail
- N316XA
- Type
- TBM9
- Flights observed
- 49
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- Jul 13, 00:55 UTC
Last known position
Country allocation
The ICAO 24-bit address A35F29 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 2 distinct
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JNX16 | - | Jul 13, 00:45 UTC | Jul 13, 00:55 UTC | 10m |
| 2026-07-12 | JNX16 | - | Jul 12, 21:35 UTC | Jul 12, 22:15 UTC | 40m |
| 2026-07-12 | JNX16 | - | Jul 12, 17:30 UTC | Jul 12, 18:50 UTC | 1h 20m |
| 2026-07-03 | JNX16 | - | Jul 3, 17:05 UTC | Jul 3, 18:20 UTC | 1h 15m |
| 2026-07-03 | JNX16 | - | Jul 3, 15:00 UTC | Jul 3, 15:50 UTC | 50m |
| 2026-07-03 | JNX16 | - | Jul 3, 12:20 UTC | Jul 3, 12:40 UTC | 20m |
| 2026-06-28 | JNX16 | - | Jun 28, 17:04 UTC | Jun 28, 17:19 UTC | 15m |
| 2026-06-26 | JNX16 | - | Jun 26, 18:20 UTC | Jun 26, 18:34 UTC | 15m |
| 2026-06-24 | JNX16 | - | Jun 24, 13:20 UTC | Jun 24, 14:04 UTC | 45m |
| 2026-06-23 | JNX16 | - | Jun 23, 23:44 UTC | Jun 24, 01:34 UTC | 1h 50m |
| 2026-06-23 | JNX16 | - | Jun 23, 19:15 UTC | Jun 23, 23:05 UTC | 3h 50m |
| 2026-06-20 | N316XA | - | Jun 20, 01:05 UTC | Jun 20, 03:09 UTC | 2h 5m |
| 2026-06-19 | N316XA | - | Jun 19, 21:09 UTC | Jun 20, 00:24 UTC | 3h 15m |
| 2026-06-19 | N316XA | - | Jun 19, 19:09 UTC | Jun 19, 20:04 UTC | 55m |
| 2026-06-17 | N316XA | - | Jun 17, 18:25 UTC | Jun 17, 21:40 UTC | 3h 15m |
| 2026-06-17 | N316XA | - | Jun 17, 16:40 UTC | Jun 17, 17:40 UTC | 1h 0m |
| 2026-06-17 | N316XA | - | Jun 17, 14:00 UTC | Jun 17, 14:20 UTC | 20m |
| 2026-06-06 | N316XA | - | Jun 6, 18:50 UTC | Jun 6, 18:59 UTC | 10m |
| 2026-06-06 | N316XA | - | Jun 6, 15:44 UTC | Jun 6, 16:24 UTC | 40m |
| 2026-06-06 | N316XA | - | Jun 6, 13:00 UTC | Jun 6, 14:59 UTC | 2h 0m |
| 2026-06-02 | N316XA | - | Jun 2, 19:25 UTC | Jun 2, 20:55 UTC | 1h 30m |
| 2026-06-02 | N316XA | - | Jun 2, 15:25 UTC | Jun 2, 18:30 UTC | 3h 5m |
| 2026-05-29 | N316XA | - | May 29, 18:50 UTC | May 29, 22:00 UTC | 3h 10m |
| 2026-05-29 | N316XA | - | May 29, 15:30 UTC | May 29, 18:05 UTC | 2h 35m |
| 2026-05-27 | N316XA | - | May 27, 21:55 UTC | May 27, 23:55 UTC | 2h 0m |
| 2026-05-27 | N316XA | - | May 27, 17:10 UTC | May 27, 20:15 UTC | 3h 5m |
| 2026-05-14 | N316XA | - | May 14, 23:25 UTC | May 15, 01:00 UTC | 1h 35m |
| 2026-05-13 | N316XA | - | May 13, 21:05 UTC | May 13, 22:20 UTC | 1h 15m |
| 2026-05-04 | N316XA | - | May 4, 16:00 UTC | May 4, 18:00 UTC | 2h 0m |
| 2026-05-03 | N316XA | - | May 3, 21:20 UTC | May 4, 00:34 UTC | 3h 15m |
| 2026-05-03 | N316XA | - | May 3, 16:20 UTC | May 3, 20:25 UTC | 4h 5m |
| 2026-05-02 | N316XA | - | May 2, 22:20 UTC | May 2, 22:50 UTC | 30m |
| 2026-04-29 | N316XA | MRK → FXE | Apr 29, 19:20 UTC | Apr 29, 19:45 UTC | 25m |
| 2026-04-29 | N316XA | - | Apr 29, 15:50 UTC | Apr 29, 18:35 UTC | 2h 45m |
| 2026-04-29 | N316XA | - | Apr 29, 14:50 UTC | Apr 29, 15:10 UTC | 20m |
| 2026-04-27 | N316XA | - | Apr 27, 21:25 UTC | Apr 27, 21:50 UTC | 25m |
| 2026-04-27 | N316XA | - | Apr 27, 16:55 UTC | Apr 27, 20:30 UTC | 3h 35m |
| 2026-04-27 | N316XA | - | Apr 27, 14:55 UTC | Apr 27, 16:00 UTC | 1h 5m |
| 2026-04-27 | N316XA | - | Apr 27, 12:05 UTC | Apr 27, 12:25 UTC | 20m |
| 2026-04-24 | N316XA | - | Apr 24, 00:00 UTC | Apr 24, 00:20 UTC | 20m |
| 2026-04-23 | N316XA | - | Apr 23, 21:05 UTC | Apr 23, 21:50 UTC | 45m |
| 2026-04-22 | N316XA | - | Apr 22, 23:00 UTC | Apr 22, 23:30 UTC | 30m |
| 2026-04-21 | N316XA | ORL → TPA | Apr 21, 23:20 UTC | Apr 21, 23:50 UTC | 30m |
| 2026-04-20 | N316XA | - | Apr 20, 23:15 UTC | Apr 21, 02:10 UTC | 2h 55m |
| 2026-04-20 | N316XA | - | Apr 20, 18:20 UTC | Apr 20, 22:20 UTC | 4h 0m |
| 2026-04-16 | N316XA | - | Apr 16, 17:15 UTC | Apr 16, 18:30 UTC | 1h 15m |
| 2026-04-16 | N316XA | - | Apr 16, 16:50 UTC | Apr 16, 17:10 UTC | 20m |
| 2026-04-13 | N316XA | - | Apr 13, 12:20 UTC | Apr 13, 15:45 UTC | 3h 25m |
| 2026-04-13 | N316XA | - | Apr 13, 10:30 UTC | Apr 13, 11:40 UTC | 1h 10m |
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 N316XA page for operator, model, and routing details .