Airborne now · flying as FDX1835 at 19,200 ft
- Flights observed
- 227 showing last 50
- Avg flight time
- 1h 55m
- Typical route
- DFW → MEM
- Last seen
- 2d ago
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-25 | DFW → MEM | Jul 25, 14:00 UTC | Jul 25, 17:20 UTC | 3h 20m |
| 2026-07-25 | DFW → MEM | Jul 25, 12:05 UTC | Jul 25, 13:00 UTC | 55m |
| 2026-07-23 | PHX → OAK | Jul 23, 03:20 UTC | Jul 23, 04:50 UTC | 1h 30m |
| 2026-07-22 | IND → PHX | Jul 22, 21:00 UTC | Jul 23, 00:10 UTC | 3h 10m |
| 2026-07-22 | IND → PHX | Jul 22, 20:55 UTC | Jul 23, 00:09 UTC | 3h 14m |
| 2026-07-22 | OAK → IND | Jul 22, 13:14 UTC | Jul 22, 15:17 UTC | 2h 3m |
| 2026-07-22 | OAK → IND | Jul 22, 13:15 UTC | Jul 22, 15:20 UTC | 2h 5m |
| 2026-07-22 | RIC → MEM | Jul 22, 01:55 UTC | Jul 22, 03:35 UTC | 1h 40m |
| 2026-07-21 | MEM → RIC | Jul 21, 21:35 UTC | Jul 21, 23:10 UTC | 1h 35m |
| 2026-07-21 | ORD → MEM | Jul 21, 13:15 UTC | Jul 21, 16:35 UTC | 3h 20m |
| 2026-07-21 | IND → LAX | Jul 21, 07:10 UTC | Jul 21, 10:50 UTC | 3h 40m |
| 2026-07-16 | PDX → IND | Jul 16, 12:55 UTC | Jul 16, 16:35 UTC | 3h 40m |
| 2026-07-16 | OAK → PDX | Jul 16, 09:45 UTC | Jul 16, 10:55 UTC | 1h 10m |
| 2026-07-16 | - | Jul 16, 05:00 UTC | Jul 16, 05:35 UTC | 35m |
| 2026-07-16 | - | Jul 16, 03:10 UTC | Jul 16, 03:35 UTC | 25m |
| 2026-07-15 | - | Jul 15, 20:40 UTC | Jul 15, 23:10 UTC | 2h 30m |
| 2026-07-15 | - | Jul 15, 12:05 UTC | Jul 15, 13:25 UTC | 1h 20m |
| 2026-07-15 | - | Jul 15, 09:25 UTC | Jul 15, 09:45 UTC | 20m |
| 2026-07-15 | - | Jul 15, 07:15 UTC | Jul 15, 08:25 UTC | 1h 10m |
| 2026-07-15 | - | Jul 15, 02:15 UTC | Jul 15, 03:20 UTC | 1h 5m |
| 2026-07-14 | - | Jul 14, 08:10 UTC | Jul 14, 09:05 UTC | 55m |
| 2026-07-14 | MSP → MEM | Jul 14, 02:25 UTC | Jul 14, 04:05 UTC | 1h 40m |
| 2026-07-11 | - | Jul 11, 09:10 UTC | Jul 11, 10:45 UTC | 1h 35m |
| 2026-07-11 | - | Jul 11, 03:15 UTC | Jul 11, 04:55 UTC | 1h 40m |
| 2026-07-10 | - | Jul 10, 09:20 UTC | Jul 10, 11:15 UTC | 1h 55m |
| 2026-07-10 | MEM → DEN | Jul 10, 09:18 UTC | Jul 10, 11:10 UTC | 1h 52m |
| 2026-07-10 | - | Jul 10, 02:30 UTC | Jul 10, 03:40 UTC | 1h 10m |
| 2026-07-09 | - | Jul 9, 08:40 UTC | Jul 9, 09:40 UTC | 1h 0m |
| 2026-07-09 | STL → IND | Jul 9, 04:05 UTC | Jul 9, 04:45 UTC | 40m |
| 2026-07-09 | STL → IND | Jul 9, 04:05 UTC | Jul 9, 04:40 UTC | 35m |
| 2026-07-08 | IND → STL | Jul 8, 09:10 UTC | Jul 8, 09:45 UTC | 35m |
| 2026-07-08 | DEN → IND | Jul 8, 03:17 UTC | Jul 8, 05:29 UTC | 2h 12m |
| 2026-07-08 | DEN → IND | Jul 8, 03:20 UTC | Jul 8, 05:30 UTC | 2h 10m |
| 2026-07-07 | - | Jul 7, 21:10 UTC | Jul 7, 23:20 UTC | 2h 10m |
| 2026-07-07 | - | Jul 7, 12:40 UTC | Jul 7, 14:45 UTC | 2h 5m |
| 2026-07-07 | - | Jul 7, 09:00 UTC | Jul 7, 10:45 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 03:10 UTC | Jul 7, 05:20 UTC | 2h 10m |
| 2026-07-05 | OLV → JFK | Jul 5, 20:15 UTC | Jul 5, 22:35 UTC | 2h 20m |
| 2026-07-05 | MEM → JFK | Jul 5, 20:12 UTC | Jul 5, 22:30 UTC | 2h 18m |
| 2026-07-05 | - | Jul 5, 10:45 UTC | Jul 5, 16:40 UTC | 5h 55m |
| 2026-07-04 | OAK → ANC | Jul 4, 10:20 UTC | Jul 4, 14:30 UTC | 4h 10m |
| 2026-07-04 | OAK → ANC | Jul 4, 10:19 UTC | Jul 4, 14:25 UTC | 4h 6m |
| 2026-07-03 | - | Jul 3, 08:05 UTC | Jul 3, 12:00 UTC | 3h 55m |
| 2026-07-03 | - | Jul 3, 02:45 UTC | Jul 3, 03:20 UTC | 35m |
| 2026-07-02 | - | Jul 2, 21:50 UTC | Jul 2, 23:15 UTC | 1h 25m |
| 2026-07-02 | - | Jul 2, 12:35 UTC | Jul 2, 13:40 UTC | 1h 5m |
| 2026-07-02 | - | Jul 2, 09:45 UTC | Jul 2, 10:55 UTC | 1h 10m |
| 2026-07-02 | - | Jul 2, 03:10 UTC | Jul 2, 04:20 UTC | 1h 10m |
| 2026-07-01 | - | Jul 1, 08:45 UTC | Jul 1, 09:45 UTC | 1h 0m |
| 2026-07-01 | MEM → IND | Jul 1, 02:35 UTC | Jul 1, 04:45 UTC | 2h 10m |
Specifications
| Registration | N250FE |
| Operator | FEDERAL EXPRESS CORP |
| Mode-S code | A25800 · 50454000 (octal) |
Looking for transponder-level data? View the Mode-S A25800 page for country allocation, callsign history, and ADS-B signal details.
N250FE frequently asked
Who operates N250FE?
N250FE is operated by FEDERAL EXPRESS CORP.
What is the Mode-S transponder code for N250FE?
N250FE broadcasts on Mode-S (ICAO 24-bit) address A25800 (octal 50454000). View the transponder page.
What route does N250FE typically fly?
N250FE most frequently flies between DFW and MEM based on observed flights.
Where is N250FE right now?
N250FE is currently airborne flying as FDX1835. Live position is shown on the map above.