Bessler v. Tempe, City of

District Court, D. Arizona·Decided September 9, 2021·No. 2:19-cv-04610·Unknown

Opinion

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

9 Donald Bessler, No. CV-19-04610-PHX-MTL

10 Plaintiff, ORDER

11 v.

12 City of Tempe, et al.,

13 Defendant. 14 15 Before the Court is Defendant City of Tempe’s (“Tempe”) Motion for 16 Reconsideration (Doc. 117). Plaintiff Donald Bessler filed a response. (Doc. 121.) The 17 Court held oral argument and took Tempe’s Motion under advisement. (Doc. 123.) The 18 Court now resolves this Motion as follows. 19 I. BACKGROUND 20 The Court previously set forth this case’s background in detail. (Doc. 107.) Tempe 21 filed a motion for summary judgment on Bessler’s claim of retaliation under the Age 22 Discrimination in Employment Act (“ADEA”) and on its affirmative defense of failure to 23 mitigate damages. (Doc. 100.) The Court found genuine issues of material fact exist as to 24 both the ADEA retaliation claim and the failure-to-mitigate damages defense. (Doc. 107.) 25 Accordingly, the Court denied Tempe’s motion for summary judgment on July 22, 2021. 26 (Id.) Tempe then filed the instant Motion for Reconsideration on August 5, 2021. (Doc. 27 117.) Tempe argues the Court committed clear legal error when it ruled that Bessler carried 28 his summary judgment burden of establishing “but-for” causation as part of his prima facie 1 case of retaliation under the ADEA. (Id. at 1.) Tempe also asserted the Court committed 2 clear legal error in denying summary judgment on its failure-to-mitigate damages defense. 3 (Id.) On August 6, 2021, the Court denied Tempe’s Motion as to its failure-to-mitigate 4 damages defense finding that it simply re-litigated arguments made in its motion for 5 summary judgment. (Doc. 120.) Thus, Tempe’s Motion remains only as to the issue of 6 “but-for” causation. (Id.) 7 II. LEGAL STANDARD 8 A district court has discretion to reconsider and amend prior orders. Fed. R. Civ. P. 9 54(b).* Motions for reconsideration are generally disfavored and should be denied “absent 10 a showing of manifest error or a showing of new facts or legal authority that could not have 11 been brought to [the court’s] attention earlier with reasonable diligence.” LRCiv. 7.2(g). A 12 motion for reconsideration may not repeat previously made arguments. LRCiv. 7.2(g). As 13 such, a motion for reconsideration should not be used to ask the court to rethink what it has 14 already thought through in its previous ruling. Defs. of Wildlife v. Browner, 909 F. Supp. 15 1342, 1351 (D. Ariz. 1995). Mere disagreement with the previous order is likewise an 16 insufficient basis for reconsideration. Adams v. Symetra Life Ins. Co., No. CV-18-0378- 17 TUC-JGZ (LAB), 2020 WL 4814249, at *2 (D. Ariz. Aug. 19, 2020). 18 III. DISCUSSION 19 A. Earlier Separation Decision 20 In its Order, the Court found that Bessler offered sufficient evidence to meet his 21 summary judgment burden of showing a causal link between his protected activity and his

