sensors Mode-S transponder

ADFFC9

ICAO 24-bit transponder address

Currently assigned to 65-10412 · Northrop T-38C Talon

Hex
ADFFC9
Octal
53377711
Decimal
11,403,209
Tail
65-10412
Type
T38
No current signal · last broadcast 21d ago
Flights observed
31
Distinct callsigns
20
Country
-
Last broadcast
21d ago

Last known position

Most recent position reported by Mode-S ADFFC9.

Callsign history 20 distinct

Callsign Airline Flights Last seen
GUTS41 - 2 2026-04-17
VIPER12 - 1 2026-05-08
VIPER03 - 1 2026-04-16
VIPER02 - 1 2026-04-20
SR82 - 1 2026-04-27
SPEED62 - 1 2026-04-22
SPEED51 - 1 2026-05-05
SKID51 - 1 2026-04-24
SD73 - 1 2026-04-27
SCAR32 - 1 2026-04-16
RINGO2 - 1 2026-04-24
RINGO05 - 1 2026-04-17
REEF71 - 1 2026-04-24
REEF61 - 1 2026-04-23
NA12 - 1 2026-04-15
GUTS61 - 1 2026-04-30
GUTS42 - 1 2026-05-11
GUTS22 - 1 2026-04-14
GUTS12 - 1 2026-05-01
GUNDOG3 - 1 2026-04-23

Recent flights last 31

DateFlightRouteTakeoffLandingDuration
2026-05-12 BONES21 - May 12, 16:15 UTCMay 12, 16:50 UTC35m
2026-05-11 GUTS42 - May 11, 16:35 UTCMay 11, 17:10 UTC36m
2026-05-08 VIPER12 - May 8, 20:40 UTCMay 8, 20:50 UTC10m
2026-05-06 COWBOY5 - May 6, 13:40 UTCMay 6, 13:55 UTC15m
2026-05-05 SPEED51 - May 5, 20:35 UTCMay 5, 21:05 UTC30m
2026-05-05 BONES62 - May 5, 17:10 UTCMay 5, 17:35 UTC25m
2026-05-01 GUTS12 - May 1, 12:50 UTCMay 1, 13:05 UTC15m
2026-04-30 BONES71 - Apr 30, 20:30 UTCApr 30, 21:05 UTC35m
2026-04-30 DEATH1 - Apr 30, 17:45 UTCApr 30, 18:00 UTC16m
2026-04-30 GUTS61 - Apr 30, 13:40 UTCApr 30, 14:15 UTC35m
2026-04-29 FANG71 - Apr 29, 20:25 UTCApr 29, 21:05 UTC40m
2026-04-27 SR82 - Apr 27, 20:35 UTCApr 27, 21:15 UTC40m
2026-04-27 EAGLE05 - Apr 27, 17:05 UTCApr 27, 17:15 UTC10m
2026-04-27 SD73 - Apr 27, 13:35 UTCApr 27, 14:05 UTC30m
2026-04-24 RINGO2 - Apr 24, 20:40 UTCApr 24, 21:00 UTC20m
2026-04-24 REEF71 - Apr 24, 17:05 UTCApr 24, 17:45 UTC40m
2026-04-24 SKID51 - Apr 24, 13:05 UTCApr 24, 13:30 UTC25m
2026-04-23 GUNDOG3 - Apr 23, 16:40 UTCApr 23, 17:00 UTC20m
2026-04-23 REEF61 - Apr 23, 13:30 UTCApr 23, 14:15 UTC45m
2026-04-22 SPEED62 - Apr 22, 17:05 UTCApr 22, 17:40 UTC35m
2026-04-22 FANG62 - Apr 22, 13:50 UTCApr 22, 14:30 UTC40m
2026-04-20 BASS51 - Apr 20, 20:15 UTCApr 20, 20:50 UTC35m
2026-04-20 VIPER02 - Apr 20, 16:55 UTCApr 20, 17:05 UTC10m
2026-04-17 RINGO05 - Apr 17, 20:20 UTCApr 17, 20:45 UTC25m
2026-04-17 GUTS41 - Apr 17, 17:25 UTCApr 17, 17:35 UTC10m
2026-04-17 GUTS41 - Apr 17, 16:40 UTCApr 17, 17:15 UTC35m
2026-04-16 SCAR32 - Apr 16, 20:10 UTCApr 16, 20:40 UTC30m
2026-04-16 VIPER03 - Apr 16, 16:10 UTCApr 16, 16:25 UTC15m
2026-04-15 NA12 - Apr 15, 19:35 UTCApr 15, 19:45 UTC10m
2026-04-14 GUTS22 - Apr 14, 19:45 UTCApr 14, 20:15 UTC30m
2026-04-13 EAGLE42 - Apr 13, 20:45 UTCApr 13, 21:15 UTC30m

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

Mode-S ADFFC9 frequently asked

What is Mode-S code ADFFC9?
ADFFC9 is an ICAO 24-bit transponder address. Assigned to 65-10412.
Is ADFFC9 broadcasting right now?
No active broadcast right now. Last signal was 21d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex ADFFC9, octal 53377711, decimal 11,403,209.
What flights does ADFFC9 operate?
Mode-S ADFFC9 has broadcast 20 distinct callsigns, including GUTS41, VIPER12, VIPER03, VIPER02, SR82.