David Pocock Cited (After Chiefs Super Rugby Match)

The following is a Media Release from SANZAAR.

David Pocock Cited.

Player: David Pocock
Team: Brumbies
Position: Flanker
Date of Incident: 2 April 2016
Nature of Offence: Law10.4 (e) Playing a player without the ball is dangerous play. Law 10.4 (m) Acts contrary to good sportsmanship
Elapsed time in match when incident occurred: 74 minute

David Pocock Cited (After Chiefs Super Rugby Match)

David Pocock of the Brumbies has been cited for alleged foul play during a Super Rugby match at the weekend.

Pocock is alleged to have contravened  Law 10.4 (e) Playing a player without the ball is dangerous play, and Law 10.4 (m) Acts contrary to good sportsmanship, during the match between the Brumbies and Chiefs at GIO Stadium in Canberra on 2 April 2016.

Pocock is alleged to have grasped the neck of Chiefs number eight Michael Lietch during a maul in the 74th minute of the match. Upon review of the match footage, the Citing Commissioner deemed in his opinion the incident had met the red card threshold for foul play.

The citing is to be considered in the first instance by SANZAAR Duty Judicial Officer Adam Cassleden.

All SANZAAR disciplinary matters are in the first instance referred to a Duty Judicial Officer hearing to provide the option of expediting the judicial process.

For a matter to be dispensed with at this hearing, the person appearing must plead guilty and accept the penalty offered by the DJO.

“Main photo credit”

Main Photo Caption: David Pocock of the Brumbies looks dejected after dropping a pass during the round six Super Rugby match between the Brumbies and the Chiefs at GIO Stadium on April 2, 2016 (via Getty Images).


1 Responses You are logged in as Test

  1. SANZAAR NEWS RELEASE

    David Pocock suspended for three weeks.

    The SANZAAR Duty Judicial Officer Adam Cassleden has accepted a guilty plea from David Pocock of the Brumbies for contravening Law 10.4(e) Playing a player without the ball is dangerous play, after he was Cited during a Super Rugby Match at the Weekend.

    Pocock grasped the neck of Chiefs #8 Michael Leitch during a maul in the 74th minute of the match between the Brumbies and Chiefs at GIO Stadium in Canberra on 2 April 2016.

    Pocock has been given a three week suspension for the incident and is suspended up to and including Sunday 24th April. Due to the fact the Brumbies have a scheduled bye in Rd 7, Pocock will miss Rd 8 and Rd 9 of Super Rugby, in effect making it a two match sanction.

    SANZAR Duty Judicial Officer Adam Cassleden assessed the case. In his finding, Cassleden ruled the following:

    “Having conducted a detailed review of all the available evidence, including all camera angles and additional evidence, including from the player and submissions from his legal representative I accepted the player’s admission that he had committed an act of foul play contrary to law 10.4(e).

    In its Memorandum on “Dangerous tackles (high tackles), dangerous grasping of neck and/or head area of player not in possession of the ball and dangerous grasping/holding of ball carrier above the line of the shoulder” dated 22 May 2015, World Rugby stated “this type of dangerous play which is foul play must be dealt with severely by match officials and all those involved in the disciplinary process.”

    With respect to sanction I deemed the act of foul play merited a low-end entry point of 2 weeks. I then added one week for aggravation due to the need to deter this type of dangerous foul play. However, taking into account mitigating factors including the player’s early plea, his good character, his genuine remorse and his excellent disciplinary record I reduced the suspension to a period of two weeks.”

    “The player accepted my indication of sanction of 2 weeks, and is therefore suspended from all forms of rugby up to and including Sunday, 24 April 2016. The player is free to resume playing on 25 April 2016.”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.