sensors Mode-S transponder

A992DB

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N716FG · LEARJET 45 · operated by N716FG LLC

Hex
A992DB
Octal
52311333
Decimal
11,113,179
Country
US
Tail
N716FG
Type
LJ45
No current signal · last broadcast 12d ago
Flights observed
95
Distinct callsigns
2
Country
US
Last broadcast
12d ago

Last known position

Most recent position reported by Mode-S A992DB.

Country allocation

The ICAO 24-bit address A992DB 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
FSR716 - 90 2026-07-26
N716FG - 5 2026-06-03

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 FSR716 SBA → CMI Jul 26, 15:10 UTCJul 26, 18:55 UTC3h 45m
2026-07-24 FSR716 LAS → SBA Jul 24, 19:15 UTCJul 24, 20:05 UTC50m
2026-07-23 FSR716 CMI → LAS Jul 23, 15:35 UTCJul 23, 19:00 UTC3h 25m
2026-07-21 FSR716 - Jul 21, 02:50 UTCJul 21, 03:15 UTC25m
2026-07-20 FSR716 CMI → PWK Jul 20, 19:05 UTCJul 21, 02:15 UTC7h 9m
2026-07-20 FSR716 - Jul 20, 04:35 UTCJul 20, 08:45 UTC4h 10m
2026-07-20 FSR716 VNY → FTW Jul 20, 01:15 UTCJul 20, 04:00 UTC2h 45m
2026-07-17 FSR716 LNK → VNY Jul 17, 08:35 UTCJul 17, 11:15 UTC2h 40m
2026-07-17 FSR716 BOS → LNK Jul 17, 05:04 UTCJul 17, 08:04 UTC3h 0m
2026-07-15 FSR716 TEB → BOS Jul 15, 03:40 UTCJul 15, 04:25 UTC45m
2026-07-14 FSR716 - Jul 14, 23:35 UTCJul 15, 01:15 UTC1h 40m
2026-07-13 FSR716 - Jul 13, 07:20 UTCJul 13, 09:00 UTC1h 40m
2026-07-13 FSR716 - Jul 13, 04:45 UTCJul 13, 06:35 UTC1h 50m
2026-07-12 FSR716 - Jul 12, 06:01 UTCJul 12, 07:05 UTC1h 5m
2026-07-11 FSR716 MSP → ROA Jul 11, 07:05 UTCJul 11, 08:55 UTC1h 50m
2026-07-10 FSR716 - Jul 10, 04:30 UTCJul 10, 07:15 UTC2h 45m
2026-07-09 FSR716 - Jul 9, 06:20 UTCJul 9, 06:55 UTC35m
2026-07-08 FSR716 - Jul 8, 06:00 UTCJul 8, 06:30 UTC30m
2026-07-08 FSR716 - Jul 8, 03:10 UTCJul 8, 05:20 UTC2h 10m
2026-07-08 FSR716 - Jul 8, 00:00 UTCJul 8, 02:10 UTC2h 10m
2026-06-30 FSR716 SAN → BUR Jun 30, 00:09 UTCJun 30, 00:39 UTC30m
2026-06-29 FSR716 - Jun 29, 09:00 UTCJun 29, 10:00 UTC1h 0m
2026-06-28 FSR716 - Jun 28, 07:40 UTCJun 28, 09:10 UTC1h 30m
2026-06-27 FSR716 BUR → BFI Jun 27, 06:40 UTCJun 27, 08:49 UTC2h 10m
2026-06-25 FSR716 ABQ → BUR Jun 25, 06:44 UTCJun 25, 08:24 UTC1h 40m
2026-06-24 FSR716 - Jun 24, 04:10 UTCJun 24, 07:34 UTC3h 25m
2026-06-23 FSR716 - Jun 23, 21:39 UTCJun 23, 23:14 UTC1h 35m
2026-06-18 FSR716 RST → CMI Jun 18, 20:30 UTCJun 18, 21:20 UTC50m
2026-06-18 FSR716 - Jun 18, 19:15 UTCJun 18, 20:10 UTC55m
2026-06-17 FSR716 - Jun 17, 18:20 UTCJun 17, 19:50 UTC1h 30m
2026-06-17 FSR716 - Jun 17, 12:05 UTCJun 17, 13:20 UTC1h 15m
2026-06-16 FSR716 - Jun 16, 23:20 UTCJun 17, 00:55 UTC1h 35m
2026-06-16 FSR716 - Jun 16, 20:00 UTCJun 16, 20:35 UTC35m
2026-06-16 FSR716 - Jun 16, 17:00 UTCJun 16, 19:25 UTC2h 25m
2026-06-16 FSR716 - Jun 16, 13:55 UTCJun 16, 15:45 UTC1h 50m
2026-06-14 FSR716 - Jun 14, 17:40 UTCJun 14, 19:25 UTC1h 45m
2026-06-14 FSR716 - Jun 14, 15:10 UTCJun 14, 17:00 UTC1h 50m
2026-06-12 FSR716 - Jun 12, 17:00 UTCJun 12, 18:45 UTC1h 45m
2026-06-12 FSR716 - Jun 12, 13:55 UTCJun 12, 15:30 UTC1h 35m
2026-06-11 FSR716 - Jun 11, 19:20 UTCJun 11, 20:50 UTC1h 30m
2026-06-11 FSR716 - Jun 11, 17:25 UTCJun 11, 17:40 UTC15m
2026-06-10 FSR716 - Jun 10, 20:40 UTCJun 10, 21:15 UTC35m
2026-06-10 FSR716 - Jun 10, 17:55 UTCJun 10, 18:15 UTC20m
2026-06-08 FSR716 LNK → CMI Jun 8, 13:50 UTCJun 8, 14:50 UTC1h 0m
2026-06-05 FSR716 - Jun 5, 13:40 UTCJun 5, 14:45 UTC1h 5m
2026-06-03 N716FG - Jun 3, 20:00 UTCJun 3, 22:25 UTC2h 25m
2026-06-01 N716FG - Jun 1, 13:25 UTCJun 1, 14:50 UTC1h 25m
2026-06-01 N716FG - Jun 1, 12:05 UTCJun 1, 12:30 UTC25m
2026-05-28 N716FG - May 28, 02:00 UTCMay 28, 02:50 UTC50m
2026-05-27 N716FG - May 27, 20:25 UTCMay 27, 21:20 UTC55m

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

Mode-S A992DB frequently asked

What is Mode-S code A992DB?
A992DB is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N716FG.
Where is Mode-S A992DB registered?
Mode-S code A992DB 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 A992DB broadcasting right now?
No active broadcast right now. Last signal was 12d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A992DB, octal 52311333, decimal 11,113,179.
What flights does A992DB operate?
Mode-S A992DB has broadcast 2 distinct callsigns, including FSR716, N716FG.