Not currently tracked · last seen 3d ago
- Flights observed
- 164 showing last 50
- Avg flight time
- 1h 51m
- Typical route
- PDX → IND
- Last seen
- 3d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-11 | PDX → IND | Jul 11, 12:40 UTC | Jul 11, 16:25 UTC | 3h 45m |
| 2026-07-11 | PDX → IND | Jul 11, 12:39 UTC | Jul 11, 16:21 UTC | 3h 42m |
| 2026-07-10 | - | Jul 10, 08:30 UTC | Jul 10, 12:20 UTC | 3h 50m |
| 2026-07-10 | - | Jul 10, 02:25 UTC | Jul 10, 05:00 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 21:05 UTC | Jul 9, 23:25 UTC | 2h 20m |
| 2026-07-09 | - | Jul 9, 12:10 UTC | Jul 9, 15:25 UTC | 3h 15m |
| 2026-07-09 | LAX → MEM | Jul 9, 12:06 UTC | Jul 9, 15:23 UTC | 3h 17m |
| 2026-07-09 | - | Jul 9, 09:05 UTC | Jul 9, 09:50 UTC | 45m |
| 2026-07-08 | IND → OAK | Jul 8, 21:00 UTC | Jul 9, 01:05 UTC | 4h 5m |
| 2026-07-08 | BNH → IND | Jul 8, 12:20 UTC | Jul 8, 14:15 UTC | 1h 55m |
| 2026-07-08 | - | Jul 8, 08:00 UTC | Jul 8, 10:20 UTC | 2h 20m |
| 2026-07-08 | - | Jul 8, 03:10 UTC | Jul 8, 05:05 UTC | 1h 55m |
| 2026-07-08 | - | Jul 8, 01:25 UTC | Jul 8, 01:35 UTC | 10m |
| 2026-07-07 | - | Jul 7, 23:40 UTC | Jul 8, 00:00 UTC | 20m |
| 2026-07-07 | - | Jul 7, 20:25 UTC | Jul 7, 22:10 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 13:40 UTC | Jul 7, 15:25 UTC | 1h 45m |
| 2026-07-07 | - | Jul 7, 09:20 UTC | Jul 7, 11:10 UTC | 1h 50m |
| 2026-07-07 | - | Jul 7, 03:10 UTC | Jul 7, 04:35 UTC | 1h 25m |
| 2026-07-03 | - | Jul 3, 09:15 UTC | Jul 3, 10:40 UTC | 1h 25m |
| 2026-07-02 | - | Jul 2, 20:05 UTC | Jul 3, 05:25 UTC | 9h 20m |
| 2026-07-02 | - | Jul 2, 03:55 UTC | Jul 2, 04:30 UTC | 35m |
| 2026-07-02 | IND → MEM | Jul 2, 03:50 UTC | Jul 2, 04:51 UTC | 1h 1m |
| 2026-07-01 | - | Jul 1, 12:20 UTC | Jul 1, 14:30 UTC | 2h 10m |
| 2026-07-01 | - | Jul 1, 08:20 UTC | Jul 1, 10:25 UTC | 2h 5m |
| 2026-07-01 | STL → IND | Jul 1, 04:00 UTC | Jul 1, 04:45 UTC | 45m |
| 2026-06-30 | - | Jun 30, 10:15 UTC | Jun 30, 10:55 UTC | 40m |
| 2026-06-27 | - | Jun 27, 01:39 UTC | Jun 27, 03:20 UTC | 1h 40m |
| 2026-06-27 | RIC → MEM | Jun 27, 01:38 UTC | Jun 27, 03:19 UTC | 1h 41m |
| 2026-06-26 | - | Jun 26, 09:35 UTC | Jun 26, 10:30 UTC | 55m |
| 2026-06-26 | MEM → RIC | Jun 26, 09:30 UTC | Jun 26, 11:06 UTC | 1h 36m |
| 2026-06-26 | - | Jun 26, 04:30 UTC | Jun 26, 05:24 UTC | 55m |
| 2026-06-25 | TPA → ATL | Jun 25, 23:55 UTC | Jun 26, 00:55 UTC | 1h 0m |
| 2026-06-25 | OLV → TPA | Jun 25, 20:54 UTC | Jun 25, 22:20 UTC | 1h 25m |
| 2026-06-25 | - | Jun 25, 12:10 UTC | Jun 25, 14:04 UTC | 1h 55m |
| 2026-06-25 | PHL → MEM | Jun 25, 12:04 UTC | Jun 25, 14:11 UTC | 2h 7m |
| 2026-06-25 | - | Jun 25, 09:10 UTC | Jun 25, 10:25 UTC | 1h 15m |
| 2026-06-25 | - | Jun 25, 04:14 UTC | Jun 25, 04:54 UTC | 40m |
| 2026-06-24 | - | Jun 24, 08:39 UTC | Jun 24, 09:19 UTC | 40m |
| 2026-06-24 | - | Jun 24, 02:15 UTC | Jun 24, 05:40 UTC | 3h 25m |
| 2026-06-23 | - | Jun 23, 12:40 UTC | Jun 23, 14:35 UTC | 1h 55m |
| 2026-06-23 | - | Jun 23, 08:54 UTC | Jun 23, 11:10 UTC | 2h 15m |
| 2026-06-23 | DFW → IND | Jun 23, 03:49 UTC | Jun 23, 05:20 UTC | 1h 30m |
| 2026-06-20 | - | Jun 20, 09:34 UTC | Jun 20, 10:34 UTC | 1h 0m |
| 2026-06-20 | MCI → MEM | Jun 20, 03:19 UTC | Jun 20, 04:14 UTC | 55m |
| 2026-06-19 | - | Jun 19, 08:34 UTC | Jun 19, 09:30 UTC | 55m |
| 2026-06-19 | AUS → MEM | Jun 19, 02:44 UTC | Jun 19, 03:57 UTC | 1h 13m |
| 2026-06-19 | - | Jun 19, 02:45 UTC | Jun 19, 04:00 UTC | 1h 15m |
| 2026-06-18 | - | Jun 18, 09:25 UTC | Jun 18, 10:40 UTC | 1h 15m |
| 2026-06-18 | - | Jun 18, 02:25 UTC | Jun 18, 03:30 UTC | 1h 5m |
| 2026-06-17 | - | Jun 17, 09:20 UTC | Jun 17, 10:20 UTC | 1h 0m |
Specifications
| Registration | N256FE |
| Operator | FEDERAL EXPRESS CORP |
| Mode-S code | A26E4A · 50467112 (octal) |
Looking for transponder-level data? View the Mode-S A26E4A page for country allocation, callsign history, and ADS-B signal details.
N256FE frequently asked
Who operates N256FE?
N256FE is operated by FEDERAL EXPRESS CORP.
What is the Mode-S transponder code for N256FE?
N256FE broadcasts on Mode-S (ICAO 24-bit) address A26E4A (octal 50467112). View the transponder page.
What route does N256FE typically fly?
N256FE most frequently flies between PDX and IND based on observed flights.
Where is N256FE right now?
N256FE is not currently being tracked; last seen 3d ago.