Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A46462

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N382TA · CESSNA 208 Caravan · operated by SEAPLANE LLC

Hex
A46462
Octal
51062142
Decimal
10,773,602
Country
US
Tail
N382TA
Type
C208
No current signal · last broadcast 4d ago
Flights observed
67
Distinct callsigns
1
Country
US
Last broadcast
4d ago

Last known position

Most recent position reported by Mode-S A46462.

Country allocation

The ICAO 24-bit address A46462 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
FTO382 Tropic Ocean Airways 67 2026-05-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-25 FTO382 NAS → BCT May 25, 23:19 UTCMay 25, 23:35 UTC15m
2026-05-25 FTO382 NAS → BCT May 25, 22:30 UTCMay 25, 23:04 UTC35m
2026-05-25 FTO382 NAS → BCT May 25, 21:09 UTCMay 25, 21:54 UTC45m
2026-05-25 FTO382 NAS → BCT May 25, 20:19 UTCMay 25, 20:50 UTC30m
2026-05-25 FTO382 NAS → BCT May 25, 18:55 UTCMay 25, 19:35 UTC40m
2026-05-22 FTO382 NAS → BCT May 22, 22:30 UTCMay 22, 23:00 UTC30m
2026-05-22 FTO382 NAS → BCT May 22, 21:15 UTCMay 22, 21:55 UTC40m
2026-05-22 FTO382 NAS → BCT May 22, 20:25 UTCMay 22, 20:50 UTC25m
2026-05-22 FTO382 NAS → BCT May 22, 18:55 UTCMay 22, 19:35 UTC40m
2026-05-22 FTO382 NAS → BCT May 22, 17:55 UTCMay 22, 18:25 UTC30m
2026-05-22 FTO382 NAS → BCT May 22, 14:40 UTCMay 22, 15:25 UTC45m
2026-05-22 FTO382 NAS → BCT May 22, 14:05 UTCMay 22, 14:20 UTC15m
2026-05-21 FTO382 NAS → BCT May 21, 20:50 UTCMay 21, 21:35 UTC45m
2026-05-21 FTO382 NAS → BCT May 21, 19:30 UTCMay 21, 20:10 UTC40m
2026-05-21 FTO382 NAS → BCT May 21, 18:50 UTCMay 21, 19:05 UTC15m
2026-05-21 FTO382 NAS → BCT May 21, 16:35 UTCMay 21, 16:50 UTC15m
2026-05-21 FTO382 NAS → BCT May 21, 16:10 UTCMay 21, 16:15 UTC5m
2026-05-21 FTO382 NAS → BCT May 21, 15:35 UTCMay 21, 15:45 UTC10m
2026-05-21 FTO382 NAS → BCT May 21, 14:55 UTCMay 21, 15:00 UTC5m
2026-05-21 FTO382 NAS → BCT May 21, 13:55 UTCMay 21, 14:10 UTC15m
2026-05-10 FTO382 NAS → BCT May 10, 17:59 UTCMay 10, 18:15 UTC15m
2026-05-10 FTO382 NAS → BCT May 10, 17:10 UTCMay 10, 17:30 UTC20m
2026-05-10 FTO382 NAS → BCT May 10, 16:44 UTCMay 10, 16:55 UTC10m
2026-05-10 FTO382 NAS → BCT May 10, 16:00 UTCMay 10, 16:40 UTC40m
2026-05-09 FTO382 NAS → BCT May 9, 07:20 UTCMay 9, 08:45 UTC1h 25m
2026-05-09 FTO382 NAS → BCT May 9, 03:30 UTCMay 9, 06:25 UTC2h 55m
2026-05-09 FTO382 NAS → BCT May 9, 00:25 UTCMay 9, 02:25 UTC2h 0m
2026-05-05 FTO382 NAS → BCT May 5, 15:25 UTCMay 5, 15:55 UTC30m
2026-05-03 FTO382 NAS → BCT May 3, 22:09 UTCMay 3, 22:30 UTC20m
2026-05-03 FTO382 NAS → BCT May 3, 19:25 UTCMay 3, 19:34 UTC10m
2026-05-03 FTO382 NAS → BCT May 3, 16:40 UTCMay 3, 17:00 UTC20m
2026-05-01 FTO382 NAS → BCT May 1, 16:35 UTCMay 1, 16:45 UTC10m
2026-05-01 FTO382 NAS → BCT May 1, 14:10 UTCMay 1, 14:20 UTC10m
2026-05-01 FTO382 NAS → BCT May 1, 12:45 UTCMay 1, 12:55 UTC10m
2026-04-26 FTO382 NAS → BCT Apr 26, 20:30 UTCApr 26, 20:50 UTC20m
2026-04-26 FTO382 NAS → BCT Apr 26, 16:55 UTCApr 26, 17:20 UTC25m
2026-04-26 FTO382 NAS → BCT Apr 26, 14:05 UTCApr 26, 14:15 UTC10m
2026-04-26 FTO382 NAS → BCT Apr 26, 12:50 UTCApr 26, 13:00 UTC10m
2026-04-24 FTO382 NAS → BCT Apr 24, 19:40 UTCApr 24, 19:50 UTC10m
2026-04-24 FTO382 NAS → BCT Apr 24, 16:55 UTCApr 24, 17:15 UTC20m
2026-04-24 FTO382 NAS → BCT Apr 24, 15:00 UTCApr 24, 15:20 UTC20m
2026-04-24 FTO382 NAS → BCT Apr 24, 13:15 UTCApr 24, 13:35 UTC20m
2026-04-23 FTO382 NAS → BCT Apr 23, 22:45 UTCApr 23, 23:00 UTC15m
2026-04-23 FTO382 NAS → BCT Apr 23, 19:45 UTCApr 23, 20:00 UTC15m
2026-04-23 FTO382 NAS → BCT Apr 23, 17:20 UTCApr 23, 17:40 UTC19m
2026-04-23 FTO382 NAS → BCT Apr 23, 16:00 UTCApr 23, 16:10 UTC10m
2026-04-22 FTO382 NAS → BCT Apr 22, 17:40 UTCApr 22, 18:05 UTC25m
2026-04-22 FTO382 NAS → BCT Apr 22, 16:25 UTCApr 22, 16:45 UTC20m
2026-04-20 FTO382 NAS → BCT Apr 20, 20:55 UTCApr 20, 21:25 UTC30m
2026-04-20 FTO382 NAS → BCT Apr 20, 12:15 UTCApr 20, 12:40 UTC25m

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

Mode-S A46462 frequently asked

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