sensors Mode-S transponder
ADBE4A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N985FX · CESSNA 208 Caravan · operated by FEDERAL EXPRESS CORP
- Hex
- ADBE4A
- Octal
- 53337112
- Decimal
- 11,386,442
- Country
- US
- Tail
- N985FX
- Type
- C208
- Flights observed
- 79
- Distinct callsigns
- 9
- Country
- US
- Last broadcast
- 29d ago
Last known position
Country allocation
The ICAO 24-bit address ADBE4A 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | MTN8311 | - | Jul 21, 13:50 UTC | Jul 21, 15:05 UTC | 1h 15m |
| 2026-07-21 | MTN8300 | - | Jul 21, 09:05 UTC | Jul 21, 10:15 UTC | 1h 10m |
| 2026-07-21 | MTN8300 | - | Jul 21, 07:05 UTC | Jul 21, 08:25 UTC | 1h 20m |
| 2026-07-17 | MTN8300 | IAD → EWR | Jul 17, 08:59 UTC | Jul 17, 10:10 UTC | 1h 10m |
| 2026-07-17 | MTN8300 | - | Jul 17, 07:00 UTC | Jul 17, 08:25 UTC | 1h 25m |
| 2026-07-16 | MTN8311 | - | Jul 16, 15:30 UTC | Jul 16, 16:30 UTC | 1h 0m |
| 2026-07-16 | MTN8311 | - | Jul 16, 13:10 UTC | Jul 16, 14:50 UTC | 1h 40m |
| 2026-07-16 | MTN8300 | - | Jul 16, 09:05 UTC | Jul 16, 10:20 UTC | 1h 15m |
| 2026-07-16 | MTN8300 | - | Jul 16, 07:05 UTC | Jul 16, 08:35 UTC | 1h 30m |
| 2026-07-15 | MTN8313 | - | Jul 15, 15:35 UTC | Jul 15, 17:10 UTC | 1h 35m |
| 2026-07-15 | MTN8313 | EWR → IAD | Jul 15, 13:20 UTC | Jul 15, 14:55 UTC | 1h 35m |
| 2026-07-15 | MTN8302 | - | Jul 15, 10:15 UTC | Jul 15, 11:40 UTC | 1h 25m |
| 2026-07-15 | MTN8302 | - | Jul 15, 07:50 UTC | Jul 15, 09:10 UTC | 1h 20m |
| 2026-07-14 | MTN8313 | IAD → EWR | Jul 14, 15:40 UTC | Jul 14, 17:05 UTC | 1h 25m |
| 2026-07-14 | MTN8313 | - | Jul 14, 13:30 UTC | Jul 14, 14:50 UTC | 1h 20m |
| 2026-07-14 | MTN8302 | - | Jul 14, 08:05 UTC | Jul 14, 11:10 UTC | 3h 5m |
| 2026-07-10 | MTN8313 | - | Jul 10, 15:45 UTC | Jul 10, 17:10 UTC | 1h 25m |
| 2026-07-10 | MTN8313 | - | Jul 10, 12:40 UTC | Jul 10, 14:10 UTC | 1h 30m |
| 2026-07-10 | MTN8302 | - | Jul 10, 07:50 UTC | Jul 10, 11:00 UTC | 3h 10m |
| 2026-07-09 | MTN8311 | - | Jul 9, 15:05 UTC | Jul 9, 16:15 UTC | 1h 10m |
| 2026-07-09 | MTN8311 | LDJ → BWI | Jul 9, 13:10 UTC | Jul 9, 14:25 UTC | 1h 15m |
| 2026-07-09 | MTN8300 | - | Jul 9, 09:05 UTC | Jul 9, 10:30 UTC | 1h 25m |
| 2026-07-09 | MTN8300 | - | Jul 9, 07:10 UTC | Jul 9, 08:30 UTC | 1h 20m |
| 2026-07-08 | MTN8311 | - | Jul 8, 14:45 UTC | Jul 8, 15:45 UTC | 1h 0m |
| 2026-07-08 | MTN8311 | - | Jul 8, 13:05 UTC | Jul 8, 14:10 UTC | 1h 5m |
| 2026-07-08 | MTN8300 | - | Jul 8, 09:00 UTC | Jul 8, 10:10 UTC | 1h 10m |
| 2026-07-08 | MTN8300 | - | Jul 8, 06:55 UTC | Jul 8, 08:15 UTC | 1h 20m |
| 2026-07-01 | N985FX | - | Jul 1, 15:40 UTC | Jul 1, 16:55 UTC | 1h 15m |
| 2026-07-01 | N985FX | - | Jul 1, 13:35 UTC | Jul 1, 14:55 UTC | 1h 20m |
| 2026-06-26 | N985FX | - | Jun 26, 17:59 UTC | Jun 26, 20:15 UTC | 2h 15m |
| 2026-06-26 | N985FX | - | Jun 26, 14:39 UTC | Jun 26, 14:55 UTC | 15m |
| 2026-06-17 | MTN5 | ERI → SVH | Jun 17, 12:55 UTC | Jun 17, 15:30 UTC | 2h 35m |
| 2026-06-17 | MTN8459 | - | Jun 17, 11:35 UTC | Jun 17, 12:05 UTC | 30m |
| 2026-06-16 | MTN8459 | - | Jun 16, 12:55 UTC | Jun 16, 13:30 UTC | 35m |
| 2026-06-16 | MTN8459 | - | Jun 16, 11:45 UTC | Jun 16, 12:14 UTC | 30m |
| 2026-06-12 | MTN8459 | ERI → CLE | Jun 12, 13:20 UTC | Jun 12, 13:55 UTC | 35m |
| 2026-06-12 | MTN8459 | - | Jun 12, 12:20 UTC | Jun 12, 12:50 UTC | 30m |
| 2026-06-11 | MTN8459 | - | Jun 11, 11:45 UTC | Jun 11, 13:15 UTC | 1h 30m |
| 2026-06-10 | MTN8459 | - | Jun 10, 11:20 UTC | Jun 10, 13:00 UTC | 1h 40m |
| 2026-06-09 | MTN8459 | CLE → CLE | Jun 9, 12:25 UTC | Jun 9, 14:00 UTC | 1h 35m |
| 2026-06-05 | MTN8459 | - | Jun 5, 11:35 UTC | Jun 5, 13:10 UTC | 1h 35m |
| 2026-06-04 | MTN8459 | - | Jun 4, 12:55 UTC | Jun 4, 13:25 UTC | 30m |
| 2026-06-04 | MTN8459 | - | Jun 4, 11:45 UTC | Jun 4, 12:20 UTC | 35m |
| 2026-06-03 | MTN8459 | - | Jun 3, 13:15 UTC | Jun 3, 13:55 UTC | 40m |
| 2026-06-03 | MTN8459 | - | Jun 3, 12:05 UTC | Jun 3, 12:40 UTC | 35m |
| 2026-06-02 | MTN8459 | - | Jun 2, 13:50 UTC | Jun 2, 14:25 UTC | 35m |
| 2026-06-02 | MTN8459 | - | Jun 2, 12:35 UTC | Jun 2, 13:10 UTC | 35m |
| 2026-05-29 | MTN8459 | - | May 29, 13:00 UTC | May 29, 13:35 UTC | 35m |
| 2026-05-29 | MTN8459 | - | May 29, 11:50 UTC | May 29, 12:25 UTC | 35m |
| 2026-05-28 | MTN8459 | CLE → CLE | May 28, 12:00 UTC | May 28, 13:45 UTC | 1h 45m |
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 N985FX page for operator, model, and routing details .