At 9.28 AM on April 22, 2022, a travel content writer posted a presentation about the whereabouts of his lost luggage on Twitter when he found that the AerLingus airline, which operates in Ireland, had not picked up the luggage from Frankfurt.
The presentation was posted on Twitter as a video, which the passenger introduced by saying, “Perhaps this will help you find my bag, which you’ve lost and given to the wrong person.”
The video presentation explains the journey from Frankfurt to London Heathrow through Dublin. With three bags at Frankfurt airport, he said, “the bags were close to being boarded”, as he could see that they moved right next to them but weren’t loaded. He thought they would be put on another flight for him to collect later in the day.
However, only two were returned to him after 10 pm the following day; one of the bags did not reach the right destination.
It seems that the luggage, as quoted by @AviosAdventurer (Twitter Feed Video), “has gone walkabout: it’s ended up in Pimlico in London.”
The video can be watched at the above link.
The possibility of knowing the lost luggage’s whereabouts is possible due to a tracking device installed, allowing you to see the location of the missing luggage in real-time. In the presentation, with real-time justification, the passenger explained that he could see the luggage’s live location. He told Aer Lingus ‘multiple times’ where it was and that the airline’s response was ‘not good enough.’
A screenshot of a map and the exterior of a building has been shown to give the missing luggage’s whereabouts as to a detailed location: pinned to a street address in the Pimlico London area.
He is using this to claim that the luggage has been given to the wrong person and has been poorly kept up to date about the luggage’s whereabouts or whether he will receive it.
As of today, since April 22, 2022, we haven’t heard a response about the luggage’s whereabouts or whether he will receive it from Aer Lingus.
For more updates on the lost luggage, you can log in on Twitter and see whether the issue has been resolved.
