Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A46B3E

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N384ME · CESSNA 172 Skyhawk · operated by SJ FLYERS LLC

Hex
A46B3E
Octal
51065476
Decimal
10,775,358
Country
US
Tail
N384ME
Type
C172
No current signal · last broadcast 1d ago
Flights observed
84
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S A46B3E.

Country allocation

The ICAO 24-bit address A46B3E 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
N384ME - 84 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 N384ME SQL → SQL May 29, 00:20 UTCMay 29, 00:50 UTC30m
2026-05-29 N384ME SQL → SQL May 29, 00:00 UTCMay 29, 00:10 UTC10m
2026-05-28 N384ME SQL → SQL May 28, 23:40 UTCMay 28, 23:55 UTC15m
2026-05-28 N384ME SQL → SQL May 28, 23:15 UTCMay 28, 23:20 UTC5m
2026-05-20 N384ME SQL → SQL May 20, 18:00 UTCMay 20, 19:10 UTC1h 10m
2026-05-20 N384ME SQL → SQL May 20, 15:40 UTCMay 20, 16:15 UTC35m
2026-05-19 N384ME SQL → PAO May 19, 05:05 UTCMay 19, 05:20 UTC15m
2026-05-18 N384ME SQL → SQL May 18, 01:55 UTCMay 18, 02:25 UTC30m
2026-05-17 N384ME - May 17, 17:20 UTCMay 17, 17:45 UTC25m
2026-05-17 N384ME - May 17, 15:20 UTCMay 17, 16:40 UTC1h 20m
2026-05-16 N384ME SQL → SQL May 16, 21:35 UTCMay 17, 00:00 UTC2h 25m
2026-05-16 N384ME SQL → SQL May 16, 17:50 UTCMay 16, 19:20 UTC1h 30m
2026-05-16 N384ME - May 16, 00:45 UTCMay 16, 00:55 UTC10m
2026-05-15 N384ME SQL → HWD May 15, 23:35 UTCMay 16, 00:40 UTC1h 5m
2026-05-15 N384ME SQL → SQL May 15, 15:00 UTCMay 15, 16:05 UTC1h 5m
2026-05-15 N384ME SQL → SQL May 15, 01:15 UTCMay 15, 02:00 UTC45m
2026-05-14 N384ME SQL → SQL May 14, 20:00 UTCMay 14, 20:10 UTC10m
2026-05-14 N384ME SQL → SQL May 14, 19:10 UTCMay 14, 19:15 UTC5m
2026-05-13 N384ME SQL → SQL May 13, 23:15 UTCMay 14, 00:20 UTC1h 5m
2026-05-13 N384ME SQL → SQL May 13, 01:20 UTCMay 13, 01:30 UTC10m
2026-05-13 N384ME SQL → SQL May 13, 01:05 UTCMay 13, 01:15 UTC10m
2026-05-13 N384ME SQL → SQL May 13, 00:55 UTCMay 13, 01:00 UTC5m
2026-05-12 N384ME SQL → SQL May 12, 20:25 UTCMay 12, 21:40 UTC1h 15m
2026-05-11 N384ME SQL → SQL May 11, 18:50 UTCMay 11, 19:30 UTC40m
2026-05-11 N384ME SQL → SQL May 11, 18:25 UTCMay 11, 18:35 UTC10m
2026-05-10 N384ME SQL → SQL May 10, 22:30 UTCMay 11, 00:45 UTC2h 15m
2026-05-10 N384ME - May 10, 20:25 UTCMay 10, 21:10 UTC45m
2026-05-10 N384ME SQL → SQL May 10, 20:00 UTCMay 10, 20:09 UTC10m
2026-05-09 N384ME SQL → SQL May 9, 15:55 UTCMay 9, 16:10 UTC15m
2026-05-09 N384ME SQL → SQL May 9, 02:05 UTCMay 9, 02:25 UTC20m
2026-05-09 N384ME SQL → SQL May 9, 01:45 UTCMay 9, 02:00 UTC15m
2026-05-07 N384ME SQL → SQL May 7, 22:40 UTCMay 7, 23:39 UTC59m
2026-05-07 N384ME SQL → SQL May 7, 19:00 UTCMay 7, 20:15 UTC1h 15m
2026-05-07 N384ME SQL → SQL May 7, 04:20 UTCMay 7, 04:35 UTC15m
2026-05-06 N384ME SQL → SQL May 6, 22:45 UTCMay 6, 23:55 UTC1h 10m
2026-05-06 N384ME - May 6, 20:20 UTCMay 6, 20:40 UTC20m
2026-05-06 N384ME - May 6, 19:05 UTCMay 6, 19:35 UTC30m
2026-05-05 N384ME SQL → SQL May 5, 16:25 UTCMay 5, 16:30 UTC5m
2026-05-05 N384ME SQL → SQL May 5, 16:10 UTCMay 5, 16:20 UTC10m
2026-05-04 N384ME SQL → SQL May 4, 20:10 UTCMay 4, 20:25 UTC15m
2026-05-04 N384ME SQL → SQL May 4, 19:55 UTCMay 4, 20:05 UTC10m
2026-05-04 N384ME SQL → SQL May 4, 19:30 UTCMay 4, 19:40 UTC10m
2026-05-04 N384ME SQL → SQL May 4, 19:15 UTCMay 4, 19:25 UTC10m
2026-05-04 N384ME SQL → SQL May 4, 19:05 UTCMay 4, 19:10 UTC5m
2026-05-03 N384ME SQL → SQL May 3, 23:50 UTCMay 4, 00:55 UTC1h 5m
2026-05-02 N384ME SQL → SQL May 2, 22:00 UTCMay 3, 00:30 UTC2h 30m
2026-05-02 N384ME SQL → SQL May 2, 19:20 UTCMay 2, 21:00 UTC1h 40m
2026-05-02 N384ME SQL → SQL May 2, 00:30 UTCMay 2, 01:45 UTC1h 15m
2026-04-30 N384ME SQL → SQL Apr 30, 23:00 UTCApr 30, 23:20 UTC20m
2026-04-29 N384ME - Apr 29, 23:45 UTCApr 30, 00:00 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.

Prefer a tail-number view? See the N384ME page for operator, model, and routing details .

Mode-S A46B3E frequently asked

What is Mode-S code A46B3E?
A46B3E is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N384ME.
Where is Mode-S A46B3E registered?
Mode-S code A46B3E 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 A46B3E 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 A46B3E, octal 51065476, decimal 10,775,358.
What flights does A46B3E operate?
Mode-S A46B3E has broadcast 1 distinct callsign, including N384ME.