Espinoza v. Ryan

District Court, D. Arizona·Decided August 14, 2020·No. 2:17-cv-03983·Unknown

Opinion

WO

Adrien Joshua Espinoza, No. CV-17-03983-PHX-ROS

Plaintiff, ORDER

v.

David Shinn, et al.,

Defendants. Plaintiff Adrien Joshua Espinoza (“Espinoza”) commenced this action in 2017. Despite repeated cautions that failure to comply with discovery obligations could result in sanctions including dismissal, and allowances for Espinoza’s mental health, he has never appropriately responded to Defendants’ discovery requests. (Docs. 102, 169.) Defendants have now moved for dismissal sanctions, Doc. 181, and Magistrate Judge James F. Metcalf recommends the motion be granted and the action be dismissed without prejudice. (Doc. 192.) The recommendation will be adopted. The factual background is set forth in detail in the Report and Recommendation (“R&R”). Espinoza objected to many of the facts set forth in the R&R, but generally did not identify the factual or legal basis for his objections. As the recommended relief is dispositive, the Court reviews de novo the portions of the R&R that have been properly objected to. Fed. R. Civ. P. 72(b)(3). Espinoza commenced this case on October 27, 2017, and upon screening the Court found that Espinoza sufficiently stated two claims, a First Amendment mail and retaliation claim regarding retaliatory prohibitions on Espinoza’s receipt of publications, and an Eighth Amendment claim regarding cockroaches in Espinoza’s cell. (Doc. 17 at 13.) In September 2018 the Magistrate Judge issued a scheduling order, and Defendants served discovery requests on Espinoza on January 14, 2019. On February 7, 2019, the Magistrate Judge concluded that Espinoza was not capable of pursuing litigation, due to his placement on persistent mental health watch and in a mental health unit, and vacated all deadlines. (Doc. 67.) On May 7, 2019, after Defendants reported Espinoza was no longer on a mental health watch, and after Espinoza filed a series of motions and objections, the Magistrate Judge concluded Espinoza was “prepared to continue litigating this case, and the reasons for holding the matter in abeyance no longer apply,” and reset the litigation schedule. (Doc. 93.) When Espinoza failed to respond to Defendants’ discovery requests, Defendants filed a motion to compel. (Doc. 101.) The Magistrate Judge “perceive[d] that the intervening stay of proceedings may have impacted [Espinoza’s] understanding of the deadlines for responding,” and denied the motion to compel without prejudice. (Doc. 102 at 2.) Espinoza was given until June 28, 2019 to respond, but was cautioned “that aside from being subject to an award of expenses (including attorneys fees) in the event a motion to compel is granted, his failure to comply with an order compelling discovery may result in a variety of sanctions, up to and including dismissal of this action.” (Doc. 102 at 3.) On July 12, 2019, Espinoza filed a document titled “Notice of Service/Motion for Appointment of Counsel,” which begins “Plaintiff notifies the Court he is E-filing defendants’ Interrogatories and Requests for Production on 6/26/19.” (Docs. 119, 20.) This three-page document had a signature and a certificate of service, dated June 26, 2019. (Doc. 119 at 3.) Appended to the document were copies of Defendants’ Interrogatories with hand- written objections and responses, but no signatures, and no certificates of service. (Docs. 119, 120.) On August 5, 2019, Defendants filed a motion to compel. (Doc. 136.) The Magistrate Judge granted the motion, finding Espinoza failed to respond to the discovery requests because his “supposed responses” were filed two weeks later, and were therefore untimely; he failed to sign his responses; and the responses were unresponsive, in part because they failed to specifically identify documents. (Doc. 169.) The Magistrate Judge specifically addressed Espinoza’s “proffer[] to send his ‘stack of documents’ for Defendants to copy and return.” (Doc. 169 at 4.) The Magistrate Judge warned Espinoza that it “is generally not sufficient to simply produce a ‘stack of documents’ and leave it to Defendants to discern which documents relate to which request” because discovery “must be produced in a responsive manner, i.e. with the response to each request designating the documents being produced in response.” (Doc. 169 at 4.) The Magistrate Judge ordered Espinoza to “specifically identify for each request which documents or sub group of documents i[s] offered in response” in his responses to the requests for production and gave Espinoza 21 days to fully respond to the requests. (Doc. 169 at 4.) Finally, the Magistrate Judge cautioned Espinoza that “failure to fully and adequately respond to the discovery requests will result in sanctions, including . . . dismissing the action or proceeding in whole or in part.” (Doc. 169 at 5.) Espinoza appealed that order to the Court, which denied the appeal and cautioned him that he “must comply with the Magistrate Judge’s order regarding the discovery sought by Defendants.” (Docs. 171, 174.) Espinoza moved for reconsideration, and that motion was denied. (Docs. 179, 188.) On the same date his appeal was denied, October 24, 2019, Espinoza filed a one- page Notice of Service, stating “Defendants[’] Interrogatories and Requests for Production were sent to Defendants 10/22/19,” Doc. 176, as well as a motion for an extension of time “to file the remainder of his Interrogatories and Requests for Production,” Doc. 175. Defendants responded to the extension motion, stating that on October 25, 2019 they received “the same interrogatory responses that Espinoza had previously served” and “three manila envelopes, stuffed with hundreds of pages of completely disorganized papers . . ., but no written response to their Requests for Production indicating how the hundreds of documents respond to the discovery requests.” (Doc. 180 at 1–2.) Defendants argued Espinoza had failed to explain why no real updates or written production responses were provided, and submitted Espinoza’s failure to “identify the facts supporting his claims or any documentation he has that support his factual allegations” “left the Court with no reasonable option other than to dismiss this action without prejudice based on Espinoza’s continuing failure to prosecute this action or to comply with the Federal Rules or the Court’s Orders under Fed. R. Civ. P. 37(b) and 41(b).” (Doc. 180 at 3.) Espinoza never replied, and objects now that he “was not afforded an opportunity to respond” because his motion for an extension of time to reply was not granted. (Doc. 200 at 3.) But Espinoza’s motion for an extension of time to reply was granted the day after it was filed, and although he was given until November 20, 2019 to reply, he never did. (Docs. 182, 183.) On November 25, 2019, the Magistrate Judge denied Espinoza’s motion to extend the time to complete his discovery responses, finding that the motion was delinquent and there was no excusable neglect justifying the failure to file on time. (Doc. 187.) On November 12, 2019, Defendants filed the instant motion for sanctions. (Doc. 181.) Defendants argue Espinoza failed to comply with the Court’s Order to respond to their discovery requests when he did not provide any meaningful additional responses, and the Court should issue an order for sanctions pursuant to Fed. R. Civ. P. 37(b)(2)(A). (Doc. 181 at 2–3.) Defendants submit that the most appropriate of the seven orders contemplated by the Rule is dismissal, because any other order “would merely be putting off the inevitable dismissal of this case in light of Espinoza’s ongoing failure to prosecute his case according to the Federal Rules and Court’s prior discovery Orders.”

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

Espinoza v. Ryan, (D. Ariz. 2020).

Espinoza v. Ryan (Espinoza v. Ryan) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related