Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A2DED1

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N284WF · operated by AIMS COMMUNITY COLLEGE

Hex
A2DED1
Octal
50557321
Decimal
10,673,873
Country
US
Tail
N284WF
Type
P28A
No current signal · last broadcast 4h ago
Flights observed
192
Distinct callsigns
1
Country
US
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S A2DED1.

Country allocation

The ICAO 24-bit address A2DED1 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
RTY284 - 192 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 RTY284 FNL → FNL Jul 14, 14:05 UTCJul 14, 15:05 UTC1h 0m
2026-07-13 RTY284 FNL → FNL Jul 13, 17:30 UTCJul 13, 19:20 UTC1h 50m
2026-07-13 RTY284 - Jul 13, 14:15 UTCJul 13, 14:45 UTC30m
2026-07-13 RTY284 - Jul 13, 13:05 UTCJul 13, 13:35 UTC30m
2026-07-12 RTY284 FNL → FNL Jul 12, 19:20 UTCJul 12, 20:40 UTC1h 20m
2026-07-12 RTY284 FNL → FNL Jul 12, 15:15 UTCJul 12, 18:15 UTC3h 0m
2026-07-11 RTY284 FNL → FNL Jul 11, 19:30 UTCJul 11, 20:50 UTC1h 20m
2026-07-10 RTY284 FNL → FNL Jul 10, 17:45 UTCJul 10, 19:10 UTC1h 25m
2026-07-10 RTY284 FNL → FNL Jul 10, 15:10 UTCJul 10, 16:05 UTC55m
2026-07-09 RTY284 FNL → FNL Jul 9, 16:30 UTCJul 9, 17:45 UTC1h 15m
2026-07-09 RTY284 FNL → FNL Jul 9, 14:30 UTCJul 9, 15:40 UTC1h 10m
2026-07-07 RTY284 - Jul 7, 16:40 UTCJul 7, 17:45 UTC1h 5m
2026-07-07 RTY284 FNL → FNL Jul 7, 14:30 UTCJul 7, 15:50 UTC1h 20m
2026-07-06 RTY284 FNL → FNL Jul 6, 16:55 UTCJul 6, 19:40 UTC2h 45m
2026-07-06 RTY284 FNL → FNL Jul 6, 13:30 UTCJul 6, 15:20 UTC1h 50m
2026-07-01 RTY284 FNL → FNL Jul 1, 20:35 UTCJul 1, 22:05 UTC1h 30m
2026-07-01 RTY284 FNL → FNL Jul 1, 17:40 UTCJul 1, 19:05 UTC1h 25m
2026-07-01 RTY284 - Jul 1, 15:50 UTCJul 1, 16:25 UTC35m
2026-07-01 RTY284 - Jul 1, 13:00 UTCJul 1, 14:25 UTC1h 25m
2026-06-30 RTY284 FNL → FNL Jun 30, 13:30 UTCJun 30, 14:40 UTC1h 10m
2026-06-29 RTY284 - Jun 29, 16:50 UTCJun 29, 17:30 UTC40m
2026-06-29 RTY284 - Jun 29, 12:49 UTCJun 29, 13:30 UTC40m
2026-06-28 RTY284 FNL → FNL Jun 28, 20:19 UTCJun 28, 21:20 UTC1h 0m
2026-06-28 RTY284 FNL → FNL Jun 28, 17:10 UTCJun 28, 18:14 UTC1h 5m
2026-06-28 RTY284 FNL → FNL Jun 28, 14:19 UTCJun 28, 15:49 UTC1h 30m
2026-06-27 RTY284 FNL → FNL Jun 27, 12:34 UTCJun 27, 14:00 UTC1h 25m
2026-06-26 RTY284 FNL → FNL Jun 26, 17:54 UTCJun 26, 19:14 UTC1h 20m
2026-06-26 RTY284 FNL → FNL Jun 26, 15:29 UTCJun 26, 16:44 UTC1h 15m
2026-06-26 RTY284 FNL → FNL Jun 26, 12:55 UTCJun 26, 14:05 UTC1h 10m
2026-06-25 RTY284 FNL → FNL Jun 25, 22:45 UTCJun 26, 00:15 UTC1h 30m
2026-06-23 RTY284 FNL → FNL Jun 23, 13:09 UTCJun 23, 14:10 UTC1h 0m
2026-06-23 RTY284 FNL → FNL Jun 23, 00:30 UTCJun 23, 01:15 UTC45m
2026-06-22 RTY284 FNL → FNL Jun 22, 17:00 UTCJun 22, 18:19 UTC1h 20m
2026-06-22 RTY284 FNL → FNL Jun 22, 14:49 UTCJun 22, 15:14 UTC25m
2026-06-21 RTY284 FNL → FNL Jun 21, 19:24 UTCJun 21, 19:29 UTC5m
2026-06-18 RTY284 FNL → FNL Jun 18, 22:50 UTCJun 18, 23:45 UTC55m
2026-06-18 RTY284 FNL → FNL Jun 18, 20:15 UTCJun 18, 21:30 UTC1h 15m
2026-06-18 RTY284 FNL → FNL Jun 18, 18:05 UTCJun 18, 19:15 UTC1h 10m
2026-06-18 RTY284 FNL → FNL Jun 18, 15:15 UTCJun 18, 16:25 UTC1h 10m
2026-06-18 RTY284 FNL → FNL Jun 18, 12:40 UTCJun 18, 13:50 UTC1h 10m
2026-06-17 RTY284 FNL → FNL Jun 17, 14:45 UTCJun 17, 15:50 UTC1h 5m
2026-06-16 RTY284 FNL → FNL Jun 16, 21:15 UTCJun 16, 22:35 UTC1h 20m
2026-06-16 RTY284 FNL → FNL Jun 16, 18:05 UTCJun 16, 19:10 UTC1h 5m
2026-06-16 RTY284 - Jun 16, 15:20 UTCJun 16, 16:55 UTC1h 35m
2026-06-16 RTY284 FNL → PUB Jun 16, 12:45 UTCJun 16, 14:15 UTC1h 30m
2026-06-15 RTY284 FNL → FNL Jun 15, 20:04 UTCJun 15, 21:40 UTC1h 35m
2026-06-15 RTY284 LAR → FNL Jun 15, 16:59 UTCJun 15, 17:40 UTC40m
2026-06-15 RTY284 - Jun 15, 16:04 UTCJun 15, 16:24 UTC20m
2026-06-15 RTY284 - Jun 15, 14:34 UTCJun 15, 14:50 UTC15m
2026-06-15 RTY284 - Jun 15, 13:05 UTCJun 15, 13:45 UTC40m

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

Mode-S A2DED1 frequently asked

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