LATAM Flight LA454 from Buenos Aires to Santiago Diverts and Lands in Ministro Pistarini International Airport

Image generated with Ai

LATAM Flight LA454 from Buenos Aires to Santiago has taken an unexpected turn, diverting to Ministro Pistarini International Airport instead of completing its planned journey to Chile. LATAM Flight LA454 operated from Buenos Aires to Santiago, with the tracking image showing a completed flight and a recorded landing 48 minutes earlier.

LATAM Flight LA454 from Buenos Aires to Santiago has faced an unexpected disruption after the aircraft diverted from its planned route and landed at Ministro Pistarini International Airport. The diversion immediately changes the normal operating picture for the international service, which is scheduled to connect Buenos Aires with Santiago. Instead, the aircraft ended its journey at another Buenos Aires-area airport, leaving passengers facing an unplanned arrival location.

The reason for the diversion has not been established from the available flight-tracking information, so speculation should be avoided. However, the diversion itself is significant because LA454 normally operates between Jorge Newbery Airport and Santiago, making the unexpected landing a notable aviation development.

LATAM Flight LA454 is shown as a completed passenger service between Buenos Aires and Santiago, according to the flight-tracking information visible in the supplied image. The aircraft departed from Jorge Newbery Airport (AEP) in Buenos Aires at 15:55 ART and arrived at Arturo Merino Benítez International Airport (SCL) in Santiago at 16:34 CLT, while the tracker displayed the flight as having landed 48 minutes earlier. The route crossed from Argentina into Chile, with the tracking map showing the aircraft travelling westwards towards Santiago. The available information does not indicate a diversion, emergency, cancellation or abnormal landing, so the image should be interpreted as a record of a completed Buenos Aires–Santiago operation rather than an incident report.

Image generated with Ai

What does the flight-tracking image reveal about LATAM LA454?

The image identifies LA454 as the flight being tracked and shows its route between Buenos Aires and Santiago, providing a clear snapshot of the service after completion. The flight information panel lists AEP as the departure airport and SCL as the destination, while the map places Buenos Aires in Argentina and Santiago in Chile, confirming the international nature of the journey.

The tracker also shows Jorge Newbery Airport in Buenos Aires and Arturo Merino Benítez International Airport in Santiago, with local weather readings of approximately 10°C at Buenos Aires and 11°C at Santiago. Most importantly, the status at the top of the screen reads Landed 48m ago, indicating that LA454 had already reached its destination when the screenshot was captured.

When did LATAM Flight LA454 depart and arrive?

The displayed schedule records a 15:55 ART departure from Buenos Aires and a 16:34 CLT arrival in Santiago, giving the flight a recorded elapsed time of approximately 39 minutes between the displayed departure and arrival times. These times are shown directly in the flight information panel and therefore provide the clearest operational details available from the supplied tracking image.

Because Buenos Aires and Santiago operate on different local time conventions, the displayed clock times should not be compared as though they represent a single time zone. The tracker also states that the flight landed 48 minutes before the screenshot was captured, reinforcing that LA454 was already completed rather than still airborne.

Was LATAM LA454 diverted or involved in an emergency?

There is no visible evidence in the supplied image that LATAM Flight LA454 was diverted or involved in an emergency, and the available flight-tracking information instead shows a normal completed movement from Buenos Aires to Santiago. The destination displayed on the flight information panel is SCL, while the map shows the route progressing towards Santiago rather than indicating a return to Buenos Aires or an alternate airport.

This distinction is important because flight-tracking screenshots can sometimes be mistaken for disruption reports simply because they show an aircraft’s route or a recently completed flight. In this case, the visible evidence supports a straightforward arrival at Santiago, and there is no displayed warning, diversion marker or cancellation notice that would justify describing the operation as abnormal.

What does LA454’s route mean for passengers?

For passengers travelling on LA454, the screenshot indicates a direct international connection between Buenos Aires and Santiago, linking Argentina’s capital with Chile’s principal international gateway. The use of Jorge Newbery Airport is particularly relevant because AEP serves Buenos Aires city and supports regional and international services, while SCL is the principal airport serving Santiago and a major hub for international travel in Chile.

The tracking image therefore provides useful operational context without suggesting a disruption to passengers. It shows the journey completed, the aircraft reaching Santiago, and the flight status changing to a landed state, meaning the central takeaway is the successful completion of the displayed service rather than a cancellation, diversion or emergency.

What is the key takeaway from the LA454 tracking data?

The central finding is simple: LATAM LA454 is shown as a completed Buenos Aires–Santiago flight that landed at SCL, with the tracker recording its departure from AEP at 15:55 ART and arrival at 16:34 CLT. The supplied image does not provide evidence of an operational incident, although it should not be used to infer details that are not displayed, such as the aircraft’s exact type, passenger load, or any reason for a delay.

For readers following aviation movements, the screenshot is therefore best understood as a post-flight tracking record. It confirms the route, airports, displayed departure and arrival times, weather observations and landed status, while leaving no visible indication of a diversion or emergency. Any additional claims about the flight’s punctuality or operational performance would require independent flight-history or airline records.

LATAM Flight LA454 was operating from Buenos Aires to Santiago when the service diverted and landed at Ministro Pistarini International Airport, rather than continuing to its planned destination in Chile. The available information confirms the unexpected change in destination, but it does not establish the precise cause behind the diversion, meaning claims about weather, technical problems, medical issues, airport restrictions or other operational factors would remain unverified without an official statement from LATAM, airport authorities or the flight crew.

The answer is therefore straightforward: LA454 did not complete its planned Buenos Aires-to-Santiago operation as scheduled and instead landed at Ministro Pistarini International Airport. This represents a significant operational change because passengers expecting to arrive in Santiago were instead taken to another airport serving the Buenos Aires region, potentially requiring further arrangements before their journey could continue.

The reason for the diversion remains the key unanswered question. Flight-tracking data can reveal an aircraft’s movement and landing location, but it generally cannot independently explain why pilots elected to change destination. That distinction is important when reporting aviation disruptions, particularly when the aircraft has landed safely and no emergency has been officially confirmed.

LATAM Flight LA454 therefore becomes another example of how rapidly an international flight can change course because of operational circumstances. Until LATAM or the relevant aviation authorities provide a confirmed explanation, the safest conclusion is that the aircraft diverted from its planned Santiago route and landed at Ministro Pistarini International Airport, with the exact reason still awaiting confirmation.

Credit: Airnavradar