sensors Mode-S transponder
AAC3A9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N793FB · GULFSTREAM G600 · operated by N793WF LEASE LLC
- Hex
- AAC3A9
- Octal
- 52541651
- Decimal
- 11,191,209
- Country
- US
- Tail
- N793FB
- Type
- GA6C
- Flights observed
- 46
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 39m ago
Current position
Country allocation
The ICAO 24-bit address AAC3A9 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 |
|---|---|---|---|
| N793FB | - | 46 | 2026-07-14 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | N793FB | - | Jul 14, 17:50 UTC | Jul 14, 20:15 UTC | 2h 25m |
| 2026-07-13 | N793FB | - | Jul 13, 20:05 UTC | Jul 13, 22:35 UTC | 2h 30m |
| 2026-07-09 | N793FB | - | Jul 9, 16:30 UTC | Jul 9, 17:00 UTC | 30m |
| 2026-07-09 | N793FB | - | Jul 9, 14:15 UTC | Jul 9, 14:40 UTC | 25m |
| 2026-07-07 | N793FB | - | Jul 7, 18:35 UTC | Jul 7, 19:05 UTC | 30m |
| 2026-07-07 | N793FB | - | Jul 7, 17:50 UTC | Jul 7, 18:15 UTC | 25m |
| 2026-07-07 | N793FB | - | Jul 7, 15:50 UTC | Jul 7, 16:25 UTC | 35m |
| 2026-07-07 | N793FB | - | Jul 7, 15:00 UTC | Jul 7, 15:30 UTC | 30m |
| 2026-06-30 | N793FB | - | Jun 30, 21:25 UTC | Jun 30, 22:35 UTC | 1h 10m |
| 2026-06-25 | N793FB | - | Jun 25, 15:15 UTC | Jun 25, 17:44 UTC | 2h 30m |
| 2026-06-23 | N793FB | - | Jun 23, 20:10 UTC | Jun 24, 00:09 UTC | 4h 0m |
| 2026-06-23 | N793FB | - | Jun 23, 14:44 UTC | Jun 23, 19:04 UTC | 4h 20m |
| 2026-06-22 | N793FB | DAL → NTR | Jun 22, 18:04 UTC | Jun 22, 19:14 UTC | 1h 10m |
| 2026-06-22 | N793FB | - | Jun 22, 15:10 UTC | Jun 22, 17:44 UTC | 2h 35m |
| 2026-06-19 | N793FB | - | Jun 19, 01:04 UTC | Jun 19, 05:05 UTC | 4h 0m |
| 2026-06-17 | N793FB | IAD → PDK | Jun 17, 19:25 UTC | Jun 17, 20:35 UTC | 1h 10m |
| 2026-06-16 | N793FB | - | Jun 16, 15:24 UTC | Jun 16, 19:19 UTC | 3h 55m |
| 2026-06-01 | N793FB | - | Jun 1, 00:15 UTC | Jun 1, 00:40 UTC | 25m |
| 2026-05-31 | N793FB | - | May 31, 23:15 UTC | May 31, 23:30 UTC | 15m |
| 2026-05-30 | N793FB | - | May 30, 16:05 UTC | May 30, 16:30 UTC | 25m |
| 2026-05-29 | N793FB | - | May 29, 18:15 UTC | May 29, 20:55 UTC | 2h 40m |
| 2026-05-28 | N793FB | - | May 28, 21:15 UTC | May 29, 00:10 UTC | 2h 55m |
| 2026-05-28 | N793FB | - | May 28, 01:05 UTC | May 28, 02:30 UTC | 1h 25m |
| 2026-05-26 | N793FB | - | May 26, 19:45 UTC | May 26, 22:59 UTC | 3h 15m |
| 2026-05-16 | N793FB | - | May 16, 15:40 UTC | May 16, 16:05 UTC | 25m |
| 2026-05-16 | N793FB | HND → LAX | May 16, 06:06 UTC | May 16, 15:01 UTC | 8h 55m |
| 2026-05-15 | N793FB | - | May 15, 06:50 UTC | May 15, 12:55 UTC | 6h 5m |
| 2026-05-14 | N793FB | - | May 14, 04:00 UTC | May 14, 06:35 UTC | 2h 35m |
| 2026-05-12 | N793FB | HND → GMP | May 12, 23:50 UTC | May 13, 01:30 UTC | 1h 40m |
| 2026-05-11 | N793FB | - | May 11, 20:20 UTC | May 12, 06:45 UTC | 10h 25m |
| 2026-05-07 | N793FB | - | May 7, 17:25 UTC | May 7, 22:30 UTC | 5h 5m |
| 2026-05-05 | N793FB | - | May 5, 22:01 UTC | May 5, 23:10 UTC | 1h 10m |
| 2026-05-05 | N793FB | - | May 5, 15:15 UTC | May 5, 18:35 UTC | 3h 20m |
| 2026-05-03 | N793FB | - | May 3, 01:45 UTC | May 3, 05:30 UTC | 3h 44m |
| 2026-04-30 | N793FB | - | Apr 30, 16:40 UTC | Apr 30, 19:40 UTC | 3h 0m |
| 2026-04-23 | N793FB | - | Apr 23, 16:30 UTC | Apr 23, 20:50 UTC | 4h 20m |
| 2026-04-23 | N793FB | - | Apr 23, 13:45 UTC | Apr 23, 15:20 UTC | 1h 35m |
| 2026-04-22 | N793FB | - | Apr 22, 14:10 UTC | Apr 22, 18:25 UTC | 4h 15m |
| 2026-04-16 | N793FB | - | Apr 16, 03:09 UTC | Apr 16, 04:49 UTC | 1h 40m |
| 2026-04-16 | N793FB | - | Apr 16, 01:10 UTC | Apr 16, 03:04 UTC | 1h 55m |
| 2026-04-15 | N793FB | - | Apr 15, 23:20 UTC | Apr 16, 01:05 UTC | 1h 45m |
| 2026-04-14 | N793FB | - | Apr 14, 18:55 UTC | Apr 14, 19:05 UTC | 10m |
| 2026-04-14 | N793FB | - | Apr 14, 18:10 UTC | Apr 14, 18:45 UTC | 35m |
| 2026-04-13 | N793FB | - | Apr 13, 20:05 UTC | Apr 13, 23:30 UTC | 3h 25m |
| 2026-04-13 | N793FB | - | Apr 13, 00:20 UTC | Apr 13, 00:30 UTC | 10m |
| 2026-04-12 | N793FB | - | Apr 12, 23:55 UTC | Apr 13, 00:30 UTC | 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 N793FB page for operator, model, and routing details .