Flight
MFX301
Flight history and live tracking for MFX301, operated by My Freighter LLC. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | My Freighter LLC |
| Observed route | LTCE → LTBQ |
Flight history 42 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-20estimated | ? | ? | 03:39Z | 05:34Z | 1h 54m | 507CAB |
| 2026-08-15estimated | ? | ? | 10:31Z | 15:12Z | 4h 41m | 507CBD |
| 2026-08-13estimated | ? | ? | 05:37Z | 06:48Z | 1h 10m | 507CAB |
| 2026-08-12estimated | ? | ? | 10:45Z | 15:08Z | 4h 23m | 507CAC |
Earlier flights (38) - back to 2026-04-02
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 03:54Z | 05:08Z | 1h 13m | 507CBD |
| 2026-07-22estimated | ? | ? | 10:44Z | 15:21Z | 4h 36m | 507CBD |
| 2026-07-18estimated | ? | ? | 10:29Z | 14:48Z | 4h 18m | 507CBD |
| 2026-07-16estimated | ? | ? | 04:12Z | 08:39Z | 4h 26m | 507CBD |
| 2026-07-15estimated | ? | ? | 11:29Z | 15:08Z | 3h 39m | 507CBD |
| 2026-07-13estimated | LTCE | LTBQ | 12:09 +03 | 13:22 +03 | 1h 12m | 507CBD |
| 2026-07-09estimated | LTCE | LTBX | 06:58 +03 | 11:26 +03 | 4h 28m | 507CBD |
| 2026-07-08 | LTCE | LTBX | 13:45 +03 | 17:56 +03 | 4h 11m | 507CBD |
| 2026-07-06estimated | LTCE | LTBQ | 12:45 +03 | 14:32 +03 | 1h 47m | 507CBD |
| 2026-07-04 | LTCE | LTBX | 06:51 +03 | 08:16 +03 | 1h 24m | 507CBD |
| 2026-07-02 | LTCE | LTBX | 07:29 +03 | 11:23 +03 | 3h 54m | 507CBD |
| 2026-07-01estimated | LTCE | LTBX | 13:35 +03 | 17:48 +03 | 4h 12m | 507CBD |
| 2026-06-29estimated | LTCE | LTBX | 07:31 +03 | 11:19 +03 | 3h 48m | 507CBD |
| 2026-06-27 | LTCE | LTBX | 07:00 +03 | 10:58 +03 | 3h 57m | 507CBD |
| 2026-06-25estimated | LTCE | LTBQ | 07:43 +03 | 09:02 +03 | 1h 18m | 507CAB |
| 2026-06-24estimated | LTCE | ? | 13:47 +03 | 12:08Z | 1h 20m | 507CB6 |
| 2026-06-22estimated | LTCE | LTBQ | 07:36 +03 | 11:22 +03 | 3h 45m | 507CB6 |
| 2026-06-20estimated | LTCE | LTBQ | 07:58 +03 | 09:10 +03 | 1h 11m | 507CB6 |
| 2026-06-18estimated | LTCE | LTBQ | 07:26 +03 | 08:40 +03 | 1h 13m | 507CB6 |
| 2026-06-15estimated | LTCE | LTBQ | 07:02 +03 | 11:16 +03 | 4h 13m | 507CB6 |
| 2026-06-13estimated | LTCE | LTBQ | 09:55 +03 | 11:06 +03 | 1h 10m | 507CB6 |
| 2026-05-28estimated | LTCE | LTBP | 07:15 +03 | 11:32 +03 | 4h 16m | 507CB6 |
| 2026-05-25estimated | LTCE | LTBQ | 06:38 +03 | 11:34 +03 | 4h 55m | 507CB6 |
| 2026-05-23estimated | LTAR | LTBQ | 11:44 +03 | 12:30 +03 | 0h 46m | 507CB6 |
| 2026-05-21estimated | LTCE | LTBP | 06:55 +03 | 11:38 +03 | 4h 43m | 507CB6 |
| 2026-05-19estimated | LTCE | LTBQ | 09:31 +03 | 01:53 +03 | 16h 21m | 507CB6 |
| 2026-05-11estimated | LTCE | LTBX | 07:06 +03 | 11:20 +03 | 4h 13m | 507CB6 |
| 2026-05-09estimated | LTCE | LTBQ | 07:08 +03 | 08:18 +03 | 1h 09m | 507CB6 |
| 2026-05-07estimated | LTCE | LTBP | 06:58 +03 | 11:49 +03 | 4h 50m | 507CB6 |
| 2026-05-04estimated | LTCE | LTBX | 06:49 +03 | 11:22 +03 | 4h 33m | 507CB6 |
| 2026-05-02estimated | LTCE | LTBX | 06:39 +03 | 10:56 +03 | 4h 16m | 507CB6 |
| 2026-04-25estimated | LTAR | LTBX | 07:27 +03 | 10:52 +03 | 3h 25m | 507C97 |
| 2026-04-20estimated | ? | ? | 04:22Z | 04:58Z | 0h 35m | 507C97 |
| 2026-04-13estimated | ? | ? | 04:12Z | 07:59Z | 3h 47m | 507CC3 |
| 2026-04-11estimated | ? | ? | 04:19Z | 05:00Z | 0h 40m | 507CB3 |
| 2026-04-06estimated | ? | ? | 04:09Z | 04:46Z | 0h 36m | 507C97 |
| 2026-04-04estimated | ? | ? | 03:34Z | 07:50Z | 4h 16m | 507CC3 |
| 2026-04-02estimated | ? | ? | 05:08Z | 08:49Z | 3h 40m | 507C97 |
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.
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]