Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AD07A6

ICAO 24-bit transponder address · allocated to United States

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

Hex
AD07A6
Octal
53203646
Decimal
11,339,686
Country
US
Tail
N939FS
Type
B350
No current signal · last broadcast 4h ago
Flights observed
150
Distinct callsigns
9
Country
US
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S AD07A6.

Country allocation

The ICAO 24-bit address AD07A6 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
NFX104 - 21 2026-07-14
NFX102 - 21 2026-07-13
NFX103 - 20 2026-07-13
NFX101 - 19 2026-07-13
NFX603 - 17 2026-07-02
NFX602 - 16 2026-07-01
NFX600 - 15 2026-07-02
NFX601 - 14 2026-06-29
N939FS - 7 2026-06-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 NFX104 SJC → BUR Jul 14, 01:20 UTCJul 14, 02:30 UTC1h 10m
2026-07-13 NFX103 BUR → SJC Jul 13, 23:05 UTCJul 14, 00:05 UTC1h 0m
2026-07-13 NFX102 SJC → BUR Jul 13, 15:50 UTCJul 13, 17:05 UTC1h 15m
2026-07-13 NFX101 BUR → SJC Jul 13, 13:55 UTCJul 13, 14:55 UTC1h 0m
2026-07-10 NFX104 - Jul 10, 00:40 UTCJul 10, 01:45 UTC1h 5m
2026-07-09 NFX103 BUR → SJC Jul 9, 22:50 UTCJul 10, 00:05 UTC1h 15m
2026-07-09 NFX104 - Jul 9, 00:50 UTCJul 9, 01:55 UTC1h 5m
2026-07-08 NFX103 BUR → SJC Jul 8, 23:05 UTCJul 9, 00:15 UTC1h 10m
2026-07-08 NFX102 - Jul 8, 15:45 UTCJul 8, 16:50 UTC1h 5m
2026-07-08 NFX101 BUR → SJC Jul 8, 13:50 UTCJul 8, 15:00 UTC1h 10m
2026-07-08 NFX104 - Jul 8, 00:45 UTCJul 8, 01:50 UTC1h 5m
2026-07-07 NFX103 BUR → SJC Jul 7, 22:50 UTCJul 8, 00:00 UTC1h 10m
2026-07-07 NFX102 - Jul 7, 15:40 UTCJul 7, 16:45 UTC1h 5m
2026-07-07 NFX101 BUR → SJC Jul 7, 13:45 UTCJul 7, 14:50 UTC1h 5m
2026-07-06 NFX102 - Jul 6, 15:30 UTCJul 6, 16:35 UTC1h 5m
2026-07-06 NFX101 BUR → SJC Jul 6, 13:50 UTCJul 6, 15:00 UTC1h 10m
2026-07-03 NFX104 SJC → BUR Jul 3, 00:40 UTCJul 3, 01:45 UTC1h 5m
2026-07-02 NFX103 BUR → SJC Jul 2, 22:45 UTCJul 2, 23:55 UTC1h 10m
2026-07-02 NFX600 SJC → BUR Jul 2, 14:15 UTCJul 2, 15:15 UTC1h 0m
2026-07-02 NFX603 - Jul 2, 00:50 UTCJul 2, 01:55 UTC1h 5m
2026-07-01 NFX602 SJC → BUR Jul 1, 23:10 UTCJul 2, 00:15 UTC1h 5m
2026-06-29 NFX601 BUR → SJC Jun 29, 16:04 UTCJun 29, 17:10 UTC1h 5m
2026-06-29 NFX600 SJC → BUR Jun 29, 14:09 UTCJun 29, 15:14 UTC1h 5m
2026-06-26 NFX603 BUR → SJC Jun 26, 01:10 UTCJun 26, 02:20 UTC1h 10m
2026-06-23 NFX104 RHV → BUR Jun 23, 00:54 UTCJun 23, 01:59 UTC1h 5m
2026-06-22 NFX103 BUR → SJC Jun 22, 22:59 UTCJun 23, 00:09 UTC1h 10m
2026-06-22 NFX102 - Jun 22, 15:45 UTCJun 22, 16:50 UTC1h 5m
2026-06-22 NFX101 BUR → SJC Jun 22, 13:19 UTCJun 22, 14:29 UTC1h 10m
2026-06-19 NFX104 - Jun 19, 00:49 UTCJun 19, 01:59 UTC1h 10m
2026-06-18 NFX103 BUR → SJC Jun 18, 23:05 UTCJun 19, 00:10 UTC1h 4m
2026-06-11 N939FS BUR → BUR Jun 11, 05:15 UTCJun 11, 05:25 UTC10m
2026-06-11 N939FS - Jun 11, 04:40 UTCJun 11, 04:45 UTC5m
2026-06-11 N939FS BUR → BUR Jun 11, 04:15 UTCJun 11, 04:25 UTC10m
2026-06-11 NFX104 - Jun 11, 01:10 UTCJun 11, 02:15 UTC1h 5m
2026-06-10 NFX103 BUR → SJC Jun 10, 23:15 UTCJun 11, 00:25 UTC1h 10m
2026-06-10 NFX102 SJC → BUR Jun 10, 15:55 UTCJun 10, 17:00 UTC1h 5m
2026-06-10 NFX101 BUR → SJC Jun 10, 14:00 UTCJun 10, 15:05 UTC1h 5m
2026-06-10 NFX104 SJC → BUR Jun 10, 00:55 UTCJun 10, 02:00 UTC1h 5m
2026-06-09 NFX103 BUR → SJC Jun 9, 23:10 UTCJun 10, 00:20 UTC1h 10m
2026-06-09 NFX102 - Jun 9, 16:45 UTCJun 9, 17:15 UTC30m
2026-06-09 NFX101 BUR → SJC Jun 9, 14:10 UTCJun 9, 15:20 UTC1h 10m
2026-06-09 NFX104 - Jun 9, 00:40 UTCJun 9, 01:40 UTC1h 0m
2026-06-08 NFX103 BUR → SJC Jun 8, 23:00 UTCJun 9, 00:10 UTC1h 10m
2026-06-08 NFX102 SJC → BUR Jun 8, 15:55 UTCJun 8, 17:05 UTC1h 10m
2026-06-08 NFX101 BUR → SJC Jun 8, 14:00 UTCJun 8, 15:04 UTC1h 5m
2026-06-02 NFX602 SJC → BUR Jun 2, 22:45 UTCJun 2, 23:50 UTC1h 5m
2026-06-02 NFX601 BUR → SJC Jun 2, 16:20 UTCJun 2, 17:25 UTC1h 5m
2026-06-02 NFX600 SJC → BUR Jun 2, 14:20 UTCJun 2, 15:30 UTC1h 10m
2026-06-02 NFX603 - Jun 2, 00:55 UTCJun 2, 02:00 UTC1h 5m
2026-06-01 NFX602 - Jun 1, 23:10 UTCJun 2, 00:15 UTC1h 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 N939FS page for operator, model, and routing details .

Mode-S AD07A6 frequently asked

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