sensors Mode-S transponder

A47303

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N386QS · EMBRAER EMB-505 Phenom 300 · operated by NETJETS SALES INC, PINTO FAMILY LLC, AEROEQUITY AIRCRAFT I LLC, LBA A T LLC

Hex
A47303
Octal
51071403
Decimal
10,777,347
Country
US
Tail
N386QS
Type
E55P
No current signal · last broadcast 1h ago
Flights observed
84
Distinct callsigns
2
Country
US
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S A47303.

Country allocation

The ICAO 24-bit address A47303 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 2 distinct

Callsign Airline Flights Last seen
EJA386 NetJets 79 2026-05-30
N386QS - 5 2026-05-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 EJA386 LAX → SDX May 30, 02:20 UTCMay 30, 03:50 UTC1h 30m
2026-05-30 EJA386 LAX → SDX May 30, 01:00 UTCMay 30, 01:10 UTC10m
2026-05-28 EJA386 LAX → SDX May 28, 19:00 UTCMay 28, 19:45 UTC45m
2026-05-28 EJA386 LAX → SDX May 28, 16:45 UTCMay 28, 17:25 UTC40m
2026-05-28 EJA386 LAX → SDX May 28, 12:50 UTCMay 28, 15:40 UTC2h 50m
2026-05-28 EJA386 LAX → SDX May 28, 10:25 UTCMay 28, 11:25 UTC1h 0m
2026-05-27 EJA386 LAX → SDX May 27, 18:45 UTCMay 27, 20:40 UTC1h 55m
2026-05-27 EJA386 LAX → SDX May 27, 16:35 UTCMay 27, 17:15 UTC40m
2026-05-27 EJA386 LAX → SDX May 27, 14:15 UTCMay 27, 15:40 UTC1h 25m
2026-05-27 EJA386 LAX → SDX May 27, 12:30 UTCMay 27, 12:55 UTC25m
2026-05-26 EJA386 LAX → SDX May 26, 16:50 UTCMay 26, 18:14 UTC1h 25m
2026-05-26 EJA386 LAX → SDX May 26, 15:20 UTCMay 26, 15:54 UTC35m
2026-05-26 EJA386 LAX → SDX May 26, 13:50 UTCMay 26, 14:24 UTC35m
2026-05-26 EJA386 LAX → SDX May 26, 10:25 UTCMay 26, 12:10 UTC1h 45m
2026-05-25 EJA386 LAX → SDX May 25, 23:40 UTCMay 26, 01:05 UTC1h 25m
2026-05-25 N386QS - May 25, 15:25 UTCMay 25, 21:19 UTC5h 54m
2026-05-24 EJA386 LAX → SDX May 24, 20:50 UTCMay 24, 21:45 UTC55m
2026-05-24 EJA386 LAX → SDX May 24, 18:35 UTCMay 24, 18:50 UTC15m
2026-05-24 EJA386 LAX → SDX May 24, 15:25 UTCMay 24, 16:45 UTC1h 20m
2026-05-21 EJA386 LAX → SDX May 21, 12:40 UTCMay 21, 12:55 UTC15m
2026-05-04 EJA386 LAX → SDX May 4, 00:15 UTCMay 4, 00:40 UTC25m
2026-05-03 EJA386 LAX → SDX May 3, 22:09 UTCMay 3, 23:30 UTC1h 20m
2026-05-03 EJA386 LAX → SDX May 3, 17:54 UTCMay 3, 19:10 UTC1h 15m
2026-05-03 EJA386 LAX → SDX May 3, 15:00 UTCMay 3, 16:45 UTC1h 45m
2026-05-02 EJA386 LAX → SDX May 2, 23:15 UTCMay 3, 00:20 UTC1h 5m
2026-05-02 EJA386 LAX → SDX May 2, 19:40 UTCMay 2, 22:05 UTC2h 25m
2026-05-02 EJA386 LAX → SDX May 2, 18:20 UTCMay 2, 18:30 UTC10m
2026-05-02 EJA386 LAX → SDX May 2, 16:20 UTCMay 2, 17:15 UTC55m
2026-05-02 EJA386 LAX → SDX May 2, 14:10 UTCMay 2, 15:00 UTC50m
2026-05-01 EJA386 LAX → SDX May 1, 14:25 UTCMay 1, 16:25 UTC2h 0m
2026-04-30 EJA386 LAX → SDX Apr 30, 22:20 UTCApr 30, 23:20 UTC1h 0m
2026-04-30 EJA386 LAX → SDX Apr 30, 20:05 UTCApr 30, 21:10 UTC1h 5m
2026-04-30 EJA386 LAX → SDX Apr 30, 16:40 UTCApr 30, 17:20 UTC40m
2026-04-30 EJA386 LAX → SDX Apr 30, 15:20 UTCApr 30, 15:55 UTC35m
2026-04-30 EJA386 LAX → SDX Apr 30, 15:10 UTCApr 30, 15:15 UTC5m
2026-04-29 EJA386 LAX → SDX Apr 29, 15:15 UTCApr 29, 17:15 UTC2h 0m
2026-04-29 EJA386 LAX → SDX Apr 29, 12:30 UTCApr 29, 13:25 UTC55m
2026-04-29 EJA386 LAX → SDX Apr 29, 10:50 UTCApr 29, 11:35 UTC45m
2026-04-28 EJA386 LAX → SDX Apr 28, 19:15 UTCApr 28, 20:20 UTC1h 5m
2026-04-28 EJA386 LAX → SDX Apr 28, 17:10 UTCApr 28, 18:10 UTC1h 0m
2026-04-28 EJA386 LAX → SDX Apr 28, 15:25 UTCApr 28, 15:45 UTC20m
2026-04-27 EJA386 LAX → SDX Apr 27, 13:45 UTCApr 27, 14:35 UTC50m
2026-04-26 EJA386 LAX → SDX Apr 26, 23:50 UTCApr 27, 00:40 UTC50m
2026-04-26 EJA386 LAX → SDX Apr 26, 21:10 UTCApr 26, 22:05 UTC55m
2026-04-26 EJA386 LAX → SDX Apr 26, 18:20 UTCApr 26, 19:25 UTC1h 5m
2026-04-26 EJA386 LAX → SDX Apr 26, 15:35 UTCApr 26, 16:15 UTC40m
2026-04-26 EJA386 LAX → SDX Apr 26, 14:05 UTCApr 26, 14:50 UTC45m
2026-04-23 EJA386 LAX → SDX Apr 23, 21:20 UTCApr 23, 22:15 UTC55m
2026-04-23 EJA386 LAX → SDX Apr 23, 18:40 UTCApr 23, 19:55 UTC1h 15m
2026-04-23 EJA386 LAX → SDX Apr 23, 16:50 UTCApr 23, 17:40 UTC49m

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

Mode-S A47303 frequently asked

What is Mode-S code A47303?
A47303 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N386QS.
Where is Mode-S A47303 registered?
Mode-S code A47303 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 A47303 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 A47303, octal 51071403, decimal 10,777,347.
What flights does A47303 operate?
Mode-S A47303 has broadcast 2 distinct callsigns, including EJA386, N386QS.