Has OO3144 landed?
Yes: OO3144 landed at San Diego (SAN) between 20:34 and 20:37 UTC on Nov 16, after taking off from Phoenix (PHX) between 19:40 and 19:43 UTC on Nov 16. 2 separate flights were observed under this callsign on Nov 16, newest first: landed at San Diego (SAN) between 20:34 and 20:37 UTC on Nov 16, after taking off from Phoenix (PHX) between 19:40 and 19:43 UTC on Nov 16; landed at Phoenix (PHX) between 18:08 and 18:13 UTC on Nov 16, after taking off from San Diego (SAN) between 17:20 and 17:23 UTC on Nov 16.
| Date (UTC) | From | Took off | To | Landed |
|---|---|---|---|---|
| Nov 16 | Phoenix (PHX) | between 19:40 and 19:43 UTC on Nov 16 | San Diego (SAN) | between 20:34 and 20:37 UTC on Nov 16 |
| Nov 16 | San Diego (SAN) | between 17:20 and 17:23 UTC on Nov 16 | Phoenix (PHX) | between 18:08 and 18:13 UTC on Nov 16 |
| Nov 15 | Phoenix (PHX) | between 19:10 and 19:13 UTC on Nov 15 | San Diego (SAN) | between 20:01 and 20:06 UTC on Nov 15 |
| Nov 15 | San Diego (SAN) | between 16:15 and 16:17 UTC on Nov 15 | Phoenix (PHX) | between 17:04 and 17:08 UTC on Nov 15 |
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 for OO3144 is on our record, so no delay or on-time verdict can be given.
Flights are matched by the callsign the aircraft broadcast (SKW3144), 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: OO3146, OO3148, OO3150, OO3151, OO3152, OO3153, OO3155, OO3156