Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AAC3B8

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N793FS · BEECHCRAFT Super King Air 350 · operated by WILMINGTON TRUST CO TRUSTEE

Hex
AAC3B8
Octal
52541670
Decimal
11,191,224
Country
US
Tail
N793FS
Type
B350
No current signal · last broadcast 12d ago
Flights observed
136
Distinct callsigns
10
Country
US
Last broadcast
12d ago

Last known position

Most recent position reported by Mode-S AAC3B8.

Country allocation

The ICAO 24-bit address AAC3B8 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 10 distinct

Callsign Airline Flights Last seen
NFX600 - 24 2026-06-22
NFX603 - 21 2026-06-18
NFX601 - 20 2026-06-18
NFX602 - 19 2026-06-17
N793FS - 12 2026-06-12
NFX101 - 11 2026-07-01
NFX102 - 10 2026-06-30
NFX104 - 9 2026-07-01
NFX103 - 9 2026-06-30
NFX105 - 1 2026-07-01

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-01 NFX105 - Jul 1, 15:40 UTCJul 1, 17:45 UTC2h 5m
2026-07-01 NFX101 - Jul 1, 14:05 UTCJul 1, 15:15 UTC1h 10m
2026-07-01 NFX104 - Jul 1, 00:40 UTCJul 1, 01:40 UTC1h 0m
2026-06-30 NFX103 BUR → SJC Jun 30, 23:00 UTCJul 1, 00:05 UTC1h 5m
2026-06-30 NFX102 - Jun 30, 15:45 UTCJun 30, 16:45 UTC1h 0m
2026-06-30 NFX101 BUR → SJC Jun 30, 14:00 UTCJun 30, 15:05 UTC1h 5m
2026-06-30 NFX104 - Jun 30, 00:49 UTCJun 30, 01:50 UTC1h 1m
2026-06-29 NFX103 - Jun 29, 23:05 UTCJun 30, 00:14 UTC1h 10m
2026-06-29 NFX102 - Jun 29, 15:34 UTCJun 29, 16:35 UTC1h 0m
2026-06-29 NFX101 BUR → SJC Jun 29, 13:49 UTCJun 29, 15:00 UTC1h 10m
2026-06-26 NFX104 - Jun 26, 01:10 UTCJun 26, 02:14 UTC1h 5m
2026-06-25 NFX103 BUR → SJC Jun 25, 23:14 UTCJun 26, 00:20 UTC1h 5m
2026-06-25 NFX102 RHV → BUR Jun 25, 15:54 UTCJun 25, 16:59 UTC1h 5m
2026-06-25 NFX101 BUR → SJC Jun 25, 14:04 UTCJun 25, 15:10 UTC1h 5m
2026-06-25 NFX104 - Jun 25, 00:55 UTCJun 25, 01:59 UTC1h 5m
2026-06-24 NFX103 BUR → SJC Jun 24, 23:10 UTCJun 25, 00:14 UTC1h 5m
2026-06-24 NFX102 - Jun 24, 16:05 UTCJun 24, 17:14 UTC1h 10m
2026-06-24 NFX101 BUR → SJC Jun 24, 14:15 UTCJun 24, 15:24 UTC1h 10m
2026-06-24 NFX104 - Jun 24, 00:55 UTCJun 24, 02:05 UTC1h 10m
2026-06-23 NFX103 - Jun 23, 23:10 UTCJun 24, 00:15 UTC1h 5m
2026-06-23 NFX102 SJC → BUR Jun 23, 15:59 UTCJun 23, 17:09 UTC1h 10m
2026-06-23 NFX101 BUR → SJC Jun 23, 13:59 UTCJun 23, 14:59 UTC1h 0m
2026-06-22 NFX600 SJC → BUR Jun 22, 14:14 UTCJun 22, 15:20 UTC1h 5m
2026-06-18 NFX601 - Jun 18, 15:55 UTCJun 18, 17:00 UTC1h 5m
2026-06-18 NFX600 SJC → BUR Jun 18, 14:10 UTCJun 18, 15:15 UTC1h 5m
2026-06-18 NFX603 BUR → SJC Jun 18, 00:50 UTCJun 18, 01:50 UTC1h 0m
2026-06-17 NFX602 SJC → BUR Jun 17, 23:00 UTCJun 18, 00:05 UTC1h 5m
2026-06-17 NFX601 BUR → SJC Jun 17, 15:55 UTCJun 17, 17:00 UTC1h 5m
2026-06-17 NFX600 SJC → BUR Jun 17, 14:05 UTCJun 17, 15:15 UTC1h 10m
2026-06-17 NFX603 BUR → SJC Jun 17, 00:55 UTCJun 17, 01:55 UTC1h 0m
2026-06-16 NFX602 SJC → BUR Jun 16, 22:55 UTCJun 17, 00:05 UTC1h 10m
2026-06-16 NFX601 - Jun 16, 15:55 UTCJun 16, 17:00 UTC1h 5m
2026-06-16 NFX600 SJC → BUR Jun 16, 14:05 UTCJun 16, 15:09 UTC1h 5m
2026-06-16 NFX603 BUR → SJC Jun 16, 00:45 UTCJun 16, 01:50 UTC1h 5m
2026-06-15 NFX602 SJC → BUR Jun 15, 22:54 UTCJun 16, 00:00 UTC1h 5m
2026-06-15 NFX601 - Jun 15, 16:09 UTCJun 15, 17:10 UTC1h 0m
2026-06-15 NFX600 SJC → BUR Jun 15, 13:54 UTCJun 15, 15:00 UTC1h 5m
2026-06-12 N793FS VNY → SJC Jun 12, 23:50 UTCJun 13, 00:55 UTC1h 5m
2026-06-12 N793FS SJC → VNY Jun 12, 13:30 UTCJun 12, 14:35 UTC1h 5m
2026-06-12 NFX603 BUR → SJC Jun 12, 00:55 UTCJun 12, 02:05 UTC1h 10m
2026-06-11 NFX602 SJC → BUR Jun 11, 22:55 UTCJun 12, 00:00 UTC1h 5m
2026-06-11 NFX601 BUR → SJC Jun 11, 16:15 UTCJun 11, 17:20 UTC1h 5m
2026-06-11 NFX600 SJC → BUR Jun 11, 14:05 UTCJun 11, 15:10 UTC1h 5m
2026-06-11 NFX603 BUR → SJC Jun 11, 01:15 UTCJun 11, 02:25 UTC1h 10m
2026-06-11 NFX602 - Jun 11, 00:40 UTCJun 11, 01:10 UTC30m
2026-06-10 NFX602 - Jun 10, 23:30 UTCJun 11, 00:35 UTC1h 5m
2026-06-10 NFX601 BUR → SJC Jun 10, 16:00 UTCJun 10, 17:10 UTC1h 10m
2026-06-10 NFX600 SJC → BUR Jun 10, 14:00 UTCJun 10, 15:00 UTC1h 0m
2026-06-10 N793FS SJC → SJC Jun 10, 05:05 UTCJun 10, 05:15 UTC10m
2026-06-10 N793FS SJC → SJC Jun 10, 04:50 UTCJun 10, 04:55 UTC5m

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 N793FS page for operator, model, and routing details .

Mode-S AAC3B8 frequently asked

What is Mode-S code AAC3B8?
AAC3B8 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N793FS.
Where is Mode-S AAC3B8 registered?
Mode-S code AAC3B8 is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is AAC3B8 broadcasting right now?
No active broadcast right now. Last signal was 12d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AAC3B8, octal 52541670, decimal 11,191,224.
What flights does AAC3B8 operate?
Mode-S AAC3B8 has broadcast 10 distinct callsigns, including NFX600, NFX603, NFX601, NFX602, N793FS.