sensors Mode-S transponder

A46B3C

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N384MC · CESSNA 172 Skyhawk · operated by AERO-TECH SERVICES INC

Hex
A46B3C
Octal
51065474
Decimal
10,775,356
Country
US
Tail
N384MC
Type
C172
No current signal · last broadcast 11h ago
Flights observed
161
Distinct callsigns
1
Country
US
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S A46B3C.

Country allocation

The ICAO 24-bit address A46B3C 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
N384MC - 161 2026-06-02

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-02 N384MC LNS → LNS Jun 2, 20:55 UTCJun 2, 21:30 UTC35m
2026-06-02 N384MC - Jun 2, 17:50 UTCJun 2, 18:40 UTC50m
2026-06-02 N384MC LNS → RDG Jun 2, 17:15 UTCJun 2, 17:40 UTC25m
2026-06-01 N384MC LNS → LNS Jun 1, 23:50 UTCJun 2, 00:35 UTC45m
2026-06-01 N384MC LNS → LNS Jun 1, 19:50 UTCJun 1, 20:45 UTC55m
2026-06-01 N384MC LNS → LNS Jun 1, 15:45 UTCJun 1, 17:30 UTC1h 45m
2026-06-01 N384MC LNS → LNS Jun 1, 01:05 UTCJun 1, 01:45 UTC40m
2026-05-31 N384MC LNS → LNS May 31, 22:50 UTCMay 31, 23:45 UTC55m
2026-05-31 N384MC LNS → LNS May 31, 21:25 UTCMay 31, 21:55 UTC30m
2026-05-31 N384MC LNS → LNS May 31, 17:40 UTCMay 31, 19:15 UTC1h 35m
2026-05-31 N384MC LNS → LNS May 31, 14:45 UTCMay 31, 15:50 UTC1h 5m
2026-05-30 N384MC LNS → LNS May 30, 14:15 UTCMay 30, 15:40 UTC1h 25m
2026-05-29 N384MC PVD → LNS May 29, 16:10 UTCMay 29, 19:55 UTC3h 45m
2026-05-29 N384MC - May 29, 10:55 UTCMay 29, 14:05 UTC3h 10m
2026-05-29 N384MC - May 29, 00:25 UTCMay 29, 01:00 UTC35m
2026-05-28 N384MC - May 28, 23:05 UTCMay 28, 23:55 UTC50m
2026-05-28 N384MC LNS → LNS May 28, 20:45 UTCMay 28, 21:40 UTC55m
2026-05-28 N384MC LNS → LNS May 28, 19:10 UTCMay 28, 19:45 UTC35m
2026-05-28 N384MC LNS → LNS May 28, 16:30 UTCMay 28, 17:40 UTC1h 10m
2026-05-28 N384MC LNS → LNS May 28, 11:50 UTCMay 28, 12:30 UTC40m
2026-05-28 N384MC - May 28, 00:30 UTCMay 28, 01:10 UTC40m
2026-05-27 N384MC - May 27, 23:00 UTCMay 27, 23:50 UTC50m
2026-05-27 N384MC LNS → LNS May 27, 19:40 UTCMay 27, 20:50 UTC1h 10m
2026-05-27 N384MC LNS → LNS May 27, 17:40 UTCMay 27, 18:45 UTC1h 5m
2026-05-27 N384MC LNS → LNS May 27, 13:40 UTCMay 27, 14:35 UTC55m
2026-05-26 N384MC LNS → LNS May 26, 19:55 UTCMay 26, 20:45 UTC50m
2026-05-26 N384MC LNS → LNS May 26, 18:24 UTCMay 26, 18:30 UTC5m
2026-05-26 N384MC LNS → LNS May 26, 17:50 UTCMay 26, 18:10 UTC20m
2026-05-26 N384MC LNS → LNS May 26, 16:59 UTCMay 26, 17:39 UTC40m
2026-05-25 N384MC LNS → LNS May 25, 21:09 UTCMay 25, 21:40 UTC30m
2026-05-25 N384MC LNS → LNS May 25, 15:25 UTCMay 25, 16:05 UTC40m
2026-05-23 N384MC - May 23, 14:20 UTCMay 23, 15:00 UTC40m
2026-05-23 N384MC LNS → LNS May 23, 14:00 UTCMay 23, 14:05 UTC5m
2026-05-22 N384MC - May 22, 22:35 UTCMay 22, 23:10 UTC35m
2026-05-19 N384MC LNS → THV May 19, 20:15 UTCMay 19, 20:40 UTC25m
2026-05-19 N384MC LNS → LNS May 19, 19:10 UTCMay 19, 19:50 UTC40m
2026-05-19 N384MC LNS → LNS May 19, 16:50 UTCMay 19, 17:45 UTC55m
2026-05-18 N384MC LNS → LNS May 18, 23:10 UTCMay 18, 23:45 UTC35m
2026-05-18 N384MC LNS → LNS May 18, 21:25 UTCMay 18, 21:55 UTC30m
2026-05-18 N384MC LNS → LNS May 18, 16:50 UTCMay 18, 18:15 UTC1h 25m
2026-05-18 N384MC LNS → LNS May 18, 14:55 UTCMay 18, 15:30 UTC35m
2026-05-18 N384MC - May 18, 13:30 UTCMay 18, 13:35 UTC5m
2026-05-18 N384MC LNS → LNS May 18, 13:00 UTCMay 18, 13:15 UTC15m
2026-05-17 N384MC LNS → LNS May 17, 20:10 UTCMay 17, 20:45 UTC35m
2026-05-17 N384MC LNS → LNS May 17, 17:50 UTCMay 17, 18:25 UTC35m
2026-05-17 N384MC LNS → LNS May 17, 13:45 UTCMay 17, 14:50 UTC1h 5m
2026-05-16 N384MC LNS → LNS May 16, 16:00 UTCMay 16, 17:25 UTC1h 25m
2026-05-16 N384MC - May 16, 14:11 UTCMay 16, 14:51 UTC40m
2026-05-16 N384MC - May 16, 12:25 UTCMay 16, 13:01 UTC35m
2026-05-15 N384MC LNS → LNS May 15, 23:50 UTCMay 16, 00:40 UTC50m

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

Mode-S A46B3C frequently asked

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