File / bariloche-1995
The Bariloche Approach
An airliner on final, a town in darkness, and an official report that answered a question nobody had asked
On a night approach into Bariloche, the crew of a scheduled Boeing 727 reported a light that paced the aircraft, stopped, climbed vertically and repositioned ahead of them. The approach was held because the town and the airport had lost power. A second crew, the tower and people on the ground reported the same light.
Official position
The Argentine Air Force investigated and concluded that there was no evidence the object was a craft of unknown origin presenting a concrete risk.
Alternative hypotheses
- An aircraft not shown on the traffic picture, military or otherwise. This fits the pacing and the repositioning, and fits the reported vertical climb far less well.
- A bright celestial object, most plausibly a planet, misjudged for range during a high-workload approach in darkness. This fits a fixed light and fits a light that stops within a few hundred metres of an aircraft much less well.
- Coincidence: an ordinary light source seen during an unrelated power failure, with the two joined together afterwards in the telling.
Why this case is here, and what it is not
Argentina is in this database for a specific reason: the case is a clean example of the commonest strong shape in the whole field. A crew doing a demanding job at night reports something they cannot place, several independent parties report the same thing, and then no instrument recorded any of it.
The multi-channel part is people, not sensors. That is a real strength and a real ceiling at the same time.
What is genuinely strong here
The reports are contemporaneous. The crew reported the light while flying, the tower staff reported it while working the approach, and the press carried both accounts within two days. Nothing here depends on someone remembering an evening thirty years later.
The witnesses were also independent in the sense that matters: they were in different places, doing different jobs, with different views of the sky. A second aircraft holding in the area reported the same object.
The approach itself is documented, because it had to be. The aircraft was held because Bariloche and its airport had lost power. That is an operational fact with a paper trail, separate from anybody’s account of a light.
What must not be presented as measurement
The reported behaviour, a stop within a few hundred metres of the aircraft and a vertical climb, is perceived behaviour. No radar record has been published. Without one, distance is unknown, and without distance every statement about speed, size and manoeuvre is a statement about an assumption. This is the same trap the Sensor Sanity Toolkit exists to demonstrate.
The power failure is the part that gets treated as proof and is not. Two things happening in the same half hour is a coincidence until someone checks the distribution records and shows they were not. Nobody has published that check.
The official position, and why it is unsatisfying
The Air Force conclusion, that there was no evidence of a craft of unknown origin presenting a concrete risk, is not wrong. It is simply an answer to a different question. Whether something posed a risk to aviation and what that something was are separate questions, and only the first was answered.
That gap is the case’s real subject. It is why the file still circulates, and why it resurfaced in 2026 when it was noticed inside a batch of declassified United States material, which transmits the case without adding a single measurement to it.
What would settle it
Primary radar recordings from Bariloche approach control for the period, if any were retained; the full Air Force file rather than its conclusion; and the power distribution log for that night. The first would convert a sighting into a track. The third would turn a coincidence into a correlation or retire it.
← All case files