sensors Mode-S transponder
A5034D
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N422CP · BOMBARDIER BD-100 Challenger 350 · operated by POHLAD CHARLES B, POHLAD JAMES O, POHLAD ROBERT C, POHLAD CHRISTOPHER R, POHLAD THOMAS O, POHLAD JOSEPH C
- Hex
- A5034D
- Octal
- 51201515
- Decimal
- 10,814,285
- Country
- US
- Tail
- N422CP
- Type
- CL35
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 12d ago
Current position
Country allocation
The ICAO 24-bit address A5034D 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 |
|---|---|---|---|
| N422CP | - | 66 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | N422CP | - | Jul 25, 18:35 UTC | Jul 25, 20:10 UTC | 1h 35m |
| 2026-07-25 | N422CP | - | Jul 25, 15:35 UTC | Jul 25, 17:25 UTC | 1h 50m |
| 2026-07-23 | N422CP | - | Jul 23, 17:05 UTC | Jul 23, 19:30 UTC | 2h 25m |
| 2026-07-22 | N422CP | - | Jul 22, 18:15 UTC | Jul 22, 20:05 UTC | 1h 50m |
| 2026-07-18 | N422CP | - | Jul 18, 16:45 UTC | Jul 18, 18:25 UTC | 1h 40m |
| 2026-07-18 | N422CP | - | Jul 18, 12:55 UTC | Jul 18, 14:25 UTC | 1h 30m |
| 2026-07-12 | N422CP | - | Jul 12, 14:30 UTC | Jul 12, 17:40 UTC | 3h 10m |
| 2026-07-09 | N422CP | - | Jul 9, 16:55 UTC | Jul 9, 20:05 UTC | 3h 10m |
| 2026-07-07 | N422CP | - | Jul 7, 18:10 UTC | Jul 7, 20:50 UTC | 2h 40m |
| 2026-07-07 | N422CP | - | Jul 7, 12:50 UTC | Jul 7, 16:05 UTC | 3h 15m |
| 2026-07-05 | N422CP | - | Jul 5, 15:15 UTC | Jul 5, 17:00 UTC | 1h 45m |
| 2026-07-05 | N422CP | - | Jul 5, 12:40 UTC | Jul 5, 14:25 UTC | 1h 45m |
| 2026-07-01 | N422CP | - | Jul 1, 20:15 UTC | Jul 1, 21:50 UTC | 1h 35m |
| 2026-07-01 | N422CP | - | Jul 1, 14:55 UTC | Jul 1, 18:50 UTC | 3h 55m |
| 2026-06-30 | N422CP | - | Jun 30, 15:30 UTC | Jun 30, 19:00 UTC | 3h 30m |
| 2026-06-29 | N422CP | - | Jun 29, 14:19 UTC | Jun 29, 16:04 UTC | 1h 45m |
| 2026-06-28 | N422CP | - | Jun 28, 18:55 UTC | Jun 28, 21:45 UTC | 2h 50m |
| 2026-06-28 | N422CP | MSP → BLI | Jun 28, 15:29 UTC | Jun 28, 18:19 UTC | 2h 50m |
| 2026-06-26 | N422CP | - | Jun 26, 19:39 UTC | Jun 26, 21:55 UTC | 2h 15m |
| 2026-06-26 | N422CP | - | Jun 26, 17:00 UTC | Jun 26, 18:44 UTC | 1h 45m |
| 2026-06-25 | N422CP | - | Jun 25, 19:05 UTC | Jun 25, 21:44 UTC | 2h 40m |
| 2026-06-25 | N422CP | MSP → BLI | Jun 25, 15:24 UTC | Jun 25, 18:29 UTC | 3h 5m |
| 2026-06-24 | N422CP | - | Jun 24, 19:15 UTC | Jun 24, 20:49 UTC | 1h 35m |
| 2026-06-24 | N422CP | - | Jun 24, 14:20 UTC | Jun 24, 18:09 UTC | 3h 50m |
| 2026-06-22 | N422CP | MSP → TEB | Jun 22, 14:55 UTC | Jun 22, 17:00 UTC | 2h 5m |
| 2026-06-07 | N422CP | SBA → MSP | Jun 7, 18:00 UTC | Jun 7, 21:20 UTC | 3h 20m |
| 2026-06-05 | N422CP | MSP → SBA | Jun 5, 14:40 UTC | Jun 5, 18:05 UTC | 3h 25m |
| 2026-06-05 | N422CP | - | Jun 5, 00:50 UTC | Jun 5, 03:20 UTC | 2h 30m |
| 2026-06-04 | N422CP | - | Jun 4, 21:50 UTC | Jun 5, 00:15 UTC | 2h 25m |
| 2026-06-03 | N422CP | - | Jun 3, 23:30 UTC | Jun 4, 01:50 UTC | 2h 20m |
| 2026-06-03 | N422CP | MSP → TEB | Jun 3, 19:10 UTC | Jun 3, 21:20 UTC | 2h 10m |
| 2026-05-30 | N422CP | - | May 30, 19:00 UTC | May 30, 20:30 UTC | 1h 30m |
| 2026-05-30 | N422CP | - | May 30, 16:20 UTC | May 30, 17:55 UTC | 1h 35m |
| 2026-05-28 | N422CP | - | May 28, 17:30 UTC | May 28, 19:05 UTC | 1h 35m |
| 2026-05-26 | N422CP | - | May 26, 14:14 UTC | May 26, 15:54 UTC | 1h 40m |
| 2026-05-22 | N422CP | TEB → MSP | May 22, 22:05 UTC | May 23, 00:45 UTC | 2h 40m |
| 2026-05-19 | N422CP | - | May 19, 13:45 UTC | May 19, 14:25 UTC | 40m |
| 2026-05-18 | N422CP | MSP → BWI | May 18, 16:25 UTC | May 18, 18:25 UTC | 2h 0m |
| 2026-05-17 | N422CP | MFR → MSP | May 17, 20:05 UTC | May 17, 23:00 UTC | 2h 55m |
| 2026-05-15 | N422CP | MSP → MFR | May 15, 14:45 UTC | May 15, 18:10 UTC | 3h 24m |
| 2026-05-10 | N422CP | - | May 10, 13:49 UTC | May 10, 15:24 UTC | 1h 35m |
| 2026-05-09 | N422CP | MSP → CLE | May 9, 17:20 UTC | May 9, 18:35 UTC | 1h 15m |
| 2026-05-09 | N422CP | - | May 9, 00:00 UTC | May 9, 02:45 UTC | 2h 45m |
| 2026-05-07 | N422CP | - | May 7, 12:55 UTC | May 7, 16:05 UTC | 3h 10m |
| 2026-05-04 | N422CP | - | May 4, 16:40 UTC | May 4, 19:20 UTC | 2h 41m |
| 2026-05-03 | N422CP | - | May 3, 14:00 UTC | May 3, 17:05 UTC | 3h 5m |
| 2026-05-01 | N422CP | - | May 1, 00:40 UTC | May 1, 03:40 UTC | 3h 0m |
| 2026-04-28 | N422CP | - | Apr 28, 13:50 UTC | Apr 28, 17:20 UTC | 3h 30m |
| 2026-04-26 | N422CP | - | Apr 26, 17:05 UTC | Apr 26, 19:40 UTC | 2h 35m |
| 2026-04-26 | N422CP | - | Apr 26, 12:30 UTC | Apr 26, 15:40 UTC | 3h 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 N422CP page for operator, model, and routing details .