My client David Farrington was at the London City Airport in September 2016. He was booked on a British Airways flight to Amsterdam, where he was scheduled to meet his girlfriend.
As he proceeded to board the aircraft, he was stopped and detained by four Police Officers from the Metropolitan Police.
He was advised that he was under arrest as a result of an outstanding warrant issued by Lewes Crown Court in August for failing to appear in respect of breach proceedings linked to the imposition of a community order.
David immediately made it clear to the Officers that he had no knowledge of the warrant and that they had the wrong man.
Despite his protestations he was handcuffed and removed from the airport in the presence of fellow holiday makers and airport staff, a humiliating experience.
He was later transferred into custody at Barking and Dagenham Custody Centre.
Following his arrival into Police custody, David was able to notify his parents that he was under arrest. David’s parents made enquiries at Lewes Crown Court and established that the only information which had been contained on the warrant was the name, date of birth and address of the wanted man.
The real offender bore a similar, but not identical, name to David: the offender was David Farrington, whereas my client was David Charles Farrington.
David’s parents were able to demonstrate, by the production of identification, that their son was not the offender.
Following investigation, it transpired that details of the warrant had been entered onto the Police National Computer (PNC) by Sussex Police. Sadly, David’s personal details, as opposed to the actual offender’s were entered onto the system.
Eventually, Sussex Police were able to furnish the Metropolitan Police with a photograph of the real offender, together with details of his fingerprints and after 8 and a half hours, David was finally released from Police custody.
I pursued a claim on behalf of David and he recovered £6,000 in compensation plus his legal fees.
My client’s name has been changed.
You must be logged in to post a comment.