Skip to content

Has MQ3933 landed?

Yes: MQ3933 landed at Dallas-Fort Worth (DFW) between 16:39 and 16:45 UTC on Nov 16, after taking off from Waco (ACT) between 16:13 and 16:18 UTC on Nov 16. 3 separate flights were observed under this callsign on Nov 16, newest first: landed at Dallas-Fort Worth (DFW) between 16:39 and 16:45 UTC on Nov 16, after taking off from Waco (ACT) between 16:13 and 16:18 UTC on Nov 16; landed at Waco (ACT) between 15:29 and 15:33 UTC on Nov 16, after taking off from Dallas-Fort Worth (DFW) between 15:05 and 15:08 UTC on Nov 16; landed at Dallas-Fort Worth (DFW) between 03:08 and 03:13 UTC on Nov 16, takeoff not observed.

Flights observed on 3 UTC days (Nov 17, Nov 16, and Nov 15), newest first
Date (UTC)FromTook offToLanded
Nov 16Waco (ACT)between 16:13 and 16:18 UTC on Nov 16Dallas-Fort Worth (DFW)between 16:39 and 16:45 UTC on Nov 16
Nov 16Dallas-Fort Worth (DFW)between 15:05 and 15:08 UTC on Nov 16Waco (ACT)between 15:29 and 15:33 UTC on Nov 16
Nov 16Not observedNot observedDallas-Fort Worth (DFW)between 03:08 and 03:13 UTC on Nov 16
Nov 15Dallas-Fort Worth (DFW)between 15:21 and 15:23 UTC on Nov 15Waco (ACT)between 15:45 and 15:51 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 MQ3933 is on our record, so no delay or on-time verdict can be given.

Flights are matched by the callsign the aircraft broadcast (ENY3933), 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.