sensors Mode-S transponder

A39173

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N329TL · BOMBARDIER CL-600 Challenger · operated by BLUE SPRUCE SEVEN LLC

Hex
A39173
Octal
50710563
Decimal
10,719,603
Country
US
Tail
N329TL
Type
CL60
No current signal · last broadcast 1d ago
Flights observed
60
Distinct callsigns
1
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S A39173.

Country allocation

The ICAO 24-bit address A39173 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
JTL329 - 60 2026-07-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 JTL329 - Jul 13, 02:50 UTCJul 13, 03:05 UTC15m
2026-07-13 JTL329 - Jul 13, 00:05 UTCJul 13, 01:30 UTC1h 25m
2026-07-10 JTL329 - Jul 10, 19:35 UTCJul 10, 21:20 UTC1h 45m
2026-07-10 JTL329 - Jul 10, 17:15 UTCJul 10, 17:30 UTC15m
2026-07-08 JTL329 BFI → DAL Jul 8, 00:55 UTCJul 8, 04:10 UTC3h 15m
2026-07-07 JTL329 - Jul 7, 17:15 UTCJul 7, 20:55 UTC3h 40m
2026-07-05 JTL329 - Jul 5, 17:15 UTCJul 5, 18:05 UTC50m
2026-07-02 JTL329 - Jul 2, 15:15 UTCJul 2, 16:00 UTC45m
2026-06-23 JTL329 - Jun 23, 17:39 UTCJun 23, 18:39 UTC1h 0m
2026-06-22 JTL329 - Jun 22, 22:05 UTCJun 23, 01:00 UTC2h 55m
2026-06-22 JTL329 - Jun 22, 17:34 UTCJun 22, 20:34 UTC3h 0m
2026-06-21 JTL329 - Jun 21, 18:00 UTCJun 21, 19:55 UTC1h 55m
2026-06-21 JTL329 - Jun 21, 13:20 UTCJun 21, 15:05 UTC1h 45m
2026-06-20 JTL329 - Jun 20, 17:29 UTCJun 20, 18:04 UTC35m
2026-06-20 JTL329 - Jun 20, 11:34 UTCJun 20, 12:04 UTC30m
2026-06-19 JTL329 - Jun 19, 20:34 UTCJun 19, 23:14 UTC2h 40m
2026-06-19 JTL329 - Jun 19, 16:44 UTCJun 19, 19:29 UTC2h 45m
2026-06-18 JTL329 DFW → DAL Jun 18, 22:30 UTCJun 18, 22:40 UTC10m
2026-06-18 JTL329 - Jun 18, 19:25 UTCJun 18, 21:30 UTC2h 5m
2026-06-18 JTL329 - Jun 18, 11:55 UTCJun 18, 13:40 UTC1h 45m
2026-06-17 JTL329 - Jun 17, 20:30 UTCJun 17, 21:00 UTC30m
2026-06-14 JTL329 - Jun 14, 19:50 UTCJun 14, 22:25 UTC2h 35m
2026-06-12 JTL329 FTW → TEB Jun 12, 20:40 UTCJun 12, 22:10 UTC1h 30m
2026-06-12 JTL329 FTW → TEB Jun 12, 15:30 UTCJun 12, 16:55 UTC1h 25m
2026-06-11 JTL329 FTW → TEB Jun 11, 18:25 UTCJun 11, 21:10 UTC2h 45m
2026-06-05 JTL329 FTW → TEB Jun 5, 23:30 UTCJun 6, 01:40 UTC2h 10m
2026-06-05 JTL329 FTW → TEB Jun 5, 18:50 UTCJun 5, 20:40 UTC1h 50m
2026-05-26 JTL329 FTW → TEB May 26, 22:29 UTCMay 27, 00:30 UTC2h 0m
2026-05-26 JTL329 FTW → TEB May 26, 18:24 UTCMay 26, 19:25 UTC1h 0m
2026-05-25 JTL329 FTW → TEB May 25, 22:05 UTCMay 26, 01:20 UTC3h 15m
2026-05-22 JTL329 FTW → TEB May 22, 01:15 UTCMay 22, 04:10 UTC2h 55m
2026-05-21 JTL329 FTW → TEB May 21, 20:10 UTCMay 21, 21:40 UTC1h 30m
2026-05-20 JTL329 FTW → TEB May 20, 21:15 UTCMay 20, 22:10 UTC55m
2026-05-20 JTL329 FTW → TEB May 20, 16:20 UTCMay 20, 20:00 UTC3h 40m
2026-05-20 JTL329 FTW → TEB May 20, 13:15 UTCMay 20, 14:35 UTC1h 20m
2026-05-17 JTL329 FTW → TEB May 17, 19:50 UTCMay 17, 21:45 UTC1h 55m
2026-05-15 JTL329 FTW → TEB May 15, 19:35 UTCMay 15, 21:30 UTC1h 55m
2026-05-11 JTL329 FTW → TEB May 11, 01:15 UTCMay 11, 03:30 UTC2h 15m
2026-05-08 JTL329 FTW → TEB May 8, 15:00 UTCMay 8, 16:40 UTC1h 40m
2026-05-03 JTL329 FTW → TEB May 3, 21:05 UTCMay 3, 22:49 UTC1h 45m
2026-05-03 JTL329 FTW → TEB May 3, 18:25 UTCMay 3, 19:10 UTC45m
2026-05-02 JTL329 FTW → TEB May 2, 20:50 UTCMay 2, 22:40 UTC1h 50m
2026-05-01 JTL329 FTW → TEB May 1, 17:00 UTCMay 1, 19:40 UTC2h 40m
2026-04-30 JTL329 FTW → TEB Apr 30, 22:50 UTCMay 1, 19:40 UTC20h 50m
2026-04-30 JTL329 FTW → TEB Apr 30, 22:05 UTCMay 1, 19:40 UTC21h 35m
2026-04-30 JTL329 FTW → TEB Apr 30, 18:35 UTCApr 30, 20:10 UTC1h 35m
2026-04-24 JTL329 FTW → TEB Apr 24, 20:00 UTCApr 24, 21:10 UTC1h 10m
2026-04-23 JTL329 FTW → TEB Apr 23, 16:05 UTCApr 23, 19:35 UTC3h 30m
2026-04-21 JTL329 FTW → TEB Apr 21, 16:40 UTCApr 21, 18:50 UTC2h 10m
2026-04-20 JTL329 FTW → TEB Apr 20, 19:05 UTCApr 20, 22:35 UTC3h 30m

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

Mode-S A39173 frequently asked

What is Mode-S code A39173?
A39173 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N329TL.
Where is Mode-S A39173 registered?
Mode-S code A39173 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 A39173 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 A39173, octal 50710563, decimal 10,719,603.
What flights does A39173 operate?
Mode-S A39173 has broadcast 1 distinct callsign, including JTL329.