Skip to content

Has PT5832 landed?

Yes: PT5832 landed at Philadelphia (PHL) between 16:51 and 16:54 UTC on Nov 17 (still settling), after taking off from Wilmington (ILM) between 15:43 and 15:48 UTC on Nov 17. 2 separate flights were observed under this callsign on Nov 17, newest first: landed at Philadelphia (PHL) between 16:51 and 16:54 UTC on Nov 17 (still settling), after taking off from Wilmington (ILM) between 15:43 and 15:48 UTC on Nov 17; took off from Philadelphia (PHL) between 13:33 and 13:35 UTC on Nov 17, landing not observed.

Flights observed on 3 UTC days (Nov 17, Nov 16, and Nov 15), newest first
Date (UTC)FromTook offToLanded
Nov 17Wilmington (ILM)between 15:43 and 15:48 UTC on Nov 17Philadelphia (PHL)between 16:51 and 16:54 UTC on Nov 17 (still settling)
Nov 17Philadelphia (PHL)between 13:33 and 13:35 UTC on Nov 17Not observedNot observed
Nov 16Wilmington (ILM)between 15:37 and 15:38 UTC on Nov 16Philadelphia (PHL)between 16:42 and 16:46 UTC on Nov 16
Nov 16Philadelphia (PHL)between 13:33 and 13:35 UTC on Nov 16Not observedNot observed
Nov 15Not observedNot observedPhiladelphia (PHL)between 16:45 and 16:48 UTC on Nov 15
Nov 15Philadelphia (PHL)between 13:31 and 13:35 UTC on Nov 15Wilmington (ILM)between 14:34 and 14:40 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 PT5832 is on our record, so no delay or on-time verdict can be given.

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