sensors Mode-S transponder
A6831E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N519CP · BOMBARDIER BD-700 Global 6000/6500 · operated by AIRCRAFT GUARANTY CORP TRUSTEE
- Hex
- A6831E
- Octal
- 51501436
- Decimal
- 10,912,542
- Country
- US
- Tail
- N519CP
- Type
- GLEX
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address A6831E 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 |
|---|---|---|---|
| N519CP | - | 48 | 2026-07-24 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N519CP | - | Jul 24, 07:25 UTC | Jul 24, 09:25 UTC | 2h 0m |
| 2026-07-24 | N519CP | - | Jul 24, 06:25 UTC | Jul 24, 06:35 UTC | 10m |
| 2026-07-21 | N519CP | - | Jul 21, 09:10 UTC | Jul 21, 09:20 UTC | 10m |
| 2026-07-21 | N519CP | - | Jul 21, 06:10 UTC | Jul 21, 06:40 UTC | 30m |
| 2026-07-19 | N519CP | HND → GMP | Jul 19, 04:50 UTC | Jul 19, 06:30 UTC | 1h 40m |
| 2026-07-17 | N519CP | - | Jul 17, 03:05 UTC | Jul 17, 05:15 UTC | 2h 10m |
| 2026-07-17 | N519CP | - | Jul 17, 02:15 UTC | Jul 17, 02:25 UTC | 10m |
| 2026-07-15 | N519CP | - | Jul 15, 10:30 UTC | Jul 15, 10:45 UTC | 15m |
| 2026-07-15 | N519CP | - | Jul 15, 07:40 UTC | Jul 15, 07:55 UTC | 15m |
| 2026-07-15 | N519CP | - | Jul 15, 03:50 UTC | Jul 15, 04:00 UTC | 10m |
| 2026-07-14 | N519CP | - | Jul 14, 09:50 UTC | Jul 14, 12:50 UTC | 3h 0m |
| 2026-07-11 | N519CP | - | Jul 11, 07:15 UTC | Jul 11, 07:35 UTC | 20m |
| 2026-07-11 | N519CP | - | Jul 11, 06:01 UTC | Jul 11, 06:15 UTC | 15m |
| 2026-07-11 | N519CP | - | Jul 11, 04:40 UTC | Jul 11, 04:50 UTC | 10m |
| 2026-07-11 | N519CP | - | Jul 11, 03:30 UTC | Jul 11, 03:40 UTC | 10m |
| 2026-07-09 | N519CP | - | Jul 9, 01:25 UTC | Jul 9, 01:55 UTC | 30m |
| 2026-07-02 | N519CP | - | Jul 2, 20:40 UTC | Jul 3, 07:15 UTC | 10h 35m |
| 2026-07-02 | N519CP | - | Jul 2, 16:20 UTC | Jul 2, 19:05 UTC | 2h 45m |
| 2026-06-28 | N519CP | ATH → LBG | Jun 28, 15:34 UTC | Jun 28, 18:14 UTC | 2h 40m |
| 2026-06-28 | N519CP | - | Jun 28, 04:40 UTC | Jun 28, 14:14 UTC | 9h 35m |
| 2026-06-20 | N519CP | - | Jun 20, 12:45 UTC | Jun 20, 14:54 UTC | 2h 10m |
| 2026-06-20 | N519CP | - | Jun 20, 02:40 UTC | Jun 20, 02:54 UTC | 15m |
| 2026-06-20 | N519CP | - | Jun 20, 00:19 UTC | Jun 20, 00:54 UTC | 35m |
| 2026-06-16 | N519CP | - | Jun 16, 03:04 UTC | Jun 16, 04:45 UTC | 1h 40m |
| 2026-06-12 | N519CP | - | Jun 12, 02:30 UTC | Jun 12, 02:45 UTC | 15m |
| 2026-06-12 | N519CP | - | Jun 12, 01:15 UTC | Jun 12, 01:45 UTC | 30m |
| 2026-06-11 | N519CP | - | Jun 11, 07:40 UTC | Jun 11, 11:50 UTC | 4h 10m |
| 2026-06-04 | N519CP | - | Jun 4, 07:15 UTC | Jun 4, 09:25 UTC | 2h 10m |
| 2026-05-27 | N519CP | - | May 27, 13:10 UTC | May 28, 03:05 UTC | 13h 55m |
| 2026-05-24 | N519CP | - | May 24, 23:10 UTC | May 25, 14:35 UTC | 15h 25m |
| 2026-05-23 | N519CP | DMK → NRT | May 23, 22:35 UTC | May 24, 04:20 UTC | 5h 45m |
| 2026-05-22 | N519CP | - | May 22, 19:15 UTC | May 23, 00:20 UTC | 5h 5m |
| 2026-05-22 | N519CP | - | May 22, 11:05 UTC | May 22, 17:45 UTC | 6h 40m |
| 2026-05-22 | N519CP | - | May 22, 03:40 UTC | May 22, 10:25 UTC | 6h 45m |
| 2026-05-19 | N519CP | ANC → TEB | May 19, 22:00 UTC | May 20, 04:05 UTC | 6h 5m |
| 2026-05-19 | N519CP | - | May 19, 14:45 UTC | May 19, 21:05 UTC | 6h 20m |
| 2026-05-19 | N519CP | - | May 19, 08:15 UTC | May 19, 13:35 UTC | 5h 20m |
| 2026-05-17 | N519CP | - | May 17, 06:30 UTC | May 17, 06:55 UTC | 25m |
| 2026-05-13 | N519CP | - | May 13, 06:30 UTC | May 13, 13:50 UTC | 7h 20m |
| 2026-05-12 | N519CP | TEB → ANC | May 12, 22:55 UTC | May 13, 05:35 UTC | 6h 40m |
| 2026-05-11 | N519CP | - | May 11, 16:55 UTC | May 11, 17:20 UTC | 26m |
| 2026-05-10 | N519CP | YYZ → HPN | May 10, 17:05 UTC | May 10, 18:05 UTC | 1h 0m |
| 2026-05-07 | N519CP | VCE → YYZ | May 7, 18:45 UTC | May 8, 02:59 UTC | 8h 15m |
| 2026-05-07 | N519CP | - | May 7, 14:40 UTC | May 7, 16:50 UTC | 2h 10m |
| 2026-05-07 | N519CP | - | May 7, 02:50 UTC | May 7, 13:05 UTC | 10h 15m |
| 2026-04-30 | N519CP | - | Apr 30, 06:55 UTC | Apr 30, 08:40 UTC | 1h 45m |
| 2026-04-26 | N519CP | - | Apr 26, 06:15 UTC | Apr 26, 06:20 UTC | 5m |
| 2026-04-26 | N519CP | - | Apr 26, 04:50 UTC | Apr 26, 05:20 UTC | 30m |
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 N519CP page for operator, model, and routing details .