Has ET3505 landed?
Yes: ET3505 landed at Muscat (MCT) between 16:19 and 16:22 UTC on Nov 19, after taking off from Lagos (LOS) between 08:50 and 08:54 UTC on Nov 19.
| Date (UTC) | From | Took off | To | Landed |
|---|---|---|---|---|
| Nov 19 | Lagos (LOS) | between 08:50 and 08:54 UTC on Nov 19 | Muscat (MCT) | between 16:19 and 16:22 UTC on Nov 19 |
| Nov 18 | Santiago (SCL) | between 21:30 and 21:32 UTC on Nov 18 | Lagos (LOS) | between 07:06 and 07:11 UTC on Nov 19 |
| Nov 15 | Lagos (LOS) | between 13:13 and 13:14 UTC on Nov 15 | Muscat (MCT) | between 20:43 and 20:48 UTC on Nov 15 |
| Nov 15 | Santiago (SCL) | between 01:50 and 01:54 UTC on Nov 15 | Lagos (LOS) | between 11:30 and 11:33 UTC on Nov 15 |
| Nov 12 | Lagos (LOS) | between 18:58 and 19:01 UTC on Nov 12 | Muscat (MCT) | between 02:35 and 02:40 UTC on Nov 13 |
| Nov 12 | Santiago (SCL) | between 07:54 and 07:57 UTC on Nov 12 | Lagos (LOS) | between 17:33 and 17:36 UTC on Nov 12 |
How these times were observed
These takeoffs and landings were read off the aircraft’s own position reports, broadcast by its transponder. Each happened somewhere between two reports, so every time is shown as an interval in UTC, never as one exact minute.
No schedule is linked to these observed movements of ET3505, so no delay or on-time verdict can be given.
Flights are matched by the callsign the aircraft broadcast (ETH3505), not by an airline timetable or a ticket.
A time marked “still settling” is recent: a later position report can still narrow it, change its airport or withdraw it.
More flights of the same airline observed landing recently: ET3516, ET3605, ET3612, ET3613, ET3618, ET3619, ET3623, ET3638