Origin and destination
Understand where a tracked flight is coming from and where it is headed.
Central Aviation Tracking
Find the aircraft first, then inspect its available track and route details. An observed trail shows reported positions; it does not by itself confirm the destination or the full planned route.
Understand where a tracked flight is coming from and where it is headed.
Follow the aircraft within the wider traffic picture.
Keep route information, nearby traffic and weather accessible from one workspace.
Start with the flight identifier and travel date, or use a confirmed tail number for a particular aircraft. Then compare the available origin and destination with the airports you expect. City names alone may refer to more than one airport. CAT’s map is not a complete timetable of every flight between a pair of cities.
A trail connects available aircraft observations and can have gaps. Origin or destination details depend on a matching route source; when those details are absent, do not infer them from the aircraft’s heading or the nearest airport. A straight line between airports is not a flown track or a filed flight plan.
Scheduled, estimated and actual times describe different events. Confirm operational changes with the airline, aircraft operator or airport rather than treating map movement as a cancellation or arrival notice.
For a journey between Orlando International and St. Louis Lambert, use the airport pair MCO/KMCO and STL/KSTL. Open the Orlando airport tracker and the St. Louis airport tracker, then locate your specific flight in CAT using its identifier. This helps distinguish your flight from other aircraft near either airport; it does not imply a particular service is operating today.
Use the arrivals and departures guide to interpret airport-area traffic. For a known airframe rather than a city pair, use aircraft tracking.