sensors Mode-S transponder
ACCA7B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N923N · GULFSTREAM G600 · operated by NICHOLAS SERVICES LLC
- Hex
- ACCA7B
- Octal
- 53145173
- Decimal
- 11,324,027
- Country
- US
- Tail
- N923N
- Type
- GA6C
- Flights observed
- 69
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address ACCA7B 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 |
|---|---|---|---|
| JTZ923 | - | 69 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | JTZ923 | - | Jul 25, 14:30 UTC | Jul 25, 15:15 UTC | 45m |
| 2026-07-25 | JTZ923 | - | Jul 25, 13:00 UTC | Jul 25, 13:15 UTC | 15m |
| 2026-07-24 | JTZ923 | - | Jul 24, 21:50 UTC | Jul 25, 00:00 UTC | 2h 10m |
| 2026-07-24 | JTZ923 | - | Jul 24, 19:25 UTC | Jul 24, 20:50 UTC | 1h 25m |
| 2026-07-24 | JTZ923 | - | Jul 24, 15:20 UTC | Jul 24, 17:10 UTC | 1h 50m |
| 2026-07-19 | JTZ923 | - | Jul 19, 20:45 UTC | Jul 19, 22:45 UTC | 2h 0m |
| 2026-07-18 | JTZ923 | - | Jul 18, 20:40 UTC | Jul 18, 22:15 UTC | 1h 35m |
| 2026-07-18 | JTZ923 | - | Jul 18, 19:15 UTC | Jul 18, 19:45 UTC | 30m |
| 2026-07-18 | JTZ923 | - | Jul 18, 14:10 UTC | Jul 18, 14:45 UTC | 35m |
| 2026-07-16 | JTZ923 | - | Jul 16, 21:35 UTC | Jul 16, 22:30 UTC | 55m |
| 2026-07-16 | JTZ923 | - | Jul 16, 13:00 UTC | Jul 16, 14:10 UTC | 1h 10m |
| 2026-07-13 | JTZ923 | - | Jul 13, 00:50 UTC | Jul 13, 18:50 UTC | 18h 0m |
| 2026-07-13 | JTZ923 | - | Jul 13, 00:20 UTC | Jul 13, 18:50 UTC | 18h 30m |
| 2026-07-12 | JTZ923 | - | Jul 12, 20:35 UTC | Jul 12, 22:55 UTC | 2h 20m |
| 2026-07-11 | JTZ923 | - | Jul 11, 16:20 UTC | Jul 11, 18:05 UTC | 1h 45m |
| 2026-07-10 | JTZ923 | - | Jul 10, 16:20 UTC | Jul 10, 18:55 UTC | 2h 35m |
| 2026-07-09 | JTZ923 | - | Jul 9, 20:50 UTC | Jul 10, 18:55 UTC | 22h 5m |
| 2026-07-09 | JTZ923 | - | Jul 9, 19:45 UTC | Jul 10, 18:45 UTC | 23h 0m |
| 2026-07-09 | JTZ923 | - | Jul 9, 16:45 UTC | Jul 9, 17:10 UTC | 25m |
| 2026-07-06 | JTZ923 | - | Jul 6, 20:25 UTC | Jul 6, 21:05 UTC | 40m |
| 2026-07-05 | JTZ923 | - | Jul 5, 15:50 UTC | Jul 5, 22:35 UTC | 6h 45m |
| 2026-07-02 | JTZ923 | - | Jul 2, 13:55 UTC | Jul 2, 15:50 UTC | 1h 55m |
| 2026-07-01 | JTZ923 | - | Jul 1, 18:20 UTC | Jul 1, 20:25 UTC | 2h 5m |
| 2026-06-30 | JTZ923 | - | Jun 30, 18:50 UTC | Jul 1, 18:45 UTC | 23h 55m |
| 2026-06-30 | JTZ923 | - | Jun 30, 18:40 UTC | Jun 30, 20:15 UTC | 1h 35m |
| 2026-06-30 | JTZ923 | - | Jun 30, 14:10 UTC | Jun 30, 15:05 UTC | 55m |
| 2026-06-28 | JTZ923 | - | Jun 28, 17:50 UTC | Jun 28, 18:40 UTC | 50m |
| 2026-06-25 | JTZ923 | - | Jun 25, 22:39 UTC | Jun 25, 23:30 UTC | 50m |
| 2026-06-25 | JTZ923 | - | Jun 25, 19:09 UTC | Jun 25, 19:59 UTC | 50m |
| 2026-06-19 | JTZ923 | - | Jun 19, 18:09 UTC | Jun 19, 21:19 UTC | 3h 10m |
| 2026-06-19 | JTZ923 | - | Jun 19, 13:24 UTC | Jun 19, 17:04 UTC | 3h 40m |
| 2026-06-17 | JTZ923 | BCN → BNA | Jun 17, 17:40 UTC | Jun 18, 02:25 UTC | 8h 45m |
| 2026-06-17 | JTZ923 | - | Jun 17, 14:50 UTC | Jun 17, 15:05 UTC | 15m |
| 2026-06-14 | JTZ923 | - | Jun 14, 19:10 UTC | Jun 14, 20:05 UTC | 55m |
| 2026-06-14 | JTZ923 | - | Jun 14, 11:05 UTC | Jun 14, 11:15 UTC | 10m |
| 2026-06-12 | JTZ923 | - | Jun 12, 00:05 UTC | Jun 12, 07:25 UTC | 7h 21m |
| 2026-06-09 | JTZ923 | - | Jun 9, 20:25 UTC | Jun 9, 20:40 UTC | 15m |
| 2026-06-03 | JTZ923 | - | Jun 3, 21:50 UTC | Jun 3, 23:30 UTC | 1h 40m |
| 2026-06-02 | JTZ923 | - | Jun 2, 13:55 UTC | Jun 2, 15:15 UTC | 1h 20m |
| 2026-06-01 | JTZ923 | - | Jun 1, 20:30 UTC | Jun 1, 20:40 UTC | 10m |
| 2026-05-30 | JTZ923 | - | May 30, 22:00 UTC | May 30, 22:35 UTC | 35m |
| 2026-05-30 | JTZ923 | - | May 30, 17:25 UTC | May 30, 21:10 UTC | 3h 45m |
| 2026-05-30 | JTZ923 | - | May 30, 15:00 UTC | May 30, 15:20 UTC | 20m |
| 2026-05-29 | JTZ923 | - | May 29, 21:15 UTC | May 29, 22:45 UTC | 1h 30m |
| 2026-05-29 | JTZ923 | - | May 29, 14:50 UTC | May 29, 15:25 UTC | 35m |
| 2026-05-27 | JTZ923 | - | May 27, 14:25 UTC | May 27, 15:10 UTC | 45m |
| 2026-05-26 | JTZ923 | - | May 26, 21:14 UTC | May 27, 00:10 UTC | 2h 55m |
| 2026-05-25 | JTZ923 | SBA → BOI | May 25, 21:04 UTC | May 25, 22:44 UTC | 1h 40m |
| 2026-05-24 | JTZ923 | - | May 24, 21:00 UTC | May 24, 23:46 UTC | 2h 46m |
| 2026-05-24 | JTZ923 | - | May 24, 16:05 UTC | May 24, 19:35 UTC | 3h 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 N923N page for operator, model, and routing details .