sensors Mode-S transponder
AD82E4
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N97SH · BOMBARDIER BD-100 Challenger 300 · operated by WEST RIDGE AIR II LLC
- Hex
- AD82E4
- Octal
- 53301344
- Decimal
- 11,371,236
- Country
- US
- Tail
- N97SH
- Type
- CL30
- Flights observed
- 64
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 15:00 UTC
Last known position
Country allocation
The ICAO 24-bit address AD82E4 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 |
|---|---|---|---|
| N97SH | - | 64 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N97SH | - | Jul 26, 14:30 UTC | Jul 26, 15:00 UTC | 30m |
| 2026-07-26 | N97SH | - | Jul 26, 13:00 UTC | Jul 26, 13:50 UTC | 50m |
| 2026-07-21 | N97SH | - | Jul 21, 23:40 UTC | Jul 22, 01:10 UTC | 1h 30m |
| 2026-07-21 | N97SH | - | Jul 21, 16:20 UTC | Jul 21, 17:25 UTC | 1h 5m |
| 2026-07-20 | N97SH | - | Jul 20, 18:00 UTC | Jul 20, 18:25 UTC | 25m |
| 2026-07-20 | N97SH | - | Jul 20, 15:20 UTC | Jul 20, 15:45 UTC | 25m |
| 2026-07-18 | N97SH | - | Jul 18, 13:35 UTC | Jul 18, 14:50 UTC | 1h 15m |
| 2026-07-17 | N97SH | - | Jul 17, 14:15 UTC | Jul 17, 15:44 UTC | 1h 30m |
| 2026-07-15 | N97SH | - | Jul 15, 12:50 UTC | Jul 15, 13:55 UTC | 1h 5m |
| 2026-07-14 | N97SH | - | Jul 14, 14:05 UTC | Jul 14, 15:05 UTC | 1h 0m |
| 2026-07-11 | N97SH | - | Jul 11, 02:30 UTC | Jul 11, 03:15 UTC | 45m |
| 2026-07-10 | N97SH | - | Jul 10, 15:50 UTC | Jul 10, 16:50 UTC | 1h 0m |
| 2026-07-09 | N97SH | - | Jul 9, 02:25 UTC | Jul 9, 03:20 UTC | 55m |
| 2026-07-08 | N97SH | - | Jul 8, 15:10 UTC | Jul 8, 15:40 UTC | 30m |
| 2026-07-07 | N97SH | - | Jul 7, 13:50 UTC | Jul 7, 15:15 UTC | 1h 25m |
| 2026-07-01 | N97SH | - | Jul 1, 00:30 UTC | Jul 1, 01:15 UTC | 45m |
| 2026-06-30 | N97SH | - | Jun 30, 20:05 UTC | Jun 30, 21:05 UTC | 1h 0m |
| 2026-06-27 | N97SH | - | Jun 27, 02:39 UTC | Jun 27, 03:25 UTC | 45m |
| 2026-06-26 | N97SH | - | Jun 26, 17:59 UTC | Jun 26, 19:04 UTC | 1h 5m |
| 2026-06-24 | N97SH | BOS → GVE | Jun 24, 13:00 UTC | Jun 24, 14:04 UTC | 1h 5m |
| 2026-06-22 | N97SH | - | Jun 22, 14:29 UTC | Jun 22, 15:35 UTC | 1h 5m |
| 2026-06-21 | N97SH | - | Jun 21, 02:45 UTC | Jun 21, 03:25 UTC | 40m |
| 2026-06-20 | N97SH | - | Jun 20, 16:14 UTC | Jun 20, 16:55 UTC | 40m |
| 2026-06-19 | N97SH | - | Jun 19, 02:39 UTC | Jun 19, 03:24 UTC | 45m |
| 2026-06-18 | N97SH | - | Jun 18, 20:30 UTC | Jun 18, 21:15 UTC | 45m |
| 2026-06-14 | N97SH | - | Jun 14, 16:15 UTC | Jun 14, 17:05 UTC | 50m |
| 2026-06-14 | N97SH | - | Jun 14, 14:30 UTC | Jun 14, 15:25 UTC | 55m |
| 2026-06-12 | N97SH | - | Jun 12, 15:40 UTC | Jun 12, 17:50 UTC | 2h 10m |
| 2026-06-11 | N97SH | - | Jun 11, 14:30 UTC | Jun 11, 16:10 UTC | 1h 40m |
| 2026-06-10 | N97SH | - | Jun 10, 12:35 UTC | Jun 10, 13:25 UTC | 50m |
| 2026-06-07 | N97SH | - | Jun 7, 15:00 UTC | Jun 7, 15:30 UTC | 30m |
| 2026-06-06 | N97SH | - | Jun 6, 13:25 UTC | Jun 6, 14:09 UTC | 45m |
| 2026-06-05 | N97SH | - | Jun 5, 16:25 UTC | Jun 5, 19:10 UTC | 2h 45m |
| 2026-06-05 | N97SH | - | Jun 5, 15:05 UTC | Jun 5, 15:40 UTC | 35m |
| 2026-06-04 | N97SH | - | Jun 4, 13:55 UTC | Jun 4, 16:30 UTC | 2h 35m |
| 2026-06-02 | N97SH | - | Jun 2, 14:45 UTC | Jun 2, 15:55 UTC | 1h 10m |
| 2026-05-31 | N97SH | - | May 31, 13:55 UTC | May 31, 15:40 UTC | 1h 45m |
| 2026-05-29 | N97SH | - | May 29, 13:55 UTC | May 29, 15:40 UTC | 1h 45m |
| 2026-05-28 | N97SH | - | May 28, 00:10 UTC | May 28, 01:05 UTC | 55m |
| 2026-05-26 | N97SH | - | May 26, 13:10 UTC | May 26, 14:20 UTC | 1h 10m |
| 2026-05-24 | N97SH | - | May 24, 13:25 UTC | May 24, 14:20 UTC | 55m |
| 2026-05-23 | N97SH | - | May 23, 14:40 UTC | May 23, 15:50 UTC | 1h 10m |
| 2026-05-18 | N97SH | - | May 18, 15:05 UTC | May 18, 18:45 UTC | 3h 39m |
| 2026-05-15 | N97SH | - | May 15, 14:10 UTC | May 15, 18:20 UTC | 4h 9m |
| 2026-05-14 | N97SH | - | May 14, 13:45 UTC | May 14, 15:10 UTC | 1h 25m |
| 2026-05-13 | N97SH | - | May 13, 16:00 UTC | May 13, 17:25 UTC | 1h 25m |
| 2026-05-12 | N97SH | - | May 12, 13:35 UTC | May 12, 14:45 UTC | 1h 10m |
| 2026-05-11 | N97SH | - | May 11, 12:05 UTC | May 11, 13:05 UTC | 1h 0m |
| 2026-05-10 | N97SH | - | May 10, 20:09 UTC | May 10, 21:19 UTC | 1h 10m |
| 2026-05-09 | N97SH | - | May 9, 13:50 UTC | May 9, 15:45 UTC | 1h 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 N97SH page for operator, model, and routing details .