Northern Edition

Select Edition

Northern Northern
Southern Southern
Global Global
New Zealand New Zealand
France France

The disciplinary hearing evidence presented by red-carded Beno Obano

Beno Obano leaves the field at Twickenham following his red card (Photo by David Rogers/Getty Images)

The RFU have published the seven-page disciplinary hearing written verdict that confirmed a four-game ban for Beno Obano, a sanction that can be reduced to three if the prop successfully completes tackle school. Last Saturday’s Gallagher Premiership final had stopped in the 22nd minute so that referee Christophe Ridley and his officials could review the collision that had taken place when Bath front-rower Obano tackled Northampton’s Juarno Augustus.

ADVERTISEMENT

Ridley decided that what Obano did with his shoulder to the head of Augustus merited a red card and that left Bath a player short for the remainder of a match they were to lose 21-25 following Alex Mitchell’s converted 73rd-minute try. The sending-off then resulted in a midweek disciplinary hearing chaired by Matthew Weaver with Leon Lloyd and Mitch Read.

At it, Obano admitted an act of foul play but disputed that it reached the red card threshold. “The panel upheld the charge and the player received a four-match ban which will be reduced to three if he makes an application to World Rugby to undertake the coaching intervention programme (CIP).”

Video Spacer

URC Head of Match Officials Tappe Henning reveals some stunning red-card statistics

Video Player is loading.
Current Time 0:00
Duration 4:58
Loaded: 0%
Stream Type LIVE
Remaining Time 4:58
 
