Espinoza v. Ryan

CourtDistrict Court, D. Arizona
DecidedAugust 14, 2020
Docket2:17-cv-03983
StatusUnknown

This text of Espinoza v. Ryan (Espinoza v. Ryan) is published on Counsel Stack Legal Research, covering District Court, D. Arizona primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

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

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

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

10 Plaintiff, ORDER

11 v.

12 David Shinn, et al.,

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

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Espinoza v. Ryan, Counsel Stack Legal Research, https://law.counselstack.com/opinion/espinoza-v-ryan-azd-2020.