Ronald L. Atkinson v. United States

121 A.3d 780, 2015 D.C. App. LEXIS 295, 2015 WL 4604326
CourtDistrict of Columbia Court of Appeals
DecidedJuly 30, 2015
Docket14-CF-0008
StatusPublished
Cited by7 cases

This text of 121 A.3d 780 (Ronald L. Atkinson v. United States) is published on Counsel Stack Legal Research, covering District of Columbia Court of Appeals primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Ronald L. Atkinson v. United States, 121 A.3d 780, 2015 D.C. App. LEXIS 295, 2015 WL 4604326 (D.C. 2015).

Opinion

NEBEKER, Senior Judge:

Following a jury trial, Ronald L. Atkinson appeals his conviction of one count of stalking, in violation of D.C.Code § 22-3133(a)(3) (2012 Repl.), and six counts of Violating a Civil Protection Order (CPO), in violation of D.C.Code §§ 16 — 1004(d), - 1005(g) (2012 Repl.). 1 Appellant contends that the trial court erred in three respects, each requiring reversal of his convictions: (1) the trial court committed reversible error when it failed to instruct the jury on the statutory definition for the term “course of conduct”; (2) the trial court issued instructions that merged alternative theories of liability with respect to the stalking charge; (3) the trial court erred when it denied appellant’s request for a mistrial. Having reviewed the record, we conclude that the trial court only committed error when it issued an instruction that merged alternative theories of liability under the stalking statute. However, given the substantial evidence put forward by the government with respect to appellant’s objectively alarming behavior, the error was harmless. Accordingly, we affirm appellant’s convictions.

I.

This case stems from actions taken by appellant after the demise of his relationship with Ms. Halima Roebuck. Appellant and Roebuck first met in 1998, and began a cordial friendship that became “intimate” after both individuals moved to the District of Columbia in 2002. Sometime around 2003, the relationship began “unraveling.” Roebuck last communicated with appellant at the end of February 2004. From 2005 to 2011, appellant sent Roebuck numerous emails from multiple email addresses in an attempt to reconcile their differences and reestablish contact. Roebuck never responded.

At some point, appellant — for reasons not revealed in the record-believed that he and Roebuck had a child together, 2 and in December of 2011 escalated his attempts to try to contact Roebuck. On the morning of December 23, 2011, appellant called Roebuck and left a voicemail. Appellant then called her multiple times throughout the evening, often “back-to-back.” The phone calls continued into the early morning hours of December 24, 2011, when appellant called Roebuck’s residence at *783 1:48 a.m. At some point, Roebuck’s' flaneé 3 answered the phone and told appellant that he “need[ed] to stop calling.” Appellant told Roebuck’s flaneé to “put Halima on-the phone, put Halima on the phone.” Roebuck’s flaneé responded with “Halima doesn’t want to talk to you,” and that “I don’t want you calling this house anymore.” Following appellant’s phone calls,. Roebuck unplugged her phone and eventually obtained an unlisted number.

After calling Roebuck’s residence a number of times unsuccessfully, appellant attempted to contact members of Roebuck’s family — including her mother and her father — and told each parent that he and Roebuck had a child together. Roebuck’s mother refused to speak with appellant and called the police. Roebuck’s father “specifically” told appellant not to “communicate ‘ with any of [the Roebuck family]” because appellant’s behavior' “was bordering on harassment.” He also “told [appellant] that [Roebuck] does not have a child,” that he was “not a grandfather,” and that appellant “should try to seek some sort of treatment.” 4 On December 27, 2011, appellant appeared at an apartment building where Roebuck had previously lived. 5 Appellant “stood outside for a couple of minutes,” and then “came inside” and used the call box to dial the direct number to Roebuck’s old apartment. When appellant ■ was approached by the security guard, appellant told the guard that he was “family,” and asked if he could “go upstairs and wait by the door.” Appellant was rebuffed in his attempts, and left. He returned the following day. Roebuck, however, had obtained a Temporary Protection Order (TPO) 6 against him that had been disseminated to the apartment building’s security staff. When appellant arrived, security informed him that he was not permitted in. the building. He was called into the property manager’s office, and then' the -police were called. Appellant, however, left the building before po-. lice arrived.

•On May 6, 2012, appellant’s conduct toward Roebuck reached a head. At 1:30 a.m., Roebuck received “back-to-back” phone calls from a number that registered as private on her caller I.D. Roebuck then began to receive calls on her cell phone indicating that someone was ringing the call box outside of her apartment building. Roebuck thought it was appellant contacting her again because of the “pattern” of his behavior, - but could not be certain. Roebuck eventually called the police. She testified that she was fearful because she was alone in the apartment; her flaneé was out of town. At 3:00 a.m., she re *784 ceived multiple phone calls from a “blocked number.” Later that morning, Roebuck took “precautions,” and contacted JaBen Early, her “godbrother,” 7 and told him that she was “receiving nonstop calls” from a “private” number. Early did not know whether Roebuck told him that the calls she had received were actually from appellant, but Early suspected it was “in relationship to that.” Early agreed to stay with Roebuck at her residence until her fiancé returned.

Early arrived at Roebuck’s apartment building at approximately 12:30 p.m. on May 6th, and observed appellant standing outside of the building, glancing at his cellphone and pacing back and forth. 8 When Early saw appellant attempt to follow several unaffiliated people into the building, Early confronted appellant and “told him not to go inside.” 9 Appellant responded that he “just want[ed] to talk to her” because “[s]he has my baby.” At this point, Metropolitan Police Department (MPD) motorcycle officer Richard West arrived in response to a 9-1-1 call placed by Roebuck. As Officer West approached both Early and appellant, Early told Officer West that “there he is right there, Officer; that’s the one that has the CPO order against him.” In response, appellant pointed at Early “and said no, he’s the one who has the CPO order against him.” Early repeated that Officer West “need[ed] to get him” because “[he]’s stalking my God sister.” To sort through the conflicting stories, Officer West “engaged [appellant] in a conversation about their relationship.” As appellant was conversing with Officer West, Officer Warren Jones — West’s partner — arrived at the scene. Early again told the two officers that “they needed to arrest [appellant] because [Roebuck] has a civil protection order against him.” Appellant responded by telling the MPD officers “that he had a child with [Roebuck].” He then glanced at Early “and then just ran away.”

Appellant fled from the officers down an adjacent alleyway and jumped a fence, but did not have “anywhere to go.” The officers pursued him up to the fence.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Keerikkattil v. United States
District of Columbia Court of Appeals, 2024
Dugger v. United States
District of Columbia Court of Appeals, 2023
Mashaud v. Boone
District of Columbia Court of Appeals, 2023
Darryl Malloy v. United States
186 A.3d 802 (District of Columbia Court of Appeals, 2018)
ALAZAJUAN M. GRAY and CLIFTON SMITH v. UNITED STATES.
147 A.3d 791 (District of Columbia Court of Appeals, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
121 A.3d 780, 2015 D.C. App. LEXIS 295, 2015 WL 4604326, Counsel Stack Legal Research, https://law.counselstack.com/opinion/ronald-l-atkinson-v-united-states-dc-2015.