1x
    • Chapters
    • descriptions off, selected
    • captions off, selected
    • en (Main), selected
    Video Spacer

    URC Head of Match Officials Tappe Henning reveals some stunning red-card statistics

    The RFU statement announcing the ban was accompanied by the written disciplinary verdict which included the evidence presented at the hearing by Obano. It read: “The player firstly expressed his regret at the incident and was plainly remorseful. He accepted that his actions amounted to foul play and did not seek to dispute that he made direct contact with the opposition player’s, Juarno Augustus (JA), neck/chin area.

    “He confirmed that, on reflection, he would have wanted the tackle to be better executed but when questioned by the panel on the specifics of what he would do differently, he was extremely honest and confirmed that whilst there is, in his view, no ‘perfect tackle’, he did not consider that he could or should have done anything differently. That said, he was clear that he regretted the outcome of the tackle.

    Penalties

    13
    Penalties Conceded
    10
    0
    Yellow Cards
    0
    0
    Red Cards
    1

    “The player described the build-up to the tackle and the tackle itself. He confirmed that he was chasing a kick off and was moving at speed. He saw JA catch the ball and evade a tackler to the player’s inside. It was clear at that stage, that JA was running towards the player.

    “As such, the player described that he ‘put the brakes on’ and dropped his height by bending at the knees and hips and also through the back. As a result of lowering his height in this way, the player was looking at JA ‘through his eyebrows’.

    ADVERTISEMENT

    “He observed that JA was upright and his intention was to make contact with the ball when making his tackle. He recalled targeting the ball, dropping his head to make the tackle and then realising that he had made contact with something other than the ball, at which point he began to attempt to reduce his momentum.

    “The player confirmed that his last sighting of JA before the tackle was JA in an upright position and recalled thinking that he could not attempt to tackle JA’s legs as they were too far in front of the player.

    “Had the player attempted to tackle JA’s legs, he concluded that he would have had to have been off his own feet, making the tackle reckless. He stated that his movement in the tackle was forward rather than upwards. 14. After the match, the player shook hands with the opposition players including JA.”

    A summary of the evidence presented at the hearing by referee Ridley was also included in the written verdict. “The referee’s evidence was that he considered, as he always does, the various factors concerning head contact, namely whether there was head contact; whether there was foul play; and any mitigation. He was of the view that whilst the player was low, he was not low enough and could have dropped his height further to make the tackle legal.

    ADVERTISEMENT

    “As such, he concluded that there was foul play. He then considered mitigation and concluded that the player had a clear line of sight to JA prior to the tackle and that there had been no sudden and significant drop in height on the part of JA or any significant change in the dynamics of the incident.

    “He was specifically asked whether he considered the height of the tackler when making his assessment and he confirmed that he did, as part of his assessment as to whether the head contact was avoidable and, therefore, whether the tackle was an act of foul play.

    “When asked about his comments at the time of the player ‘hitting up’ in the tackle, he confirmed that he had identified this but, on reflection, now considered this to be an irrelevant consideration as the key question for him was whether the player started at a height which rendered the tackle an act of foul play.

    “The referee was cross-examined by the player’s counsel on whether he took account of the player’s attempts to lower his body height. Whilst the referee did not initially identify the tackler’s height as a relevant mitigation consideration, he confirmed that he considered all circumstances of the tackle when arriving at this decision to issue the red card and that he was familiar with the World Rugby head contact process guidelines (the HCP guidelines), having viewed them ‘more than one hundred times’.

    “When it was put to the referee that he did not take account of the player’s attempt to lower his body height when assessing mitigation, the referee stated that he always considers all mitigation factors whether or not he expresses that in his conversation with the TMO and other match officials. His ultimate aim is to establish to what extent the dangerous tackle was avoidable.”

    ADVERTISEMENT

    Boks Office | Episode 39 | The Investec Champions Cup is back

    Argentina v France | HSBC SVNS Hong Kong 2025 | Men's Match Highlights

    New Zealand v Australia | HSBC SVNS Hong Kong 2025 | Women's Match Highlights

    Tokyo Sungoliath vs Shizuoka BlueRevs | Japan Rugby League One 2024/25 | Full Match Replay

    Reds vs Force | Super Rugby W 2025 | Full Match Replay

    The Rise of Kenya | The Report

    New Zealand in Hong Kong | Brady Rush | Sevens Wonders | Episode 4

    The Fixture: How This Rugby Rivalry Has Lasted 59 Years

    Trending on RugbyPass

    Comments

    0 Comments
    Be the first to comment...

    Join free and tell us what you really think!

    Sign up for free
    ADVERTISEMENT

    Latest Features

    Comments on RugbyPass

    C
    ChristelLoewe 12 minutes ago
    Waratahs turn to 'tough bugger' for captaincy with more history on the line

    REACH OUT TO TECH CYBER FORCE RECOVERY FOR A GREAT JOB

    WhatsApp +15617263697

    Fine wine and crypto do not always blend well, especially after a few drinks. I learned this the hard way after a record harvest at my vineyard. Swirling an old Cabernet under the stars, I was a financial connoisseur, my $720,000 Bitcoin wallet aging well for future returns. But the next morning, with a hangover as intense as my Merlion, I realized I'd forgotten my wallet password. Even worse, my recovery phrase, which I'd written down in my wine cellar notebook, had vanished. My eager new assistant had tidied up, mistaking my scribbled security notes for wine tasting spillage, and donated the entire book to the recycling gods. I dove into the garbage cans like a desperate sommelier searching for a quality grape but came up with broken dreams and soggy cardboard. Panic set in faster than cork taint. I faced the bitter truth: my digital fortune was bottled up tighter than a corked bottle with no opener. I sank into denial, questioning whether my future vineyard expansion would now be reduced to selling boxed wine. I panicked, pored over industry publications, and came across a wine industry newsletter that mentioned Tech Cyber Force Recovery. Their slogan, something playful about "decanting lost crypto," seemed like a sign from God. I contacted them, half-expecting snobbery or skepticism. What I received instead were tech wizards who tackled my case with humor and precision. Their team labored over my case like veteran sommeliers dissecting terroir. They painstakingly reconstructed transaction flows, timestamp records, and subtle wallet behavior. It was as if I was watching wine connoisseurs sniff out hints of blackcurrant and oak, but with algorithms and blockchain forensics. Each day, they provided updates with the finesse of tasting notes. “We’re detecting progress, notes of potential access, hints of password recovery on the finish.” Their creativity lightened my anxiety, and ten days later, they uncorked my digital vault. When I saw my Bitcoin balance restored, I nearly opened a bottle of my best vintage at 9 AM. My assistant and I shared a hearty laugh; he's still working for me, but now he labels my ledgers with "DO NOT TOUCH" in bold. My wine business is thriving thanks to Tech Cyber Force Recovery, and I have a new rule: passwords before Pinot. Cheers to their genius!

    0 Go to comments
    C
    ChristelLoewe 1 hour ago
    Don't get out over your skis on the Highlanders

    REACH OUT TO TECH CYBER FORCE RECOVERY FOR A GREAT JOBWhatsApp +15617263697Fine wine and crypto do not always blend well, especially after a few drinks. I learned this the hard way after a record harvest at my vineyard. Swirling an old Cabernet under the stars, I was a financial connoisseur, my $720,000 Bitcoin wallet aging well for future returns. But the next morning, with a hangover as intense as my Merlion, I realized I'd forgotten my wallet password. Even worse, my recovery phrase, which I'd written down in my wine cellar notebook, had vanished.My eager new assistant had tidied up, mistaking my scribbled security notes for wine tasting spillage, and donated the entire book to the recycling gods. I dove into the garbage cans like a desperate sommelier searching for a quality grape but came up with broken dreams and soggy cardboard.Panic set in faster than cork taint. I faced the bitter truth: my digital fortune was bottled up tighter than a corked bottle with no opener. I sank into denial, questioning whether my future vineyard expansion would now be reduced to selling boxed wine.I panicked, pored over industry publications, and came across a wine industry newsletter that mentioned Tech Cyber Force Recovery. Their slogan, something playful about "decanting lost crypto," seemed like a sign from God.I contacted them, half-expecting snobbery or skepticism. What I received instead were tech wizards who tackled my case with humor and precision. Their team labored over my case like veteran sommeliers dissecting terroir. They painstakingly reconstructed transaction flows, timestamp records, and subtle wallet behavior. It was as if I was watching wine connoisseurs sniff out hints of blackcurrant and oak, but with algorithms and blockchain forensics.Each day, they provided updates with the finesse of tasting notes. “We’re detecting progress, notes of potential access, hints of password recovery on the finish.” Their creativity lightened my anxiety, and ten days later, they uncorked my digital vault.When I saw my Bitcoin balance restored, I nearly opened a bottle of my best vintage at 9 AM. My assistant and I shared a hearty laugh; he's still working for me, but now he labels my ledgers with "DO NOT TOUCH" in bold.My wine business is thriving thanks to Tech Cyber Force Recovery, and I have a new rule: passwords before Pinot. Cheers to their genius!

    4 Go to comments
    S
    Steven Bullock 1 hour ago
    Six Nations: 5 things we've learned from half-way point weekend

    My wife won’t let me make love to her without the use of protection (condom) this has been going on for over 3 years ever since we got married and I have been worried about this cause she won’t let us make babies, a friend of mine referred me to a hacker to hack into her phone to know the root and why she won’t let me make love to her without protection so I hired darkhatthacker@gmail.com When the phone hack was successfully done I had access to her phone, from her WhatsApp to her text messages and also deleted messages then I saw that my wife has been having an affair with someone else and planning on relocating with the man, also she is getting married to him in few months time that’s why she has been avoiding getting pregnant for me. I cried my eyes out because I loved and respected her but all thanks to my friend for referring me to someone like darkhatthacker@gmail.com This hacker did a great job for me even till now my wife doesn’t know I know all her plans.

    5 Go to comments
    H
    HarunParisha 2 hours ago
    Sale Sharks refuse to give up on new stadium dream

    It's a fact: Reddit has always been, is, and will be my source for crypto discussions, security tips, and market trends. Little did I know it would be the same site that helped save me from financial ruin. Some months ago, an AMA thread about Trust Geeks Hack Expert showed up. People asked them anything: from lost wallet recoveries to phishing scams; their answers sounded really detailed, transparent, and full of insight. At the time, I didn't know that their help was near. It all started with what I thought was a routine software update. I had received an e-mail from what looked like a trusted exchange, telling me to install an important patch. The email looked *legit—*matching the branding, formatting, and even the usual tone of messages I had received before. Without a second thought, I downloaded the update and installed it. Biggest mistake of my life. It froze within minutes, and then it automatically restarted. My crypto wallet was empty when I regained access. $200,000-gone. At first, I thought it was some kind of glitch, but as I dug deeper, the cold reality hit me hard: I had been hacked. The "update" was a form of malware designed to drain wallets by injecting malicious code. Panic set in, but rather than spiral, I remembered the Trust Geeks Hack Expert AMA. Their confidence in handling cases like mine had stood out to me. I rushed back to the thread, found their contact details Website https://trustgeekshackexpert.com/-- Email: trustgeekshackexpert{@}fastservice{.}com, and reached out immediately. Their response was prompt and very reassuring. They asked for every little detail I could remember-from the time of the installation of the fake update to the exact nature of the transactions I had done prior to this. They got to work, tracing the movement of my stolen funds using some advanced blockchain forensics.

    Days went by, and I had my doubts, but they kept me updated. Then came a message that I was praying for; they had recovered my $200,000. It sounded like a dream come true. All stress, regret, and anger vanished at that moment. Trust Geeks Hack Expert saved not only my funds but also taught me a lesson which will never be forgotten: never trust email links. Now, I double-check every update; use cold storage for large amounts; don't click on anything that's remotely suspicious. If not for that Reddit AMA, I would have never found the only team skilled enough to turn my disaster into a comeback story.

    0 Go to comments
    LONG READ
    LONG READ Why NZR's Ineos settlement may be the most important victory they'll enjoy this year Why NZR's Ineos settlement may be the most important victory they'll enjoy this year
    Search