Has OO5005 landed?
Yes: OO5005 landed at Chicago (ORD) between 23:05 and 23:09 UTC on Nov 16, after taking off from Cleveland (CLE) between 22:15 and 22:19 UTC on Nov 16. 2 separate flights were observed under this callsign on Nov 16, newest first: landed at Chicago (ORD) between 23:05 and 23:09 UTC on Nov 16, after taking off from Cleveland (CLE) between 22:15 and 22:19 UTC on Nov 16; landed at Cleveland (CLE) between 20:55 and 21:02 UTC on Nov 16, after taking off from Chicago (ORD) between 20:04 and 20:07 UTC on Nov 16.
| Date (UTC) | From | Took off | To | Landed |
|---|---|---|---|---|
| Nov 16 | Cleveland (CLE) | between 22:15 and 22:19 UTC on Nov 16 | Chicago (ORD) | between 23:05 and 23:09 UTC on Nov 16 |
| Nov 16 | Chicago (ORD) | between 20:04 and 20:07 UTC on Nov 16 | Cleveland (CLE) | between 20:55 and 21:02 UTC on Nov 16 |
| Nov 15 | Cleveland (CLE) | between 23:58 UTC on Nov 15 and 00:01 UTC on Nov 16 | Chicago (ORD) | between 00:53 and 00:59 UTC on Nov 16 |
| Nov 15 | Chicago (ORD) | between 22:07 and 22:08 UTC on Nov 15 | Cleveland (CLE) | between 22:56 and 22:59 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 OO5005 is on our record, so no delay or on-time verdict can be given.
Flights are matched by the callsign the aircraft broadcast (SKW5005), 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: OO5006, OO5007, OO5008, OO5009, OO5010, OO5012, OO5013, OO5014