Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AD6543

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N962TF · VANS RV-12 · operated by FLYING 12 CLUB LLC

Hex
AD6543
Octal
53262503
Decimal
11,363,651
Country
US
Tail
N962TF
Type
RV12
No current signal · last broadcast 1d ago
Flights observed
60
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S AD6543.

Country allocation

The ICAO 24-bit address AD6543 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
N962TF - 60 2026-07-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-16 N962TF - Jul 16, 22:40 UTCJul 16, 23:10 UTC30m
2026-07-16 N962TF - Jul 16, 20:15 UTCJul 16, 20:45 UTC30m
2026-07-14 N962TF - Jul 14, 23:15 UTCJul 14, 23:40 UTC25m
2026-07-14 N962TF - Jul 14, 21:10 UTCJul 14, 22:25 UTC1h 15m
2026-07-14 N962TF - Jul 14, 18:15 UTCJul 14, 19:30 UTC1h 15m
2026-07-13 N962TF - Jul 13, 03:10 UTCJul 13, 03:25 UTC15m
2026-07-13 N962TF SQL → LVK Jul 13, 00:30 UTCJul 13, 00:50 UTC20m
2026-07-12 N962TF SQL → SQL Jul 12, 22:20 UTCJul 12, 23:05 UTC45m
2026-07-12 N962TF - Jul 12, 20:10 UTCJul 12, 20:25 UTC15m
2026-07-12 N962TF - Jul 12, 17:40 UTCJul 12, 18:10 UTC30m
2026-07-12 N962TF SQL → SQL Jul 12, 00:10 UTCJul 12, 01:55 UTC1h 45m
2026-07-11 N962TF - Jul 11, 21:10 UTCJul 11, 21:55 UTC45m
2026-07-11 N962TF - Jul 11, 18:55 UTCJul 11, 19:30 UTC35m
2026-07-11 N962TF - Jul 11, 00:25 UTCJul 11, 01:25 UTC1h 0m
2026-07-10 N962TF - Jul 10, 23:35 UTCJul 11, 00:20 UTC45m
2026-07-09 N962TF - Jul 9, 19:10 UTCJul 9, 20:10 UTC1h 0m
2026-07-09 N962TF - Jul 9, 16:45 UTCJul 9, 17:45 UTC1h 0m
2026-07-05 N962TF - Jul 5, 04:30 UTCJul 5, 05:15 UTC45m
2026-07-05 N962TF - Jul 5, 00:45 UTCJul 5, 03:25 UTC2h 40m
2026-07-04 N962TF - Jul 4, 18:10 UTCJul 4, 20:45 UTC2h 35m
2026-07-04 N962TF - Jul 4, 00:40 UTCJul 4, 01:15 UTC35m
2026-07-03 N962TF - Jul 3, 23:35 UTCJul 3, 23:50 UTC15m
2026-07-03 N962TF - Jul 3, 21:35 UTCJul 3, 21:50 UTC15m
2026-07-03 N962TF SQL → SQL Jul 3, 17:30 UTCJul 3, 18:10 UTC40m
2026-06-30 N962TF - Jun 30, 05:05 UTCJun 30, 05:15 UTC10m
2026-06-30 N962TF SQL → HWD Jun 30, 04:40 UTCJun 30, 04:55 UTC15m
2026-06-28 N962TF - Jun 28, 00:15 UTCJun 28, 01:29 UTC1h 15m
2026-06-27 N962TF - Jun 27, 22:09 UTCJun 27, 23:25 UTC1h 15m
2026-06-25 N962TF - Jun 25, 20:25 UTCJun 25, 20:39 UTC15m
2026-06-25 N962TF SQL → LVK Jun 25, 18:04 UTCJun 25, 18:24 UTC20m
2026-06-25 N962TF SQL → SQL Jun 25, 17:14 UTCJun 25, 17:30 UTC15m
2026-06-04 N962TF SQL → SQL Jun 4, 22:50 UTCJun 5, 00:05 UTC1h 15m
2026-05-31 N962TF SQL → SQL May 31, 18:05 UTCMay 31, 18:25 UTC20m
2026-05-31 N962TF SQL → SQL May 31, 17:00 UTCMay 31, 17:55 UTC55m
2026-05-30 N962TF SQL → SQL May 30, 17:25 UTCMay 30, 18:25 UTC1h 0m
2026-05-26 N962TF - May 26, 00:14 UTCMay 26, 00:24 UTC10m
2026-05-25 N962TF SQL → SQL May 25, 23:30 UTCMay 26, 00:00 UTC30m
2026-05-24 N962TF - May 24, 23:00 UTCMay 24, 23:46 UTC46m
2026-05-23 N962TF - May 23, 22:05 UTCMay 23, 22:50 UTC45m
2026-05-23 N962TF - May 23, 19:45 UTCMay 23, 20:30 UTC45m
2026-05-21 N962TF - May 21, 20:00 UTCMay 21, 20:50 UTC50m
2026-05-21 N962TF - May 21, 17:20 UTCMay 21, 18:05 UTC45m
2026-05-16 N962TF SQL → SQL May 16, 19:25 UTCMay 16, 20:05 UTC40m
2026-05-11 N962TF - May 11, 01:50 UTCMay 11, 02:15 UTC25m
2026-05-11 N962TF - May 11, 00:10 UTCMay 11, 00:45 UTC35m
2026-05-10 N962TF - May 10, 21:04 UTCMay 10, 21:35 UTC30m
2026-05-10 N962TF - May 10, 18:20 UTCMay 10, 18:55 UTC35m
2026-04-29 N962TF SQL → SQL Apr 29, 18:50 UTCApr 29, 19:15 UTC25m
2026-04-25 N962TF PAO → SQL Apr 25, 17:20 UTCApr 25, 17:25 UTC5m
2026-04-24 N962TF - Apr 24, 23:15 UTCApr 25, 00:10 UTC55m

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

Mode-S AD6543 frequently asked

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