Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AB8B8C

ICAO 24-bit transponder address · allocated to United States

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

Hex
AB8B8C
Octal
52705614
Decimal
11,242,380
Country
US
Tail
N843FS
Type
B350
No current signal · last broadcast 3d ago
Flights observed
107
Distinct callsigns
9
Country
US
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S AB8B8C.

Country allocation

The ICAO 24-bit address AB8B8C 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 9 distinct

Callsign Airline Flights Last seen
NFX101 - 23 2026-06-17
NFX102 - 21 2026-06-17
NFX104 - 19 2026-06-18
NFX103 - 18 2026-06-17
N843FS - 11 2026-06-17
NFX601 - 5 2026-05-12
NFX602 - 4 2026-05-12
NFX600 - 4 2026-05-12
NFX603 - 2 2026-05-01

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-18 NFX104 - Jun 18, 00:45 UTCJun 18, 01:50 UTC1h 5m
2026-06-17 NFX103 BUR → SJC Jun 17, 22:45 UTCJun 17, 23:50 UTC1h 5m
2026-06-17 NFX102 SJC → BUR Jun 17, 15:50 UTCJun 17, 17:00 UTC1h 10m
2026-06-17 NFX101 BUR → SJC Jun 17, 13:55 UTCJun 17, 15:00 UTC1h 5m
2026-06-17 N843FS BUR → BUR Jun 17, 04:05 UTCJun 17, 04:15 UTC10m
2026-06-17 NFX104 SJC → BUR Jun 17, 00:50 UTCJun 17, 01:55 UTC1h 5m
2026-06-16 NFX103 BUR → SJC Jun 16, 22:55 UTCJun 16, 23:55 UTC1h 0m
2026-06-16 NFX102 SJC → BUR Jun 16, 15:45 UTCJun 16, 16:50 UTC1h 5m
2026-06-16 NFX101 BUR → SJC Jun 16, 13:55 UTCJun 16, 15:00 UTC1h 5m
2026-06-15 NFX102 RHV → BUR Jun 15, 15:35 UTCJun 15, 16:35 UTC1h 0m
2026-06-15 NFX101 BUR → SJC Jun 15, 14:00 UTCJun 15, 15:04 UTC1h 5m
2026-06-12 NFX104 - Jun 12, 00:55 UTCJun 12, 02:00 UTC1h 5m
2026-06-11 NFX103 BUR → SJC Jun 11, 23:10 UTCJun 12, 00:15 UTC1h 5m
2026-06-11 NFX102 SJC → BUR Jun 11, 15:35 UTCJun 11, 16:40 UTC1h 5m
2026-06-11 NFX101 BUR → SJC Jun 11, 14:00 UTCJun 11, 15:00 UTC1h 0m
2026-06-08 N843FS SFO → BUR Jun 8, 23:35 UTCJun 9, 00:50 UTC1h 15m
2026-06-08 N843FS CLD → SFO Jun 8, 20:10 UTCJun 8, 22:00 UTC1h 50m
2026-06-07 N843FS BUR → CLD Jun 7, 17:15 UTCJun 7, 17:45 UTC30m
2026-06-05 NFX104 SJC → BUR Jun 5, 01:00 UTCJun 5, 02:05 UTC1h 5m
2026-06-04 NFX103 BUR → SJC Jun 4, 23:05 UTCJun 5, 00:15 UTC1h 10m
2026-06-04 NFX102 - Jun 4, 15:55 UTCJun 4, 16:55 UTC1h 0m
2026-06-04 NFX101 BUR → SJC Jun 4, 14:05 UTCJun 4, 15:10 UTC1h 5m
2026-06-04 NFX104 - Jun 4, 00:50 UTCJun 4, 01:55 UTC1h 5m
2026-06-03 NFX103 - Jun 3, 23:10 UTCJun 4, 00:20 UTC1h 10m
2026-06-03 NFX101 - Jun 3, 15:45 UTCJun 3, 16:50 UTC1h 5m
2026-06-03 NFX101 BUR → SJC Jun 3, 14:00 UTCJun 3, 15:05 UTC1h 5m
2026-06-03 NFX104 SJC → BUR Jun 3, 00:40 UTCJun 3, 01:45 UTC1h 5m
2026-06-02 NFX103 BUR → SJC Jun 2, 22:45 UTCJun 2, 23:50 UTC1h 5m
2026-06-02 NFX102 SJC → BUR Jun 2, 16:00 UTCJun 2, 17:10 UTC1h 10m
2026-06-02 NFX101 BUR → SJC Jun 2, 14:00 UTCJun 2, 15:05 UTC1h 5m
2026-06-02 NFX104 SJC → BUR Jun 2, 01:05 UTCJun 2, 02:15 UTC1h 10m
2026-06-01 NFX103 VNY → SJC Jun 1, 23:10 UTCJun 2, 00:10 UTC1h 0m
2026-06-01 NFX102 - Jun 1, 15:50 UTCJun 1, 16:55 UTC1h 5m
2026-06-01 NFX101 BUR → SJC Jun 1, 13:55 UTCJun 1, 15:00 UTC1h 5m
2026-05-27 NFX104 - May 27, 01:14 UTCMay 27, 02:14 UTC1h 0m
2026-05-26 NFX102 - May 26, 15:49 UTCMay 26, 16:50 UTC1h 0m
2026-05-26 NFX101 BUR → SJC May 26, 13:54 UTCMay 26, 15:05 UTC1h 10m
2026-05-22 NFX104 - May 22, 00:40 UTCMay 22, 01:45 UTC1h 5m
2026-05-21 NFX103 BUR → SJC May 21, 23:05 UTCMay 22, 00:10 UTC1h 5m
2026-05-21 NFX102 - May 21, 15:40 UTCMay 21, 16:40 UTC1h 0m
2026-05-21 NFX101 BUR → SJC May 21, 13:55 UTCMay 21, 14:55 UTC1h 0m
2026-05-21 NFX104 - May 21, 00:50 UTCMay 21, 02:00 UTC1h 10m
2026-05-20 NFX103 - May 20, 23:10 UTCMay 21, 00:15 UTC1h 5m
2026-05-20 NFX102 SJC → BUR May 20, 15:55 UTCMay 20, 16:55 UTC1h 0m
2026-05-20 NFX101 BUR → SJC May 20, 14:00 UTCMay 20, 15:00 UTC1h 0m
2026-05-20 NFX104 - May 20, 00:45 UTCMay 20, 01:50 UTC1h 5m
2026-05-19 NFX103 - May 19, 23:05 UTCMay 20, 00:10 UTC1h 5m
2026-05-19 NFX102 - May 19, 15:45 UTCMay 19, 16:45 UTC1h 0m
2026-05-19 NFX101 BUR → SJC May 19, 14:00 UTCMay 19, 15:10 UTC1h 10m
2026-05-19 NFX104 SJC → BUR May 19, 01:00 UTCMay 19, 02:00 UTC1h 0m

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

Mode-S AB8B8C frequently asked

What is Mode-S code AB8B8C?
AB8B8C is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N843FS.
Where is Mode-S AB8B8C registered?
Mode-S code AB8B8C 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 AB8B8C broadcasting right now?
No active broadcast right now. Last signal was 3d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AB8B8C, octal 52705614, decimal 11,242,380.
What flights does AB8B8C operate?
Mode-S AB8B8C has broadcast 9 distinct callsigns, including NFX101, NFX102, NFX104, NFX103, N843FS.