sensors Mode-S transponder

A68A9D

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N520TF · operated by TANGO FLIGHT INC

Hex
A68A9D
Octal
51505235
Decimal
10,914,461
Country
US
Tail
N520TF
Type
RV12
No current signal · last broadcast 16h ago
Flights observed
78
Distinct callsigns
1
Country
US
Last broadcast
16h ago

Last known position

Most recent position reported by Mode-S A68A9D.

Country allocation

The ICAO 24-bit address A68A9D 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
N520TF - 78 2026-06-02

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-02 N520TF DVT → DVT Jun 2, 16:20 UTCJun 2, 17:35 UTC1h 15m
2026-06-01 N520TF DVT → DVT Jun 1, 16:05 UTCJun 1, 17:20 UTC1h 15m
2026-05-31 N520TF DVT → DVT May 31, 14:45 UTCMay 31, 16:10 UTC1h 25m
2026-05-28 N520TF DVT → DVT May 28, 15:20 UTCMay 28, 16:45 UTC1h 25m
2026-05-26 N520TF - May 26, 15:00 UTCMay 26, 15:29 UTC30m
2026-05-26 N520TF - May 26, 13:24 UTCMay 26, 13:50 UTC25m
2026-05-22 N520TF - May 22, 17:40 UTCMay 22, 18:20 UTC40m
2026-05-22 N520TF - May 22, 15:45 UTCMay 22, 16:25 UTC40m
2026-05-21 N520TF DVT → DVT May 21, 13:55 UTCMay 21, 16:10 UTC2h 15m
2026-05-21 N520TF OCN → DVT May 21, 00:40 UTCMay 21, 03:25 UTC2h 45m
2026-05-20 N520TF - May 20, 16:30 UTCMay 20, 16:50 UTC20m
2026-05-20 N520TF - May 20, 13:50 UTCMay 20, 15:30 UTC1h 40m
2026-05-18 N520TF - May 18, 18:05 UTCMay 18, 19:10 UTC1h 4m
2026-05-18 N520TF - May 18, 15:45 UTCMay 18, 16:40 UTC55m
2026-05-17 N520TF - May 17, 16:50 UTCMay 17, 17:30 UTC40m
2026-05-17 N520TF - May 17, 15:40 UTCMay 17, 16:05 UTC25m
2026-05-16 N520TF - May 16, 20:30 UTCMay 16, 21:10 UTC40m
2026-05-16 N520TF - May 16, 17:15 UTCMay 16, 17:50 UTC35m
2026-05-14 N520TF - May 14, 16:25 UTCMay 14, 17:25 UTC1h 0m
2026-05-14 N520TF - May 14, 15:01 UTCMay 14, 15:50 UTC50m
2026-05-13 N520TF OCN → DVT May 13, 20:05 UTCMay 13, 23:15 UTC3h 10m
2026-05-13 N520TF - May 13, 14:35 UTCMay 13, 17:45 UTC3h 10m
2026-05-12 N520TF - May 12, 16:50 UTCMay 12, 17:25 UTC35m
2026-05-12 N520TF - May 12, 14:10 UTCMay 12, 14:40 UTC30m
2026-05-12 N520TF - May 12, 02:45 UTCMay 12, 05:25 UTC2h 40m
2026-05-11 N520TF - May 11, 16:55 UTCMay 11, 17:35 UTC41m
2026-05-11 N520TF - May 11, 14:45 UTCMay 11, 15:20 UTC35m
2026-05-08 N520TF DVT → DVT May 8, 18:45 UTCMay 8, 20:30 UTC1h 45m
2026-05-08 N520TF DVT → DVT May 8, 01:04 UTCMay 8, 03:49 UTC2h 45m
2026-05-07 N520TF - May 7, 19:15 UTCMay 7, 19:45 UTC30m
2026-05-01 N520TF AZA → DVT May 1, 17:40 UTCMay 1, 18:20 UTC40m
2026-05-01 N520TF DVT → AZA May 1, 14:35 UTCMay 1, 15:10 UTC35m
2026-04-30 N520TF DVT → DVT Apr 30, 14:30 UTCApr 30, 17:15 UTC2h 45m
2026-04-29 N520TF - Apr 29, 17:55 UTCApr 29, 20:55 UTC3h 0m
2026-04-29 N520TF - Apr 29, 13:45 UTCApr 29, 16:05 UTC2h 20m
2026-04-28 N520TF - Apr 28, 20:05 UTCApr 28, 21:30 UTC1h 25m
2026-04-28 N520TF - Apr 28, 16:20 UTCApr 28, 17:55 UTC1h 35m
2026-04-28 N520TF - Apr 28, 13:55 UTCApr 28, 14:55 UTC1h 0m
2026-04-27 N520TF - Apr 27, 18:05 UTCApr 27, 19:05 UTC1h 0m
2026-04-27 N520TF - Apr 27, 13:40 UTCApr 27, 14:30 UTC50m
2026-04-24 N520TF DVT → DVT Apr 24, 16:35 UTCApr 24, 17:30 UTC55m
2026-04-23 N520TF DVT → DVT Apr 23, 13:55 UTCApr 23, 15:25 UTC1h 30m
2026-04-22 N520TF - Apr 22, 15:30 UTCApr 22, 17:10 UTC1h 40m
2026-04-22 N520TF - Apr 22, 14:10 UTCApr 22, 14:55 UTC45m
2026-04-21 N520TF - Apr 21, 02:40 UTCApr 21, 03:40 UTC1h 0m
2026-04-20 N520TF - Apr 20, 22:05 UTCApr 21, 00:40 UTC2h 35m
2026-04-20 N520TF - Apr 20, 16:40 UTCApr 20, 18:55 UTC2h 15m
2026-04-20 N520TF - Apr 20, 14:25 UTCApr 20, 15:15 UTC50m
2026-04-20 N520TF - Apr 20, 01:55 UTCApr 20, 02:35 UTC40m
2026-04-20 N520TF - Apr 20, 00:00 UTCApr 20, 01:05 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 N520TF page for operator, model, and routing details .

Mode-S A68A9D frequently asked

What is Mode-S code A68A9D?
A68A9D is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N520TF.
Where is Mode-S A68A9D registered?
Mode-S code A68A9D 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 A68A9D broadcasting right now?
No active broadcast right now. Last signal was 16h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A68A9D, octal 51505235, decimal 10,914,461.
What flights does A68A9D operate?
Mode-S A68A9D has broadcast 1 distinct callsign, including N520TF.