Skip to content

Has OO3736 landed?

Yes: OO3736 landed at Seattle (SEA) between 21:34 and 21:38 UTC on Nov 16, after taking off from San Jose (SJC) between 19:58 and 20:01 UTC on Nov 16. 2 separate flights were observed under this callsign on Nov 16, newest first: landed at Seattle (SEA) between 21:34 and 21:38 UTC on Nov 16, after taking off from San Jose (SJC) between 19:58 and 20:01 UTC on Nov 16; landed at San Jose (SJC) between 18:55 and 19:00 UTC on Nov 16, after taking off from Seattle (SEA) between 16:59 and 17:02 UTC on Nov 16.

Flights observed on 3 UTC days (Nov 17, Nov 16, and Nov 15), newest first
Date (UTC)FromTook offToLanded
Nov 16San Jose (SJC)between 19:58 and 20:01 UTC on Nov 16Seattle (SEA)between 21:34 and 21:38 UTC on Nov 16
Nov 16Seattle (SEA)between 16:59 and 17:02 UTC on Nov 16San Jose (SJC)between 18:55 and 19:00 UTC on Nov 16
Nov 15San Jose (SJC)between 20:04 and 20:07 UTC on Nov 15Seattle (SEA)between 21:41 and 21:45 UTC on Nov 15
Nov 15Seattle (SEA)between 16:59 and 17:02 UTC on Nov 15San Jose (SJC)between 19:01 and 19:05 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 OO3736 is on our record, so no delay or on-time verdict can be given.

Flights are matched by the callsign the aircraft broadcast (SKW3736), 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: OO3737, OO3739, OO3740, OO3743, OO3744, OO3745, OO3747, OO3749