Chris Brown Washington D.C. Hearing Set for Jan. 8


A D.C. Superior Court judge set a Jan. 8 hearing for an assault charge against R&B singer and actor Chris Brown.

Brown, 24, is charged with misdemeanor assault in connection with an altercation outside a District hotel Oct. 27.

Brown was accused of striking a man during a fight outside the W Hotel in the 500 block of 15th Street NW, although accounts of what actually happen differ.

A friend of Brown’s and his bodyguard Christopher Hollosy, 35, were also charged with misdemeanor assault.

The incident occurred after a party in Washington D.C. at the nightclub Park at 14th.

Brown has been in a residential treatment center since Nov. 20 under a California court order stemming from his 2009 conviction in an assault case involving his former girlfriend, singer Rihanna.

Brown’s lawyers asked that he be allowed to skip the Nov. 25 D.C. court hearing so he could remain in the 90-day treatment program and because they needed an opportunity to review evidence with him.

“It would be counter-productive to have Mr. Brown check-out of an inpatient treatment program and travel across the country to attend a status hearing that will likely result in a continuance,” Brown’s attorney’s argued in a filing.

Click for related articles:

"Chris Brown's Probation Revoked over DC Arrest–But No Jail"

Rehab Ordered Again: Brown Threw Rock Through Mom's Car Window

R&B Singer Chris Brown out of Rehab

Brown's Lawyer Asks Judge to Block Jail Transfer

A 'Bad Day' in Rehab Costs Chris Brown His Freedom

Judge Orders Chris Brown to Remain in Jail—Another Month

Authorities: Chris Brown Arrested on Warrant

Chris Brown Rejects Plea Deal in DC Assault Case

“U.S. Marshals Take Custody of Chris Brown for Transport to Washington D.C.”

Chris Brown Trial Set to Start on Monday

Chris Brown's Washington D.C. Trial on Assault Charge Delayed

23 total views, 6 views today

Chris Brown Washington D.C. Hearing Set for Jan. 8

Comments

Latest Tweets

    Message: Rate limit exceeded, Please check your Twitter Authentication Data or internet connection.