sensors Mode-S transponder
A6B147
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N530JT · BEECH 90 King Air · operated by TVPX AIRCRAFT SOLUTIONS INC TRUSTEE
- Hex
- A6B147
- Octal
- 51530507
- Decimal
- 10,924,359
- Country
- US
- Tail
- N530JT
- Type
- BE9L
- Flights observed
- 67
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 24, 23:15 UTC
Last known position
Country allocation
The ICAO 24-bit address A6B147 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 |
|---|---|---|---|
| N530JT | - | 67 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N530JT | - | Jul 24, 20:55 UTC | Jul 24, 23:15 UTC | 2h 20m |
| 2026-07-24 | N530JT | - | Jul 24, 14:40 UTC | Jul 24, 15:20 UTC | 40m |
| 2026-07-21 | N530JT | - | Jul 21, 18:05 UTC | Jul 21, 20:00 UTC | 1h 55m |
| 2026-07-21 | N530JT | - | Jul 21, 13:25 UTC | Jul 21, 14:25 UTC | 1h 0m |
| 2026-07-21 | N530JT | - | Jul 21, 03:35 UTC | Jul 21, 04:00 UTC | 25m |
| 2026-07-20 | N530JT | - | Jul 20, 21:30 UTC | Jul 20, 22:00 UTC | 30m |
| 2026-07-17 | N530JT | - | Jul 17, 19:20 UTC | Jul 17, 20:10 UTC | 50m |
| 2026-07-17 | N530JT | - | Jul 17, 14:44 UTC | Jul 17, 15:29 UTC | 45m |
| 2026-07-13 | N530JT | - | Jul 13, 21:15 UTC | Jul 13, 22:00 UTC | 45m |
| 2026-07-13 | N530JT | - | Jul 13, 19:20 UTC | Jul 13, 20:10 UTC | 50m |
| 2026-07-08 | N530JT | - | Jul 8, 17:20 UTC | Jul 8, 18:00 UTC | 40m |
| 2026-07-07 | N530JT | - | Jul 7, 21:25 UTC | Jul 7, 21:55 UTC | 30m |
| 2026-07-06 | N530JT | - | Jul 6, 11:55 UTC | Jul 6, 12:55 UTC | 1h 0m |
| 2026-07-04 | N530JT | - | Jul 4, 13:00 UTC | Jul 4, 14:20 UTC | 1h 20m |
| 2026-07-02 | N530JT | - | Jul 2, 19:50 UTC | Jul 2, 21:10 UTC | 1h 20m |
| 2026-06-26 | N530JT | - | Jun 26, 20:34 UTC | Jun 26, 21:20 UTC | 45m |
| 2026-06-26 | N530JT | - | Jun 26, 17:25 UTC | Jun 26, 17:59 UTC | 35m |
| 2026-06-23 | N530JT | - | Jun 23, 19:50 UTC | Jun 23, 20:19 UTC | 30m |
| 2026-06-23 | N530JT | - | Jun 23, 18:25 UTC | Jun 23, 19:15 UTC | 50m |
| 2026-06-13 | N530JT | - | Jun 13, 23:50 UTC | Jun 14, 04:05 UTC | 4h 15m |
| 2026-06-13 | N530JT | - | Jun 13, 21:30 UTC | Jun 13, 21:50 UTC | 20m |
| 2026-06-13 | N530JT | - | Jun 13, 21:05 UTC | Jun 13, 21:25 UTC | 20m |
| 2026-06-12 | N530JT | - | Jun 12, 15:30 UTC | Jun 12, 17:20 UTC | 1h 50m |
| 2026-06-11 | N530JT | - | Jun 11, 13:15 UTC | Jun 11, 15:35 UTC | 2h 20m |
| 2026-06-10 | N530JT | - | Jun 10, 15:10 UTC | Jun 10, 15:55 UTC | 45m |
| 2026-06-10 | N530JT | - | Jun 10, 12:40 UTC | Jun 10, 13:20 UTC | 40m |
| 2026-06-07 | N530JT | - | Jun 7, 21:40 UTC | Jun 7, 22:10 UTC | 30m |
| 2026-06-07 | N530JT | - | Jun 7, 20:15 UTC | Jun 7, 21:05 UTC | 50m |
| 2026-05-28 | N530JT | - | May 28, 23:55 UTC | May 29, 01:30 UTC | 1h 35m |
| 2026-05-28 | N530JT | - | May 28, 19:20 UTC | May 28, 19:35 UTC | 15m |
| 2026-05-28 | N530JT | - | May 28, 12:40 UTC | May 28, 14:50 UTC | 2h 10m |
| 2026-05-22 | N530JT | - | May 22, 18:40 UTC | May 22, 19:30 UTC | 50m |
| 2026-05-22 | N530JT | - | May 22, 15:10 UTC | May 22, 15:50 UTC | 40m |
| 2026-05-19 | N530JT | - | May 19, 22:55 UTC | May 19, 23:35 UTC | 40m |
| 2026-05-19 | N530JT | - | May 19, 18:00 UTC | May 19, 18:55 UTC | 55m |
| 2026-05-19 | N530JT | - | May 19, 15:20 UTC | May 19, 16:45 UTC | 1h 25m |
| 2026-05-18 | N530JT | - | May 18, 21:45 UTC | May 18, 22:20 UTC | 35m |
| 2026-05-18 | N530JT | - | May 18, 10:05 UTC | May 18, 11:55 UTC | 1h 50m |
| 2026-05-08 | N530JT | - | May 8, 20:40 UTC | May 8, 21:35 UTC | 55m |
| 2026-05-08 | N530JT | - | May 8, 13:00 UTC | May 8, 13:40 UTC | 40m |
| 2026-05-06 | N530JT | - | May 6, 22:45 UTC | May 6, 23:20 UTC | 35m |
| 2026-05-06 | N530JT | - | May 6, 19:10 UTC | May 6, 20:15 UTC | 1h 5m |
| 2026-05-06 | N530JT | - | May 6, 17:00 UTC | May 6, 17:45 UTC | 44m |
| 2026-05-02 | N530JT | - | May 2, 01:45 UTC | May 2, 02:25 UTC | 40m |
| 2026-04-30 | N530JT | - | Apr 30, 20:50 UTC | Apr 30, 21:40 UTC | 50m |
| 2026-04-29 | N530JT | - | Apr 29, 21:35 UTC | Apr 29, 22:20 UTC | 45m |
| 2026-04-29 | N530JT | - | Apr 29, 15:35 UTC | Apr 29, 16:30 UTC | 55m |
| 2026-04-29 | N530JT | - | Apr 29, 05:35 UTC | Apr 29, 06:25 UTC | 50m |
| 2026-04-28 | N530JT | - | Apr 28, 21:45 UTC | Apr 28, 22:40 UTC | 55m |
| 2026-04-24 | N530JT | - | Apr 24, 17:25 UTC | Apr 24, 18:05 UTC | 40m |
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 N530JT page for operator, model, and routing details .