sensors Mode-S transponder
ACB0E7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N917CJ · GULFSTREAM 5 · operated by TVPX AIRCRAFT SOLUTIONS INC
- Hex
- ACB0E7
- Octal
- 53130347
- Decimal
- 11,317,479
- Country
- US
- Tail
- N917CJ
- Type
- GLF5
- Flights observed
- 72
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address ACB0E7 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 |
|---|---|---|---|
| N917CJ | - | 72 | 2026-06-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | N917CJ | - | Jun 3, 00:15 UTC | Jun 3, 01:45 UTC | 1h 30m |
| 2026-06-02 | N917CJ | - | Jun 2, 14:00 UTC | Jun 2, 23:25 UTC | 9h 25m |
| 2026-06-02 | N917CJ | - | Jun 2, 08:00 UTC | Jun 2, 11:05 UTC | 3h 5m |
| 2026-05-31 | N917CJ | - | May 31, 13:10 UTC | May 31, 21:55 UTC | 8h 45m |
| 2026-05-31 | N917CJ | - | May 31, 08:25 UTC | May 31, 11:30 UTC | 3h 5m |
| 2026-05-30 | N917CJ | - | May 30, 17:40 UTC | May 30, 18:00 UTC | 20m |
| 2026-05-30 | N917CJ | - | May 30, 15:35 UTC | May 30, 15:55 UTC | 20m |
| 2026-05-30 | N917CJ | - | May 30, 12:30 UTC | May 30, 12:55 UTC | 25m |
| 2026-05-30 | N917CJ | - | May 30, 04:35 UTC | May 30, 07:55 UTC | 3h 20m |
| 2026-05-27 | N917CJ | - | May 27, 02:34 UTC | May 27, 09:20 UTC | 6h 45m |
| 2026-05-26 | N917CJ | - | May 26, 09:45 UTC | May 26, 14:40 UTC | 4h 55m |
| 2026-05-26 | N917CJ | - | May 26, 01:30 UTC | May 26, 07:40 UTC | 6h 10m |
| 2026-05-19 | N917CJ | - | May 19, 11:30 UTC | May 19, 11:50 UTC | 20m |
| 2026-05-19 | N917CJ | - | May 19, 10:10 UTC | May 19, 10:55 UTC | 45m |
| 2026-05-19 | N917CJ | - | May 19, 06:45 UTC | May 19, 09:00 UTC | 2h 15m |
| 2026-05-19 | N917CJ | - | May 19, 04:15 UTC | May 19, 04:25 UTC | 10m |
| 2026-05-17 | N917CJ | - | May 17, 02:55 UTC | May 17, 03:30 UTC | 35m |
| 2026-05-17 | N917CJ | - | May 17, 00:15 UTC | May 17, 00:50 UTC | 35m |
| 2026-05-16 | N917CJ | - | May 16, 02:20 UTC | May 16, 07:41 UTC | 5h 21m |
| 2026-05-14 | N917CJ | - | May 14, 08:55 UTC | May 15, 03:05 UTC | 18h 10m |
| 2026-05-14 | N917CJ | - | May 14, 02:35 UTC | May 14, 06:15 UTC | 3h 40m |
| 2026-05-13 | N917CJ | - | May 13, 18:35 UTC | May 13, 19:50 UTC | 1h 15m |
| 2026-05-13 | N917CJ | - | May 13, 09:45 UTC | May 13, 10:05 UTC | 20m |
| 2026-05-13 | N917CJ | - | May 13, 07:35 UTC | May 13, 07:55 UTC | 20m |
| 2026-05-13 | N917CJ | - | May 13, 05:05 UTC | May 13, 05:40 UTC | 35m |
| 2026-05-12 | N917CJ | - | May 12, 06:40 UTC | May 13, 05:40 UTC | 23h 0m |
| 2026-05-12 | N917CJ | - | May 12, 04:45 UTC | May 12, 07:20 UTC | 2h 35m |
| 2026-05-10 | N917CJ | - | May 10, 04:19 UTC | May 10, 09:24 UTC | 5h 5m |
| 2026-05-09 | N917CJ | - | May 9, 11:10 UTC | May 9, 17:35 UTC | 6h 25m |
| 2026-05-09 | N917CJ | - | May 9, 06:45 UTC | May 9, 09:15 UTC | 2h 30m |
| 2026-05-08 | N917CJ | DMK → AMS | May 8, 17:45 UTC | May 9, 05:45 UTC | 12h 0m |
| 2026-05-08 | N917CJ | - | May 8, 15:30 UTC | May 8, 16:00 UTC | 30m |
| 2026-05-08 | N917CJ | - | May 8, 14:20 UTC | May 8, 14:30 UTC | 10m |
| 2026-05-03 | N917CJ | - | May 3, 01:20 UTC | May 3, 03:05 UTC | 1h 45m |
| 2026-05-02 | N917CJ | - | May 2, 08:55 UTC | May 2, 13:55 UTC | 5h 0m |
| 2026-05-02 | N917CJ | - | May 2, 00:55 UTC | May 2, 06:55 UTC | 6h 0m |
| 2026-05-01 | N917CJ | - | May 1, 16:20 UTC | May 1, 23:05 UTC | 6h 45m |
| 2026-04-30 | N917CJ | - | Apr 30, 21:10 UTC | Apr 30, 21:30 UTC | 20m |
| 2026-04-30 | N917CJ | - | Apr 30, 11:55 UTC | Apr 30, 12:15 UTC | 20m |
| 2026-04-29 | N917CJ | - | Apr 29, 12:15 UTC | Apr 30, 00:15 UTC | 11h 59m |
| 2026-04-29 | N917CJ | - | Apr 29, 09:25 UTC | Apr 29, 10:20 UTC | 55m |
| 2026-04-28 | N917CJ | - | Apr 28, 23:40 UTC | Apr 28, 23:54 UTC | 15m |
| 2026-04-28 | N917CJ | - | Apr 28, 05:40 UTC | Apr 28, 21:45 UTC | 16h 5m |
| 2026-04-28 | N917CJ | - | Apr 28, 03:10 UTC | Apr 28, 03:20 UTC | 10m |
| 2026-04-27 | N917CJ | - | Apr 27, 08:45 UTC | Apr 27, 21:05 UTC | 12h 20m |
| 2026-04-26 | N917CJ | - | Apr 26, 17:00 UTC | Apr 26, 21:45 UTC | 4h 45m |
| 2026-04-26 | N917CJ | - | Apr 26, 01:45 UTC | Apr 26, 08:35 UTC | 6h 50m |
| 2026-04-25 | N917CJ | - | Apr 25, 12:40 UTC | Apr 25, 23:10 UTC | 10h 30m |
| 2026-04-24 | N917CJ | - | Apr 24, 16:15 UTC | Apr 24, 21:30 UTC | 5h 15m |
| 2026-04-22 | N917CJ | - | Apr 22, 02:20 UTC | Apr 22, 02:45 UTC | 25m |
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 N917CJ page for operator, model, and routing details .