sensors Mode-S transponder
ACF506
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N934FD · BOEING 757-200 · operated by FEDERAL EXPRESS CORP
- Hex
- ACF506
- Octal
- 53172406
- Decimal
- 11,334,918
- Country
- US
- Tail
- N934FD
- Type
- B752
- Flights observed
- 36
- Distinct callsigns
- 17
- Country
- US
- Last broadcast
- Apr 30, 04:15 UTC
Last known position
Country allocation
The ICAO 24-bit address ACF506 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FDX156 | FedEx Express | 5 | 2026-04-15 |
| FDX1477 | FedEx Express | 4 | 2026-04-25 |
| FDX1329 | FedEx Express | 4 | 2026-04-28 |
| FDX5504 | FedEx Express | 3 | 2026-04-17 |
| FDX1156 | FedEx Express | 3 | 2026-04-24 |
| FDX1106 | FedEx Express | 3 | 2026-04-24 |
| FDX5503 | - | 2 | 2026-04-16 |
| FDX155 | FedEx Express | 2 | 2026-04-16 |
| FDX114 | FedEx Express | 2 | 2026-04-16 |
| FDX1512 | FedEx Express | 1 | 2026-04-17 |
| FDX1474 | FedEx Express | 1 | 2026-04-29 |
| FDX1451 | FedEx Express | 1 | 2026-04-28 |
| FDX1424 | FedEx Express | 1 | 2026-04-21 |
| FDX1362 | FedEx Express | 1 | 2026-04-29 |
| FDX1333 | FedEx Express | 1 | 2026-04-21 |
| FDX1323 | FedEx Express | 1 | 2026-04-30 |
| FDX1123 | FedEx Express | 1 | 2026-04-22 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-04-30 | FDX1323 | DAY → MEM | Apr 30, 03:00 UTC | Apr 30, 04:15 UTC | 1h 15m |
| 2026-04-29 | FDX1474 | MEM → DAY | Apr 29, 10:20 UTC | Apr 29, 11:20 UTC | 1h 0m |
| 2026-04-29 | FDX1362 | ROA → MEM | Apr 29, 01:59 UTC | Apr 29, 04:00 UTC | 2h 0m |
| 2026-04-28 | FDX1451 | MEM → ROA | Apr 28, 11:15 UTC | Apr 28, 12:20 UTC | 1h 5m |
| 2026-04-28 | FDX1329 | ATW → MEM | Apr 28, 01:00 UTC | Apr 28, 03:05 UTC | 2h 5m |
| 2026-04-28 | FDX1329 | ATW → MEM | Apr 28, 00:59 UTC | Apr 28, 03:05 UTC | 2h 6m |
| 2026-04-25 | FDX1477 | MEM → MSN | Apr 25, 10:45 UTC | Apr 25, 11:25 UTC | 40m |
| 2026-04-25 | FDX1477 | MEM → MSN | Apr 25, 09:05 UTC | Apr 25, 09:55 UTC | 50m |
| 2026-04-24 | FDX1106 | MSP → AFW | Apr 24, 14:50 UTC | Apr 24, 16:25 UTC | 1h 35m |
| 2026-04-24 | FDX1106 | MSP → AFW | Apr 24, 14:45 UTC | Apr 24, 16:25 UTC | 1h 40m |
| 2026-04-24 | FDX1156 | AFW → MSP | Apr 24, 08:15 UTC | Apr 24, 09:55 UTC | 1h 40m |
| 2026-04-24 | FDX1156 | AFW → MSP | Apr 24, 08:11 UTC | Apr 24, 09:55 UTC | 1h 44m |
| 2026-04-23 | FDX1106 | MSP → AFW | Apr 23, 02:55 UTC | Apr 23, 04:45 UTC | 1h 50m |
| 2026-04-22 | FDX1156 | AFW → MSP | Apr 22, 08:15 UTC | Apr 22, 10:10 UTC | 1h 55m |
| 2026-04-22 | FDX1123 | EWR → AFW | Apr 22, 02:35 UTC | Apr 22, 05:35 UTC | 3h 0m |
| 2026-04-21 | FDX1424 | MEM → EWR | Apr 21, 07:20 UTC | Apr 21, 09:20 UTC | 2h 0m |
| 2026-04-21 | FDX1333 | BMI → MEM | Apr 21, 03:05 UTC | Apr 21, 04:00 UTC | 55m |
| 2026-04-17 | FDX1512 | MEM → BMI | Apr 17, 09:35 UTC | Apr 17, 10:30 UTC | 55m |
| 2026-04-17 | FDX5504 | SAP → MIA | Apr 17, 01:20 UTC | Apr 17, 02:25 UTC | 1h 5m |
| 2026-04-17 | FDX5504 | SAP → MIA | Apr 17, 00:05 UTC | Apr 17, 01:15 UTC | 1h 10m |
| 2026-04-16 | FDX5504 | SAP → MIA | Apr 16, 21:30 UTC | Apr 16, 21:55 UTC | 25m |
| 2026-04-16 | FDX5503 | - | Apr 16, 15:15 UTC | Apr 16, 16:10 UTC | 55m |
| 2026-04-16 | FDX5503 | MIA → GUA | Apr 16, 13:57 UTC | Apr 16, 16:01 UTC | 2h 4m |
| 2026-04-16 | FDX114 | MEM → MIA | Apr 16, 11:09 UTC | Apr 16, 11:39 UTC | 30m |
| 2026-04-16 | FDX114 | MEM → MIA | Apr 16, 09:54 UTC | Apr 16, 11:04 UTC | 1h 10m |
| 2026-04-16 | FDX155 | MEM → ANC | Apr 16, 03:09 UTC | Apr 16, 03:55 UTC | 45m |
| 2026-04-16 | FDX155 | MEM → ANC | Apr 16, 01:10 UTC | Apr 16, 03:04 UTC | 1h 55m |
| 2026-04-15 | FDX156 | MEM → YOW | Apr 15, 11:00 UTC | Apr 15, 11:40 UTC | 40m |
| 2026-04-15 | FDX156 | MEM → YOW | Apr 15, 09:40 UTC | Apr 15, 11:40 UTC | 2h 0m |
| 2026-04-15 | FDX1329 | ATW → MEM | Apr 15, 03:05 UTC | Apr 15, 04:15 UTC | 1h 10m |
| 2026-04-15 | FDX1329 | ATW → MEM | Apr 15, 01:25 UTC | Apr 15, 02:15 UTC | 50m |
| 2026-04-14 | FDX1477 | MEM → MSN | Apr 14, 10:50 UTC | Apr 14, 11:05 UTC | 15m |
| 2026-04-14 | FDX1477 | - | Apr 14, 09:45 UTC | Apr 14, 11:05 UTC | 1h 20m |
| 2026-04-13 | FDX156 | - | Apr 13, 08:20 UTC | Apr 13, 09:00 UTC | 40m |
| 2026-04-13 | FDX156 | MTC → YOW | Apr 13, 07:55 UTC | Apr 13, 09:00 UTC | 1h 5m |
| 2026-04-13 | FDX156 | - | Apr 13, 06:45 UTC | Apr 13, 08:52 UTC | 2h 7m |
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 N934FD page for operator, model, and routing details .