Teamsters Local 617 Pension & Welfare Funds v. Apollo Group, Inc.

282 F.R.D. 216, 2012 WL 1094454, 2012 U.S. Dist. LEXIS 45794
CourtDistrict Court, D. Arizona
DecidedMarch 30, 2012
DocketNo. CIV 06-02674 PHX RCB
StatusPublished
Cited by37 cases

This text of 282 F.R.D. 216 (Teamsters Local 617 Pension & Welfare Funds v. Apollo Group, Inc.) 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
Teamsters Local 617 Pension & Welfare Funds v. Apollo Group, Inc., 282 F.R.D. 216, 2012 WL 1094454, 2012 U.S. Dist. LEXIS 45794 (D. Ariz. 2012).

Opinion

ORDER

ROBERT C. BROOMFIELD, Senior District Judge.

Background

In this securities fraud action, lead plaintiff, Pension Trust Fund for Operating Engineers (“plaintiff’), commenced this action against Apollo Group, Inc. (“Apollo”), and various Apollo officers and directors (“the individuals”).1 In an effort to satisfy the rigorous pleading standards of the Private Securities Litigation and Reform Act (“PSLRA”) and Fed.R.Civ.P. 9(b), plaintiff has made literally hundreds of pages of allegations in two separate complaints.2 After scrutinizing plaintiffs “cut and paste, ... puzzle like pleading” in Teamsters Local 617 Pension and Welfare Funds v. Apollo Group, Inc., 633 F.Supp.2d 763 (D.Ariz.2009) (“Apollo I”), vacated in part on reconsideration, 690 F.Supp.2d 959 (D.Ariz.2010), this court found, inter alia, that the first amended complaint (“FAC”) did not “satisfy the heightened pleading standards for fraud under either Rule 9(b) or the PSLRA.” Id. at 786. The court allowed plaintiff to amend the FAC and it did.

That second amended complaint (“SAC”) was the subject of another round of dismissal motions by defendants. Finding that the SAC did not plead falsity with the requisite degree of particularity, the court dismissed the SAC “with prejudice and without leave to amend.” See Teamsters Local 617 Pension and Welfare Funds v. Apollo Group, Inc., 2011 WL 1253250, at *37 (D.Ariz. March 31, 2011) (“Apollo III"). Accordingly judgment was entered in favor of defendants and against plaintiff.

Currently pending is “Lead Plaintiffs Fed.R.Civ.P. 59(e) Motion to Alter or Amend Judgment[.]” (Doc. 146) at 1. Plaintiff is seeking to have the court reopen and modify the Apollo III judgment on the following grounds: (1) two Ninth Circuit cases decided subsequent to Apollo III purportedly represent an intervening change in controlling law; (2) dismissal of certain false and misleading statements was “manifestly erroneous;” and (3) it was “clear error to dismiss the SAC with prejudice and without leave to amend.” Defendants respond that plaintiff has not satisfied the exceedingly stringent standards to warrant the “extraordinary remedy” of amending a judgment after its entry. See Allstate Ins. Co. v. Herron, 634 F.3d 1101, 1111 (9th Cir.2011) (citation and internal quotation marks omitted).

[219]*219 Discussion 3

I. Fed.R.Civ.P. 59(e)

A. Timeliness

Plaintiff specifically styles its motion as one to “alter or amend judgment” pursuant to Fed.R.Civ.P. 59(e). See Pl.’s Mot. (Doe. 146) at 14 That Rule mandates that such motions “must be filed no later than 28 days after entry of the judgment [.]” Fed. R.Civ.P. 59(e) (emphasis added). Calculating the relevant time frame in accordance with Fed.R.Civ.P. 6(a), the court “exclude[s]” April 1, 2011, the entry date of the judgment, as that is “the day of the event that triggers” Rule 59(e)’s 28 day time “period[.]” See Fed.R.Civ.P. 6(a)(1)(A). Then, “counting] every day, including intermediate Saturdays, Sundays, and legal holidays[,]” means that plaintiff had until April 29, 2011, in which to file its Rule 59(e) motion. See Fed.R.Civ.P. 6(a)(1)(B). Plaintiffs motion was filed on April 28, 2011, 27 days after the entry of the judgment. Undoubtedly, that motion was timely under Rule 59(e).

Nonetheless, defendants urge the striking of plaintiffs motion as “untimely[.]” Apollo Resp. (Doc. 149), at 8 n. 5. Defendants posit that because this Court “treats” Rule 59(e) motions “as motions for reconsideration[,]”5 id., and because plaintiff is seeking to have this court “reconsider its judgment[,]” Pl.’s Mot. (Doc. 146) at 6:7, LRCiv 7.2(g)(2) provides the relevant time frame, not Rule 59(e). In accordance with that former Rule, “[a]b-sent good cause shown, any motion for reconsideration shall be filed no later than fourteen (14) days after the date of the filing of the Order that is the subject of the motion.” LRCiv 7.2(g)(2) (emphasis added). Defendants proceed to argue that because plaintiffs motion “was filed 28 days after the entry of the Order (Dkt. No. 145)[,]” it was not timely under that Local Rule. See Apollo Resp. (Doc. 149) at 8, n. 5 (emphasis added).

There are two primary flaws with this statement. For starters, it is ambiguous because although Apollo specifically refers to “the Order[J” it cites to the judgment. Apollo Resp. (Doc. 149) at 8 n.5. An order and a judgment are not necessarily synonymous. Second, the just quoted statement is internally inconsistent given defendants’ proverbial comparison of apples to oranges. The defendants indicate that “entry of the Order” is the relevant event under LRCiv 7.2(g)(2), see id. (emphasis added), however, pursuant to that Local Rule it is the “filing of the Order[,]” not its “entry” which is the triggering event. See LRCiv 7.2(g)(2) (emphasis added). On the other hand, “entry of the judgment, as opposed to the order, is the triggering event under Fed.R.Civ.P. 59(e), which plaintiff argues applies here.

Taking defendants’ statement at face value, ie., looking to the date of entry of the Order, they also inaccurately calculate the time frame. As with the judgment, the order was filed on March 31, 2011, but it was not entered until April 1, 2011. See Doc. 144. Thus, as discussed above with respect to the entry of the judgment, plaintiffs motion was filed 27, not “28 days after ... entry of the Order[,]” as defendants assert. See Apollo Resp. (Doc. 149) at 8, n. 5 (citation omitted) (emphasis added).

With this clarification, the issue remains whether LRCiv 7.2(g) (2), as defendants urge, or Fed.R.Civ.P.Rule 59(e), as [220]*220plaintiff assumes, governs the timeliness of the pending motion. Defendants are mistaken that “constru[ing] plaintiffs Rule 59(e) motion as one for reconsideration means that it “should be stricken” as untimely based upon LRCiv 7.2(g)’s 14 day filing deadline. See id. That Local Rule does not apply in this situation because that Rule expressly pertains only to motions to reconsider “orders,” as opposed to judgments. See LRCiv 7.2(g).

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
282 F.R.D. 216, 2012 WL 1094454, 2012 U.S. Dist. LEXIS 45794, Counsel Stack Legal Research, https://law.counselstack.com/opinion/teamsters-local-617-pension-welfare-funds-v-apollo-group-inc-azd-2012.