Has OO4234 landed?
Yes: OO4234 landed at Salt Lake City (SLC) between 21:23 and 21:28 UTC on Nov 16, after taking off from Grand Junction (GJT) between 20:40 and 20:42 UTC on Nov 16. 2 separate flights were observed under this callsign on Nov 16, newest first: landed at Salt Lake City (SLC) between 21:23 and 21:28 UTC on Nov 16, after taking off from Grand Junction (GJT) between 20:40 and 20:42 UTC on Nov 16; landed at Grand Junction (GJT) between 19:30 and 19:34 UTC on Nov 16, after taking off from Salt Lake City (SLC) between 18:54 and 18:56 UTC on Nov 16.
| Date (UTC) | From | Took off | To | Landed |
|---|---|---|---|---|
| Nov 16 | Grand Junction (GJT) | between 20:40 and 20:42 UTC on Nov 16 | Salt Lake City (SLC) | between 21:23 and 21:28 UTC on Nov 16 |
| Nov 16 | Salt Lake City (SLC) | between 18:54 and 18:56 UTC on Nov 16 | Grand Junction (GJT) | between 19:30 and 19:34 UTC on Nov 16 |
| Nov 15 | Grand Junction (GJT) | between 20:10 and 20:14 UTC on Nov 15 | Salt Lake City (SLC) | between 20:51 and 20:57 UTC on Nov 15 |
| Nov 15 | Salt Lake City (SLC) | between 18:38 and 18:42 UTC on Nov 15 | Grand Junction (GJT) | between 19:12 and 19:16 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 OO4234 is on our record, so no delay or on-time verdict can be given.
Flights are matched by the callsign the aircraft broadcast (SKW4234), 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.