sensors Mode-S transponder
A02E72
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N110Z · SHORT 360 · operated by USDA FOREST SERVICE, FIRE & AVIATION
- Hex
- A02E72
- Octal
- 50027162
- Decimal
- 10,497,650
- Country
- US
- Tail
- N110Z
- Type
- SH36
- Flights observed
- 55
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address A02E72 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 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | JPR10 | - | Jul 25, 18:45 UTC | Jul 25, 19:10 UTC | 25m |
| 2026-07-24 | JPR10 | - | Jul 24, 03:45 UTC | Jul 24, 04:10 UTC | 25m |
| 2026-07-24 | JPR10 | - | Jul 24, 02:05 UTC | Jul 24, 02:15 UTC | 10m |
| 2026-07-24 | JPR10 | - | Jul 24, 00:10 UTC | Jul 24, 00:25 UTC | 15m |
| 2026-07-23 | JPR10 | - | Jul 23, 19:25 UTC | Jul 23, 19:55 UTC | 30m |
| 2026-07-23 | JPR10 | - | Jul 23, 18:25 UTC | Jul 23, 18:45 UTC | 20m |
| 2026-07-20 | JPR10 | - | Jul 20, 01:25 UTC | Jul 20, 01:50 UTC | 25m |
| 2026-07-20 | JPR10 | - | Jul 20, 00:25 UTC | Jul 20, 00:40 UTC | 15m |
| 2026-07-19 | JPR10 | - | Jul 19, 18:45 UTC | Jul 19, 18:55 UTC | 10m |
| 2026-07-19 | JPR10 | - | Jul 19, 17:45 UTC | Jul 19, 18:00 UTC | 15m |
| 2026-07-18 | JPR10 | - | Jul 18, 23:05 UTC | Jul 19, 01:15 UTC | 2h 10m |
| 2026-07-18 | JPR10 | - | Jul 18, 02:50 UTC | Jul 18, 03:10 UTC | 20m |
| 2026-07-17 | JPR10 | - | Jul 17, 20:04 UTC | Jul 17, 20:20 UTC | 15m |
| 2026-07-15 | JPR10 | - | Jul 15, 00:20 UTC | Jul 15, 00:35 UTC | 15m |
| 2026-07-14 | JPR10 | - | Jul 14, 22:20 UTC | Jul 14, 23:40 UTC | 1h 19m |
| 2026-07-11 | JPR10 | RDD → RDD | Jul 11, 18:15 UTC | Jul 11, 18:20 UTC | 5m |
| 2026-07-02 | JPR10 | - | Jul 2, 18:40 UTC | Jul 2, 19:30 UTC | 50m |
| 2026-07-01 | JPR10 | RDD → RDD | Jul 1, 18:45 UTC | Jul 1, 19:30 UTC | 45m |
| 2026-06-26 | JPR10 | - | Jun 26, 18:24 UTC | Jun 26, 19:04 UTC | 40m |
| 2026-06-17 | JPR10 | - | Jun 17, 21:45 UTC | Jun 17, 22:50 UTC | 1h 5m |
| 2026-06-17 | JPR10 | - | Jun 17, 18:40 UTC | Jun 17, 19:25 UTC | 45m |
| 2026-06-16 | JPR10 | - | Jun 16, 21:40 UTC | Jun 16, 23:40 UTC | 2h 0m |
| 2026-06-16 | JPR10 | RDD → RDD | Jun 16, 18:50 UTC | Jun 16, 19:35 UTC | 45m |
| 2026-06-15 | JPR10 | - | Jun 15, 18:25 UTC | Jun 15, 20:10 UTC | 1h 45m |
| 2026-06-05 | JPR10 | - | Jun 5, 20:35 UTC | Jun 5, 20:45 UTC | 10m |
| 2026-06-05 | JPR10 | - | Jun 5, 19:35 UTC | Jun 5, 19:50 UTC | 15m |
| 2026-05-31 | JPR10 | RDD → RDD | May 31, 18:55 UTC | May 31, 19:45 UTC | 50m |
| 2026-05-26 | JPR10 | - | May 26, 00:04 UTC | May 26, 00:19 UTC | 15m |
| 2026-05-25 | JPR10 | - | May 25, 22:49 UTC | May 25, 23:10 UTC | 20m |
| 2026-05-24 | JPR10 | RDD → RDD | May 24, 19:00 UTC | May 24, 19:55 UTC | 55m |
| 2026-05-23 | JPR10 | - | May 23, 18:15 UTC | May 23, 20:30 UTC | 2h 15m |
| 2026-05-22 | JPR10 | RDD → RDD | May 22, 21:40 UTC | May 22, 23:10 UTC | 1h 30m |
| 2026-05-21 | JPR10 | - | May 21, 22:00 UTC | May 21, 23:35 UTC | 1h 35m |
| 2026-05-18 | JPR10 | - | May 18, 17:25 UTC | May 18, 18:10 UTC | 45m |
| 2026-05-13 | JPR10 | - | May 13, 00:15 UTC | May 13, 01:50 UTC | 1h 35m |
| 2026-05-11 | JPR10 | - | May 11, 20:30 UTC | May 11, 21:15 UTC | 45m |
| 2026-05-11 | JPR10 | RDD → RDD | May 11, 16:25 UTC | May 11, 17:10 UTC | 45m |
| 2026-05-08 | JPR10 | RDD → RDD | May 8, 20:50 UTC | May 8, 21:45 UTC | 55m |
| 2026-05-08 | JPR10 | - | May 8, 18:35 UTC | May 8, 19:10 UTC | 35m |
| 2026-05-08 | JPR10 | - | May 8, 01:49 UTC | May 8, 02:04 UTC | 15m |
| 2026-05-08 | JPR10 | - | May 8, 00:40 UTC | May 8, 00:49 UTC | 10m |
| 2026-05-07 | N110Z | - | May 7, 23:39 UTC | May 7, 23:55 UTC | 15m |
| 2026-05-07 | N110Z | - | May 7, 22:40 UTC | May 7, 22:54 UTC | 14m |
| 2026-05-07 | N110Z | - | May 7, 15:00 UTC | May 7, 15:15 UTC | 15m |
| 2026-05-07 | N110Z | - | May 7, 13:55 UTC | May 7, 14:10 UTC | 15m |
| 2026-04-30 | JPR10 | RDD → RDD | Apr 30, 21:00 UTC | Apr 30, 22:00 UTC | 1h 0m |
| 2026-04-30 | JPR10 | - | Apr 30, 16:00 UTC | Apr 30, 16:45 UTC | 45m |
| 2026-04-30 | JPR10 | - | Apr 30, 14:55 UTC | Apr 30, 15:25 UTC | 30m |
| 2026-04-29 | JPR10 | - | Apr 29, 21:05 UTC | Apr 29, 22:00 UTC | 55m |
| 2026-04-29 | JPR10 | - | Apr 29, 16:40 UTC | Apr 29, 17:20 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 N110Z page for operator, model, and routing details .