{"id":22017,"date":"2026-08-10T13:21:09","date_gmt":"2026-08-10T13:21:09","guid":{"rendered":"https:\/\/futureknowledge.in\/?p=22017"},"modified":"2026-08-10T13:21:09","modified_gmt":"2026-08-10T13:21:09","slug":"radio-station-falsely-announced-kings-death-then-broadcast-16-minutes-of-silence-as-panicked-presenter-ran-away","status":"publish","type":"post","link":"https:\/\/futureknowledge.in\/?p=22017","title":{"rendered":"Radio station falsely announced King\u2019s death then broadcast 16 minutes of silence as panicked presenter ran away"},"content":{"rendered":"<p>The station said the staff member who played the files had been \u2018reprimanded\u2019 and had \u2018apologised\u2019<\/p>\n<p>I would like to be emailed about offers, events and updates from The Independent. Read our Privacy notice<\/p>\n<p>Radio Caroline has been found to have breached Ofcom rules when it accidentally announced that the King had died.<\/p>\n<p>The Essex broadcaster apologised in May after the messages were played on The Barry Marsh Show, one of which said \u201cwe have suspended our normal programmes until further notice as a mark of respect following the passing of His Majesty King Charles III\u201d.<\/p>\n<p>The messages were followed by the national anthem and around 16 minutes of silence before the presenter apologised for the error.<\/p>\n<p>He said: \u201cI\u2019ve just been informed that we\u2019ve played in error some information a little earlier. I didn\u2019t hear this myself, but it is incorrect, it\u2019s a technical issue, and of course we apologise.\u201d<\/p>\n<p>An Ofcom ruling said that once the presenter realised what he had done, he stopped the files and \u201cpanicked and left the premises\u201d.<\/p>\n<p>The media regulator said it had received two complaints about the broadcast, and said it had breached rules 5.1, requiring that news is reported accurately and impartially, and 5.2, requiring that mistakes in news are acknowledged and corrected on air quickly.<\/p>\n<p>An Ofcom statement read: \u201cWe considered this to have been a very significant inaccuracy about an issue of particular public importance.<\/p>\n<p>\u201cAs outlined above, Radio Caroline did not broadcast an apology and clarification until approximately 30 minutes after the inaccurate announcements were first broadcast.<\/p>\n<p>\u201cWe noted that the Licensee was monitoring the output around the time of the incident and that an engineer was already aware of the issue, but that it took some time to understand what had occurred and reinstate the scheduled programme, with that being exacerbated by the circumstances of the presenter streaming the programme remotely.\u201d<\/p>\n<p>The station said the files that contained the messages were accompanied by \u201ca set of strict instructions to presenters and managers\u201d to follow before playing them, but that a member of staff played them out of curiosity.<\/p>\n<p>Radio Caroline said that they \u201ctook the matter very seriously\u201d, and that they had acted \u201cas soon as possible\u201d.<\/p>\n<p>The station said the staff member who played the files had been \u201creprimanded\u201d and had \u201capologised\u201d, and that in order to prevent a recurrence of this issue, Radio Caroline had removed the relevant files from the desktop on the studio computer.<\/p>\n<p>It also said that its presenters and support staff had been reminded of the relevant procedures.<\/p>\n<p><em>Source: <a href='https:\/\/www.independent.co.uk\/news\/uk\/home-news\/king-charles-death-radio-caroline-announcement-b3030359.html' target='_blank'>Read the original article on www.independent.co.uk<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The station said the staff member who played the files had been \u2018reprimanded\u2019 and had \u2018apologised\u2019 I would like to be emailed about offers, events and updates from The Independent. Read our Privacy notice Radio Caroline has been found to have breached Ofcom rules when it accidentally announced that the King had died. The Essex [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":22018,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-22017","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/futureknowledge.in\/index.php?rest_route=\/wp\/v2\/posts\/22017","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/futureknowledge.in\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/futureknowledge.in\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/futureknowledge.in\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/futureknowledge.in\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=22017"}],"version-history":[{"count":0,"href":"https:\/\/futureknowledge.in\/index.php?rest_route=\/wp\/v2\/posts\/22017\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/futureknowledge.in\/index.php?rest_route=\/wp\/v2\/media\/22018"}],"wp:attachment":[{"href":"https:\/\/futureknowledge.in\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=22017"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/futureknowledge.in\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=22017"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/futureknowledge.in\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=22017"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}