sensors Mode-S transponder
AD4EEA
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N957CR · BOMBARDIER BD-100 Challenger 350 · operated by MMR WEST LLC
- Hex
- AD4EEA
- Octal
- 53247352
- Decimal
- 11,357,930
- Country
- US
- Tail
- N957CR
- Type
- CL35
- Flights observed
- 51
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address AD4EEA 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 |
|---|---|---|---|
| N957CR | - | 51 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-23 | N957CR | DVT → BTR | Jun 23, 22:19 UTC | Jun 24, 00:55 UTC | 2h 35m |
| 2026-06-23 | N957CR | - | Jun 23, 20:59 UTC | Jun 23, 21:39 UTC | 40m |
| 2026-06-23 | N957CR | - | Jun 23, 17:04 UTC | Jun 23, 20:15 UTC | 3h 10m |
| 2026-06-23 | N957CR | - | Jun 23, 00:15 UTC | Jun 23, 01:00 UTC | 45m |
| 2026-06-22 | N957CR | - | Jun 22, 22:59 UTC | Jun 22, 23:39 UTC | 40m |
| 2026-06-22 | N957CR | - | Jun 22, 21:49 UTC | Jun 22, 22:40 UTC | 50m |
| 2026-06-22 | N957CR | - | Jun 22, 13:14 UTC | Jun 22, 14:49 UTC | 1h 35m |
| 2026-06-22 | N957CR | - | Jun 22, 11:54 UTC | Jun 22, 12:30 UTC | 35m |
| 2026-06-21 | N957CR | - | Jun 21, 16:14 UTC | Jun 21, 16:59 UTC | 45m |
| 2026-06-21 | N957CR | - | Jun 21, 15:09 UTC | Jun 21, 15:44 UTC | 35m |
| 2026-06-20 | N957CR | - | Jun 20, 00:39 UTC | Jun 20, 03:44 UTC | 3h 5m |
| 2026-06-19 | N957CR | PHX → SLC | Jun 19, 23:00 UTC | Jun 20, 00:04 UTC | 1h 5m |
| 2026-06-19 | N957CR | - | Jun 19, 17:04 UTC | Jun 19, 18:14 UTC | 1h 10m |
| 2026-06-19 | N957CR | - | Jun 19, 13:29 UTC | Jun 19, 16:39 UTC | 3h 10m |
| 2026-06-18 | N957CR | - | Jun 18, 16:00 UTC | Jun 18, 16:50 UTC | 50m |
| 2026-06-18 | N957CR | BTR → DAL | Jun 18, 12:55 UTC | Jun 18, 15:20 UTC | 2h 25m |
| 2026-06-17 | N957CR | - | Jun 17, 11:50 UTC | Jun 17, 23:35 UTC | 11h 45m |
| 2026-06-15 | N957CR | - | Jun 15, 16:45 UTC | Jun 15, 20:45 UTC | 4h 0m |
| 2026-06-11 | N957CR | - | Jun 11, 14:35 UTC | Jun 11, 18:10 UTC | 3h 35m |
| 2026-06-10 | N957CR | - | Jun 10, 13:50 UTC | Jun 11, 00:00 UTC | 10h 10m |
| 2026-06-10 | N957CR | - | Jun 10, 02:25 UTC | Jun 10, 03:10 UTC | 45m |
| 2026-06-09 | N957CR | - | Jun 9, 21:35 UTC | Jun 9, 22:25 UTC | 50m |
| 2026-06-02 | N957CR | - | Jun 2, 20:20 UTC | Jun 2, 22:10 UTC | 1h 50m |
| 2026-06-01 | N957CR | - | Jun 1, 16:05 UTC | Jun 1, 17:55 UTC | 1h 50m |
| 2026-05-30 | N957CR | - | May 30, 14:10 UTC | May 30, 15:45 UTC | 1h 35m |
| 2026-05-30 | N957CR | - | May 30, 12:55 UTC | May 30, 13:25 UTC | 30m |
| 2026-05-28 | N957CR | - | May 28, 20:10 UTC | May 28, 20:30 UTC | 20m |
| 2026-05-28 | N957CR | - | May 28, 17:50 UTC | May 28, 19:25 UTC | 1h 35m |
| 2026-05-18 | N957CR | - | May 18, 17:10 UTC | May 18, 18:05 UTC | 55m |
| 2026-05-11 | N957CR | - | May 11, 12:15 UTC | May 11, 13:20 UTC | 1h 5m |
| 2026-05-08 | N957CR | - | May 8, 18:50 UTC | May 8, 20:50 UTC | 2h 0m |
| 2026-05-07 | N957CR | - | May 7, 12:15 UTC | May 7, 13:40 UTC | 1h 25m |
| 2026-05-06 | N957CR | - | May 6, 16:00 UTC | May 6, 17:20 UTC | 1h 20m |
| 2026-05-05 | N957CR | - | May 5, 20:15 UTC | May 5, 21:20 UTC | 1h 5m |
| 2026-05-04 | N957CR | - | May 4, 18:50 UTC | May 4, 19:30 UTC | 40m |
| 2026-05-04 | N957CR | - | May 4, 17:25 UTC | May 4, 18:15 UTC | 50m |
| 2026-05-03 | N957CR | - | May 3, 16:30 UTC | May 3, 20:15 UTC | 3h 45m |
| 2026-05-03 | N957CR | - | May 3, 12:55 UTC | May 3, 14:15 UTC | 1h 20m |
| 2026-04-30 | N957CR | - | Apr 30, 20:05 UTC | Apr 30, 21:35 UTC | 1h 30m |
| 2026-04-30 | N957CR | - | Apr 30, 16:30 UTC | Apr 30, 18:40 UTC | 2h 10m |
| 2026-04-30 | N957CR | - | Apr 30, 13:30 UTC | Apr 30, 14:35 UTC | 1h 5m |
| 2026-04-26 | N957CR | - | Apr 26, 14:40 UTC | Apr 26, 16:45 UTC | 2h 5m |
| 2026-04-23 | N957CR | - | Apr 23, 15:15 UTC | Apr 23, 16:50 UTC | 1h 35m |
| 2026-04-15 | N957CR | - | Apr 15, 23:10 UTC | Apr 16, 00:55 UTC | 1h 45m |
| 2026-04-15 | N957CR | - | Apr 15, 13:01 UTC | Apr 15, 14:40 UTC | 1h 40m |
| 2026-04-15 | N957CR | - | Apr 15, 12:20 UTC | Apr 15, 12:55 UTC | 35m |
| 2026-04-14 | N957CR | - | Apr 14, 18:55 UTC | Apr 14, 19:55 UTC | 1h 0m |
| 2026-04-14 | N957CR | - | Apr 14, 12:50 UTC | Apr 14, 13:35 UTC | 45m |
| 2026-04-14 | N957CR | - | Apr 14, 12:25 UTC | Apr 14, 12:45 UTC | 20m |
| 2026-04-12 | N957CR | - | Apr 12, 19:00 UTC | Apr 12, 19:45 UTC | 45m |
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 N957CR page for operator, model, and routing details .