sensors Mode-S transponder
AA54EF
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N765JM · CESSNA T182 Turbo Skylane · operated by RUPPEL WILLI
- Hex
- AA54EF
- Octal
- 52452357
- Decimal
- 11,162,863
- Country
- US
- Tail
- N765JM
- Type
- C82S
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 21:30 UTC
Last known position
Country allocation
The ICAO 24-bit address AA54EF 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 |
|---|---|---|---|
| N765JM | - | 56 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N765JM | - | Jul 26, 21:20 UTC | Jul 26, 21:30 UTC | 10m |
| 2026-07-25 | N765JM | - | Jul 25, 22:00 UTC | Jul 25, 22:10 UTC | 10m |
| 2026-07-25 | N765JM | - | Jul 25, 00:30 UTC | Jul 25, 02:35 UTC | 2h 5m |
| 2026-07-24 | N765JM | - | Jul 24, 20:15 UTC | Jul 24, 21:40 UTC | 1h 25m |
| 2026-07-22 | N765JM | - | Jul 22, 22:25 UTC | Jul 22, 22:40 UTC | 15m |
| 2026-07-22 | N765JM | - | Jul 22, 20:10 UTC | Jul 22, 20:30 UTC | 20m |
| 2026-07-20 | N765JM | - | Jul 20, 20:45 UTC | Jul 20, 20:55 UTC | 10m |
| 2026-07-18 | N765JM | - | Jul 18, 00:55 UTC | Jul 18, 02:19 UTC | 1h 25m |
| 2026-07-17 | N765JM | - | Jul 17, 19:25 UTC | Jul 17, 20:55 UTC | 1h 30m |
| 2026-07-15 | N765JM | - | Jul 15, 23:40 UTC | Jul 15, 23:55 UTC | 15m |
| 2026-07-15 | N765JM | - | Jul 15, 19:45 UTC | Jul 15, 20:05 UTC | 20m |
| 2026-07-10 | N765JM | - | Jul 10, 23:25 UTC | Jul 11, 00:00 UTC | 35m |
| 2026-07-10 | N765JM | - | Jul 10, 22:10 UTC | Jul 10, 22:45 UTC | 35m |
| 2026-07-09 | N765JM | - | Jul 9, 22:10 UTC | Jul 10, 00:10 UTC | 2h 0m |
| 2026-07-09 | N765JM | - | Jul 9, 20:05 UTC | Jul 9, 20:35 UTC | 30m |
| 2026-07-04 | N765JM | - | Jul 4, 07:45 UTC | Jul 4, 07:55 UTC | 10m |
| 2026-07-03 | N765JM | - | Jul 3, 23:55 UTC | Jul 4, 01:10 UTC | 1h 15m |
| 2026-07-03 | N765JM | - | Jul 3, 18:50 UTC | Jul 3, 20:10 UTC | 1h 20m |
| 2026-07-01 | N765JM | - | Jul 1, 23:55 UTC | Jul 2, 01:15 UTC | 1h 20m |
| 2026-07-01 | N765JM | - | Jul 1, 18:50 UTC | Jul 1, 20:20 UTC | 1h 30m |
| 2026-06-25 | N765JM | - | Jun 25, 14:44 UTC | Jun 25, 14:59 UTC | 15m |
| 2026-06-22 | N765JM | MEV → MEV | Jun 22, 21:30 UTC | Jun 22, 22:34 UTC | 1h 5m |
| 2026-06-11 | N765JM | - | Jun 11, 22:35 UTC | Jun 11, 22:45 UTC | 10m |
| 2026-06-11 | N765JM | - | Jun 11, 19:40 UTC | Jun 11, 20:00 UTC | 20m |
| 2026-06-06 | N765JM | - | Jun 6, 00:00 UTC | Jun 6, 00:10 UTC | 10m |
| 2026-06-05 | N765JM | - | Jun 5, 19:55 UTC | Jun 5, 20:10 UTC | 15m |
| 2026-06-04 | N765JM | - | Jun 4, 01:00 UTC | Jun 4, 01:10 UTC | 10m |
| 2026-06-03 | N765JM | - | Jun 3, 15:40 UTC | Jun 3, 15:55 UTC | 15m |
| 2026-06-02 | N765JM | - | Jun 2, 01:05 UTC | Jun 2, 01:50 UTC | 45m |
| 2026-06-01 | N765JM | - | Jun 1, 23:10 UTC | Jun 1, 23:55 UTC | 45m |
| 2026-05-21 | N765JM | - | May 21, 22:25 UTC | May 21, 23:00 UTC | 35m |
| 2026-05-21 | N765JM | - | May 21, 20:15 UTC | May 21, 20:50 UTC | 35m |
| 2026-05-20 | N765JM | - | May 20, 01:45 UTC | May 20, 03:10 UTC | 1h 25m |
| 2026-05-19 | N765JM | - | May 19, 19:30 UTC | May 19, 20:50 UTC | 1h 20m |
| 2026-05-18 | N765JM | - | May 18, 23:05 UTC | May 18, 23:20 UTC | 15m |
| 2026-05-18 | N765JM | - | May 18, 20:30 UTC | May 18, 20:50 UTC | 20m |
| 2026-05-08 | N765JM | - | May 8, 20:35 UTC | May 8, 20:50 UTC | 15m |
| 2026-05-08 | N765JM | - | May 8, 16:45 UTC | May 8, 17:05 UTC | 20m |
| 2026-05-06 | N765JM | - | May 6, 22:25 UTC | May 6, 23:40 UTC | 1h 15m |
| 2026-05-06 | N765JM | - | May 6, 21:05 UTC | May 6, 21:40 UTC | 35m |
| 2026-05-01 | N765JM | - | May 1, 23:05 UTC | May 1, 23:15 UTC | 10m |
| 2026-05-01 | N765JM | - | May 1, 20:15 UTC | May 1, 20:35 UTC | 20m |
| 2026-04-29 | N765JM | - | Apr 29, 22:25 UTC | Apr 29, 22:35 UTC | 10m |
| 2026-04-29 | N765JM | - | Apr 29, 16:40 UTC | Apr 29, 16:50 UTC | 10m |
| 2026-04-25 | N765JM | - | Apr 25, 02:15 UTC | Apr 25, 03:05 UTC | 50m |
| 2026-04-25 | N765JM | - | Apr 25, 01:05 UTC | Apr 25, 01:35 UTC | 30m |
| 2026-04-24 | N765JM | - | Apr 24, 20:10 UTC | Apr 24, 21:25 UTC | 1h 15m |
| 2026-04-23 | N765JM | - | Apr 23, 23:25 UTC | Apr 24, 00:15 UTC | 50m |
| 2026-04-23 | N765JM | - | Apr 23, 21:15 UTC | Apr 23, 21:55 UTC | 40m |
| 2026-04-17 | N765JM | - | Apr 17, 00:25 UTC | Apr 17, 00:35 UTC | 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 N765JM page for operator, model, and routing details .