Not currently tracked · last seen Jul 24, 10:05 UTC
- Flights observed
- 208 showing last 50
- Avg flight time
- 2h 7m
- Typical route
- MEM → IND
- Last seen
- Jul 24, 10:05 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-24 | IND → YYZ | Jul 24, 08:55 UTC | Jul 24, 10:00 UTC | 1h 5m |
| 2026-07-24 | IAH → IND | Jul 24, 03:50 UTC | Jul 24, 05:30 UTC | 1h 40m |
| 2026-07-23 | IND → IAH | Jul 23, 08:10 UTC | Jul 23, 09:50 UTC | 1h 40m |
| 2026-07-23 | GSO → IND | Jul 23, 02:05 UTC | Jul 23, 03:55 UTC | 1h 50m |
| 2026-07-22 | - | Jul 22, 02:10 UTC | Jul 22, 04:25 UTC | 2h 15m |
| 2026-07-21 | SAT → ELP | Jul 21, 10:00 UTC | Jul 21, 10:50 UTC | 50m |
| 2026-07-21 | SAT → ELP | Jul 21, 08:20 UTC | Jul 21, 09:00 UTC | 40m |
| 2026-07-21 | ATL → AFW | Jul 21, 03:30 UTC | Jul 21, 05:10 UTC | 1h 40m |
| 2026-07-17 | - | Jul 17, 08:45 UTC | Jul 17, 09:45 UTC | 1h 0m |
| 2026-07-17 | - | Jul 17, 02:54 UTC | Jul 17, 03:55 UTC | 1h 0m |
| 2026-07-16 | - | Jul 16, 08:40 UTC | Jul 16, 10:00 UTC | 1h 20m |
| 2026-07-16 | SEA → MEM | Jul 16, 02:00 UTC | Jul 16, 05:42 UTC | 3h 42m |
| 2026-07-16 | - | Jul 16, 02:00 UTC | Jul 16, 05:45 UTC | 3h 45m |
| 2026-07-15 | IND → SEA | Jul 15, 09:15 UTC | Jul 15, 12:55 UTC | 3h 40m |
| 2026-07-14 | - | Jul 14, 13:05 UTC | Jul 14, 14:30 UTC | 1h 25m |
| 2026-07-14 | - | Jul 14, 09:35 UTC | Jul 14, 11:10 UTC | 1h 35m |
| 2026-07-10 | AWM → IND | Jul 10, 08:25 UTC | Jul 10, 09:40 UTC | 1h 15m |
| 2026-07-10 | MEM → IND | Jul 10, 08:20 UTC | Jul 10, 09:37 UTC | 1h 17m |
| 2026-07-09 | - | Jul 9, 20:05 UTC | Jul 10, 05:10 UTC | 9h 5m |
| 2026-07-09 | - | Jul 9, 13:40 UTC | Jul 9, 16:45 UTC | 3h 5m |
| 2026-07-09 | OAK → ONT | Jul 9, 09:30 UTC | Jul 9, 10:20 UTC | 50m |
| 2026-07-09 | - | Jul 9, 09:30 UTC | Jul 9, 09:45 UTC | 15m |
| 2026-07-09 | - | Jul 9, 04:35 UTC | Jul 9, 05:30 UTC | 55m |
| 2026-07-09 | LAX → OAK | Jul 9, 04:31 UTC | Jul 9, 05:26 UTC | 55m |
| 2026-07-08 | - | Jul 8, 20:20 UTC | Jul 8, 23:30 UTC | 3h 10m |
| 2026-07-08 | MEM → LAX | Jul 8, 20:17 UTC | Jul 8, 23:30 UTC | 3h 13m |
| 2026-07-08 | - | Jul 8, 12:55 UTC | Jul 8, 14:25 UTC | 1h 30m |
| 2026-07-08 | - | Jul 8, 09:05 UTC | Jul 8, 10:35 UTC | 1h 30m |
| 2026-07-08 | - | Jul 8, 02:05 UTC | Jul 8, 05:30 UTC | 3h 25m |
| 2026-07-07 | IND → SJC | Jul 7, 19:35 UTC | Jul 7, 23:25 UTC | 3h 50m |
| 2026-07-07 | ONT → IND | Jul 7, 14:00 UTC | Jul 7, 17:30 UTC | 3h 30m |
| 2026-07-07 | - | Jul 7, 09:10 UTC | Jul 7, 12:20 UTC | 3h 10m |
| 2026-07-07 | - | Jul 7, 01:40 UTC | Jul 7, 03:10 UTC | 1h 30m |
| 2026-07-07 | MCO → MEM | Jul 7, 01:39 UTC | Jul 7, 03:10 UTC | 1h 31m |
| 2026-07-05 | - | Jul 5, 21:05 UTC | Jul 5, 22:35 UTC | 1h 30m |
| 2026-07-05 | PHL → MEM | Jul 5, 12:45 UTC | Jul 5, 15:45 UTC | 3h 0m |
| 2026-07-05 | PHL → MEM | Jul 5, 12:43 UTC | Jul 5, 15:55 UTC | 3h 12m |
| 2026-07-04 | MEM → IND | Jul 4, 20:10 UTC | Jul 4, 23:40 UTC | 3h 30m |
| 2026-07-04 | MEM → IND | Jul 4, 20:06 UTC | Jul 4, 23:34 UTC | 3h 28m |
| 2026-07-03 | - | Jul 3, 02:15 UTC | Jul 3, 03:50 UTC | 1h 35m |
| 2026-07-03 | TPA → MEM | Jul 3, 02:13 UTC | Jul 3, 03:48 UTC | 1h 35m |
| 2026-07-02 | - | Jul 2, 08:25 UTC | Jul 2, 10:10 UTC | 1h 45m |
| 2026-07-02 | - | Jul 2, 02:15 UTC | Jul 2, 04:20 UTC | 2h 5m |
| 2026-07-01 | - | Jul 1, 21:35 UTC | Jul 1, 23:35 UTC | 2h 0m |
| 2026-07-01 | - | Jul 1, 12:30 UTC | Jul 1, 13:45 UTC | 1h 15m |
| 2026-07-01 | PHL → MEM | Jul 1, 12:28 UTC | Jul 1, 14:19 UTC | 1h 51m |
| 2026-07-01 | - | Jul 1, 09:05 UTC | Jul 1, 10:25 UTC | 1h 20m |
| 2026-07-01 | - | Jul 1, 03:40 UTC | Jul 1, 05:00 UTC | 1h 20m |
| 2026-07-01 | - | Jul 1, 00:05 UTC | Jul 1, 02:00 UTC | 1h 55m |
| 2026-06-30 | - | Jun 30, 02:30 UTC | Jun 30, 03:50 UTC | 1h 20m |
Specifications
| Registration | N251FE |
| Operator | FEDERAL EXPRESS CORP |
| Mode-S code | A25BB7 · 50455667 (octal) |
Looking for transponder-level data? View the Mode-S A25BB7 page for country allocation, callsign history, and ADS-B signal details.
N251FE frequently asked
Who operates N251FE?
N251FE is operated by FEDERAL EXPRESS CORP.
What is the Mode-S transponder code for N251FE?
N251FE broadcasts on Mode-S (ICAO 24-bit) address A25BB7 (octal 50455667). View the transponder page.
What route does N251FE typically fly?
N251FE most frequently flies between MEM and IND based on observed flights.
Where is N251FE right now?
N251FE is not currently being tracked; last seen Jul 24, 10:05 UTC.