sensors Mode-S transponder

ADE5B7

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N995FD · BOEING 757-200 · operated by FEDERAL EXPRESS CORP

Hex
ADE5B7
Octal
53362667
Decimal
11,396,535
Country
US
Tail
N995FD
Type
B752
No current signal · last broadcast 1d ago
Flights observed
65
Distinct callsigns
6
Country
US
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S ADE5B7.

Country allocation

The ICAO 24-bit address ADE5B7 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 6 distinct

Callsign Airline Flights Last seen
FDX1889 FedEx Express 30 2026-05-22
FDX1839 FedEx Express 28 2026-05-27
FDX1619 FedEx Express 2 2026-05-29
FDX1485 FedEx Express 2 2026-05-28
FDX3686 FedEx Express 1 2026-05-27
FDX1267 FedEx Express 1 2026-05-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 FDX1619 TYS → IND May 29, 04:45 UTCMay 29, 05:20 UTC35m
2026-05-29 FDX1619 TYS → IND May 29, 03:20 UTCMay 29, 04:05 UTC45m
2026-05-28 FDX1485 MEM → TYS May 28, 09:30 UTCMay 28, 10:15 UTC45m
2026-05-28 FDX1485 MEM → TYS May 28, 09:27 UTCMay 28, 10:15 UTC48m
2026-05-27 FDX1267 SDF → MEM May 27, 21:50 UTCMay 28, 05:25 UTC7h 35m
2026-05-27 FDX3686 OAK → MEM May 27, 15:05 UTCMay 27, 18:35 UTC3h 30m
2026-05-27 FDX1839 SAN → OAK May 27, 03:20 UTCMay 27, 04:28 UTC1h 8m
2026-05-22 FDX1889 OAK → SAN May 22, 10:05 UTCMay 22, 11:05 UTC1h 0m
2026-05-22 FDX1839 SAN → OAK May 22, 03:30 UTCMay 22, 04:35 UTC1h 5m
2026-05-21 FDX1889 OAK → SAN May 21, 10:10 UTCMay 21, 11:10 UTC1h 0m
2026-05-21 FDX1839 SAN → OAK May 21, 03:25 UTCMay 21, 04:30 UTC1h 5m
2026-05-20 FDX1889 OAK → SAN May 20, 10:15 UTCMay 20, 11:20 UTC1h 5m
2026-05-20 FDX1839 SAN → OAK May 20, 03:35 UTCMay 20, 04:40 UTC1h 6m
2026-05-19 FDX1889 OAK → SAN May 19, 10:10 UTCMay 19, 11:10 UTC1h 0m
2026-05-19 FDX1839 SAN → OAK May 19, 03:40 UTCMay 19, 04:45 UTC1h 5m
2026-05-19 - SAN → SAN May 19, 02:30 UTCMay 19, 02:45 UTC15m
2026-05-15 FDX1889 OAK → SAN May 15, 10:00 UTCMay 15, 10:55 UTC55m
2026-05-15 FDX1839 SAN → OAK May 15, 03:31 UTCMay 15, 04:37 UTC1h 6m
2026-05-15 FDX1839 SAN → OAK May 15, 03:30 UTCMay 15, 03:45 UTC15m
2026-05-14 FDX1889 OAK → SAN May 14, 10:00 UTCMay 14, 11:01 UTC1h 0m
2026-05-14 FDX1839 SAN → OAK May 14, 03:35 UTCMay 14, 04:40 UTC1h 5m
2026-05-13 FDX1889 OAK → SAN May 13, 10:00 UTCMay 13, 11:00 UTC1h 0m
2026-05-13 FDX1839 SAN → OAK May 13, 03:25 UTCMay 13, 04:25 UTC1h 0m
2026-05-12 FDX1889 OAK → SAN May 12, 10:10 UTCMay 12, 11:15 UTC1h 5m
2026-05-12 FDX1839 SAN → OAK May 12, 03:45 UTCMay 12, 04:45 UTC1h 0m
2026-05-12 FDX1839 SAN → OAK May 12, 03:43 UTCMay 12, 04:44 UTC1h 1m
2026-05-08 FDX1889 OAK → SAN May 8, 10:09 UTCMay 8, 11:09 UTC1h 0m
2026-05-08 FDX1839 SAN → OAK May 8, 03:35 UTCMay 8, 04:34 UTC1h 0m
2026-05-08 FDX1839 SAN → OAK May 8, 03:30 UTCMay 8, 04:35 UTC1h 5m
2026-05-07 FDX1889 OAK → SAN May 7, 09:59 UTCMay 7, 11:00 UTC1h 1m
2026-05-07 FDX1889 OAK → SAN May 7, 10:00 UTCMay 7, 11:05 UTC1h 5m
2026-05-07 FDX1839 SAN → OAK May 7, 03:30 UTCMay 7, 04:35 UTC1h 5m
2026-05-06 FDX1889 OAK → SAN May 6, 10:01 UTCMay 6, 11:00 UTC1h 0m
2026-05-06 FDX1839 SAN → OAK May 6, 03:25 UTCMay 6, 04:30 UTC1h 5m
2026-05-05 FDX1889 OAK → SAN May 5, 10:20 UTCMay 5, 11:25 UTC1h 5m
2026-05-05 FDX1839 SAN → OAK May 5, 03:30 UTCMay 5, 04:35 UTC1h 5m
2026-05-01 FDX1889 OAK → SAN May 1, 10:15 UTCMay 1, 11:15 UTC1h 0m
2026-05-01 FDX1839 SAN → OAK May 1, 03:30 UTCMay 1, 04:40 UTC1h 10m
2026-04-30 FDX1889 OAK → SAN Apr 30, 10:00 UTCApr 30, 11:05 UTC1h 5m
2026-04-30 FDX1839 SAN → OAK Apr 30, 03:30 UTCApr 30, 04:35 UTC1h 5m
2026-04-29 FDX1889 OAK → SAN Apr 29, 10:10 UTCApr 29, 11:15 UTC1h 5m
2026-04-29 FDX1839 SAN → OAK Apr 29, 03:24 UTCApr 29, 04:29 UTC1h 5m
2026-04-28 FDX1889 OAK → SAN Apr 28, 10:20 UTCApr 28, 11:35 UTC1h 15m
2026-04-28 FDX1889 OAK → SAN Apr 28, 10:20 UTCApr 28, 11:25 UTC1h 5m
2026-04-28 FDX1839 SAN → OAK Apr 28, 03:35 UTCApr 28, 04:40 UTC1h 5m
2026-04-24 FDX1889 OAK → SAN Apr 24, 09:55 UTCApr 24, 10:55 UTC1h 0m
2026-04-24 FDX1839 SAN → OAK Apr 24, 03:25 UTCApr 24, 04:30 UTC1h 5m
2026-04-23 FDX1889 OAK → SAN Apr 23, 10:00 UTCApr 23, 11:14 UTC1h 14m
2026-04-23 FDX1889 OAK → SAN Apr 23, 10:01 UTCApr 23, 11:01 UTC1h 0m
2026-04-23 FDX1839 SAN → OAK Apr 23, 03:31 UTCApr 23, 04:39 UTC1h 8m

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

Mode-S ADE5B7 frequently asked

What is Mode-S code ADE5B7?
ADE5B7 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N995FD.
Where is Mode-S ADE5B7 registered?
Mode-S code ADE5B7 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 ADE5B7 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex ADE5B7, octal 53362667, decimal 11,396,535.
What flights does ADE5B7 operate?
Mode-S ADE5B7 has broadcast 6 distinct callsigns, including FDX1889, FDX1839, FDX1619, FDX1485, FDX3686.