Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

ADBB9E

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N984SP · CESSNA 172 Skyhawk · operated by REDSTONE ARSENAL FLYING ACTIVITY

Hex
ADBB9E
Octal
53335636
Decimal
11,385,758
Country
US
Tail
N984SP
Type
C172
No current signal · last broadcast 4d ago
Flights observed
146
Distinct callsigns
1
Country
US
Last broadcast
4d ago

Last known position

Most recent position reported by Mode-S ADBB9E.

Country allocation

The ICAO 24-bit address ADBB9E 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
N984SP - 146 2026-07-10

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-10 N984SP HUA → HUA Jul 10, 14:05 UTCJul 10, 14:50 UTC45m
2026-07-10 N984SP HUA → HUA Jul 10, 11:45 UTCJul 10, 12:10 UTC25m
2026-07-08 N984SP HUA → HUA Jul 8, 17:50 UTCJul 8, 18:35 UTC45m
2026-07-06 N984SP - Jul 6, 01:20 UTCJul 6, 02:10 UTC50m
2026-07-05 N984SP - Jul 5, 23:45 UTCJul 6, 00:05 UTC20m
2026-07-05 N984SP - Jul 5, 19:35 UTCJul 5, 21:20 UTC1h 45m
2026-07-05 N984SP - Jul 5, 18:40 UTCJul 5, 19:00 UTC20m
2026-07-03 N984SP - Jul 3, 18:45 UTCJul 3, 19:00 UTC15m
2026-07-03 N984SP - Jul 3, 17:40 UTCJul 3, 17:50 UTC10m
2026-07-03 N984SP - Jul 3, 16:00 UTCJul 3, 16:25 UTC25m
2026-07-03 N984SP - Jul 3, 14:30 UTCJul 3, 15:30 UTC1h 0m
2026-07-02 N984SP - Jul 2, 15:30 UTCJul 2, 16:45 UTC1h 15m
2026-07-01 N984SP HUA → HUA Jul 1, 13:00 UTCJul 1, 14:00 UTC1h 0m
2026-06-30 N984SP - Jun 30, 22:25 UTCJun 30, 23:30 UTC1h 5m
2026-06-30 N984SP HUA → HUA Jun 30, 15:10 UTCJun 30, 16:10 UTC1h 0m
2026-06-29 N984SP - Jun 29, 23:54 UTCJun 30, 01:55 UTC2h 1m
2026-06-29 N984SP - Jun 29, 16:04 UTCJun 29, 16:25 UTC20m
2026-06-29 N984SP - Jun 29, 15:09 UTCJun 29, 15:30 UTC20m
2026-06-28 N984SP HUA → HUA Jun 28, 14:54 UTCJun 28, 15:49 UTC55m
2026-06-26 N984SP - Jun 26, 15:10 UTCJun 26, 16:24 UTC1h 15m
2026-06-25 N984SP HUA → HUA Jun 25, 16:05 UTCJun 25, 17:20 UTC1h 15m
2026-06-24 N984SP - Jun 24, 15:35 UTCJun 24, 16:54 UTC1h 20m
2026-06-24 N984SP - Jun 24, 13:10 UTCJun 24, 14:20 UTC1h 10m
2026-06-23 N984SP HUA → HUA Jun 23, 21:14 UTCJun 23, 21:54 UTC40m
2026-06-19 N984SP - Jun 19, 22:39 UTCJun 19, 23:54 UTC1h 15m
2026-06-19 N984SP - Jun 19, 17:59 UTCJun 19, 18:20 UTC20m
2026-06-19 N984SP - Jun 19, 17:04 UTCJun 19, 17:19 UTC15m
2026-06-19 N984SP - Jun 19, 13:59 UTCJun 19, 15:59 UTC2h 0m
2026-06-17 N984SP - Jun 17, 18:40 UTCJun 17, 19:25 UTC45m
2026-06-17 N984SP - Jun 17, 15:50 UTCJun 17, 17:00 UTC1h 10m
2026-06-16 N984SP HUA → HUA Jun 16, 22:25 UTCJun 17, 00:25 UTC2h 0m
2026-06-16 N984SP HUA → HUA Jun 16, 18:05 UTCJun 16, 19:15 UTC1h 10m
2026-06-16 N984SP HUA → HUA Jun 16, 13:04 UTCJun 16, 14:05 UTC1h 0m
2026-06-16 N984SP - Jun 16, 00:15 UTCJun 16, 01:19 UTC1h 5m
2026-06-15 N984SP HUA → HUA Jun 15, 14:55 UTCJun 15, 16:04 UTC1h 10m
2026-06-13 N984SP - Jun 13, 20:05 UTCJun 13, 20:40 UTC35m
2026-06-13 N984SP - Jun 13, 18:25 UTCJun 13, 19:20 UTC55m
2026-06-13 N984SP HUA → HUA Jun 13, 16:20 UTCJun 13, 17:30 UTC1h 10m
2026-06-13 N984SP - Jun 13, 13:05 UTCJun 13, 15:25 UTC2h 20m
2026-06-12 N984SP - Jun 12, 15:00 UTCJun 12, 15:40 UTC40m
2026-06-12 N984SP HUA → HUA Jun 12, 00:40 UTCJun 12, 01:45 UTC1h 5m
2026-06-11 N984SP - Jun 11, 23:10 UTCJun 11, 23:20 UTC10m
2026-06-11 N984SP - Jun 11, 21:00 UTCJun 11, 22:00 UTC1h 0m
2026-06-11 N984SP - Jun 11, 17:25 UTCJun 11, 17:40 UTC15m
2026-06-11 N984SP - Jun 11, 13:45 UTCJun 11, 15:10 UTC1h 25m
2026-06-10 N984SP - Jun 10, 21:00 UTCJun 10, 22:00 UTC1h 0m
2026-06-10 N984SP HUA → HUA Jun 10, 18:05 UTCJun 10, 18:50 UTC45m
2026-06-10 N984SP - Jun 10, 14:55 UTCJun 10, 15:45 UTC50m
2026-06-10 N984SP - Jun 10, 00:10 UTCJun 10, 00:40 UTC30m
2026-06-09 N984SP - Jun 9, 23:15 UTCJun 9, 23:30 UTC15m

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

Mode-S ADBB9E frequently asked

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