Flight
MAC378
Flight history and live tracking for MAC378. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 15 flights since Oct 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (15) - back to 2025-10-26
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2025-12-15 | LEBL | GMTT | 20:20 CET | 22:08 +01 | 1h 47m | 02019C |
| 2025-12-14estimated | LEBL | ? | 17:05 CET | 17:36Z | 1h 30m | 02019C |
| 2025-12-13estimated | ? | ? | 12:45Z | 14:34Z | 1h 48m | CN-NMI |
| 2025-12-12estimated | LEBL | ? | 09:49 CET | 10:20Z | 1h 30m | 02019C |
| 2025-12-11estimated | LEBL | ? | 19:42 CET | 20:16Z | 1h 34m | CN-NMO |
| 2025-12-10estimated | LEBL | ? | 21:43 CET | 22:06Z | 1h 22m | 02019C |
| 2025-12-02estimated | ? | ? | 08:52Z | 09:20Z | 0h 27m | 2019C |
| 2025-11-28estimated | ? | ? | 08:54Z | 10:20Z | 1h 25m | 20176 |
| 2025-11-27estimated | ? | GMTT | 19:03Z | 21:32 +01 | 1h 28m | 2019C |
| 2025-11-26estimated | ? | GMTT | 20:08Z | 22:40 +01 | 1h 31m | 20176 |
| 2025-10-30estimated | ? | ? | 18:45Z | 19:54Z | 1h 08m | 20176 |
| 2025-10-29 | ? | GMTT | 19:39Z | 22:46 +01 | 2h 06m | 20176 |
| 2025-10-28 | GMTT | ? | 07:00 +01 | 10:22Z | 4h 21m | 20176 |
| 2025-10-27estimated | ? | GMTT | 20:33Z | 23:00 +01 | 1h 26m | 20176 |
| 2025-10-26estimated | ? | GMTT | 14:50Z | 17:30 +01 | 1h 39m | 20118 |
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 MAC378 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]