Departure (MH3516 Flight Schedule)
Miri, Malaysia+08 00:00:00 DAY
Arrival (MH3516 Flight Schedule)
+08 00:00:00 DAY
Flight Radar Checker MH 3516
Live Flight Tracker Map
Flight MH3516 from Miri to Lawas is operated by MASKargo. Scheduled time of departure from Miri is 15:00 +08 and scheduled time of arrival in Lawas Airport is 15:45 +08. The duration of the flight is 45 minutes.
Not Rated
Flight Finder
from Lawas to Miri
| Flight | Departure | Arrival |
|---|---|---|
| MH3511 09:00 |
Lawas Airport (LWY) |
Miri (MYY) |
| MH3513 09:50 |
Lawas Airport (LWY) |
Miri (MYY) |
| MH3515 11:20 |
Lawas Airport (LWY) |
Miri (MYY) |
| MH3521 11:20 |
Lawas Airport (LWY) |
Miri (MYY) |
| MH3541 12:10 |
Lawas Airport (LWY) |
Miri (MYY) |
| MH3525 15:50 |
Lawas Airport (LWY) |
Miri (MYY) |
| MH3517 16:50 |
Lawas Airport (LWY) |
Miri (MYY) |
| MH3519 18:10 |
Lawas Airport (LWY) |
Miri (MYY) |
History Flight Information for MH3516 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Fri, 02 May | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Thu, 01 May | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Wed, 30 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Tue, 29 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:20 +08 | 16:05 +08 | |||
| Mon, 28 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Sun, 27 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:30 +08 | 16:15 +08 | |||
| Sat, 26 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Fri, 25 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Thu, 24 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Wed, 23 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Tue, 22 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:20 +08 | 16:05 +08 | |||
| Mon, 21 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Sun, 20 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:30 +08 | 16:15 +08 | |||
| Sat, 19 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Fri, 18 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Thu, 17 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Wed, 16 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Tue, 15 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:20 +08 | 16:05 +08 | |||
| Mon, 14 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Sun, 13 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:30 +08 | 16:15 +08 | |||
| Sat, 12 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Fri, 11 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Thu, 10 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Wed, 09 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Tue, 08 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:20 +08 | 16:05 +08 | |||
| Mon, 07 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Sun, 06 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Sat, 05 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Fri, 04 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 14:50 +08 | 15:35 +08 | |||
| Thu, 03 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Wed, 02 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:00 +08 | 15:45 +08 | |||
| Tue, 01 Apr | MH3516 | Miri (MYY) | Lawas Airport (LWY) | 15:20 +08 | 16:05 +08 | |||
Disclaimer for MH3516 Flight Radar Data
Flight MH3516 from Miri to Lawas Airport data is collected from different sources. The data is for informational purposes only and PlaneMapper is not responsible for the accuracy and reliability of flight MH3516 data.
