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 1h ago
Flights observed
164
Distinct callsigns
1
Country
US
Last broadcast
1h 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 - 164 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 N384ME SQL → SQL Jul 14, 19:45 UTCJul 14, 20:25 UTC40m
2026-07-14 N384ME SQL → SQL Jul 14, 18:45 UTCJul 14, 19:25 UTC40m
2026-07-14 N384ME SQL → SQL Jul 14, 00:55 UTCJul 14, 01:35 UTC40m
2026-07-13 N384ME SQL → SQL Jul 13, 21:00 UTCJul 13, 21:10 UTC10m
2026-07-13 N384ME SQL → SQL Jul 13, 19:40 UTCJul 13, 20:55 UTC1h 15m
2026-07-13 N384ME SQL → SQL Jul 13, 02:40 UTCJul 13, 02:50 UTC10m
2026-07-13 N384ME SQL → SQL Jul 13, 02:25 UTCJul 13, 02:35 UTC10m
2026-07-13 N384ME SQL → SQL Jul 13, 01:05 UTCJul 13, 02:20 UTC1h 15m
2026-07-12 N384ME SQL → SQL Jul 12, 22:15 UTCJul 12, 23:50 UTC1h 35m
2026-07-11 N384ME SQL → SQL Jul 11, 00:00 UTCJul 11, 01:10 UTC1h 10m
2026-07-10 N384ME SQL → SQL Jul 10, 21:15 UTCJul 10, 22:10 UTC55m
2026-07-10 N384ME SQL → SQL Jul 10, 18:20 UTCJul 10, 18:30 UTC10m
2026-07-10 N384ME SQL → SQL Jul 10, 16:50 UTCJul 10, 17:05 UTC15m
2026-07-09 N384ME SQL → SQL Jul 9, 21:25 UTCJul 9, 22:20 UTC55m
2026-07-08 N384ME SQL → SQL Jul 8, 22:05 UTCJul 8, 22:20 UTC15m
2026-07-08 N384ME SQL → SQL Jul 8, 20:40 UTCJul 8, 21:50 UTC1h 10m
2026-07-07 N384ME SQL → SQL Jul 7, 22:35 UTCJul 7, 22:55 UTC20m
2026-07-07 N384ME - Jul 7, 22:20 UTCJul 7, 22:30 UTC10m
2026-07-07 N384ME SQL → SQL Jul 7, 21:55 UTCJul 7, 22:10 UTC15m
2026-07-07 N384ME SQL → SQL Jul 7, 21:40 UTCJul 7, 21:50 UTC10m
2026-07-07 N384ME SQL → SQL Jul 7, 21:15 UTCJul 7, 21:25 UTC10m
2026-07-07 N384ME SQL → SQL Jul 7, 21:05 UTCJul 7, 21:10 UTC5m
2026-07-07 N384ME SQL → SQL Jul 7, 01:15 UTCJul 7, 01:45 UTC30m
2026-07-05 N384ME - Jul 5, 22:05 UTCJul 5, 23:05 UTC1h 0m
2026-07-05 N384ME SQL → WVI Jul 5, 21:05 UTCJul 5, 21:35 UTC30m
2026-07-04 N384ME SQL → SQL Jul 4, 22:35 UTCJul 4, 22:45 UTC10m
2026-07-04 N384ME SQL → SQL Jul 4, 21:25 UTCJul 4, 22:30 UTC1h 5m
2026-07-04 N384ME SQL → SQL Jul 4, 19:10 UTCJul 4, 20:00 UTC50m
2026-07-04 N384ME SQL → SQL Jul 4, 01:15 UTCJul 4, 02:20 UTC1h 5m
2026-07-03 N384ME SQL → SQL Jul 3, 23:15 UTCJul 3, 23:50 UTC35m
2026-07-03 N384ME - Jul 3, 19:50 UTCJul 3, 20:40 UTC50m
2026-07-03 N384ME SQL → SQL Jul 3, 19:10 UTCJul 3, 19:30 UTC20m
2026-07-02 N384ME SQL → SQL Jul 2, 19:10 UTCJul 2, 20:05 UTC55m
2026-07-01 N384ME SQL → SQL Jul 1, 15:10 UTCJul 1, 15:50 UTC40m
2026-07-01 N384ME SQL → SQL Jul 1, 14:55 UTCJul 1, 15:00 UTC5m
2026-06-30 N384ME SQL → SQL Jun 30, 17:55 UTCJun 30, 18:55 UTC1h 0m
2026-06-30 N384ME SQL → SQL Jun 30, 00:45 UTCJun 30, 01:50 UTC1h 5m
2026-06-29 N384ME SQL → SQL Jun 29, 19:44 UTCJun 29, 20:30 UTC45m
2026-06-29 N384ME SQL → SQL Jun 29, 19:20 UTCJun 29, 19:39 UTC20m
2026-06-29 N384ME SQL → SQL Jun 29, 19:09 UTCJun 29, 19:15 UTC5m
2026-06-28 N384ME SQL → SQL Jun 28, 18:05 UTCJun 28, 18:49 UTC45m
2026-06-25 N384ME SQL → SQL Jun 25, 00:09 UTCJun 25, 00:35 UTC25m
2026-06-24 N384ME - Jun 24, 19:10 UTCJun 24, 19:49 UTC40m
2026-06-24 N384ME SQL → SQL Jun 24, 18:55 UTCJun 24, 19:04 UTC10m
2026-06-24 N384ME SQL → SQL Jun 24, 18:34 UTCJun 24, 18:39 UTC5m
2026-06-24 N384ME SQL → SQL Jun 24, 02:15 UTCJun 24, 03:00 UTC45m
2026-06-23 N384ME PAO → SQL Jun 23, 03:29 UTCJun 23, 03:54 UTC25m
2026-06-23 N384ME SQL → SQL Jun 23, 01:54 UTCJun 23, 02:29 UTC35m
2026-06-22 N384ME PAO → SQL Jun 22, 17:34 UTCJun 22, 17:50 UTC15m
2026-06-22 N384ME SQL → PAO Jun 22, 14:59 UTCJun 22, 15:10 UTC10m

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 1h 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.