Not currently tracked · last seen Jul 26, 14:00 UTC
- Flights observed
- 148 showing last 50
- Avg flight time
- 1h 26m
- Typical route
- AFW → ORD
- Last seen
- Jul 26, 14:00 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | JFK → MEM | Jul 26, 11:50 UTC | Jul 26, 14:00 UTC | 2h 10m |
| 2026-07-24 | MEM → JFK | Jul 24, 08:15 UTC | Jul 24, 10:15 UTC | 2h 0m |
| 2026-07-24 | TPA → MEM | Jul 24, 02:00 UTC | Jul 24, 03:25 UTC | 1h 25m |
| 2026-07-23 | IND → TPA | Jul 23, 08:50 UTC | Jul 23, 10:30 UTC | 1h 40m |
| 2026-07-23 | ELP → IND | Jul 23, 02:10 UTC | Jul 23, 04:25 UTC | 2h 15m |
| 2026-07-22 | ATL → AFW | Jul 22, 03:20 UTC | Jul 22, 04:55 UTC | 1h 35m |
| 2026-07-21 | - | Jul 21, 07:55 UTC | Jul 21, 08:45 UTC | 50m |
| 2026-07-21 | - | Jul 21, 02:40 UTC | Jul 21, 04:35 UTC | 1h 55m |
| 2026-07-19 | MEM → FLL | Jul 19, 22:00 UTC | Jul 19, 23:50 UTC | 1h 50m |
| 2026-07-18 | - | Jul 18, 04:20 UTC | Jul 18, 05:30 UTC | 1h 10m |
| 2026-07-18 | ORD → MEM | Jul 18, 04:16 UTC | Jul 18, 05:31 UTC | 1h 15m |
| 2026-07-17 | - | Jul 17, 10:15 UTC | Jul 17, 11:30 UTC | 1h 15m |
| 2026-07-17 | - | Jul 17, 03:14 UTC | Jul 17, 04:20 UTC | 1h 5m |
| 2026-07-16 | - | Jul 16, 08:30 UTC | Jul 16, 09:20 UTC | 50m |
| 2026-07-16 | MEM → MCI | Jul 16, 08:25 UTC | Jul 16, 09:20 UTC | 55m |
| 2026-07-16 | - | Jul 16, 03:00 UTC | Jul 16, 03:50 UTC | 50m |
| 2026-07-15 | - | Jul 15, 09:40 UTC | Jul 15, 10:30 UTC | 50m |
| 2026-07-15 | - | Jul 15, 03:15 UTC | Jul 15, 04:40 UTC | 1h 25m |
| 2026-07-14 | - | Jul 14, 09:10 UTC | Jul 14, 10:35 UTC | 1h 25m |
| 2026-07-14 | MEM → SAT | Jul 14, 09:06 UTC | Jul 14, 10:28 UTC | 1h 22m |
| 2026-07-14 | - | Jul 14, 02:20 UTC | Jul 14, 03:45 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 08:50 UTC | Jul 10, 10:10 UTC | 1h 20m |
| 2026-07-10 | - | Jul 10, 02:20 UTC | Jul 10, 03:25 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 09:40 UTC | Jul 9, 10:35 UTC | 55m |
| 2026-07-08 | - | Jul 8, 14:20 UTC | Jul 8, 17:35 UTC | 3h 15m |
| 2026-07-08 | IND → OAK | Jul 8, 08:30 UTC | Jul 8, 12:20 UTC | 3h 50m |
| 2026-07-08 | - | Jul 8, 03:10 UTC | Jul 8, 03:45 UTC | 35m |
| 2026-07-07 | AFW → ORD | Jul 7, 07:45 UTC | Jul 7, 09:25 UTC | 1h 40m |
| 2026-07-07 | AFW → ORD | Jul 7, 07:40 UTC | Jul 7, 09:27 UTC | 1h 47m |
| 2026-07-07 | SAT → AFW | Jul 7, 03:25 UTC | Jul 7, 04:05 UTC | 40m |
| 2026-07-05 | - | Jul 5, 22:25 UTC | Jul 5, 23:55 UTC | 1h 30m |
| 2026-07-03 | - | Jul 3, 07:15 UTC | Jul 3, 08:35 UTC | 1h 20m |
| 2026-07-02 | - | Jul 2, 07:40 UTC | Jul 2, 09:25 UTC | 1h 45m |
| 2026-07-02 | SAT → AFW | Jul 2, 03:30 UTC | Jul 2, 04:15 UTC | 45m |
| 2026-07-01 | - | Jul 1, 09:10 UTC | Jul 1, 10:30 UTC | 1h 20m |
| 2026-07-01 | MCI → MEM | Jul 1, 04:35 UTC | Jul 1, 05:35 UTC | 1h 0m |
| 2026-06-30 | - | Jun 30, 09:20 UTC | Jun 30, 10:10 UTC | 50m |
| 2026-06-30 | - | Jun 30, 03:10 UTC | Jun 30, 04:00 UTC | 50m |
| 2026-06-26 | - | Jun 26, 09:14 UTC | Jun 26, 10:05 UTC | 50m |
| 2026-06-26 | - | Jun 26, 03:24 UTC | Jun 26, 05:30 UTC | 2h 5m |
| 2026-06-25 | IND → DEN | Jun 25, 09:05 UTC | Jun 25, 11:25 UTC | 2h 20m |
| 2026-06-25 | MSP → IND | Jun 25, 02:57 UTC | Jun 25, 04:10 UTC | 1h 13m |
| 2026-06-25 | MSP → IND | Jun 25, 02:59 UTC | Jun 25, 04:14 UTC | 1h 15m |
| 2026-06-24 | MEM → MSP | Jun 24, 21:19 UTC | Jun 24, 22:55 UTC | 1h 35m |
| 2026-06-24 | MEM → MSP | Jun 24, 21:18 UTC | Jun 24, 22:54 UTC | 1h 36m |
| 2026-06-24 | - | Jun 24, 12:09 UTC | Jun 24, 14:04 UTC | 1h 55m |
| 2026-06-24 | - | Jun 24, 08:55 UTC | Jun 24, 10:04 UTC | 1h 10m |
| 2026-06-24 | - | Jun 24, 02:45 UTC | Jun 24, 03:29 UTC | 45m |
| 2026-06-23 | - | Jun 23, 22:05 UTC | Jun 23, 23:24 UTC | 1h 20m |
| 2026-06-23 | - | Jun 23, 11:29 UTC | Jun 23, 13:09 UTC | 1h 40m |
Specifications
| Registration | N289FE |
| Operator | FEDERAL EXPRESS CORP |
| Mode-S code | A2EFEC · 50567754 (octal) |
Looking for transponder-level data? View the Mode-S A2EFEC page for country allocation, callsign history, and ADS-B signal details.
N289FE frequently asked
Who operates N289FE?
N289FE is operated by FEDERAL EXPRESS CORP.
What is the Mode-S transponder code for N289FE?
N289FE broadcasts on Mode-S (ICAO 24-bit) address A2EFEC (octal 50567754). View the transponder page.
What route does N289FE typically fly?
N289FE most frequently flies between AFW and ORD based on observed flights.
Where is N289FE right now?
N289FE is not currently being tracked; last seen Jul 26, 14:00 UTC.