Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A8A343

ICAO 24-bit transponder address · allocated to United States

Hex
A8A343
Octal
52121503
Decimal
11,051,843
Country
US
No current signal · last broadcast 12d ago
Flights observed
87
Distinct callsigns
3
Country
US
Last broadcast
12d ago

Last known position

Most recent position reported by Mode-S A8A343.

Country allocation

The ICAO 24-bit address A8A343 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 3 distinct

Callsign Airline Flights Last seen
VTE656 Corporate Flight Management 61 2026-05-31
VTE7656 Corporate Flight Management 25 2026-05-30
VTE9656 - 1 2026-04-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-31 VTE656 SOP → MQY May 31, 22:25 UTCMay 31, 22:45 UTC20m
2026-05-31 VTE656 SOP → MQY May 31, 16:45 UTCMay 31, 17:05 UTC20m
2026-05-31 VTE656 SOP → MQY May 31, 14:10 UTCMay 31, 15:15 UTC1h 5m
2026-05-30 VTE656 SOP → MQY May 30, 21:50 UTCMay 30, 22:35 UTC45m
2026-05-30 VTE656 SOP → MQY May 30, 19:35 UTCMay 30, 21:10 UTC1h 35m
2026-05-30 VTE7656 RBD → MKE May 30, 17:55 UTCMay 30, 18:35 UTC40m
2026-05-30 VTE656 SOP → MQY May 30, 15:10 UTCMay 30, 17:00 UTC1h 50m
2026-05-29 VTE7656 RBD → MKE May 29, 22:00 UTCMay 29, 23:20 UTC1h 20m
2026-05-29 VTE656 SOP → MQY May 29, 16:35 UTCMay 29, 18:15 UTC1h 40m
2026-05-29 VTE656 SOP → MQY May 29, 13:55 UTCMay 29, 15:25 UTC1h 30m
2026-05-28 VTE7656 RBD → MKE May 28, 21:10 UTCMay 28, 22:15 UTC1h 5m
2026-05-28 VTE656 SOP → MQY May 28, 17:30 UTCMay 28, 18:30 UTC1h 0m
2026-05-27 VTE7656 RBD → MKE May 27, 19:15 UTCMay 27, 20:35 UTC1h 20m
2026-05-27 VTE656 SOP → MQY May 27, 15:45 UTCMay 27, 17:55 UTC2h 10m
2026-05-27 VTE7656 RBD → MKE May 27, 14:10 UTCMay 27, 14:45 UTC35m
2026-05-26 VTE656 SOP → MQY May 26, 21:40 UTCMay 27, 00:44 UTC3h 5m
2026-05-26 VTE7656 RBD → MKE May 26, 19:15 UTCMay 26, 20:24 UTC1h 10m
2026-05-26 VTE656 SOP → MQY May 26, 14:24 UTCMay 26, 15:29 UTC1h 5m
2026-05-26 VTE7656 RBD → MKE May 26, 12:24 UTCMay 26, 13:15 UTC50m
2026-05-25 VTE656 SOP → MQY May 25, 22:40 UTCMay 25, 23:35 UTC55m
2026-05-25 VTE7656 RBD → MKE May 25, 20:34 UTCMay 25, 21:24 UTC50m
2026-05-25 VTE656 SOP → MQY May 25, 17:50 UTCMay 25, 19:00 UTC1h 10m
2026-05-25 VTE656 SOP → MQY May 25, 14:45 UTCMay 25, 16:20 UTC1h 35m
2026-05-24 VTE7656 RBD → MKE May 24, 18:30 UTCMay 24, 19:15 UTC45m
2026-05-24 VTE656 SOP → MQY May 24, 13:45 UTCMay 24, 14:35 UTC50m
2026-05-23 VTE7656 RBD → MKE May 23, 21:50 UTCMay 23, 22:55 UTC1h 5m
2026-05-23 VTE656 SOP → MQY May 23, 19:25 UTCMay 23, 20:40 UTC1h 15m
2026-05-23 VTE7656 RBD → MKE May 23, 15:55 UTCMay 23, 18:25 UTC2h 31m
2026-05-23 VTE656 SOP → MQY May 23, 12:50 UTCMay 23, 13:50 UTC1h 0m
2026-05-22 VTE7656 RBD → MKE May 22, 19:35 UTCMay 22, 21:05 UTC1h 30m
2026-05-20 VTE656 SOP → MQY May 20, 17:05 UTCMay 20, 19:05 UTC2h 0m
2026-05-19 VTE7656 RBD → MKE May 19, 23:55 UTCMay 20, 01:40 UTC1h 45m
2026-05-19 VTE656 SOP → MQY May 19, 19:55 UTCMay 19, 21:35 UTC1h 40m
2026-05-19 VTE7656 RBD → MKE May 19, 18:00 UTCMay 19, 18:50 UTC50m
2026-05-18 VTE7656 RBD → MKE May 18, 02:25 UTCMay 18, 03:01 UTC35m
2026-05-17 VTE656 SOP → MQY May 17, 22:40 UTCMay 18, 00:30 UTC1h 50m
2026-05-17 VTE7656 RBD → MKE May 17, 19:10 UTCMay 17, 20:35 UTC1h 25m
2026-05-17 VTE656 SOP → MQY May 17, 01:10 UTCMay 17, 02:00 UTC50m
2026-05-16 VTE7656 RBD → MKE May 16, 22:20 UTCMay 16, 22:30 UTC10m
2026-05-13 VTE656 SOP → MQY May 13, 17:20 UTCMay 13, 18:20 UTC1h 0m
2026-05-12 VTE656 SOP → MQY May 12, 18:25 UTCMay 12, 21:30 UTC3h 5m
2026-05-11 VTE656 SOP → MQY May 11, 19:30 UTCMay 11, 19:45 UTC15m
2026-05-11 VTE656 SOP → MQY May 11, 16:05 UTCMay 11, 17:40 UTC1h 36m
2026-05-10 VTE656 SOP → MQY May 10, 16:20 UTCMay 10, 16:55 UTC35m
2026-05-10 VTE656 SOP → MQY May 10, 14:09 UTCMay 10, 15:29 UTC1h 20m
2026-05-09 VTE656 SOP → MQY May 9, 16:30 UTCMay 9, 18:05 UTC1h 35m
2026-05-09 VTE656 SOP → MQY May 9, 13:25 UTCMay 9, 15:15 UTC1h 50m
2026-05-09 VTE656 SOP → MQY May 9, 11:10 UTCMay 9, 11:50 UTC40m
2026-05-08 VTE656 SOP → MQY May 8, 18:35 UTCMay 8, 21:05 UTC2h 30m
2026-05-08 VTE656 SOP → MQY May 8, 12:30 UTCMay 8, 12:44 UTC15m

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.

Mode-S A8A343 frequently asked

What is Mode-S code A8A343?
A8A343 is an ICAO 24-bit transponder address. Allocated to United States.
Where is Mode-S A8A343 registered?
Mode-S code A8A343 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 A8A343 broadcasting right now?
No active broadcast right now. Last signal was 12d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A8A343, octal 52121503, decimal 11,051,843.
What flights does A8A343 operate?
Mode-S A8A343 has broadcast 3 distinct callsigns, including VTE656, VTE7656, VTE9656.