22 * Although Tempe references Rule 59(e) of the Federal Rules of Civil Procedure, the Court presumes it meant to bring its motion for reconsideration under Rule 54(b), which allows 23 district courts to revise any order that does not adjudicate all the claims in a case at any time before the entry of a final judgment adjudicating all the claims. Fed. R. Civ. P. 54(b); 24 see also Motorola, Inc. v. J.B. Rodgers Mech. Contractors, 215 F.R.D. 581, 582 (D. Ariz. 2003). Tempe cites Ervco, Inc. v. Texaco Ref. & Mktg., Inc., 422 F. Supp. 2d 1084 (D. 25 Ariz. 2006), for the proposition that Rule 59(e) is a proper vehicle for seeking reconsideration of a summary judgment ruling. (Doc. 117 at 5.) But in Ervco, it was the 26 Plaintiff seeking reconsideration of an order granting summary judgment in favor of the defendant. Id. at 1086. Because the Court’s Order denying Tempe’s motion for summary 27 judgment did not adjudicate all the claims in the case the proper vehicle for a motion for reconsideration is Rule 54(b). Cf. Motorola, 215 F.R.D. at 583 (holding party could not 28 rely on Rule 59(e) in seeking reconsideration of discovery order because it did not adjudicate all claims in the case). 1 separation. (Doc. 107 at 16.) To establish a causal link, an employee must show the 2 protected activity was the “but-for” cause of the adverse employment action. See Univ. of 3 Tex. Sw. Med. Ctr. v. Nassar, 570 U.S. 338, 360 (2013). On September 24, 2018, Bessler 4 informed Tempe that he filed a charge of age discrimination with the Equal Employment 5 Opportunity Commission (“EEOC”). (Docs. 100 at 6; 101 at 8.) Two days later, Tempe 6 informed Bessler, for the first time, that his employment would end in 2018. (Docs. 100 at 7 8; 101 at 8.) Bessler was never issued a performance review or written warning before this 8 date. (Doc. 101–4 at 6–7.) Moreover, less than two months before Tempe informed Bessler 9 his employment would end, Tempe’s City Manager, Andrew Ching, told Bessler that he 10 had several more years of utility left to serve Tempe. (Id. at 19–20.) Based on this 11 circumstantial evidence, the Court concluded that Bessler met his summary judgment 12 burden of showing a causal link between his protected activity and his separation. 13 Nevertheless, Tempe argues the Court overlooked evidence that it made the decision 14 to terminate Bessler before it learned of his protected activity. Tempe also argues that the 15 Court applied a non-existent legal standard when it found there was a dispute as to when 16 Tempe finalized its separation decision. (Doc. 117 at 5‒8.) Tempe specifically takes issue 17 with the Court’s reliance on Conroy v. Hewlett-Packard Co., No. 3:14-CV-01580-AC, 18 2016 WL 1276552 (D. Or. Mar. 31, 2016). (Doc. 117 at 7.) In that case the court held the 19 employee established a causal link for purposes of her prima facie case of retaliation. Id. 20 at *15‒16. The court rejected the employer’s argument that a causal link did not exist 21 because it made the adverse employment decision before it learned of the protected 22 activity. Id. at *16. As the court explained, the employer was aware of the employee’s 23 protected activity at the time it finalized its decision to eliminate the employee’s position. 24 Id. Thus, the causal link between the protected activity and the adverse employment action 25 was left firmly intact. Id. 26 Here, there is a genuine issue of material fact regarding whether Tempe was aware 27 of Bessler’s charge of discrimination at the time it finalized the decision to separate him. 28 Specifically, in his declaration, Ching stated he made the decision to separate Bessler on 1 September 6, 2018. (Doc. 100–5 at 25.) Yet Ching also inconsistently claims that he and 2 Tempe’s deputy city managers met and agreed to separate Bessler on September 10, 2018. 3 (Id. at 20, 26, 29.) Moreover, at his deposition, Ching testified that at this meeting, he 4 instructed one of the deputy city mangers to reconnect with Bessler to “explore exactly 5 what he meant . . . by him [Bessler] being done,” which suggests that Tempe had not 6 finalized a decision to separate Bessler by this date. (Doc. 100–2 at 59.) Tempe did not 7 inform Bessler his employment would be ending until September 26, 2018. (Id. at 8; Doc. 8 101 at 8.) Tempe was also attempting to negotiate Bessler’s terms of separation as late as 9 October 11, 2018. (Doc. 100 at 8.) Like Conroy, a reasonable jury could find that Tempe 10 made the decision to terminate Bessler after learning of his protected activity.

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

Bessler v. Tempe, City of, (D. Ariz. 2021).

Bessler v. Tempe, City of (Bessler v. Tempe, City of) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
United States v. DeFries
909 F. Supp. 13 (District of Columbia, 1995)
Ervco, Inc. v. Texaco Refining and Marketing, Inc.
422 F. Supp. 2d 1084 (D. Arizona, 2006)