Skip to content

Has MQ3340 landed?

Yes: MQ3340 landed at Chicago (ORD) between 18:18 and 18:22 UTC on Nov 16, after taking off from Nashville (BNA) between 17:06 and 17:10 UTC on Nov 16. 2 separate flights were observed under this callsign on Nov 16, newest first: landed at Chicago (ORD) between 18:18 and 18:22 UTC on Nov 16, after taking off from Nashville (BNA) between 17:06 and 17:10 UTC on Nov 16; landed at Nashville (BNA) between 15:42 and 15:48 UTC on Nov 16, after taking off from Chicago (ORD) between 14:40 and 14:42 UTC on Nov 16.

Latest position report, at 14:43 UTC: altitude 3,269 m (10,725 ft), ground speed 573 km/h (309 kn), at 41.67° N, 87.89° W.

Flights observed on 3 UTC days (Nov 17, Nov 16, and Nov 15), newest first
Date (UTC)FromTook offToLanded
Nov 16Nashville (BNA)between 17:06 and 17:10 UTC on Nov 16Chicago (ORD)between 18:18 and 18:22 UTC on Nov 16
Nov 16Chicago (ORD)between 14:40 and 14:42 UTC on Nov 16Nashville (BNA)between 15:42 and 15:48 UTC on Nov 16
Nov 15Nashville (BNA)between 17:53 and 17:55 UTC on Nov 15Chicago (ORD)between 19:05 and 19:10 UTC on Nov 15
Nov 15Chicago (ORD)between 14:55 and 14:59 UTC on Nov 15Nashville (BNA)between 16:03 and 16:06 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 MQ3340 is on our record, so no delay or on-time verdict can be given.

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