EES confused twins at Romania's border. What went wrong.

A British woman was stopped and questioned at Cluj-Napoca airport in Romania this spring because EES showed a Schengen entry with no matching exit. The entry belonged to her identical twin sister, who had visited Amsterdam in April 2026 and whose exit had not been properly recorded in the system. Romanian border officers, relying on facial recognition alone, linked the woman’s face to her twin’s open record and accused her of overstaying in the Schengen area. She had never been to the Netherlands.

What EES actually recorded

When the twin visited Amsterdam, EES logged her arrival at Schiphol, capturing her fingerprints, facial image and travel-document data. The problem came on departure. Her exit was not registered, whether through a system error or a crossing point that had not yet completed its EES rollout. That left an open entry record in the EES database: a facial image, fingerprints, and passport data, but no corresponding exit.

When the other twin arrived at Cluj-Napoca weeks later, Romanian officers ran a facial scan. The system returned a match to the open Amsterdam record. Officers interpreted the missing exit as evidence that this person had never left the Schengen area after April, assumed they were dealing with the same individual using a different passport, and escalated to a suspected overstay and possible document irregularity.

Why a fingerprint check would have resolved it immediately

EES collects two biometric identifiers: a facial image and fingerprints. Identical twins share DNA, facial structure, and almost all distinguishing physical features. They do not share fingerprints. Fingerprint patterns form independently in the womb and are unique to each person, including identical twins.

Had Romanian officers run a fingerprint check against the stored record, the mismatch would have been instant. The woman’s fingerprints would not have matched her twin’s enrolled biometric data. The error would have been caught at the desk rather than leading to an extended stop and formal questioning.

Romanian Border Police confirmed the outcome after an internal review. EES itself had worked as designed: the system stored and retrieved the data it was given. The failure was procedural. Officers had not followed all verification steps, specifically the requirement to cross-check fingerprints when flagging a potential overstay. The data was corrected in the system and additional training was issued.

What this reveals about how EES handles facial recognition

The case is unusual. It is the first publicly reported instance of EES linking two people through facial recognition in this way, and it required a specific set of circumstances: identical twins with independent travel histories and an unregistered exit in the system. For the vast majority of travellers, EES will work without incident.

But the case illustrates something important about the system’s design. Facial recognition is one input, not a final determination. The full biometric check, face and fingerprints together, is what EES is built around. Skipping the fingerprint step removes the safeguard that makes the system reliable.

Missing exit records are a separate, known issue in the early months of EES operation. The system became fully operational on 10 April 2026, but the preceding rollout phase involved partial deployment at different crossing points at different times. Some exits from the October 2025 to April 2026 period may not have been captured correctly. That affects the data quality of EES records from the transition period.

What to do if EES shows something incorrect about you

If a border officer raises a discrepancy at the desk, ask them to run a full biometric check including fingerprints, not just a facial scan. Under EU Regulation 2017/2226, EES records can be corrected where data is inaccurate. The responsible authority is the member state whose border agency created the record. You have the right to know what is held and to request correction.

The process for doing this outside a live border encounter is covered in the guide to checking and correcting your EES record. It explains how to submit a data subject access request to the relevant national supervisory authority, what timelines apply, and what to do if a correction is refused.

Does EES have an error-correction route for missing exits?

Yes. If your EES record shows an entry with no exit and you did leave the Schengen area correctly, the member state where the exit should have been recorded can be asked to investigate and correct the file. This may require supporting evidence: a boarding pass, a dated bank transaction from outside Schengen, or a passport stamp from a non-Schengen country if applicable. The process takes time, so it is worth checking your record before you travel again if you suspect an exit was not captured.

For a full explanation of what EES records, how long that data is held and what the EES system is designed to do, the main EES guide covers the detail.