sensors Mode-S transponder
A83C91
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N63NB · GULFSTREAM G600 · operated by WATER FORCE ONE LLC
- Hex
- A83C91
- Octal
- 52036221
- Decimal
- 11,025,553
- Country
- US
- Tail
- N63NB
- Type
- GA6C
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address A83C91 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 |
|---|---|---|---|
| N63NB | - | 55 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N63NB | - | Jul 24, 22:25 UTC | Jul 24, 22:45 UTC | 20m |
| 2026-07-22 | N63NB | - | Jul 22, 03:15 UTC | Jul 22, 03:25 UTC | 10m |
| 2026-07-22 | N63NB | - | Jul 22, 01:50 UTC | Jul 22, 02:40 UTC | 50m |
| 2026-07-21 | N63NB | - | Jul 21, 20:25 UTC | Jul 21, 21:10 UTC | 45m |
| 2026-07-21 | N63NB | - | Jul 21, 15:55 UTC | Jul 21, 16:35 UTC | 40m |
| 2026-07-20 | N63NB | - | Jul 20, 19:25 UTC | Jul 21, 00:15 UTC | 4h 49m |
| 2026-07-20 | N63NB | - | Jul 20, 16:25 UTC | Jul 20, 16:45 UTC | 20m |
| 2026-07-18 | N63NB | - | Jul 18, 22:05 UTC | Jul 18, 22:20 UTC | 15m |
| 2026-07-18 | N63NB | - | Jul 18, 15:05 UTC | Jul 18, 20:45 UTC | 5h 40m |
| 2026-07-15 | N63NB | FTY → SNA | Jul 15, 18:35 UTC | Jul 15, 22:10 UTC | 3h 35m |
| 2026-07-15 | N63NB | - | Jul 15, 13:25 UTC | Jul 15, 17:20 UTC | 3h 55m |
| 2026-07-12 | N63NB | - | Jul 12, 00:35 UTC | Jul 12, 04:45 UTC | 4h 10m |
| 2026-07-10 | N63NB | - | Jul 10, 17:00 UTC | Jul 10, 17:50 UTC | 50m |
| 2026-07-06 | N63NB | - | Jul 6, 18:15 UTC | Jul 6, 22:40 UTC | 4h 25m |
| 2026-06-30 | N63NB | - | Jun 30, 19:55 UTC | Jul 1, 01:00 UTC | 5h 5m |
| 2026-06-30 | N63NB | - | Jun 30, 14:35 UTC | Jun 30, 19:05 UTC | 4h 30m |
| 2026-06-29 | N63NB | - | Jun 29, 00:24 UTC | Jun 29, 01:44 UTC | 1h 20m |
| 2026-06-25 | N63NB | - | Jun 25, 16:55 UTC | Jun 25, 17:30 UTC | 35m |
| 2026-06-24 | N63NB | - | Jun 24, 19:29 UTC | Jun 24, 20:24 UTC | 55m |
| 2026-06-24 | N63NB | - | Jun 24, 15:35 UTC | Jun 24, 16:24 UTC | 50m |
| 2026-06-23 | N63NB | - | Jun 23, 17:04 UTC | Jun 23, 23:39 UTC | 6h 35m |
| 2026-06-19 | N63NB | - | Jun 19, 18:39 UTC | Jun 19, 23:00 UTC | 4h 20m |
| 2026-06-18 | N63NB | - | Jun 18, 22:40 UTC | Jun 18, 23:15 UTC | 35m |
| 2026-06-18 | N63NB | - | Jun 18, 14:01 UTC | Jun 18, 18:45 UTC | 4h 45m |
| 2026-06-14 | N63NB | - | Jun 14, 20:30 UTC | Jun 14, 20:55 UTC | 25m |
| 2026-06-14 | N63NB | - | Jun 14, 19:25 UTC | Jun 14, 19:50 UTC | 25m |
| 2026-06-10 | N63NB | - | Jun 10, 19:10 UTC | Jun 10, 19:15 UTC | 5m |
| 2026-06-06 | N63NB | - | Jun 6, 23:15 UTC | Jun 6, 23:19 UTC | 5m |
| 2026-06-06 | N63NB | - | Jun 6, 18:04 UTC | Jun 6, 18:45 UTC | 40m |
| 2026-05-31 | N63NB | - | May 31, 15:15 UTC | May 31, 19:10 UTC | 3h 55m |
| 2026-05-28 | N63NB | - | May 28, 19:10 UTC | May 28, 22:40 UTC | 3h 30m |
| 2026-05-26 | N63NB | - | May 26, 17:55 UTC | May 26, 19:30 UTC | 1h 35m |
| 2026-05-22 | N63NB | - | May 22, 16:45 UTC | May 22, 17:45 UTC | 1h 0m |
| 2026-05-19 | N63NB | - | May 19, 23:55 UTC | May 20, 00:40 UTC | 45m |
| 2026-05-19 | N63NB | - | May 19, 16:25 UTC | May 19, 17:10 UTC | 45m |
| 2026-05-18 | N63NB | - | May 18, 18:25 UTC | May 18, 18:40 UTC | 14m |
| 2026-05-11 | N63NB | - | May 11, 16:55 UTC | May 11, 17:10 UTC | 16m |
| 2026-05-07 | N63NB | - | May 7, 15:50 UTC | May 7, 20:25 UTC | 4h 35m |
| 2026-05-06 | N63NB | - | May 6, 17:25 UTC | May 6, 17:45 UTC | 19m |
| 2026-05-04 | N63NB | - | May 4, 18:15 UTC | May 4, 22:25 UTC | 4h 11m |
| 2026-05-04 | N63NB | - | May 4, 00:05 UTC | May 4, 00:50 UTC | 45m |
| 2026-05-01 | N63NB | - | May 1, 22:05 UTC | May 1, 22:55 UTC | 50m |
| 2026-04-24 | N63NB | - | Apr 24, 14:15 UTC | Apr 24, 18:40 UTC | 4h 25m |
| 2026-04-22 | N63NB | - | Apr 22, 21:40 UTC | Apr 22, 21:55 UTC | 15m |
| 2026-04-22 | N63NB | - | Apr 22, 18:55 UTC | Apr 22, 20:50 UTC | 1h 55m |
| 2026-04-21 | N63NB | - | Apr 21, 19:30 UTC | Apr 21, 21:55 UTC | 2h 25m |
| 2026-04-20 | N63NB | - | Apr 20, 16:25 UTC | Apr 20, 17:05 UTC | 40m |
| 2026-04-19 | N63NB | - | Apr 19, 20:45 UTC | Apr 19, 21:30 UTC | 45m |
| 2026-04-13 | N63NB | - | Apr 13, 19:50 UTC | Apr 13, 21:35 UTC | 1h 45m |
| 2026-04-13 | N63NB | - | Apr 13, 18:05 UTC | Apr 13, 20:10 UTC | 2h 5m |
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 N63NB page for operator, model, and routing details .