Skip to content

Has OO3861 landed?

Yes: OO3861 landed at Minneapolis (MSP) between 00:23 and 00:27 UTC on Nov 17, after taking off from Appleton (ATW) between 23:37 and 23:43 UTC on Nov 16. 3 separate flights were observed under this callsign on Nov 16, newest first: landed at Minneapolis (MSP) between 00:23 and 00:27 UTC on Nov 17, after taking off from Appleton (ATW) between 23:37 and 23:43 UTC on Nov 16; took off from Minneapolis (MSP) between 21:29 and 21:32 UTC on Nov 16, landing not observed; landed at Minneapolis (MSP) between 00:49 and 00:53 UTC on Nov 16, after taking off from Appleton (ATW) between 00:06 and 00:08 UTC on Nov 16.

Flights observed on 3 UTC days (Nov 17, Nov 16, and Nov 15), newest first
Date (UTC)FromTook offToLanded
Nov 16Appleton (ATW)between 23:37 and 23:43 UTC on Nov 16Minneapolis (MSP)between 00:23 and 00:27 UTC on Nov 17
Nov 16Minneapolis (MSP)between 21:29 and 21:32 UTC on Nov 16Not observedNot observed
Nov 16Appleton (ATW)between 00:06 and 00:08 UTC on Nov 16Minneapolis (MSP)between 00:49 and 00:53 UTC on Nov 16
Nov 15Minneapolis (MSP)between 22:29 and 22:33 UTC on Nov 15Appleton (ATW)between 23:11 and 23:16 UTC on Nov 15
Nov 15Appleton (ATW)between 00:44 and 00:46 UTC on Nov 15Minneapolis (MSP)between 01:24 and 01:28 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 OO3861 is on our record, so no delay or on-time verdict can be given.

Flights are matched by the callsign the aircraft broadcast (SKW3861), 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: OO3862, OO3863, OO3864, OO3865, OO3866, OO3867, OO3869, OO3870