Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A0030D

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N10HC · EMBRAER EMB-135 Legacy · operated by KBA LLC

Hex
A0030D
Octal
50001415
Decimal
10,486,541
Country
US
Tail
N10HC
Type
E35L
No current signal · last broadcast 9d ago
Flights observed
77
Distinct callsigns
1
Country
US
Last broadcast
9d ago

Last known position

Most recent position reported by Mode-S A0030D.

Country allocation

The ICAO 24-bit address A0030D 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
JTL10 - 77 2026-07-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-05 JTL10 - Jul 5, 18:35 UTCJul 5, 18:45 UTC10m
2026-07-05 JTL10 - Jul 5, 15:50 UTCJul 5, 17:55 UTC2h 5m
2026-07-04 JTL10 - Jul 4, 20:45 UTCJul 4, 21:40 UTC55m
2026-07-04 JTL10 - Jul 4, 18:40 UTCJul 4, 20:00 UTC1h 20m
2026-07-03 JTL10 - Jul 3, 18:45 UTCJul 3, 19:35 UTC50m
2026-07-02 JTL10 - Jul 2, 20:45 UTCJul 2, 21:15 UTC30m
2026-07-02 JTL10 - Jul 2, 18:30 UTCJul 2, 19:20 UTC50m
2026-07-01 JTL10 - Jul 1, 21:10 UTCJul 2, 00:40 UTC3h 30m
2026-07-01 JTL10 RST → BFI Jul 1, 17:05 UTCJul 1, 20:25 UTC3h 20m
2026-07-01 JTL10 - Jul 1, 14:10 UTCJul 1, 15:00 UTC50m
2026-06-28 JTL10 - Jun 28, 18:25 UTCJun 28, 19:34 UTC1h 10m
2026-06-27 JTL10 - Jun 27, 16:04 UTCJun 27, 17:04 UTC1h 0m
2026-06-25 JTL10 - Jun 25, 13:45 UTCJun 25, 14:50 UTC1h 5m
2026-06-24 JTL10 - Jun 24, 17:50 UTCJun 24, 18:50 UTC1h 0m
2026-06-22 JTL10 - Jun 22, 19:44 UTCJun 22, 20:24 UTC40m
2026-06-21 JTL10 TEB → MDW Jun 21, 19:34 UTCJun 21, 21:34 UTC2h 0m
2026-06-21 JTL10 - Jun 21, 15:34 UTCJun 21, 17:29 UTC1h 55m
2026-06-20 JTL10 - Jun 20, 17:59 UTCJun 20, 19:24 UTC1h 25m
2026-06-19 JTL10 - Jun 19, 19:49 UTCJun 19, 20:34 UTC45m
2026-06-18 JTL10 - Jun 18, 18:50 UTCJun 18, 19:10 UTC20m
2026-06-18 JTL10 - Jun 18, 14:05 UTCJun 18, 14:25 UTC20m
2026-06-18 JTL10 - Jun 18, 11:55 UTCJun 18, 12:40 UTC45m
2026-06-15 JTL10 - Jun 15, 19:20 UTCJun 15, 22:40 UTC3h 20m
2026-06-14 JTL10 - Jun 14, 17:50 UTCJun 14, 20:20 UTC2h 30m
2026-06-14 JTL10 - Jun 14, 14:55 UTCJun 14, 15:50 UTC55m
2026-06-12 JTL10 OPF → MRK Jun 12, 20:30 UTCJun 12, 21:00 UTC30m
2026-06-11 JTL10 OPF → MRK Jun 11, 19:35 UTCJun 11, 20:20 UTC45m
2026-06-10 JTL10 OPF → MRK Jun 10, 20:45 UTCJun 10, 21:10 UTC25m
2026-06-10 JTL10 OPF → MRK Jun 10, 18:20 UTCJun 10, 19:20 UTC1h 0m
2026-06-08 JTL10 OPF → MRK Jun 8, 22:55 UTCJun 8, 23:55 UTC1h 0m
2026-06-08 JTL10 OPF → MRK Jun 8, 18:05 UTCJun 8, 21:55 UTC3h 50m
2026-06-07 JTL10 OPF → MRK Jun 7, 16:00 UTCJun 7, 17:15 UTC1h 15m
2026-06-07 JTL10 OPF → MRK Jun 7, 12:50 UTCJun 7, 13:55 UTC1h 5m
2026-06-03 JTL10 OPF → MRK Jun 3, 18:40 UTCJun 3, 20:30 UTC1h 50m
2026-06-02 JTL10 OPF → MRK Jun 2, 18:35 UTCJun 2, 19:10 UTC35m
2026-06-02 JTL10 OPF → MRK Jun 2, 15:55 UTCJun 2, 17:45 UTC1h 50m
2026-06-01 JTL10 OPF → MRK Jun 1, 20:10 UTCJun 1, 20:25 UTC15m
2026-06-01 JTL10 OPF → MRK Jun 1, 00:00 UTCJun 1, 01:25 UTC1h 25m
2026-05-30 JTL10 OPF → MRK May 30, 19:00 UTCMay 30, 19:45 UTC45m
2026-05-30 JTL10 OPF → MRK May 30, 16:55 UTCMay 30, 18:10 UTC1h 15m
2026-05-30 JTL10 OPF → MRK May 30, 15:00 UTCMay 30, 15:25 UTC25m
2026-05-29 JTL10 OPF → MRK May 29, 12:20 UTCMay 29, 19:20 UTC7h 0m
2026-05-28 JTL10 OPF → MRK May 28, 16:45 UTCMay 28, 17:35 UTC50m
2026-05-28 JTL10 OPF → MRK May 28, 15:00 UTCMay 28, 15:45 UTC45m
2026-05-28 JTL10 OPF → MRK May 28, 11:10 UTCMay 28, 12:40 UTC1h 30m
2026-05-25 JTL10 OPF → MRK May 25, 22:44 UTCMay 25, 23:45 UTC1h 0m
2026-05-25 JTL10 OPF → MRK May 25, 20:45 UTCMay 25, 22:10 UTC1h 25m
2026-05-22 JTL10 OPF → MRK May 22, 13:45 UTCMay 22, 15:30 UTC1h 45m
2026-05-21 JTL10 OPF → MRK May 21, 17:40 UTCMay 21, 17:55 UTC15m
2026-05-21 JTL10 OPF → MRK May 21, 16:10 UTCMay 21, 17:00 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 N10HC page for operator, model, and routing details .

Mode-S A0030D frequently asked

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