sensors Mode-S transponder
ACD866
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N927CJ · GULFSTREAM G150 · operated by PHASE 4 AVIATION LLC
- Hex
- ACD866
- Octal
- 53154146
- Decimal
- 11,327,590
- Country
- US
- Tail
- N927CJ
- Type
- G150
- Flights observed
- 57
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address ACD866 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 |
|---|---|---|---|
| N927CJ | - | 57 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | N927CJ | - | Jul 17, 16:40 UTC | Jul 17, 19:40 UTC | 3h 0m |
| 2026-07-17 | N927CJ | - | Jul 17, 15:25 UTC | Jul 17, 16:00 UTC | 35m |
| 2026-07-15 | N927CJ | - | Jul 15, 23:30 UTC | Jul 15, 23:45 UTC | 15m |
| 2026-07-15 | N927CJ | BED → HYA | Jul 15, 21:30 UTC | Jul 15, 22:00 UTC | 30m |
| 2026-07-13 | N927CJ | - | Jul 13, 12:35 UTC | Jul 13, 15:05 UTC | 2h 30m |
| 2026-07-02 | N927CJ | BED → MCO | Jul 2, 21:30 UTC | Jul 3, 00:05 UTC | 2h 35m |
| 2026-07-01 | N927CJ | - | Jul 1, 00:35 UTC | Jul 1, 03:10 UTC | 2h 35m |
| 2026-06-30 | N927CJ | - | Jun 30, 22:55 UTC | Jun 30, 23:40 UTC | 45m |
| 2026-06-30 | N927CJ | - | Jun 30, 16:45 UTC | Jun 30, 17:30 UTC | 45m |
| 2026-06-30 | N927CJ | - | Jun 30, 13:40 UTC | Jun 30, 14:15 UTC | 35m |
| 2026-06-28 | N927CJ | - | Jun 28, 18:49 UTC | Jun 28, 19:34 UTC | 45m |
| 2026-06-28 | N927CJ | - | Jun 28, 16:55 UTC | Jun 28, 17:30 UTC | 35m |
| 2026-06-26 | N927CJ | - | Jun 26, 16:30 UTC | Jun 26, 17:15 UTC | 45m |
| 2026-06-23 | N927CJ | - | Jun 23, 17:44 UTC | Jun 23, 20:29 UTC | 2h 45m |
| 2026-06-20 | N927CJ | - | Jun 20, 22:00 UTC | Jun 20, 22:10 UTC | 10m |
| 2026-06-19 | N927CJ | - | Jun 19, 12:19 UTC | Jun 19, 13:09 UTC | 50m |
| 2026-06-17 | N927CJ | - | Jun 17, 21:15 UTC | Jun 17, 21:25 UTC | 10m |
| 2026-06-17 | N927CJ | ORL → ACK | Jun 17, 18:05 UTC | Jun 17, 20:30 UTC | 2h 25m |
| 2026-06-17 | N927CJ | - | Jun 17, 14:50 UTC | Jun 17, 15:40 UTC | 50m |
| 2026-06-16 | N927CJ | - | Jun 16, 16:05 UTC | Jun 16, 16:45 UTC | 40m |
| 2026-06-16 | N927CJ | - | Jun 16, 14:30 UTC | Jun 16, 15:15 UTC | 45m |
| 2026-06-14 | N927CJ | - | Jun 14, 14:25 UTC | Jun 14, 15:00 UTC | 35m |
| 2026-06-14 | N927CJ | TPA → MCO | Jun 14, 04:05 UTC | Jun 14, 04:25 UTC | 20m |
| 2026-06-13 | N927CJ | MCO → TPA | Jun 13, 20:50 UTC | Jun 13, 21:10 UTC | 20m |
| 2026-06-01 | N927CJ | - | Jun 1, 20:50 UTC | Jun 1, 21:35 UTC | 45m |
| 2026-05-31 | N927CJ | - | May 31, 16:55 UTC | May 31, 17:30 UTC | 35m |
| 2026-05-31 | N927CJ | - | May 31, 12:50 UTC | May 31, 15:15 UTC | 2h 25m |
| 2026-05-29 | N927CJ | - | May 29, 20:20 UTC | May 29, 20:30 UTC | 10m |
| 2026-05-26 | N927CJ | - | May 26, 17:30 UTC | May 26, 17:50 UTC | 20m |
| 2026-05-26 | N927CJ | - | May 26, 14:05 UTC | May 26, 16:24 UTC | 2h 20m |
| 2026-05-25 | N927CJ | - | May 25, 17:30 UTC | May 25, 18:20 UTC | 50m |
| 2026-05-23 | N927CJ | - | May 23, 14:45 UTC | May 23, 15:20 UTC | 35m |
| 2026-05-14 | N927CJ | - | May 14, 17:10 UTC | May 14, 19:55 UTC | 2h 45m |
| 2026-05-11 | N927CJ | - | May 11, 14:30 UTC | May 11, 15:05 UTC | 35m |
| 2026-05-11 | N927CJ | MCO → ISP | May 11, 11:30 UTC | May 11, 13:35 UTC | 2h 5m |
| 2026-05-04 | N927CJ | OPF → MCO | May 4, 23:05 UTC | May 5, 00:35 UTC | 1h 30m |
| 2026-05-04 | N927CJ | - | May 4, 20:25 UTC | May 4, 21:15 UTC | 50m |
| 2026-05-03 | N927CJ | - | May 3, 17:50 UTC | May 3, 20:35 UTC | 2h 45m |
| 2026-05-03 | N927CJ | TPA → BED | May 3, 14:00 UTC | May 3, 16:30 UTC | 2h 30m |
| 2026-05-02 | N927CJ | - | May 2, 16:35 UTC | May 2, 17:15 UTC | 40m |
| 2026-05-02 | N927CJ | - | May 2, 15:05 UTC | May 2, 15:50 UTC | 45m |
| 2026-05-01 | N927CJ | - | May 1, 15:25 UTC | May 1, 15:50 UTC | 25m |
| 2026-05-01 | N927CJ | - | May 1, 11:50 UTC | May 1, 14:40 UTC | 2h 50m |
| 2026-04-30 | N927CJ | - | Apr 30, 21:15 UTC | Apr 30, 23:40 UTC | 2h 25m |
| 2026-04-30 | N927CJ | - | Apr 30, 19:25 UTC | Apr 30, 20:25 UTC | 1h 0m |
| 2026-04-30 | N927CJ | - | Apr 30, 11:20 UTC | Apr 30, 12:25 UTC | 1h 5m |
| 2026-04-29 | N927CJ | HWO → MCO | Apr 29, 23:40 UTC | Apr 30, 00:20 UTC | 40m |
| 2026-04-29 | N927CJ | - | Apr 29, 19:15 UTC | Apr 29, 19:55 UTC | 40m |
| 2026-04-29 | N927CJ | - | Apr 29, 16:55 UTC | Apr 29, 17:30 UTC | 35m |
| 2026-04-22 | N927CJ | - | Apr 22, 12:10 UTC | Apr 22, 13:45 UTC | 1h 35m |
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 N927CJ page for operator, model, and routing details .