Church of England leader who married Harry and Meghan steps down following pedophile scandal

Archbishop Justin Welby takes responsibility for mishandling abuse reports linked to church camps.


Pop Culture & Art November 13, 2024
Courtesy: Reuters

Archbishop of Canterbury Justin Welby, the head of the Church of England and the global Anglican Communion, announced his resignation on Tuesday following intense criticism over his handling of abuse allegations within the church. 

Welby, who officiated the wedding of Prince Harry and Meghan Markle and led the coronation of King Charles III, will step down after the Makin Report revealed how the church mishandled abuse allegations against the late John Smyth, a former church-camp operator who reportedly sexually abused up to 130 boys in Britain and Africa.

In a statement, Welby expressed deep regret, saying, “It is very clear that I must take personal and institutional responsibility for the long and re-traumatizing period between 2013 and 2024.” 

He added that he had initially been informed of the allegations in 2013 and was told police had been notified. “I believed wrongly that an appropriate resolution would follow,” Welby said, reflecting on his initial decision to trust the process rather than take further action.

The Makin Report, an independent investigation into Smyth’s abuses, released last Friday, ignited public outcry and exposed what Welby described as “the long-maintained conspiracy of silence about the heinous abuses.” 

Although Smyth passed away in 2018, the report’s findings have rocked the church, revealing the extent of the abuse against young boys and the institution’s failure to act decisively.

While Welby initially stated he would not resign, mounting pressure over the weekend led him to change course. 

His office confirmed that “precise timings” for his departure would be shared after a review of his remaining obligations.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