Flight
FIE711
Flight history and live tracking for FIE711. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Observed route | LTCE → LEAL |
Flight history 15 flights since Jun 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-20estimated | ? | ? | 15:25Z | 19:52Z | 4h 26m | 504E85 |
| 2026-08-16estimated | ? | ? | 14:35Z | 21:22Z | 6h 47m | 504E8E |
| 2026-08-13estimated | ? | ? | 13:30Z | 20:23Z | 6h 53m | 504E85 |
Earlier flights (12) - back to 2026-06-14
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 14:28Z | 19:26Z | 4h 58m | 504E85 |
| 2026-07-19estimated | ? | ? | 14:09Z | 20:26Z | 6h 16m | ER-00007 |
| 2026-07-16estimated | ? | ? | 13:01Z | 19:36Z | 6h 34m | ER-00007 |
| 2026-07-12estimated | LTCE | LEAL | 16:49 +03 | 20:30 CEST | 4h 40m | ER-00007 |
| 2026-07-09estimated | LTCE | LEAL | 16:28 +03 | 20:10 CEST | 4h 41m | 504E8E |
| 2026-07-05estimated | LTCE | LEAL | 20:37 +03 | 01:49 CEST | 6h 12m | 504E7E |
| 2026-07-02estimated | LTCE | LEAL | 17:11 +03 | 21:47 CEST | 5h 35m | ER-00007 |
| 2026-06-28estimated | LTCE | LEAL | 16:56 +03 | 20:10 CEST | 4h 13m | 504E8E |
| 2026-06-25estimated | LTCE | LEAL | 16:04 +03 | 19:36 CEST | 4h 31m | ER-00007 |
| 2026-06-21estimated | LTCE | LEAL | 16:06 +03 | 21:36 CEST | 6h 29m | ER-00007 |
| 2026-06-18estimated | LTCE | LEAL | 18:50 +03 | 23:13 CEST | 5h 23m | 504E8E |
| 2026-06-14estimated | LTCE | LEAL | 20:01 +03 | 23:00 CEST | 3h 58m | ER-00007 |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when FIE711 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our own receiver network archive. Questions: [email protected]