Flight
MUSX2
Flight history and live tracking for MUSX2. 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-28partial | LFST | ? | 08:56 CEST | 709FH | ||
| 2026-09-27partial | LFST | ? | 15:06 CEST | 709FG | ||
| 2026-09-26partial | LFST | ? | 14:24 CEST | 709FG | ||
| 2026-09-07partial | LFAQ | ? | 09:09 CEST | 709FC | ||
| 2026-09-06partial | LFAQ | ? | 17:20 CEST | 709FM | ||
| 2026-09-05partial | LFAQ | ? | 18:30 CEST | 709FM |
Earlier flights (12) - back to 2025-10-14
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-04partial | LFAQ | ? | 19:01 CEST | 709FC | ||
| 2026-09-04estimated | ? | ? | 12:10Z | 13:30Z | 1h 19m | 709FC |
| 2026-08-30partial | LFAQ | ? | 10:06 CEST | 709FK | ||
| 2026-08-29partial | LFAQ | ? | 13:36 CEST | 709FK | ||
| 2026-08-28estimated | LFBG | LFAQ | 18:00 CEST | 18:40 CEST | 0h 39m | 709FK |
| 2026-08-28 | LFBG | LFAQ | 13:55 CEST | 15:08 CEST | 1h 12m | 709FK |
| 2026-08-24estimated | LFLB | ? | 09:23 CEST | 07:42Z | 0h 18m | 709FP |
| 2026-08-23partial | LFLS | ? | 15:29 CEST | 709FP | ||
| 2026-08-23partial | LFLS | ? | 11:01 CEST | 709FP | ||
| 2026-08-22partial | LFLS | ? | 16:29 CEST | 709FC | ||
| 2026-08-21estimated | ? | LFLS | 12:54Z | 15:24 CEST | 0h 29m | 709FC |
| 2025-10-14partial | LFBG | ? | 17:02 CEST | 3B752A |
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 MUSX2 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]