sensors Mode-S transponder

AD8F18

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N973DC · operated by CBG LLC

Hex
AD8F18
Octal
53307430
Decimal
11,374,360
Country
US
Tail
N973DC
Type
E145
No current signal · last broadcast 13d ago
Flights observed
346
Distinct callsigns
20
Country
US
Last broadcast
13d ago

Last known position

Most recent position reported by Mode-S AD8F18.

Country allocation

The ICAO 24-bit address AD8F18 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 20 distinct

Callsign Airline Flights Last seen
LYM5730 - 37 2026-06-30
LYM3914 - 37 2026-06-28
LYM3912 - 36 2026-06-28
LYM5872 Key Lime Air 32 2026-06-29
LYM5880 - 31 2026-06-29
LYM5745 - 30 2026-06-29
LYM5882 - 29 2026-06-28
LYM5870 - 28 2026-06-29
LYM5775 - 24 2026-06-29
LYM5760 - 19 2026-06-29
LYM5110 Key Lime Air 7 2026-04-28
LYM5107 Key Lime Air 7 2026-04-29
LYM5111 Key Lime Air 6 2026-04-29
LYM5115 Key Lime Air 5 2026-04-28
LYM825 Key Lime Air 3 2026-05-25
LYM5120 Key Lime Air 2 2026-04-24
LYM5112 Key Lime Air 2 2026-04-24
LYM733 Key Lime Air 1 2026-06-05
LYM602 Key Lime Air 1 2026-05-24
LYM5799 Key Lime Air 1 2026-06-09

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-30 LYM288 GEG → OAK Jun 30, 14:50 UTCJun 30, 17:00 UTC2h 10m
2026-06-30 LYM5730 - Jun 30, 12:30 UTCJun 30, 13:10 UTC40m
2026-06-29 LYM5775 - Jun 29, 23:44 UTCJun 30, 00:09 UTC25m
2026-06-29 LYM5760 - Jun 29, 21:24 UTCJun 29, 21:54 UTC30m
2026-06-29 LYM5745 ORD → MKG Jun 29, 19:39 UTCJun 29, 20:09 UTC30m
2026-06-29 LYM5880 - Jun 29, 16:29 UTCJun 29, 17:55 UTC1h 25m
2026-06-29 LYM5872 ATL → MKL Jun 29, 15:00 UTCJun 29, 15:45 UTC45m
2026-06-29 LYM5870 - Jun 29, 13:04 UTCJun 29, 13:54 UTC50m
2026-06-28 LYM5882 - Jun 28, 22:20 UTCJun 28, 23:25 UTC1h 5m
2026-06-28 LYM3914 - Jun 28, 20:09 UTCJun 28, 21:04 UTC55m
2026-06-28 LYM3912 - Jun 28, 18:10 UTCJun 28, 18:59 UTC50m
2026-06-28 LYM5730 - Jun 28, 12:29 UTCJun 28, 13:04 UTC35m
2026-06-27 LYM5745 ORD → MKG Jun 27, 19:29 UTCJun 27, 19:55 UTC25m
2026-06-27 LYM5880 - Jun 27, 16:39 UTCJun 27, 17:59 UTC1h 20m
2026-06-27 LYM5872 ATL → MKL Jun 27, 15:05 UTCJun 27, 15:49 UTC45m
2026-06-27 LYM5870 - Jun 27, 13:20 UTCJun 27, 14:09 UTC50m
2026-06-26 LYM5882 - Jun 26, 22:19 UTCJun 26, 23:30 UTC1h 10m
2026-06-26 LYM3914 - Jun 26, 20:00 UTCJun 26, 20:50 UTC50m
2026-06-26 LYM3912 - Jun 26, 18:04 UTCJun 26, 18:44 UTC40m
2026-06-26 LYM5730 - Jun 26, 12:24 UTCJun 26, 12:55 UTC30m
2026-06-25 LYM5745 ORD → MKG Jun 25, 22:59 UTCJun 25, 23:30 UTC30m
2026-06-25 LYM3914 - Jun 25, 20:05 UTCJun 25, 20:54 UTC50m
2026-06-25 LYM3912 ORD → ARV Jun 25, 18:24 UTCJun 25, 19:05 UTC40m
2026-06-25 LYM5730 MKG → ORD Jun 25, 12:44 UTCJun 25, 13:14 UTC30m
2026-06-25 LYM5775 ORD → MKG Jun 25, 01:04 UTCJun 25, 01:24 UTC20m
2026-06-24 LYM5760 - Jun 24, 21:40 UTCJun 24, 22:10 UTC30m
2026-06-24 LYM5745 ORD → MKG Jun 24, 20:24 UTCJun 24, 20:54 UTC30m
2026-06-23 LYM5880 - Jun 23, 17:20 UTCJun 23, 18:39 UTC1h 20m
2026-06-23 LYM5872 ATL → MKL Jun 23, 15:40 UTCJun 23, 16:29 UTC50m
2026-06-23 LYM5870 - Jun 23, 13:15 UTCJun 23, 13:59 UTC45m
2026-06-22 LYM5882 - Jun 22, 21:45 UTCJun 22, 22:44 UTC1h 0m
2026-06-22 LYM3914 - Jun 22, 19:54 UTCJun 22, 20:55 UTC1h 0m
2026-06-22 LYM3912 - Jun 22, 18:04 UTCJun 22, 18:44 UTC40m
2026-06-22 LYM5730 - Jun 22, 12:34 UTCJun 22, 13:10 UTC35m
2026-06-21 LYM5775 - Jun 21, 23:24 UTCJun 21, 23:50 UTC25m
2026-06-21 LYM5760 - Jun 21, 21:19 UTCJun 21, 22:00 UTC40m
2026-06-21 LYM5745 ORD → MKG Jun 21, 20:05 UTCJun 21, 20:34 UTC30m
2026-06-21 LYM5880 - Jun 21, 17:20 UTCJun 21, 18:50 UTC1h 30m
2026-06-21 LYM5872 ATL → MKL Jun 21, 15:34 UTCJun 21, 16:25 UTC50m
2026-06-21 LYM5870 - Jun 21, 13:09 UTCJun 21, 14:05 UTC55m
2026-06-20 LYM5882 - Jun 20, 22:05 UTCJun 20, 22:59 UTC55m
2026-06-20 LYM5730 - Jun 20, 12:24 UTCJun 20, 12:59 UTC35m
2026-06-19 LYM5775 - Jun 19, 22:49 UTCJun 19, 23:14 UTC25m
2026-06-19 LYM5760 - Jun 19, 21:24 UTCJun 19, 21:59 UTC35m
2026-06-19 LYM5745 - Jun 19, 19:39 UTCJun 19, 20:04 UTC25m
2026-06-19 LYM5880 - Jun 19, 16:44 UTCJun 19, 18:05 UTC1h 20m
2026-06-19 LYM5872 ATL → MKL Jun 19, 15:14 UTCJun 19, 15:59 UTC45m
2026-06-19 LYM5870 - Jun 19, 13:14 UTCJun 19, 13:59 UTC45m
2026-06-18 LYM5882 - Jun 18, 22:50 UTCJun 18, 23:55 UTC1h 5m
2026-06-18 LYM3914 - Jun 18, 21:00 UTCJun 18, 21:50 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 N973DC page for operator, model, and routing details .

Mode-S AD8F18 frequently asked

What is Mode-S code AD8F18?
AD8F18 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N973DC.
Where is Mode-S AD8F18 registered?
Mode-S code AD8F18 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 AD8F18 broadcasting right now?
No active broadcast right now. Last signal was 13d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AD8F18, octal 53307430, decimal 11,374,360.
What flights does AD8F18 operate?
Mode-S AD8F18 has broadcast 20 distinct callsigns, including LYM5730, LYM3914, LYM3912, LYM5872, LYM5880.