Flight
MET53
Flight history and live tracking for MET53. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 18 flights since Oct 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-25partial | LFBG | ? | 11:49 CEST | 709FR | ||
| 2026-09-15partial | LFBG | ? | 09:03 CEST | 709FP |
Earlier flights (16) - back to 2025-10-20
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-15partial | LFBG | ? | 09:16 CEST | 709FO | ||
| 2026-07-03partial | LFBG | ? | 13:46 CEST | 709FF | ||
| 2026-06-29estimated | LFBG | ? | 13:59 CEST | 12:28Z | 0h 28m | 709FP |
| 2026-06-25partial | LFBG | ? | 10:33 CEST | 709FR | ||
| 2026-06-24partial | LFBG | ? | 15:35 CEST | 709FL | ||
| 2026-05-28estimated | LFDI | LFBD | 09:17 CEST | 10:36 CEST | 1h 19m | 3B752B |
| 2026-05-27partial | LFBG | ? | 14:18 CEST | 709FK | ||
| 2026-05-22estimated | LFBG | LFCJ | 11:44 CEST | 12:18 CEST | 0h 33m | 709FL |
| 2026-03-02estimated | ? | ? | 15:17Z | 15:58Z | 0h 40m | 709FF |
| 2026-03-02partial | LFBG | ? | 09:03 CET | 709FO | ||
| 2026-02-27partial | LFBG | ? | 08:59 CET | 3B752B | ||
| 2025-11-28partial | LFBG | ? | 10:08 CET | 709FM | ||
| 2025-10-30partial | LFBG | ? | 13:57 CET | 709FC | ||
| 2025-10-24partial | LFBG | ? | 09:01 CEST | 3B752F | ||
| 2025-10-22estimated | ? | ? | 09:39Z | 10:08Z | 0h 28m | 3B7528 |
| 2025-10-20partial | LFBG | ? | 09:07 CEST | 709FO |
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 MET53 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 archive (from $9.99, with a free one-day sample). Questions: [email protected]