sensors Mode-S transponder
A83B02
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N6297J · PIPER PA-28-140/150/160/180 · operated by YALE AVIATION INC
- Hex
- A83B02
- Octal
- 52035402
- Decimal
- 11,025,154
- Country
- US
- Tail
- N6297J
- Type
- P28A
- Flights observed
- 44
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address A83B02 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 |
|---|---|---|---|
| N6297J | - | 44 | 2026-07-13 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | N6297J | - | Jul 13, 13:10 UTC | Jul 13, 14:00 UTC | 50m |
| 2026-07-12 | N6297J | - | Jul 12, 21:25 UTC | Jul 12, 22:25 UTC | 1h 0m |
| 2026-07-09 | N6297J | - | Jul 9, 01:05 UTC | Jul 9, 01:50 UTC | 45m |
| 2026-06-30 | N6297J | HVN → HVN | Jun 30, 12:30 UTC | Jun 30, 14:10 UTC | 1h 40m |
| 2026-06-29 | N6297J | - | Jun 29, 22:49 UTC | Jun 29, 23:39 UTC | 50m |
| 2026-06-28 | N6297J | - | Jun 28, 22:20 UTC | Jun 28, 22:55 UTC | 35m |
| 2026-06-28 | N6297J | - | Jun 28, 16:09 UTC | Jun 28, 17:10 UTC | 1h 0m |
| 2026-06-25 | N6297J | HVN → HVN | Jun 25, 01:54 UTC | Jun 25, 02:19 UTC | 25m |
| 2026-06-24 | N6297J | - | Jun 24, 13:10 UTC | Jun 24, 14:39 UTC | 1h 30m |
| 2026-06-21 | N6297J | - | Jun 21, 13:09 UTC | Jun 21, 14:40 UTC | 1h 30m |
| 2026-06-16 | N6297J | - | Jun 16, 14:35 UTC | Jun 16, 15:40 UTC | 1h 5m |
| 2026-06-13 | N6297J | - | Jun 13, 21:25 UTC | Jun 13, 22:55 UTC | 1h 30m |
| 2026-06-13 | N6297J | - | Jun 13, 12:55 UTC | Jun 13, 14:05 UTC | 1h 10m |
| 2026-06-12 | N6297J | - | Jun 12, 18:30 UTC | Jun 12, 19:05 UTC | 35m |
| 2026-06-12 | N6297J | HVN → BID | Jun 12, 17:10 UTC | Jun 12, 17:50 UTC | 40m |
| 2026-06-08 | N6297J | - | Jun 8, 14:10 UTC | Jun 8, 14:20 UTC | 10m |
| 2026-06-08 | N6297J | HVN → FOK | Jun 8, 13:20 UTC | Jun 8, 13:40 UTC | 20m |
| 2026-06-04 | N6297J | HVN → HVN | Jun 4, 20:40 UTC | Jun 4, 22:05 UTC | 1h 25m |
| 2026-06-04 | N6297J | HVN → HVN | Jun 4, 14:35 UTC | Jun 4, 15:55 UTC | 1h 20m |
| 2026-06-02 | N6297J | HVN → HVN | Jun 2, 21:15 UTC | Jun 2, 22:45 UTC | 1h 30m |
| 2026-05-31 | N6297J | - | May 31, 18:55 UTC | May 31, 19:20 UTC | 25m |
| 2026-05-31 | N6297J | - | May 31, 16:35 UTC | May 31, 17:10 UTC | 35m |
| 2026-05-27 | N6297J | HVN → HVN | May 27, 22:50 UTC | May 27, 23:15 UTC | 25m |
| 2026-05-27 | N6297J | HVN → HVN | May 27, 19:30 UTC | May 27, 20:40 UTC | 1h 10m |
| 2026-05-16 | N6297J | HVN → HVN | May 16, 12:50 UTC | May 16, 14:16 UTC | 1h 25m |
| 2026-05-12 | N6297J | HVN → HVN | May 12, 20:05 UTC | May 12, 20:35 UTC | 30m |
| 2026-05-12 | N6297J | HVN → HVN | May 12, 18:40 UTC | May 12, 18:55 UTC | 15m |
| 2026-05-12 | N6297J | HVN → HVN | May 12, 17:30 UTC | May 12, 17:35 UTC | 5m |
| 2026-05-12 | N6297J | - | May 12, 16:35 UTC | May 12, 17:15 UTC | 40m |
| 2026-05-12 | N6297J | HVN → HVN | May 12, 15:45 UTC | May 12, 15:50 UTC | 5m |
| 2026-05-11 | N6297J | HVN → HVN | May 11, 18:20 UTC | May 11, 18:30 UTC | 10m |
| 2026-05-11 | N6297J | HVN → HVN | May 11, 17:20 UTC | May 11, 18:10 UTC | 50m |
| 2026-05-11 | N6297J | - | May 11, 16:45 UTC | May 11, 16:55 UTC | 10m |
| 2026-05-11 | N6297J | HVN → HVN | May 11, 15:40 UTC | May 11, 16:05 UTC | 25m |
| 2026-05-08 | N6297J | - | May 8, 13:40 UTC | May 8, 14:55 UTC | 1h 15m |
| 2026-05-07 | N6297J | HVN → HVN | May 7, 13:35 UTC | May 7, 14:25 UTC | 50m |
| 2026-04-20 | N6297J | HVN → HVN | Apr 20, 13:15 UTC | Apr 20, 14:10 UTC | 55m |
| 2026-04-16 | N6297J | HVN → HVN | Apr 16, 20:40 UTC | Apr 16, 21:10 UTC | 30m |
| 2026-04-16 | N6297J | - | Apr 16, 15:15 UTC | Apr 16, 15:25 UTC | 10m |
| 2026-04-16 | N6297J | - | Apr 16, 15:00 UTC | Apr 16, 15:10 UTC | 10m |
| 2026-04-16 | N6297J | - | Apr 16, 13:54 UTC | Apr 16, 14:05 UTC | 10m |
| 2026-04-15 | N6297J | - | Apr 15, 18:40 UTC | Apr 15, 19:00 UTC | 20m |
| 2026-04-14 | N6297J | HVN → HVN | Apr 14, 14:50 UTC | Apr 14, 15:00 UTC | 10m |
| 2026-04-14 | N6297J | - | Apr 14, 13:50 UTC | Apr 14, 14:45 UTC | 55m |
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 N6297J page for operator, model, and routing details .