sensors Mode-S transponder
A9E65A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N737PJ · CESSNA 172 Skyhawk · operated by CHAWILDER LLC
- Hex
- A9E65A
- Octal
- 52363132
- Decimal
- 11,134,554
- Country
- US
- Tail
- N737PJ
- Type
- C172
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address A9E65A 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 |
|---|---|---|---|
| N737PJ | - | 66 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | N737PJ | CHA → CHA | Jul 13, 14:35 UTC | Jul 13, 15:35 UTC | 1h 0m |
| 2026-07-02 | N737PJ | - | Jul 2, 18:35 UTC | Jul 2, 19:00 UTC | 25m |
| 2026-06-30 | N737PJ | - | Jun 30, 19:30 UTC | Jun 30, 20:00 UTC | 30m |
| 2026-06-29 | N737PJ | - | Jun 29, 18:14 UTC | Jun 29, 19:20 UTC | 1h 5m |
| 2026-06-29 | N737PJ | - | Jun 29, 12:20 UTC | Jun 29, 13:59 UTC | 1h 40m |
| 2026-06-27 | N737PJ | - | Jun 27, 12:45 UTC | Jun 27, 13:49 UTC | 1h 5m |
| 2026-06-27 | N737PJ | - | Jun 27, 00:44 UTC | Jun 27, 01:00 UTC | 15m |
| 2026-06-26 | N737PJ | - | Jun 26, 22:05 UTC | Jun 27, 00:05 UTC | 2h 0m |
| 2026-06-26 | N737PJ | CHA → CHA | Jun 26, 17:15 UTC | Jun 26, 18:24 UTC | 1h 10m |
| 2026-06-26 | N737PJ | - | Jun 26, 14:44 UTC | Jun 26, 15:10 UTC | 25m |
| 2026-06-25 | N737PJ | - | Jun 25, 19:20 UTC | Jun 25, 19:54 UTC | 35m |
| 2026-06-05 | N737PJ | - | Jun 5, 20:20 UTC | Jun 5, 20:45 UTC | 25m |
| 2026-06-04 | N737PJ | - | Jun 4, 20:05 UTC | Jun 4, 20:40 UTC | 35m |
| 2026-06-04 | N737PJ | - | Jun 4, 15:55 UTC | Jun 4, 16:05 UTC | 10m |
| 2026-06-04 | N737PJ | - | Jun 4, 13:35 UTC | Jun 4, 15:10 UTC | 1h 35m |
| 2026-06-03 | N737PJ | - | Jun 3, 15:15 UTC | Jun 3, 16:05 UTC | 50m |
| 2026-06-03 | N737PJ | - | Jun 3, 13:45 UTC | Jun 3, 14:05 UTC | 20m |
| 2026-06-02 | N737PJ | - | Jun 2, 15:55 UTC | Jun 2, 16:10 UTC | 15m |
| 2026-06-02 | N737PJ | - | Jun 2, 13:30 UTC | Jun 2, 13:50 UTC | 20m |
| 2026-06-01 | N737PJ | - | Jun 1, 14:15 UTC | Jun 1, 14:55 UTC | 40m |
| 2026-06-01 | N737PJ | - | Jun 1, 12:20 UTC | Jun 1, 13:15 UTC | 55m |
| 2026-05-31 | N737PJ | CHA → CHA | May 31, 18:55 UTC | May 31, 20:10 UTC | 1h 15m |
| 2026-05-29 | N737PJ | - | May 29, 14:45 UTC | May 29, 15:00 UTC | 15m |
| 2026-05-29 | N737PJ | - | May 29, 12:55 UTC | May 29, 13:10 UTC | 15m |
| 2026-05-28 | N737PJ | - | May 28, 14:40 UTC | May 28, 15:50 UTC | 1h 10m |
| 2026-05-27 | N737PJ | - | May 27, 18:00 UTC | May 27, 19:15 UTC | 1h 15m |
| 2026-05-21 | N737PJ | - | May 21, 15:55 UTC | May 21, 16:50 UTC | 55m |
| 2026-05-20 | N737PJ | - | May 20, 15:40 UTC | May 20, 16:50 UTC | 1h 10m |
| 2026-05-15 | N737PJ | - | May 15, 18:15 UTC | May 15, 19:10 UTC | 55m |
| 2026-05-15 | N737PJ | - | May 15, 15:20 UTC | May 15, 17:35 UTC | 2h 15m |
| 2026-05-14 | N737PJ | - | May 14, 16:10 UTC | May 14, 17:25 UTC | 1h 15m |
| 2026-05-13 | N737PJ | - | May 13, 22:35 UTC | May 14, 00:50 UTC | 2h 15m |
| 2026-05-12 | N737PJ | - | May 12, 15:50 UTC | May 12, 16:45 UTC | 55m |
| 2026-05-08 | N737PJ | - | May 8, 15:20 UTC | May 8, 17:20 UTC | 2h 0m |
| 2026-05-07 | N737PJ | - | May 7, 21:40 UTC | May 7, 22:15 UTC | 35m |
| 2026-05-07 | N737PJ | - | May 7, 20:50 UTC | May 7, 21:05 UTC | 15m |
| 2026-05-07 | N737PJ | - | May 7, 18:40 UTC | May 7, 19:40 UTC | 1h 0m |
| 2026-05-07 | N737PJ | - | May 7, 12:45 UTC | May 7, 13:50 UTC | 1h 5m |
| 2026-05-06 | N737PJ | - | May 6, 17:55 UTC | May 6, 18:35 UTC | 40m |
| 2026-05-05 | N737PJ | - | May 5, 04:50 UTC | May 5, 07:30 UTC | 2h 40m |
| 2026-05-05 | N737PJ | - | May 5, 04:10 UTC | May 5, 04:40 UTC | 30m |
| 2026-05-05 | N737PJ | - | May 5, 01:50 UTC | May 5, 03:35 UTC | 1h 45m |
| 2026-05-05 | N737PJ | - | May 5, 00:30 UTC | May 5, 00:40 UTC | 10m |
| 2026-05-01 | N737PJ | - | May 1, 21:05 UTC | May 1, 21:20 UTC | 15m |
| 2026-04-30 | N737PJ | - | Apr 30, 20:20 UTC | Apr 30, 21:05 UTC | 45m |
| 2026-04-30 | N737PJ | - | Apr 30, 12:50 UTC | Apr 30, 14:55 UTC | 2h 5m |
| 2026-04-30 | N737PJ | - | Apr 30, 10:30 UTC | Apr 30, 11:10 UTC | 40m |
| 2026-04-30 | N737PJ | - | Apr 30, 08:35 UTC | Apr 30, 09:45 UTC | 1h 10m |
| 2026-04-29 | N737PJ | CHA → CHA | Apr 29, 20:05 UTC | Apr 29, 20:45 UTC | 40m |
| 2026-04-27 | N737PJ | - | Apr 27, 17:40 UTC | Apr 27, 19:50 UTC | 2h 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 N737PJ page for operator, model, and routing details .