sensors Mode-S transponder

A355AB

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N31399 · PIPER PA-28-140/150/160/180 · operated by G&M AIRCRAFT INC

Hex
A355AB
Octal
50652653
Decimal
10,704,299
Country
US
Tail
N31399
Type
P28A
No current signal · last broadcast 8h ago
Flights observed
51
Distinct callsigns
1
Country
US
Last broadcast
8h ago

Last known position

Most recent position reported by Mode-S A355AB.

Country allocation

The ICAO 24-bit address A355AB 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
N31399 - 51 2026-07-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 N31399 BJC → BJC Jul 13, 23:45 UTCJul 14, 01:00 UTC1h 15m
2026-07-13 N31399 - Jul 13, 11:45 UTCJul 13, 13:25 UTC1h 40m
2026-07-12 N31399 BJC → BJC Jul 12, 13:50 UTCJul 12, 17:01 UTC3h 10m
2026-07-12 N31399 - Jul 12, 00:25 UTCJul 12, 01:50 UTC1h 25m
2026-07-11 N31399 BJC → BJC Jul 11, 18:25 UTCJul 11, 19:45 UTC1h 20m
2026-07-11 N31399 - Jul 11, 16:20 UTCJul 11, 16:55 UTC35m
2026-07-11 N31399 BJC → GXY Jul 11, 14:50 UTCJul 11, 15:25 UTC35m
2026-07-11 N31399 BJC → BJC Jul 11, 04:20 UTCJul 11, 04:35 UTC15m
2026-07-10 N31399 BJC → BJC Jul 10, 18:55 UTCJul 10, 21:00 UTC2h 5m
2026-07-10 N31399 BJC → BJC Jul 10, 11:20 UTCJul 10, 12:05 UTC45m
2026-07-08 N31399 - Jul 8, 15:45 UTCJul 8, 17:20 UTC1h 35m
2026-07-08 N31399 BJC → BJC Jul 8, 13:25 UTCJul 8, 14:55 UTC1h 30m
2026-07-08 N31399 - Jul 8, 01:20 UTCJul 8, 02:20 UTC1h 0m
2026-07-07 N31399 BJC → BJC Jul 7, 15:15 UTCJul 7, 15:55 UTC40m
2026-07-07 N31399 BJC → BJC Jul 7, 12:10 UTCJul 7, 14:00 UTC1h 50m
2026-07-06 N31399 BJC → BJC Jul 6, 12:05 UTCJul 6, 13:50 UTC1h 45m
2026-07-06 N31399 BJC → BJC Jul 6, 00:00 UTCJul 6, 01:30 UTC1h 30m
2026-07-05 N31399 BJC → BJC Jul 5, 16:05 UTCJul 5, 17:50 UTC1h 45m
2026-07-04 N31399 BJC → BJC Jul 4, 14:00 UTCJul 4, 15:45 UTC1h 45m
2026-07-03 N31399 - Jul 3, 19:40 UTCJul 3, 21:05 UTC1h 25m
2026-07-03 N31399 BJC → BJC Jul 3, 17:05 UTCJul 3, 18:30 UTC1h 25m
2026-07-03 N31399 BJC → BJC Jul 3, 14:40 UTCJul 3, 15:45 UTC1h 5m
2026-07-03 N31399 BJC → BJC Jul 3, 00:20 UTCJul 3, 02:00 UTC1h 40m
2026-07-02 N31399 BJC → BJC Jul 2, 17:55 UTCJul 2, 19:00 UTC1h 5m
2026-07-02 N31399 BJC → BJC Jul 2, 14:20 UTCJul 2, 16:00 UTC1h 40m
2026-07-02 N31399 BJC → BJC Jul 2, 03:35 UTCJul 2, 03:45 UTC10m
2026-07-01 N31399 BJC → BJC Jul 1, 18:45 UTCJul 1, 20:20 UTC1h 35m
2026-07-01 N31399 - Jul 1, 12:20 UTCJul 1, 12:55 UTC35m
2026-07-01 N31399 - Jul 1, 05:00 UTCJul 1, 07:50 UTC2h 50m
2026-07-01 N31399 - Jul 1, 02:40 UTCJul 1, 04:30 UTC1h 50m
2026-06-30 N31399 BJC → BJC Jun 30, 20:00 UTCJun 30, 21:50 UTC1h 50m
2026-06-30 N31399 BJC → BJC Jun 30, 17:10 UTCJun 30, 18:45 UTC1h 35m
2026-06-30 N31399 - Jun 30, 15:30 UTCJun 30, 15:50 UTC20m
2026-06-30 N31399 - Jun 30, 14:50 UTCJun 30, 15:25 UTC35m
2026-06-30 N31399 BJC → BJC Jun 30, 11:25 UTCJun 30, 12:15 UTC50m
2026-06-29 N31399 BJC → BJC Jun 29, 15:45 UTCJun 29, 17:34 UTC1h 50m
2026-06-29 N31399 BJC → BJC Jun 29, 00:24 UTCJun 29, 02:00 UTC1h 35m
2026-06-28 N31399 BJC → BJC Jun 28, 18:05 UTCJun 28, 19:34 UTC1h 30m
2026-06-28 N31399 BJC → BJC Jun 28, 14:59 UTCJun 28, 16:09 UTC1h 10m
2026-06-28 N31399 BJC → BJC Jun 28, 11:45 UTCJun 28, 13:34 UTC1h 50m
2026-06-27 N31399 BJC → BJC Jun 27, 18:35 UTCJun 27, 18:45 UTC10m
2026-06-27 N31399 BJC → BJC Jun 27, 14:00 UTCJun 27, 15:05 UTC1h 5m
2026-06-27 N31399 - Jun 27, 00:34 UTCJun 27, 01:24 UTC50m
2026-06-26 N31399 BJC → BJC Jun 26, 17:35 UTCJun 26, 18:44 UTC1h 10m
2026-06-26 N31399 - Jun 26, 15:20 UTCJun 26, 16:54 UTC1h 35m
2026-06-26 N31399 BJC → BJC Jun 26, 11:49 UTCJun 26, 13:10 UTC1h 20m
2026-06-24 N31399 BJC → BJC Jun 24, 14:29 UTCJun 24, 16:14 UTC1h 45m
2026-06-23 N31399 BJC → BJC Jun 23, 16:54 UTCJun 23, 17:30 UTC35m
2026-06-23 N31399 BJC → BJC Jun 23, 11:49 UTCJun 23, 12:05 UTC15m
2026-06-10 N31399 BJC → BJC Jun 10, 11:45 UTCJun 10, 12:15 UTC30m

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

Mode-S A355AB frequently asked

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