Bajjuri v. Raytheon Technologies Corporation

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA 8 9 Pranay K Bajjuri, et al., No. CV-20-00468-TUC-JCH 10 Plaintiffs, ORDER 11 v. 12 Raytheon Technologies Corporation, et al., 13 Defendants. 14 15 Before the Court is Defendants' ("Raytheon" and certain of its individual "Officers") 16 Motion to Dismiss the Consolidated Class Action Complaint ("Motion I") (Doc. 41) and

17 Request for Judicial Notice in Support of Motion I ("Motion II") (Doc. 42). For the reasons 18 below, the Court grants both Motions and dismisses this case without prejudice.

19 I. BACKGROUND AND OVERVIEW

20 On October 30, 2020, Plaintiff Bajjuri brought a federal securities class action suit 21 against Raytheon and the Officers. (Doc. 1.) The suit claimed Raytheon and the Officers 22 made false and misleading statements through Raytheon's financial statements and by

23 certifying Raytheon's financial controls were effective. (Doc. 1.) In July 2021, the Court

24 consolidated Bajjuri's case with a related case, retained Bajjuri as the lead case, (Doc. 30),

25 and the newly consolidated Plaintiffs filed their first amended complaint ("the Complaint").

26 (Doc. 34.) In March 2022, Raytheon filed Motion I, (Doc. 41), and Motion II (Doc. 42). 27 On October 4, 2022, the Court heard oral argument on these Motions. (Doc. 48; 28 Doc. 54 (Hearing Transcript).)

1 Seen from 40,000 feet, the Complaint's allegations appear quite serious. The 2 Complaint alleges that Raytheon repeatedly and intentionally defrauded the U.S. 3 government, Raytheon's largest customer, by overcharging contracts and violating 4 numerous statutes and processes designed to control government costs. The Complaint 5 alleges this misconduct was so pervasive it affected almost all contracts and divisions at 6 Raytheon, was conducted in conspiracy with many of Raytheon's subcontractors, and 7 extends back even before the Class Period (February 10, 2016, to October 27, 2020). The 8 Complaint also alleges that Raytheon repeatedly and intentionally defrauded investors by 9 representing Raytheon's internal controls over financial reporting were effective, and by 10 filing financial statements overstating Raytheon's most important financial metrics, like 11 revenue and net income. Finally, Raytheon's misconduct culminated in a criminal subpoena 12 from the Department of Justice ("DOJ") that, when disclosed, resulted in a "precipitous" 13 drop in Raytheon's stock price and the CEO's confession of wrongdoing. 14 On closer examination of the Complaint—and unedited samples of the documents 15 it incorporates—a different and more benign view of the facts emerges. For example, the 16 CEO's confession and the DOJ investigation focused on four contracts out of tens of 17 thousands Raytheon performs annually. The "precipitous" stock drop following Raytheon's 18 disclosure of DOJ's investigation was a 7% drop that the stock recovered four trading days 19 later. Moreover, Raytheon's stock had already been falling for two days before the 20 disclosure, and Raytheon's disclosure of the DOJ investigation also disclosed that the 21 COVID-19 pandemic was significantly disrupting Raytheon's aerospace business, enough 22 to require termination of 15,000 employees. Finally, the Complaint's allegations of 23 widespread fraud are based largely on unreliable confidential witness accounts. Those few 24 allegations that one or two witnesses corroborate support only the view that Raytheon's 25 misconduct was limited to a few contracts and a few employees. 26 This more benign view is ultimately dispositive because it yields a stronger and 27 more plausible picture of the facts than the Complaint. Ordinarily, plausibility is the heart 28 of a 12(b)(6) pleading inquiry: whether the facts plausibly give rise to an inference of

3

1 wrongdoing. But the law requires more when pleading securities fraud. In the securities 2 context, the Court considers not only whether a complaint raises a plausible inference of 3 wrongdoing, but also compares that inference to other, more benign inferences. Unless a 4 complaint's inferences are at least as plausible as the more benign inferences—that is, 5 unless the complaint raises not just an inference, but a strong inference—the motion to 6 dismiss must be granted. 7 As explained below, Plaintiffs do not carry their burden under the heightened 8 securities fraud standard, and so the Court dismisses their Complaint without prejudice. 9 II. LEGAL STANDARD 10 a. Fed. R. Civ. P. 12(b)(6) Failure to State a Claim 11 When deciding a motion to dismiss for failure to state a claim, the Court must 12 "consider the complaint in its entirety" and, in doing so, "accept all factual allegations in 13 the complaint as true." Tellabs, Inc. v. Makor Issues & Rights, Ltd., 551 U.S. 308, 322 14 (2007). At the pleading stage, a plaintiff "need only allege 'enough facts to state a claim to 15 relief that is plausible on its face."' Matrixx Initiatives, Inc. v. Siracusano, 563 U.S. 27, 45 16 n.12 (2011) (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007)). 17 b. Securities Fraud under Securities Exchange Act §§ 10(b) and 20(a) 18 Plaintiffs' claims arise under the Securities Exchange Act of 1934 ("SEA") §§ 10(b) 19 (Count I) and 20(a) (Count II), and under the Securities Exchange Commission ("SEC") 20 Rule 10b-5. SEA § 10(b) makes it unlawful to employ any "manipulative or deceptive 21 device" in connection with the purchase or sale of a security, or to contravene "such rules 22 and regulations as the [SEC] may prescribe as necessary or appropriate in the public 23 interest or for the protection of investors." 15 U.S.C. § 78j(b). SEA § 20(a) extends § 10(b) 24 liability to "controlling" individuals. 15 U.S.C. § 78t(a). And SEC Rule 10b-5 prohibits 25 "any act, practice, or course of business" that operates as a "fraud or deceit" in connection 26 with the purchase or sale of a security. 17 C.F.R. § 240.10b-5(c). 27 Securities fraud complaints must meet heightened pleading requirements. Nguyen 28 v. Endologix, Inc., 962 F.3d 405, 413 (9th Cir. 2020). One source of these higher standards

4

1 is Fed. R. Civ. P. 9(b), which requires a plaintiff to state facts alleging fraud "with 2 particularity." See Zucco Partners, LLC v. Digimarc Corp., 552 F.3d 981, 990 (9th Cir. 3 2009). Another source is the Private Securities Litigation Reform Act of 1995 ("PSLRA"), 4 which was enacted in part to "curb perceived abuses of the § 10(b) private action— 5 'nuisance filings, targeting of deep-pocket defendants, vexatious discovery requests and 6 manipulation by class action lawyers.'" Tellabs, 551 U.S. at 320 (quoting Merrill Lynch, 7 Pierce, Fenner & Smith Inc. v. Dabit, 547 U.S. 71, 81 (2006)). Under the PSLRA, "the 8 complaint shall specify each statement alleged to have been misleading, the reason or 9 reasons why the statement is misleading, and, if an allegation regarding the statement or 10 omission is made on information and belief, the complaint shall state with particularity all 11 facts on which that belief is formed." 15 U.S.C. § 78u-4(b)(1). 12 Under the PSLRA and Federal Rule of Civil Procedure 9(b), a plaintiff pleading 13 securities fraud under SEA § 10(b) must adequately allege "(1) a material misrepresentation 14 or omission; (2) scienter; (3) a connection between the misrepresentation or omission and 15 the purchase or sale of a security; (4) reliance; (5) economic loss; and (6) loss causation." 16 Nguyen, 962 F.3d at 413; Or. Pub. Emps. Ret. Fund v. Apollo Grp. Inc., 774 F.3d 598, 605 17 (9th Cir. 2014) ("Rule 9(b) applies to all elements of a securities fraud action"); see also 15 18 U.S.C. §§ 78j(b), 78u-4(b)(1); 17 C.F.R. § 240.10b-5. 19 III. ANALYSIS 20 The Court begins with a housekeeping item. In Motion II, Raytheon asks the Court 21 to notice materials attached to Motion I as Exhibits 1–10. (Doc. 42.) Plaintiffs raised no 22 objection at oral argument. (Doc. 54 at 4:21–22.) Exhibits 1–4, 5, 8, and 10 are public SEC 23 filings referenced repeatedly in the Complaint, Exhibits 6 and 9 are transcripts of earnings 24 calls preceding Raytheon's October 2020 and April 2021 quarterly reports, and Exhibit 7 25 is a history of Raytheon's stock price from April 3, 2020, to March 18, 2022. (Doc. 42.) 26 The Court may consider materials outside a complaint when they are incorporated into the 27 complaint by reference or when the Court takes judicial notice of them. Tellabs, 551 U.S. 28 at 322. A document is incorporated if a complaint refers to it extensively. Khoja v. Orexigen

5

1 Therapeutics, Inc., 899 F.3d 988, 998 (9th Cir. 2018). The Court may also take judicial 2 notice of publicly available financial documents, such as SEC filings, earnings call 3 transcripts, and a company's reported stock price history. Metzler Inv. GMBH v. Corinthian 4 Colls., Inc., 540 F.3d 1049, 1064 n.7 (9th Cir. 2008). The Court therefore grants Motion 5 II, (Doc. 42), and takes judicial notice of ECF Docs. 41-2 through 41-11. 6 COUNT I 7 Motion I asserts three independent grounds under § 10(b) for granting Count I: 8 (1) the Complaint fails to plead a materially false or misleading statement with 9 particularity; (2) the Complaint fails to plead scienter; and (3) the Complaint fails to plead 10 loss causation. (Doc. 41 at 2–4.)1 11 a. Falsity 12 To plead a materially false or misleading statement, a complaint must (1) "specify 13 each statement alleged to have been misleading," (2) "specify . . . the reason or reasons 14 why the statement is misleading," and (3) "if an allegation regarding a statement or 15 omission is made on information and belief, . . . state with particularity all facts on which 16 that belief is formed." 15 U.S.C. § 78u-4(b)(1). 17 i. Statements alleged to have been false or misleading 18 The Complaint alleges two statements Raytheon made about its internal financial 19 controls were materially false or misleading. The statements appear in Raytheon's annual 20 and quarterly financial reports during the Class Period. Each describes Raytheon's internal 21 financial controls as "effective." The first statement reads, "Based on its assessment [of 22 Raytheon's internal controls over financial reporting], management has concluded that the 23 Company maintained effective internal control over financial reporting as of December 31, 24 2015, based on criteria in Internal Control – Integrated Framework, issued by the COSO 25 in 2013." (Doc. 34 ¶¶ 90, 130, 131, 167, 206, 245.) The second statement reads, 26 "Conclusion of Evaluation—Based on this evaluation, the Chief Executive Officer and 27 Chief Financial Officer concluded that our disclosure controls and procedures as of 28 1 Page citations are to the ECF document page unless otherwise noted.

6

1 December 31, 2015 were effective." (Doc. 34 ¶¶ 89, 100, 110, 120, 131, 141, 149, 157, 2 168, 178, 186, 196, 207, 217, 225, 235, 246 (emphasis omitted).) 3 The Complaint also alleges virtually all Raytheon's financial statements for the 4 Class Period were materially false and misleading. Specifically, the Complaint refers to all 5 "net sales (revenues)[,] operating expenses[,] and operating income" metrics, (Doc. 34 ¶¶ 6 93, 103, 113, 123, 134, 144, 152, 160, 171, 181, 189, 199, 210, 220, 228, 238, 249, 259), 7 as well as all financial "statements regarding Tomahawk [and Javelin missile] projects." 8 (Doc. 34 ¶¶ 98, 108, 118, 128, 139, 165, 176, 194, 204, 215, 233, 243, 254.) 9 The Court finds that these are sufficiently specific descriptions of statements alleged 10 to have been false or misleading under 15 U.S.C. § 78u-4(b)(1). 11 ii. Reasons why the alleged statements are false or misleading 12 The Complaint provides four reasons why Raytheon's statements about its internal 13 controls, costs, and revenues were materially false and misleading. First, Raytheon violated 14 government contracts and improperly recorded revenues and other metrics by "using 15 improper billing procedures, intentionally prolonging projects and making unnecessary 16 orders, failing to submit sub-contracts for competitive bidding, misappropriating funds, 17 conducting business with companies in direct violation of presidential orders, and 18 doctoring contracts to conceal misconduct." (Doc. 34 ¶ 80.) Second, Raytheon failed to 19 properly measure and "manipulated its Estimates at Completion ["EAC"]."2 (Doc. 34 ¶¶ 20 83, 91, 94, 95, 98, 101, 104, 105, 108, 111, 114, 115, 118, 121, 124, 125, 128, 132, 135, 21 136, 139, 142, 145, 146, 150, 153, 154, 158, 161, 162, 165, 169, 172, 173, 176, 179, 182, 22 183, 187, 190, 191, 194, 197, 200, 201, 204, 208, 212, 215, 218, 221, 222, 226, 229, 230, 23 233, 236, 239, 240, 243, 247, 250, 251, 254, 257, 260, 261.) Third, Raytheon "misused and 24 misappropriated funds awarded to it by the [U.S. Department of Defense ("DOD")], 25 violated protocols and parameters of its contracts . . . under [Federal Acquisition 26 27 28 2 An “Estimate at Completion” is a project-management forecasting tool used to determine the progress of a project’s budget.

7

1 Regulations ("FAR")] and [Defense Federal Acquisition Regulations ("DFAR")],3 and 2 even manipulated information it was required to provide to . . . [the Defense Contract Audit 3 Agency ("DCAA") and Defense Contract Management Agency ("DCMA")]." (Doc. 34 ¶¶ 4 94, 104, 114, 124, 135, 145, 153, 161, 182, 190, 200, 211, 221, 229, 239, 250, 260.) And 5 fourth, Raytheon "overcharged the DOD for materials or other supplies on jobs, overpaid 6 for contractors in the absence of the proper or required bidding process, [and] improperly 7 engaged and made payments to forbidden contractors." (Doc. 34 ¶¶ 95, 105, 115, 125, 136, 8 146, 154, 162, 173, 183, 191, 201, 212, 222, 230, 240, 251, 261.) 9 Viewing them as true, the Court finds these reasons sufficiently explain why 10 Raytheon's statements were false or misleading. 11 iii. Particular facts supporting these reasons 12 Plaintiffs plead the foregoing reasons on information and belief, (see Doc. 34 at 3), 13 and so the Complaint must state with particularity all facts on which the reasons are based. 14 15 U.S.C. § 78u-4(b)(1). Throughout the Complaint, Plaintiffs support their reasons with 15 a parenthetical stating "as discussed in detail above." (Doc. 34 ¶¶ 76, 91, 93, 101, 103, 111, 16 113, 121, 123, 132, 134, 144, 152, 160, 169, 171, 179, 181, 187, 189, 197, 199, 208, 210, 17 218, 220, 226, 228, 236, 238, 247, 249, 257, 259.) Given its widespread use and placement, 18 the Court interprets this parenthetical as having two possible references: (1) Raytheon's 19 disclosures of the DOJ investigation and certain statements by its CEO, (Doc. 34 ¶¶ 86– 20 88), and (2) statements by seven confidential witnesses (Doc. 34 ¶¶ 40–62). 21 1. DOJ Investigation Disclosures & CEO Statements 22 Plaintiffs first category of particular facts is the DOJ investigation disclosures and 23 certain earnings-call statements by Raytheon's CEO. Specifically, Plaintiffs identify three 24 bases for Plaintiffs' claim that Raytheon made false or misleading statements. (Doc. 34 ¶¶ 25 86–88; Doc. 43 at 18.) 26 Plaintiffs' first basis for claiming false or misleading statements is Raytheon's 27 28 3 FAR and DFAR are guidelines for “fair and reasonable pricing” mandated for companies doing business with the DOD. (Doc. 34 at 22.)

8

1 disclosure on October 27, 2020, that it received a DOJ subpoena. (Doc. 34 ¶ 8.) The 2 subpoena sought "information and documents in connection with an investigation relating 3 to financial accounting, internal controls over financing, and cost reporting regarding 4 [Raytheon's] Missiles & Defense business since 2009." (Doc. 34 ¶ 8.) Raytheon's 5 disclosure further stated, "Based on the information available to date . . . we do not believe 6 the results of this inquiry will have a material adverse effect on our financial condition, 7 results of operations or liquidity." (Doc. 41-3 at 50.) 8 Plaintiffs' second basis for claiming false or misleading statements is Raytheon's 9 disclosure on April 27, 2021, that it received another DOJ subpoena. (Doc. 34 ¶ 10.) This 10 disclosure stated: 11 The [DOJ] investigation includes potential civil defective pricing claims for three [Missiles and Defense] contracts entered into between 2011 and 2013.

12 As part of the same investigation, . . . [Raytheon] received a second criminal 13 subpoena from the DOJ seeking documents relating to a different [Missiles and Defense] contract entered into in 2017.

14 (Doc. 41-9 at 31.) The disclosure acknowledged "there is a meaningful risk of civil liability 15 for damages, interest and potential penalties," and concluded "[b]ased on the information 16 to date, however, we do not believe the results of the investigation . . . will have a material 17 adverse effect on our financial condition, results or liquidity." (Id.)

18 Plaintiffs' third basis for claiming false or misleading statements is certain remarks 19 Raytheon's CEO made on an April 27, 2021, earnings call. (Doc. 34 ¶ 10.) During the call, 20 a member of Citigroup's research division asked the CEO to clarify Raytheon's quarterly 21 report statement that the "DOJ items" were immaterial. (Doc. 41-10 at 12.) The Citigroup 22 representative also asked the CEO to say whether any "connective tissue" or "narrative"

23 existed between the DOJ items. (Id.) Raytheon's CEO replied:

24 I would tell you, again, the dollar amounts are not going to be material in our 25 view today. These -- again, these are older contracts, where it was alleged 26 that we defectively priced some contracts. Again, I can't get into much more detail than that. But again, we've looked into it. We think there is potential 27 liability for defective pricing. Clearly, we've provided for that this quarter. 28 And we're going to continue to work with DOJ to bring these things to a resolution.

9

1 I would tell you, these investigations take time. We're still going through 2 doing some work. But we don't believe there's going to be any ongoing impact to any of the businesses as a result of these investigations. We think 3 these were one-off events that occurred -- should not have occurred, but they did. And we're going to clean it up and move on. (Id.)

4 5 2. Confidential Witness Statements 6 Seven confidential witness statements form Plaintiffs' second category of particular 7 facts supporting their claim of false and misleading statements. (See Doc. 34 ¶¶ 40–62.) 8 Plaintiffs filed their original complaint three days after the October 27, 2020 report 9 revealing DOJ's first subpoena. (See Doc. 1 at 14–15, 21.) Eleven months later, Plaintiffs' 10 amended Complaint largely reiterates the original complaint but adds, among other things, 11 allegations by seven confidential witnesses. (See Doc. 34 ¶¶ 40–62.) Although these 12 confidential witness statements were added after the original complaint, they appear to 13 provide most of its basis. 14 The Court will credit confidential witness statements "where the confidential 15 witnesses are described with sufficient particularity to support the probability that a person 16 in the position occupied by the source would possess the information alleged," Zucco 17 Partners, 552 F.3d at 995 (internal quotations marks and citation omitted), and where the 18 complaint contains "adequate corroborating details," In re Daou Sys., Inc., 411 F.3d 1006, 19 1015 (9th Cir. 2005) (citation omitted). These details may include "the level of detail 20 provided . . . , the corroborative nature of the other facts alleged (including from other 21 sources), the coherence and plausibility of the allegations, the number of sources, the 22 reliability of sources, and similar indicia." Id. 23 With this guidance in mind, the Court reviews Plaintiffs confidential witness 24 statements in turn and together. See Tellabs, 551 U.S. at 322. The Court will then analyze 25 those witness statements that prove reliable together with Raytheon's disclosures and its 26 CEO's remarks under the 15 U.S.C. § 78u-4(b)(1) requirement to state "material" facts 27 "with particularity." 28 ///

10

1 a. Confidential Witness 1 ("CW1") 2 CW1 worked as a "Purchasing Agent and Subcontracts Manager" from July 2009 3 until August 2018, when CW1 was allegedly terminated for reporting misconduct. (Doc. 4 34 ¶¶ 40, 47). After termination, CW1 filed several whistleblower complaints with the 5 DOD. (Doc. 34 ¶ 49.) CW1's duties included "auditing procurement group pre-award and 6 post-award purchase order files for Contractor Purchasing System Review ('CPSR')."4 7 (Doc. 34 ¶ 40.) Because the Complaint provides CW1's title and job description, CW1 is 8 described with sufficient particularity to consider CW1's allegations. See, e.g., Daou, 411 9 F.3d at 1015 (crediting confidential witnesses that were numbered and given job 10 descriptions and responsibilities). But there is a fundamental weakness with CW1 and the 11 other witnesses that Plaintiffs may wish to address if they choose to amend the Complaint. 12 The confidential witness statements could be strengthened by providing orienting 13 information about each witness's place in Raytheon's large organization. Throughout the 14 Class Period, Raytheon employed 60,000–70,000 people. (Doc. 41-2 at 38.) In that context, 15 titles and job descriptions do not orient the Court as well as they might with a smaller 16 company or with titles like "CFO" or "COO" that need no explanation. 17 CW1 alleges "many instances of wrongdoing . . . related to a government contract 18 worth approximately $11.5 billion" and spanning throughout the Class Period. (Doc. 34 ¶ 19 41.) The contract provided various training support services for the DOD. (Doc. 34 ¶ 41.) 20 CW1 alleges misconduct under this contract including (1) failure to submit 155 sub- 21 contracts to a competitive bidding process, (2) miscoding labor as a direct charge, (3) 22 failure to provide Individual Work Authorizations to a procurement group, (4) failure to 23 receive long-lead material purchase authority for materials delivered after certain task 24 25 4 The Court takes judicial notice of the publicly available CPSR Guidebook. CPSR is 26 performed by the Defense Contract Management Agency (“DCMA”) and seeks to evaluate “the efficiency and effectiveness with which a contractor spends government funds and 27 complies with applicable contract terms, regulations, and government policy when 28 subcontracting.” DOD DCMA CPSR Guidebook (Sept. 10, 2021), https://www.dcma.mil/ Portals/31/Documents/CPSR/CPSR_Guidebook_091021.pdf.

11

1 orders' performance end date, (5) improper procurement from Chinese companies doing 2 business with North Korea, in violation of presidential executive orders, and (6) doctoring 3 dates and information on "certain contracts in advance of government reviews and audits," 4 in conspiracy with the sub-contractors. (Doc. 34 ¶¶ 41–46.) 5 Beyond the support services contract, CW1 alleges (1) "Operations & Maintenance 6 Funding" was misappropriated toward "Military Construction" in order to avoid requisite 7 approvals and oversight, (2) suppliers were improperly advanced payments, allowing 8 Raytheon to bill the government and book revenues earlier than permitted, (3) Raytheon 9 violated the Truth In Negotiations Act ("TINA") by obtaining competitor cost data "under 10 the table" and using it to secure awards, and (4) CW1 was fired for reporting this 11 misconduct to Raytheon's "Senior Director of Internal Audit" and its "Director of Ethics 12 and Business Conduct." (Doc. 34 ¶ 48.) 13 CW1's allegations about the support services contract have sufficient indicia of 14 reliability to credit them, such as the level of detail alleged and the relationship between 15 the allegations and CW1's job title and responsibilities. But CW1's allegations beyond the 16 support services contract lack adequate corroborating details because they are not clearly 17 related to CW1's job title or description. The Court therefore will credit CW1's allegations 18 about the support services contract but not with respect to the other misconduct alleged. 19 b. Confidential Witness 2 ("CW2") 20 CW2 was a "Senior Princip[al] Financial Analyst" from October 2016 to December 21 2018. (Doc. 34 ¶ 50.) CW2 reported to "the" Senior Finance Manager, and the Complaint 22 details the names of both persons in the role of Senior Finance Manager during CW2's 23 tenure. (Doc. 34 ¶ 50.) Finally, the Complaint describes CW2's employment scope as 24 "Global Business Services, working across all of Raytheon's divisions," and CW2's job 25 responsibilities as including "Internal Auditor who 'vetted [Raytheon's] proposals from 26 vendors and contractors and other companies." (Doc. 34 ¶ 50.) The Complaint states that 27 CW2's job responsibilities also included "review[ing] proposals to ensure that they were 28 financially sound [and] compliant with FAR and DFAR, and [reviewing] audit proposals

12

1 that met and/or exceeded the [TINA] threshold of $750,000 submitted through supply chain 2 management. [CW2] also audited proposals and other cost-saving initiatives." (Doc. 34 ¶ 3 51.) Because the Complaint provides CW2's title, reporting lines, and job description, CW2 4 is described with sufficient particularity to consider CW2's allegations. The Complaint 5 does not clarify whether "the" Senior Finance Manager is a single position within 6 Raytheon, what is the function of Raytheon's Global Business Services unit, and what are 7 "all Raytheon's divisions." 8 CW2 principally alleges that Raytheon failed to use a competitive bidding process 9 in awarding certain supplier contracts but nevertheless maintained the appearance of doing 10 so. (Doc. 34 ¶ 52.) CW2 explained that competitive bidding for subcontracts has the 11 "benefit" of showing the government that a company is "using due diligence to follow the 12 regulations, the guidelines they set in place." (Doc. 34 ¶ 52.) CW2 implies—but never 13 states explicitly—that competitive bidding for subcontracts is required under FAR or 14 DFAR guidelines to minimize government costs. (Doc. 34 ¶ 50.) CW2 further alleges that 15 Raytheon uses a color-coding system for its suppliers; those marked green "are good, 16 yellow means 'Go,' and Red means 'No.'" (Doc. 34 ¶ 53.) CW2 alleges that "[m]ost of the 17 suppliers Raytheon used were either green or red, and only a handful were yellow," but 18 could not explain "how a supplier could get out of the red category and go to the green one, 19 or why Raytheon didn't just cut off the suppliers in the red category." (Doc. 34 ¶ 54.) CW2 20 alleges that rather than solicit competitive bids from different suppliers, Raytheon instead 21 "favored" certain aerospace, defense, and missile suppliers they used repeatedly and placed 22 them "in the green category, irrespective of whether they qualified for the green rating." 23 (Doc. 34 ¶ 53.) CW2 estimated that "maybe about 30 percent" of the green suppliers 24 shouldn't have been green. (Doc. 34 ¶ 54.) CW2 did not explain the basis for stating that 25 certain suppliers shouldn't have been green. CW2 also did not explain the tension between 26 that statement and CW2's inability to explain Raytheon's continued use of red suppliers or 27 the criteria for a red supplier to become green. (See Doc. 34 ¶ 54.) Finally, CW2 also alleges 28 unspecified "obstacles" when working, being told "to keep my mouth shut," and that CW2's

13

1 superior said, "Just do your job. Don't ask questions." (Doc. 34 ¶ 54.) 2 Although CW2's allegations are sufficiently detailed, the Court finds CW2's 3 confusion about the color-coding system renders CW2's allegations insufficiently reliable 4 to credit on their own. 5 c. Confidential Witness 3 ("CW3") 6 CW3 worked as a "Senior Financial Analyst" from July 2012 to October 2015. (Doc. 7 34 ¶ 55.) CW3's scope of employment was "across all of the projects Raytheon handled, 8 including Missiles and Defense." (Doc. 34 ¶ 55.) Because the Complaint provides CW3's 9 title and job description, CW3 is described with sufficient particularity to consider CW3's 10 allegations. The Complaint does not clarify the relative rank of a "Senior Financial 11 Analyst," or whether "across all projects" includes literally every Raytheon contract. 12 CW3 alleges Raytheon "flowed down" its Estimates at Completion, which means 13 Raytheon slowed down the project "to get more money and more government funds." (Doc. 14 34 ¶ 55.) CW3 alleges that Raytheon "had all of the essential tools and funding" to complete 15 a project but nonetheless "would say, 'It's going to take longer. We need additional funds.'" 16 (Doc. 34 ¶ 55.) Specifically, CW3 alleges that Raytheon would slow down its Tomahawk 17 and Javelin missile projects and that the projects "could have been done sooner." (Doc. 34 18 ¶ 56.) Finally, CW3 alleges that it was "common practice for Raytheon to get extensions 19 for its projects and miss its Estimates at Completion," and that "almost every" project was 20 slowed down as it "was kind of becoming the norm around the place." (Doc. 34 ¶ 55.) 21 Although CW3's allegations are sufficiently detailed, they are insufficiently reliable 22 to credit on their own because CW3's job title and responsibilities do not clearly relate to 23 CW3's assessment that various projects could have been done sooner. 24 d. Confidential Witness 4 ("CW4") 25 CW4 was a "Principal Finance Analyst" in Raytheon's "Financial Controls 26 Department" from mid-2019 to fall 2020, reporting to the Finance Manager of Hypersonic 27 Weapons and Strategy. (Doc. 34 ¶ 58.) CW4 "handled all of the financial controls and earn 28 value" for "government contracts." (Id.) Because the Complaint provides CW4's title and

14

1 job description, CW4 is described with sufficient particularity to consider CW4's 2 allegations. The Complaint does not clarify the relative rank of a "Principal Finance 3 Analyst," what if any relationship that position has to a "Senior Financial Analyst," whether 4 Raytheon has one or many Financial Controls Departments, or the relative rank of the 5 "Finance Manager" to which CW4 reported. 6 CW4 alleges that shortly after joining Raytheon in mid-2019, CW4 learned from a 7 colleague that Raytheon was being investigated by the DOJ and "there were issues with 8 EACs." (Doc. 34 ¶ 58.) CW4 does not allege how handling "all the financial controls" for 9 government projects and measuring their value create a base of personal knowledge about 10 EACs. And although reliance on hearsay is not "automatically disqualify[ing]," hearsay 11 may be credited only where "sufficiently reliable, plausible, or coherent." Lloyd v. CVB 12 Fin. Corp., 811 F.3d 1200, 1208 (9th Cir. 2016) (crediting statements by a COO that were 13 specific in time, context, and details, and involved important communications between a 14 CEO and his Board). 15 The Court therefore finds that CW4's allegations are not sufficiently detailed or 16 reliable on their own to credit them. 17 e. Confidential Witness 5 ("CW5") 18 CW5 was a Vice President of Business Development in Raytheon's Air Warfare 19 Systems from December 2015 to mid-2017, reporting to Raytheon's Vice President of 20 Business Development for Missile Systems. (Doc. 34 ¶ 59.) Because the Complaint 21 provides CW5's title and job description, and because that title involves an obviously high- 22 level position, CW5 is described with sufficient particularity to consider CW5's allegations. 23 CW5's alleges that, after leaving Raytheon in mid-2017, "a former colleague and 24 friend still employed at Raytheon" told CW5 that (1) an internal audit showed $250 million 25 in false labor charges in several contracts within Raytheon's Missile Systems, and (2) that 26 several high-level Raytheon employees "'fudged the numbers' to ensure Raytheon met its 27 profit margins (and the employees got their bonuses)." (Doc. 34 ¶¶ 59, 60; Doc. 54 at 28 23:10–11.) These high-level employees included the "Deputy Vice President of Naval

15

1 Weapon Systems," the "Program Manager for Close-in Weapon Systems," and the 2 "Contract Director" for "the entire product line." (Doc. 34 ¶ 60.) CW5 does not say which 3 colleague and friend made the declaration, how that person was positioned to know the 4 information, or where that person got the information. CW5 also does not provide helpful 5 orienting information about the job titles of the three high-level employees. CW5's 6 deficiencies are significant because CW5's statements are hearsay. (Doc. 54 at 23:10–11.) 7 The Court therefore finds that, as with CW4, CW5's allegations are not sufficiently 8 detailed or reliable on their own to credit them. 9 f. Confidential Witness 6 ("CW6") 10 CW6 worked in Raytheon's "Executive Communications and Employee 11 Engagement" division from December 2016 to April 2020. (Doc. 34 ¶ 61.) CW6's 12 responsibilities included "among other things" writing speeches for the "president of 13 [Raytheon]" and editing Raytheon's newsletter. (Doc. 34 ¶ 61.) Because the Complaint 14 provides CW6's job description and reporting line, CW6 is described with sufficient 15 particularity to consider CW6's allegations. The Complaint does not clarify CW6's job title, 16 or the relative rank or role of "the president" of Raytheon. 17 CW6 alleges that in late 2018 or early 2019, a colleague told CW6 that "several 18 Raytheon employees" were "fudging numbers" on the contracts, and that "the Pentagon 19 was also looking into it, and they wanted answers." (Doc. 34 ¶ 61.) CW6 does not say 20 which colleague made the declaration, how that person was positioned to know the 21 information, where the person got the information, or what relationship the employees who 22 fudged numbers had to the Officers. These deficiencies are significant because CW6's 23 statements are hearsay. 24 The Court therefore finds that, as with CW4 and CW5, CW6's allegations are not 25 sufficiently detailed or reliable on their own to credit them. 26 g. Confidential Witness 7 ("CW7") 27 CW7 worked as a "Director of Digital Transformation" from October 2019 to 28 October 2020. (Doc. 34 ¶ 62.) CW7's responsibilities included "reengineering" Raytheon's

16

1 servers and "separating UTC from its parent company" after UTC merged with Raytheon. 2 (Doc. 34 ¶ 62.) Because the Complaint provides CW7's job title and description, CW7 is 3 described with sufficient particularity to consider CW7's allegations. The Complaint does 4 not clarify the relative rank of a "Director" of Digital Transformation or where CW7 sat 5 within Raytheon's corporate structure. 6 CW7 alleges that (1) "everything about Raytheon is shady," (2) "it's a** covering 7 all the way around," (3) Raytheon keeps no records of what "hundreds of millions dollars" 8 spent on outside contractors is for, (4) Raytheon paid "hundreds of millions of dollars" in 9 "funny money" to outside vendors, (5) Raytheon has no control over its contractors and no 10 accountability, and (6) "months and months" passed without contractors doing their work. 11 (Doc. 34 ¶ 62.) CW7's allegations are somewhat detailed but largely uninformed 12 impressions. See Police Ret. Sys. Of St. Louis v. Intuitive Surgical, Inc., 759 F.3d 1051, 13 1063 (9th Cir. 2014) (sales representative allegation based on three months' experience was 14 merely the "impression of a low-level employee[,] unsubstantiated [and] without substance 15 or context."). The Complaint does not establish how CW7's role upgrading servers 16 provided a basis for his sweeping pronouncements on Raytheon's management of 17 contractors or financial practices. This is significant because CW7's assertion that 18 Raytheon had "no" system of contractor accountability and control is facially implausible 19 given Raytheon's compliance obligations to the government and the apparently large 20 number of employees dedicated to ensuring government compliance. 21 The Court therefore finds that, as with CW2–CW6, CW7's allegations are not 22 sufficiently detailed or reliable on their own to credit them. 23 h. Combined Confidential Witness Allegations 24 Having reviewed the confidential witness statements individually, the Court next 25 considers them together. See Tellabs, 551 U.S. at 322 (considering the "Complaint in its 26 entirety"). At various points, the Complaint describes the confidential witnesses as 27 "corroborating" each other and Plaintiffs' theory of widespread fraud. (Doc. 34 at 2, 17, ¶¶ 28 58, 61.) The Complaint also implies that the witness statements are connected. (See Doc.

17

1 34 ¶¶ 52 ("CW2 witnessed similar misconduct"), 55 ("CW3 also witnessed misconduct"), 2 58 ("CW4 corroborates the information supplied by the other witnesses"), 59 ("CW5 also 3 recounted wrongdoing"), 61 ("The information supplied by these [witnesses] is also 4 corroborated by CW6"). Under Daou, the number of sources and "the corroborative nature 5 of other facts alleged (including from other sources)" bolsters the reliability of these 6 sources. 411 F.3d at 1015 (citation omitted). 7 At the outset, the Court disagrees with the Complaint's implication that the witness 8 statements corroborate each other and Plaintiffs' cause of action because all involve 9 misconduct. The witness statements corroborate each other only when they share specific 10 facts or elements. The witness statements corroborate Plaintiffs' cause of action only when 11 they share specific facts or elements with Plaintiffs' cause of action. Plaintiffs' cause of 12 action is not based on general misconduct, but rather specifically on misconduct revealed 13 by the DOJ investigation into Raytheon's financial accounting, internal controls over 14 financing, and cost reporting within Raytheon's Missiles and Defense business since 2009. 15 Therefore, witness statements corroborate Plaintiffs' cause of action when they relate to 16 financial accounting, internal controls over financing, and cost reporting within Raytheon's 17 Missiles and Defense business. 18 Only certain aspects of the witness statements corroborate each other. For example, 19 of CW1's many allegations, only a few are repeated in some manner by other witnesses. 20 CW1 alleges Raytheon failed to submit at least 155 sub-contracts to a competitive bidding 21 process in a support services contract with the DOD. (Doc. 34 ¶ 41, 42.) CW1 also alleges 22 Raytheon conspired with subcontractors to give the appearance of competitive bidding by 23 doctoring dates and information on "certain" subcontracts ahead of periodic government 24 audits. (Doc. 34 ¶ 46.) CW2 similarly alleges Raytheon gave the false appearance of 25 competitive bidding by placing "maybe about 30 percent" of "favored" defense and missile 26 suppliers in a green category "irrespective of whether they qualified for the green rating." 27 (Doc. 34 ¶ 52, 53.) CW1 alleges that Raytheon overcharged the government within a 28 support services contract by miscoding labor charges, mislabeling certain goods as

18

1 services, and inflating EACs. (Doc. 34 ¶¶ 43, 44.) CW3 similarly alleges that Raytheon 2 overcharged the government by charging labor to contracts when no labor was performed, 3 (Doc. 34 ¶ 60), and missing EACs by unnecessarily slowing down "almost every project." 4 (Doc. 34 ¶ 55.) CW4 similarly alleges hearing from a colleague that there were "issues" 5 with EACs subject to a DOJ investigation. (Doc. 34 ¶ 58.) Finally, CW5 alleges hearing 6 from a former colleague that an internal audit found three employees in Raytheon's Missiles 7 and Defense business had "fudged the numbers" by charging $250 million in false labor on 8 several naval weapons contracts. (Doc. 34 ¶ 60.) CW6 similarly alleges hearing from a 9 colleague that several Raytheon employees were "fudging numbers" on contracts. (Doc. 34 10 ¶ 61.) 11 The witness statements also corroborate only certain aspects of Plaintiffs' cause of 12 action. For example, CW2 alleges Raytheon avoided competitive bidding among "about 13 30%" of its defense and missile subcontractors through a color rating system. (Doc. 34 ¶ 14 53.) CW3 similarly alleges that Raytheon slowed down Tomahawk and Javelin missiles 15 projects, which presumably were within Raytheon's Missiles segment. (Doc. 34 ¶ 55, 56.) 16 CW5 similarly alleges hearing from a former colleague that an internal audit "showed at 17 least $250 million of false labor charges on several contracts related to Raytheon's naval 18 weapons system, which at the time was part of the Missile Systems." (Doc. 34 ¶ 59.) And 19 CW7 alleges that Raytheon is "shady," which could potentially speak to a pervasive culture 20 of misconduct also expressed by CW3 (slowing down contracts was "becoming the norm 21 around the place"), CW2 (when facing obstacles learned to "keep my mouth shut because 22 it didn't matter"), and CW1 (fired for reporting misconduct). 23 In conclusion, the Court's evaluation of Plaintiffs' witness statements reveals that 24 only a few are sufficiently reliable to credit. Only reliable statements can state "material" 25 facts "with particularity" under 15 U.S.C. § 78u-4(b)(1). These reliable witness 26 statements—along with Raytheon's disclosures and CEO earnings-call remarks—are the 27 Complaint's foundation for claiming Raytheon made false or misleading statements. 28 Having identified the Complaint's foundation, the Court turns to its § 78u-4(b)(1) analysis.

19

1 iv. Plaintiffs do not sufficiently allege materiality. 2 Plaintiffs' reasons for pleading Raytheon's statements were false or misleading do 3 not survive the Court's § 78u-4(b)(1) inquiry because they fail to allege materiality. 4 Although "[d]etermining materiality in securities fraud cases 'should ordinarily be left to 5 the trier of fact[,]'" SEC v. Phan, 500 F.3d 895, 908 (9th Cir. 2007) (quoting In re Apple 6 Computer Secs. Litig., 886 F.2d 1109, 1113 (9th Cir. 1989)), the Court is not instructed to 7 end all § 78u-4(b)(1) investigation where a plaintiff pleads any level of misconduct, no 8 matter how vague or apparently minor. That would set the bar for pleading a materially 9 false or misleading statement far too low—Plaintiffs could then plead a single instance of 10 misconduct to defeat a motion to dismiss on that basis. Rather, Plaintiffs "must show with 11 particularity how the [misconduct] affected the company's financial statements and 12 whether they were material in light of the company's overall financial position." Or. Pub. 13 Emps. Ret. Fund, 774 F.3d at 609 (citation omitted). Mere "conclusory statements . . . and 14 unwarranted inferences are insufficient [to state a claim]." In re Cutera Secs. Litig., 610 15 F.3d 1103, 1108 (9th Cir. 2010). The relevant inquiry is whether Plaintiffs plausibly allege 16 a "substantial likelihood that the disclosure of the omitted fact would have been viewed by 17 the reasonable investor as having significantly altered the 'total mix' of information made 18 available." TSC Indus., Inc. v. Northway, Inc., 426 U.S. 438, 449 (1976) (emphasis added) 19 (giving the summary judgment standard); Basic Inc. v. Levinson, 485 U.S. 224, 232 (1988) 20 (adopting the TSC Industries standard in a § 10(b) and Rule 10b-5 context). Therefore, 21 when assessing materiality the Court engages in "delicate assessments of the inferences a 22 'reasonable shareholder' would draw from a given set of facts and the significance of those 23 inferences to him." Siracusano, 585 F.3d at 1178. 24 Here, Plaintiffs do not quantify the extent to which Raytheon's misconduct resulted 25 in financial misstatements. For example, Plaintiffs allege Raytheon improperly recorded 26 revenues (e.g. Doc. 34 ¶ 80), but do not say how much revenue was improperly recorded. 27 Conclusory characterizations that the misstatements were "material," "gross," or 28 "significant," (see, e.g., Doc. 34 ¶¶ 4, 98), do not suffice. It also does not suffice to

20

1 accompany conclusory characterizations with general statements about how much revenue 2 Raytheon earned, leaving it to the Court to infer that if reported revenues were material, 3 any accompanying misconduct must also have been material. (See, e.g., Doc. 34 ¶ 50.) 4 Plaintiffs allege Raytheon failed to measure or manipulated its EACs by slowing down 5 projects, (e.g. Doc. 34 ¶ 83), but do not say how many contracts were involved or the degree 6 to which the projects were slowed down. Plaintiffs allege Raytheon misappropriated funds 7 and violated FAR and DFAR protocols by avoiding competitive bidding, (e.g. Doc. 34 ¶¶ 8 42, 94), but do not say what funds were misappropriated or which contracts were affected. 9 And Plaintiffs allege Raytheon overcharged DOD, overpaid for contractors due to lack of 10 competitive bidding, and made payments to forbidden contractors, (e.g. Doc. 34 ¶ 95), but 11 do not say which materials or jobs were impacted, or how many supplies or contractors. 12 Without this information, Plaintiffs cannot allege a substantial likelihood that a reasonable 13 investor would find the information material given Raytheon's overall financial position. 14 Plaintiffs' attempts to provide details through Raytheon's disclosures are similarly 15 unavailing. In fact, Raytheon's disclosures directly undermine Plaintiffs' argument. Both 16 disclosures and the CEO's earnings-call remarks stated that DOJ's investigation would not 17 have a material impact on Raytheon's financial condition. The April 2021 disclosure and 18 earnings-call remarks both described the investigation as involving three contracts from 19 2011–2013 and one from 2017—at least not obviously something a reasonable investor 20 would be alarmed about given Raytheon's "tens of thousands" of contracts per year. The 21 context of the disclosures also undermines Plaintiffs' attempt to plead materiality. The 22 October 2020 disclosure mentioned the COVID-19 pandemic more than seventy times, 23 stating "[o]ur business and operations and the industries in which we operate have been 24 significantly impacted by [COVID-19]," and "our airline customers have reported 25 significant reductions in fleet utilization . . . and have deferred and, in some cases, cancelled 26 new aircraft deliveries." (Doc. 41-3 at 14.) On an accompanying earnings call the same 27 day, Raytheon's CEO stated, "We're taking the difficult but necessary actions to reduce 28 headcount . . . . We'll reduce about 20% of our commercial aero headcount; that's about

21

1 15,000 positions. We're also taking out [an additional 5,000 contractor and corporate 2 positions]." (Doc. 41-7 at 6.) Both disclosures revealed Raytheon's assets exceeded $160 3 billion and quarterly net sales were more than $15 billion. (Doc. 41-3 at 6, 8; Doc. 41-9 at 4 5, 7.) And both disclosures included assurances from an independent auditor that 5 Raytheon's financial statements were accurate. (Doc. 41-3 at 56; Doc. 41-9 at 36.) Given 6 this context, Plaintiffs have not met their burden of alleging a substantial likelihood of 7 significantly altering the total information mix of information available to investors. 8 Plaintiffs' attempt to provide details through the confidential witness statements is 9 also unsuccessful. What the witness statements have in common does not plausibly allege 10 materiality. CW1's and CW2's allegations that Raytheon gave the false appearance of 11 competitive bidding fail to describe any overcharges at all—rather, they rest on an unstated 12 assumption that because competitive bidding typically results in lower costs, the absence 13 of competitive bidding they observed in "at least 155 sub-contracts" and "maybe about 30 14 percent" of Raytheon's subcontractors resulted in materially higher costs. Similarly, CW1's, 15 CW3's, and CW4's allegations of overcharging fail to state or even estimate the degree of 16 these overcharges. CW3's claim that Raytheon unnecessarily slowed down "almost every 17 project" gets closest to pleading materiality but cannot be fully credited because no other 18 confidential witness claimed overcharging at that scale. Finally, CW5's and CW6's 19 allegations that they heard from colleagues about a few employees fudging numbers on 20 several naval weapons contracts, even with the posited $250 million figure, does not 21 plausibly allege a substantial likelihood of material misconduct given Raytheon's more 22 than 60,000 employees, tens of thousands of annual contracts, and almost $30 billion in 23 annual sales. (See Doc. 41-2 at 38.) 24 What the witness statements have in common with Plaintiffs' cause of action also 25 does not plausibly allege materiality. Even giving full credit to CW2's allegations of false 26 competitive bidding with 30% of Raytheon's missiles and defense subcontractors, CW3's 27 allegations of slowed down Tomahawk and Javelin projects, and CW5's hearsay allegation 28 that several contracts within Raytheon's missiles and defense segment were fudged by $250

22

1 million—even then the Court cannot determine whether the alleged violations were minor 2 and technical or widespread and significant without more detail. Likewise, the witnesses' 3 various implications that Raytheon permitted a culture of widespread misconduct either are 4 not tied to Plaintiffs' cause of action, do not account for Raytheon's large compliance and 5 audit divisions, or do not estimate an effect that a reasonable investor would be 6 substantially likely to find significantly altered the total mix of available information. 7 Moreover, full credit is not warranted for the more detailed allegations. CW2 was not 8 familiar enough with the subcontractor color-coding system to determine widespread 9 issues with it. CW3's discussion of Tomahawk and Javelin overstatements is corroborated 10 by no other witness. And CW5's allegations are based on an unknown former colleague's 11 statements, corroborated only by another witness's hearsay, and potentially inconsequential 12 given Raytheon's size. 13 v. Plaintiffs do not state the Complaint's basis with particularity. 14 Plaintiffs' reasons for pleading Raytheon's statements were false or misleading also 15 do not survive the Court's § 78u-4(b)(1) inquiry because they are insufficiently particular. 16 Particularity is not established by contending that "virtually every statement made . . . 17 during the Class Period related to the company's financial . . . performance was, by 18 definition, false." Metzler, 540 F.3d at 1070. Particularity also requires more than general 19 allegations that certain practices resulted in a false or misleading report. Daou, 411 F.3d at 20 1007 (citation omitted). Rather, Plaintiffs must identify 'the who, what, when, where, and 21 how of the misconduct charged,' as well as 'what is false or misleading about [the 22 purportedly fraudulent] statement, and why it is false.'" Cafasso, United States ex rel. v. 23 Gen. Dynamics C4 Sys., Inc., 637 F.3d 1047, 1055 (9th Cir. 2011) (alteration in original) 24 (quoting Ebeid ex rel. United States v. Lungwitz, 616 F.3d 993, 998 (9th Cir. 2010)). 25 Here, Plaintiffs claim that widespread fraud at Raytheon resulted in overstatement 26 of virtually all Raytheon's finances for an unknown period of time, rendering all statements 27 about effective internal controls false or misleading. That claim is like the insufficiently 28 particular claim in Metzler, where plaintiffs alleged all of a college's financial results were

23

1 false and misleading as the result of a company-wide scheme to inflate enrollment figures 2 and misappropriate financial aid funding. Metzler, 540 F.3d at 1070. In their Response, 3 Plaintiffs underline several allegations in an attempt to clarify why the Complaint was not 4 insufficiently particularized: 5 The Complaint identifies the inflated net sales/revenues, operating expenses, and operating income for each applicable quarter, each applicable six-month 6 and nin[e]-month period, and each applicable year affected during the Class 7 Period. For example, for the three months ended July 3, 2016, the Complaint pleads inflated net sales/revenues of $6.035 billion, inflated operating 8 expense of $5.075 billion, and inflated operating income of $960 million. ¶ 9 112. For the six months ended July 3, 2016, the Complaint pleads inflated net sales/revenues of $11.798 billion, inflated operating expense of $10.226 10 billion, and inflated operating income of $1.572 billion. Id. For the quarter 11 ended September 29, 2019, the Complaint pleads inflated net sales/revenues of $7.446 billion, inflated operating expense of $6.240 billion, and inflated 12 operating income of $1.206 billion. ¶ 237 (also setting forth numbers for the 13 nine months ended September 29, 2019).

14 (Doc. 43 at 16.) But this response inadvertently underlines precisely what is wrong with 15 the Complaint: it mistakes a specific reference to specific documents for pleading a fact 16 with particularity. Daou provides a helpful contrast. In Daou, the court reversed a district 17 court order granting a motion to dismiss under different circumstances. There, the plaintiffs 18 asserted that defendants ignored their stated method of revenue recognition. Daou, 411 19 F.3d at 1017. The Daou court credited detailed allegations, directly corroborated by several 20 credible confidential witnesses, that the individual defendants would manually adjust the 21 project percent-completion metric upward without reference to how much of the project 22 was actually complete. Id. at 1018. That is very different from Plaintiffs' case. Here, the 23 confidential witness accounts are loosely connected and largely unreliable. Plaintiffs ask 24 the Court to infer from them, in essence, that some of the alleged misconduct must have 25 affected Raytheon's financial reporting at some point to some extent. To accept that 26 inference would permit improperly general allegations. 27 Plaintiffs' effort to clarify why Raytheon's line metrics were misleading is similarly 28 unavailing. The Response repeats the Complaint's section describing some of Raytheon's

24

1 accounting framework and then, without explanation, repeats several of the Complaint's 2 conclusory allegations that Raytheon "improperly recorded revenues," "misused and 3 misappropriated [DOD] funds," "violated . . . its obligations under FAR and FARS," and 4 "manipulated information [provided] to the federal government." (Doc. 43 at 16–17.) This 5 approach—placing uncontested information next to general or conclusory allegations 6 without explaining the connection—is found throughout the Complaint. For example, CW3 7 alleges that the Tomahawk and Javelin missile projects "could have been done sooner." 8 (Doc. 34 ¶ 56.) In the next paragraph, the Complaint lists all income Raytheon earned from 9 these projects between 2014 and 2019. (Doc. 34 ¶ 57.) What is lacking in both the 10 Complaint and the Response is the connection between the specific allegation and the 11 estimated extent to which it impacted a specific line item or financial statement. 12 The confidential witness allegations of myriad improper practices are also 13 insufficiently particular because they either do not support Plaintiffs' theory, are 14 insufficiently reliable, or lack specificity. If CW5's and CW6's hearsay allegations were 15 credited, for example, they would suggest misconduct by only a few employees in a few 16 contracts. That is similar to Raytheon's two disclosures and earnings call remarks, which 17 directly undercut Plaintiffs' theory because they implicate investigations of misconduct in 18 only four contracts. More importantly, many of the confidential witnesses lack a clear 19 foundation for their allegations, notwithstanding their provided job title and scope. 20 CW1 is illustrative. The Complaint does not describe CW1's place in Raytheon's 21 organization or who CW1 reported to. Given that Raytheon employed between 60,000 and 22 70,000 people during the Class Period, CW1's title of "Manager" and selected duty is less 23 helpful in assessing CW1's allegations than it might be in a smaller company. The 24 Complaint also does not articulate a connection between CW1's title, selected duty, and the 25 Complaint's allegations of ineffective financial reporting and disclosure controls, 26 manipulation of contract revenue and cost estimates, and misrepresentation of key financial 27 measures. The Complaint does not allege that CW1 was involved with financial reporting 28 or assessing Raytheon's internal controls. Instead, the Complaint implies (and Plaintiffs'

25

1 Response reiterates) that CW1 helped to "ensure compliance with U.S. government 2 requirements." (Doc. 34 ¶¶ 40–49; Doc. 43 at 12.). Given this vague description, several 3 questions remain: How much of Raytheon's business was CW1 privy to? How did CW1 4 conduct an "evaluation" of purchase-order files, and were these evaluations reported to 5 anyone within the Officers' ambit? Were CW1's purchase-order file audits supported or 6 supplemented by financial or legal divisions within Raytheon? If not, what training did 7 CW1 receive to identify financial and legal issues? If the "government requirements" that 8 underlay CW1's audits were the DCMA's CSPR, were CW1's audits coextensive with 9 CSPR guidelines and review, or more limited? Without pleading particular facts to answer 10 these questions, the foundation of CW1's many allegations is unclear. 11 CW3's and CW4's accounts suffer similar issues. As with CW1, the Complaint 12 provides no information about CW3's and CW4's reporting lines or place within Raytheon's 13 large organization. Is a "Senior Financial Analyst" working across all Raytheon projects 14 (CW3) within the same group as a "Senior Principal Financial Analyst" working across all 15 Raytheon divisions and reporting to "the" Senior Finance Manager (CW2)? The Complaint 16 does not say. The Court also notes that CW3 did not work at Raytheon during the Class 17 Period. Although that fact does not defeat all relevance given the long-term nature of many 18 Raytheon contracts, it does weaken CW3's reliability further. 19 For the reasons above, the Court finds that, without more, Plaintiffs' allegations do 20 not sufficiently allege "materially" false or misleading statements "with particularity" 21 under the PLSRA's heightened pleading standards. Although this is independently 22 sufficient to grant Motion I, the Court considers below the other contested § 10(b) 23 elements, scienter and loss causation. 24 b. Scienter 25 To adequately plead scienter, a complaint must allege at least one of the individual 26 defendant Officers "made false or misleading statements either intentionally or with 27 deliberate recklessness." Zucco Partners, 552 F.3d at 991 (citing Daou, 411 F.3d at 1014– 28 15). Plaintiffs must allege "a highly unreasonable omission, involving not merely simple,

26

1 or even inexcusable negligence, but an extreme departure from the standards of ordinary 2 care, and which presents a danger of misleading buyers or sellers that is either known to 3 the defendant or is so obvious that the actor must have been aware of it." Id. Following 4 Tellabs, courts in this circuit conduct a dual inquiry: first, determining whether any of the 5 plaintiff's allegations, standing alone, create a strong inference of scienter; and second, if 6 the allegations are individually insufficient, conducting a "holistic" review of the same 7 allegations to determine whether they combine to create a strong inference of intentional 8 conduct or deliberate recklessness. Id. at 992. 9 Under the PSLRA, a complaint must "state with particularity facts giving rise to a 10 strong inference that the defendant acted with the required state of mind." 15 U.S.C. § 78u- 11 4(b)(2)(A). The PSLRA's "strong inference" requirement "has teeth." Nguyen, 962 F.3d at 12 413. It "unequivocally raised the bar for pleading scienter." Tellabs, 551 U.S. at 321 13 (quotations omitted) (alteration adopted). Given the substantial costs that securities fraud 14 litigation can impose, the "strong inference" standard reflects Congress's attempt to halt 15 early on securities litigation that lacks merit or is even abusive, while allowing plaintiffs 16 with potentially winning claims to proceed to discovery. See id. at 323–24. A complaint 17 survives the PSLRA's "strong inference" standard "only if a reasonable person would deem 18 the inference of scienter cogent and at least as compelling as any opposing inference one 19 could draw from the facts alleged." Id. at 324. 20 Here, Plaintiffs plead the Officers' conduct was intentional or deliberately reckless 21 based on the following: (1) the seven confidential witness statements; (2) alleged violations 22 of Generally Accepted Accounting Practices ("GAAP"); (3) the DOJ investigation; (4) 23 Raytheon's Sarbanes-Oxley certifications; (5) the Officers' personal stock sales during the 24 Class Period; (6) the termination of Raytheon's Missile Systems CFO in 2018 and VP 2019; 25 and (7) that U.S. government contracts form the core of Raytheon's operation. Following 26 Tellabs, the Court addresses each of these allegations in turn, then together. 27 i. Confidential Witness Statements 28 The seven confidential witness statements form the primary basis for Plaintiffs'

27

1 argument that the Officers' conduct was intentional or deliberately reckless. The Court 2 analyzes confidential witness statements for scienter much like it analyzes them for falsity. 3 For that reason, some of the Court's analysis will draw on the foregoing falsity section 4 III(a)(iii)(2) above. A complaint relying on confidential witness statements for scienter 5 must pass two hurdles: (1) the confidential witnesses must be described with sufficient 6 particularity to establish their reliability and personal knowledge; and (2) the witness's 7 statements must be indicative of scienter. Zucco Partners, 552 F.3d at 995 (citing Daou). 8 In Zucco Partners, the Court carefully followed the Daou standard for evaluating each 9 confidential witness. Id. The Court concluded that the witnesses were described with "a 10 large degree of specificity" because their job description and responsibilities were 11 provided. Id. More specifically, the witnesses worked directly on the accounting software 12 system alleged to have been manipulated, one reported to the president of the company's 13 biggest divisions, another was the vice president of that section, and another reported 14 directly to the CEO. Id. But the Court also concluded the witness statements were 15 insufficiently based on their personal knowledge because they were "not positioned to 16 know the information alleged, many report[ed] only unreliable hearsay, and others 17 allege[d] conclusory assertions of scienter." Id. (noting also that two were not employed at 18 the company during the period in question and had only secondhand information, and other 19 allegations were vague). Armed with Daou's prongs and Zucco Partner's instruction, the 20 Court again considers Plaintiffs' confidential witnesses in turn and together. 21 Here, and as discussed above in Section III(a)(iii)(2), the Complaint describes the 22 confidential witnesses with sufficient particularity because it provides a job title and 23 description for each. But CW4, CW5, CW6, and CW7 cannot survive Daou's first prong 24 because their accounts are not based on personal knowledge—the first three are based on 25 hearsay without other indicia of reliability, and CW7's role upgrading servers does not 26 provide a sufficient basis to evaluate Raytheon's subcontractor management or financial 27 procedures. The remaining witnesses—CW1, CW2, and CW3—cannot survive Daou's 28 second prong even if they clear the first because none of them allege that they either

28

1 reported to the Officers, had any interaction with the Officers, or that any of the Officers 2 knew about any misconduct. Their accounts therefore do not indicate the Officers' scienter. 3 The confidential witness accounts are no more probative when taken together. 4 Limited corroborating aspects of their accounts produce some indication that Raytheon 5 gave the false appearance of competitive bidding and overcharged certain contracts by 6 slowing them down more than necessary, and that a few employees fudged several 7 contracts. These combined allegations still do not plausibly allege the Officers' scienter 8 because, like in Zucco Partners, the allegations are largely from people either poorly 9 positioned to know the information alleged, based on unreliable hearsay, or conclusory. 10 None specifically allege scienter. Perhaps most important, even when combined and 11 viewed favorably for Plaintiffs, the witness accounts are still less plausible than the 12 competing, benign inference urged by Raytheon that any misconduct involved only a few 13 contracts, and the Officers were unaware until they began investigating alongside the DOJ. 14 (Doc. 54 at 38:11–15.) 15 ii. Alleged GAAP Violations 16 Certain alleged GAAP violations form the second basis for Plaintiffs' argument that 17 the Officers' conduct was intentional or deliberately reckless. The Complaint alleges that 18 Raytheon committed several GAAP violations indicative of scienter, specifically by (1) 19 reporting revenue before it was earned and (2) manipulating Estimates at Completion. 20 (Doc. 34 at 35–36, 72–74; Doc. 43 at 27–28.) Publishing inaccurate accounting figures or 21 failing to follow GAAP, without more, is not sufficient to establish scienter. Lloyd, 811 22 F.3d at 1207. To raise a strong inference of scienter, the Complaint must allege facts 23 demonstrating that defendants "knowingly and recklessly engaged in an improper 24 accounting practice"—for example, that a company's external auditors counseled against a 25 practice or that a company's CFO was aware that the practice was improper. Id. (citing 26 Metzler, 540 F.3d at 1068–69). 27 Here, the alleged GAAP violations do not raise a strong inference of scienter. First, 28 Plaintiffs do not allege particularized facts showing the extent of the violations. The

29

1 Complaint states that Raytheon (1) overcharged the government with improper billing 2 procedures, (2) intentionally prolonged projects and made unnecessary orders, (3) failed to 3 submit sub-contracts for competitive bidding, (4) misappropriated funds, (5) conducted 4 business with companies in violation of executive orders, and (6) doctored contracts to 5 conceal misconduct. (Doc. 34 ¶ 80.) These allegations appear to come entirely from the 6 confidential witness statements, and consequently suffer the limitations already detailed 7 above in Sections III(a)(iii)(2) and III(b)(i). Moreover, the allegations fail to describe the 8 extent to which the practices impacted Raytheon's financial statements. Overstating 9 "revenues in violation of GAAP may support a plaintiff's claim of fraud," but only if the 10 plaintiff shows "with particularity how the adjustments affected the company's financial 11 statements and whether they were material in light of the company's overall financial 12 position." Or. Pub. Emps. Ret. Fund, 774 F.3d at 609 (citation omitted). Merely stating that 13 revenue figures "were materially overstated" (e.g. Doc. 34 ¶ 94) or "were inflated" (Doc. 14 43 at 27) is insufficiently particular because it does not permit evaluation of whether the 15 alleged GAAP violations were minor or isolated, or instead widespread and significant. 16 Second, Plaintiffs do not allege that external auditors counseled against Raytheon's 17 practices. In fact, an independent auditor certified Raytheon's controls and procedures 18 every year of the Class Period. (See, e.g., Doc. 41-2 at 87–89.) In 2019, for example, 19 Raytheon's independent-auditor report highlighted revenue recognition as a "Critical Audit 20 Matter" and stated that: 21 Due to the nature of the work required to be performed on many of the Company's performance obligations, the estimation of total revenue and cost 22 at completion is complex, subject to many variables and requires significant 23 judgment by management on a contract by contract basis.

....

24 [Continuing to detail these procedures and ultimately concluding:] In our 25 opinion, the consolidated financial statements referred to above present fairly, in all material respects, the financial position of the Company as of 26 December 31, 2019 and 2018, and the results of its operations and its cash 27 flows for each of the three years in the period ended December 31, 2019 in conformity with accounting principles generally accepted in the United 28 States of America.

30

1 (Doc. 41-2 at 88.) Plaintiffs cite several cases for the proposition that independent auditor 2 opinions do not rule out or negate an inference of scienter. (Doc. 43 at 42.) Fair enough. 3 But the Court views the independent auditor report merely as one of several things that 4 weaken the inference Raytheon's Officers knew they were violating GAAP. An 5 independent audit report may not "rule out" scienter, but it certainly increases the lengths 6 to which the Officers' fraud would have to go to avoid detection. That, in turn, decreases 7 the force of Plaintiffs' observation that, in essence, GAAP violations require intent. 8 Finally, Plaintiffs do not specifically allege that the CFO or any of the individual 9 Officers were aware that Raytheon's practices were improper—only that they must have 10 been given the severity of the violations. For all these reasons, the Court finds that the 11 Complaint's allegations of GAAP violations are insufficient on their own to support a 12 strong inference of scienter. 13 iii. DOJ Investigation 14 The DOJ investigation disclosure forms the third basis for Plaintiffs' argument that 15 the Officers' conduct was intentional or deliberately reckless. Plaintiffs' Response seeks to 16 clarify the Complaint by stating that the DOJ investigation strengthens an inference of 17 scienter. (Doc. 43 at 18.) Plaintiffs' out-of-circuit citation for this principle supports the 18 uncontroversial principle found in Tellabs that the Court must conduct a holistic analysis 19 and consider the Complaint in its entirety. Compare Tellabs, 551 U.S. at 322, with Frank 20 v. Dana Corp., 646 F.3d 954, 960–62 (6th Cir. 2011); Collier v. ModusLink Glob. Sols., 21 Inc., 9 F. Supp. 3d 61, 76 (D. Mass. 2014). But an investigation, standing alone, is not 22 enough to raise any inference of scienter, much less a strong inference. Zamir v. 23 Bridgepoint Educ., Inc., 2018 WL 1258108 (S.D. Cal. Mar. 12, 2018) (citing In re Maxim 24 Integrated Prods., Inc. Sec Litig., 639 F. Supp. 2d 1038, 1047 (N.D. Cal 2009); In re 25 Hansen Natural Corp. Sec. Litig., 527 F. Supp. 2d 1142, 1162 (C.D. Cal. 2007)). The Court 26 will therefore only consider the DOJ investigation in the context of the Tellabs holistic 27 analysis below. 28 ///

31

1 iv. Sarbanes-Oxley certifications 2 The Officers' Sarbanes-Oxley certifications form the fourth basis for Plaintiffs' 3 argument that the Officers' conduct was intentional or deliberately reckless. Plaintiffs' 4 Response seeks to clarify the Complaint by emphasizing the Officers' Sarbanes-Oxley 5 certifications support scienter "when considered with the rest of the Complaint." (Doc. 43 6 at 20–21.) The Court understands this as a concession that the certifications add nothing to 7 an inference of scienter individually. See also Zucco Partners, 552 F.3d at 1003–04 8 ("[R]equired certifications under Sarbanes–Oxley . . . add nothing substantial to the 9 scienter calculus . . . . [and] are not sufficient, without more, to raise a strong inference of 10 scienter."). The Court will therefore only consider the Officers' Sarbanes-Oxley 11 certifications in the context of the Tellabs holistic analysis below. 12 v. Officers stock sales during the Class Period 13 The Officers' personal stock sales form the fifth basis for Plaintiffs' argument that 14 the Officers' conduct was intentional or deliberately reckless. In a section titled "Additional 15 Scienter Allegations," the Complaint alleges that the Officers' disposal of Raytheon stock 16 during the Class Period supports a strong inference of scienter. (See Doc. 34 ¶¶ 272–277.) 17 The Complaint further alleges these stock sales were inconsistent with the Officers' trading 18 history because the net proceeds from these sales were grossly disproportionate to the net 19 proceeds the Officers received in "the equivalent time period pre-dating the Class Period." 20 (Doc. 34 ¶ 272.) The Complaint then compares the net proceeds of each Officer's stock 21 sales between 2011 and 2016 with the net proceeds of their stock sales between 2016 and 22 2020 (the Class Period). (Doc. 34 ¶¶ 273–275.) Finally, the Complaint cites a 2016 23 newspaper article reporting one Officer's total compensation increased 49% from 2014. 24 (Doc. 34 ¶ 277.) 25 Stock sales may provide circumstantial evidence of scienter when they are 26 "dramatically out of line with prior trading practices at times calculated to maximize the 27 personal benefit from undisclosed inside information." Ronconi v. Larkin, 253 F.3d 423, 28 437 (9th Cir. 2001). To determine whether sales were "dramatically out of line," courts

32

1 assess three factors: "(1) the amount and percentage of the shares sold; (2) the timing of 2 the sales; and (3) whether the sales were consistent with the insider's trading history." 3 Metzler, 540 F.3d at 1067. To help this analysis, the Complaint must "provide a meaningful 4 trading history for purposes of comparison to the stock sales within the class period." Zucco 5 Partners, 552 F.3d at 1005 (internal quotation marks and citation omitted). 6 Here, Plaintiffs fail to provide essential information to support their claim. The 7 Complaint does not provide the amount and percentage of the shares the Officers sold, only 8 the net proceeds from those shares. The Complaint also does not discuss the timing of these 9 sales except to show that the net proceeds between 2011 and 2016 were lower than the net 10 proceeds between 2016 and 2020. The Complaint also does not explain how the sales were 11 inconsistent with the Officers' trading history except in reference to the net proceeds of 12 these sales. But net proceeds are a function of a stock's value, which changes over time. A 13 stock sale at any time likely would yield net proceeds different from any other time. 14 Different net proceeds therefore cannot be evidence of an inconsistent trading history. That 15 may be why the Ninth Circuit factors do not include net proceeds. Finally, the Complaint 16 also does not explain how an increase in an Officer's "total compensation" is related to that 17 Officer's trading history or otherwise relevant. Because Plaintiffs have failed to allege any 18 facts showing that the Officers' stock sales were "dramatically out of line" with their trading 19 history, the Court finds that the stock sales do not support a strong inference of scienter.5 20 /// 21 5 22 If Plaintiffs choose to amend, they will want to provide substantially more information about the Officers’ stock sales. This might include how close the Officers’ sales were in 23 time to the DOJ investigation disclosure, or whether a sale was followed by a buyback 24 during the dip. Plaintiffs will also want to explain how the Officers’ stock sales in the five years preceding the Class Period provide a meaningful comparison if company-wide fraud 25 was ongoing well before the Class Period began. (See generally Doc. 34 (not alleging when 26 the fraud began); see also Doc. 26-1 at 3 (“Raytheon’s malfeasance likely preceded the start of the Class Period by six to seven years, considering that the DOJ subpoena . . . seeks 27 information . . . going back to 2009.”). Unless the fraud began at the start of the Class 28 Period, sales preceding the Class Period would provide no meaningful comparison because they would also be suspect.

33

1 vi. Raytheon's Missile Systems CFO and VP Terminations 2 Two high-level employee terminations in 2018 and 2019 form the sixth basis for 3 Plaintiffs' argument that the Officers' conduct was intentional or deliberately reckless. The 4 Complaint implies and the Response clarifies that the termination of Raytheon's Missile 5 Systems CFO and VP support a strong inference of scienter. (Doc. 34 ¶¶ 60–61; Doc. 43 6 at 30.) Plaintiffs state that Raytheon's Missile Systems CFO was terminated "around [2018, 7 when CW5 heard from a former colleague that three employees were 'fudging the number' 8 and had added $250 million in false labor charges on several contracts]." (Id.) Plaintiffs 9 also state the Missile Systems CFO reported to the Missile Systems VP, who was 10 terminated in 2019. (Id.) And Plaintiffs emphasize the Missile Systems VP reported to one 11 of the Officers. (Id.) Particularized allegations that a termination was "uncharacteristic 12 when compared to . . . typical hiring and termination patterns" or "accompanied by 13 suspicious circumstances" may support an inference of scienter. Zucco Partners, 552 F.3d 14 at 1002. In Zucco Partners, the complaint alleged scienter based on the CFO's retirement 15 just before disclosure of improper accounting and lack of financial controls, and two 16 controllers' resignations during the class period. Id. The Zucco Partners court declined to 17 infer scienter because the complaint did not allege details about the termination, and the 18 accounts were "based on vague hearsay allegations." Id. 19 The employee-termination allegations come from CW5 and CW6, whose 20 limitations due to hearsay are discussed above. But even crediting them for a moment, they 21 do not support a strong inference of scienter. Plaintiffs want the Court to infer that the 22 Missile System CFO and VP were fired because they facilitated or directed the fraud within 23 their segment. But even if the Court accepts that inference, it directly undermines Plaintiffs' 24 theory that the Officers themselves were participating in or recklessly disregarding 25 widespread misconduct. Terminating wrongdoers for committing fraud is the opposite of 26 recklessly disregarding fraud. Plaintiffs similarly do not explain why terminations for fraud 27 suggest the Officers were complicit. And Plaintiffs do not explain how the terminations 28 support an inference the Officers knew their internal controls or financial statements were

34

1 misleading—if anything, an internal audit uncovering fraud supports the benign inference 2 that internal controls were working as intended to root out bad behavior. The Court must 3 weigh Plaintiffs' inference against all competing, benign inferences. Here, the more 4 plausible inference is that the CFO and VP terminations either were unrelated to fraud 5 involving several contracts in their segment or were a consequence of their failure to 6 uncover the fraud before an internal audit did. Either way, these benign inferences are more 7 plausible than the inference that the terminations were for participation in fraud—and 8 certainly more plausible than the convoluted inference that the Officers somehow both 9 participated in or disregarded the fraud while also taking steps to address it. For these 10 reasons, the Court finds that, even when credited despite their appearance in vague hearsay 11 allegations, the Missile Systems CFO and VP terminations do not support a strong 12 inference of scienter. 13 vii. "Core Operations" theory 14 Plaintiffs' Response raises a "core operations" theory not found in the Complaint but 15 drawing on several of its allegations. (Doc. 43 at 18–22.) This theory forms the seventh 16 basis for Plaintiffs' argument that the Officers' conduct was intentional or deliberately 17 reckless. The Court construes Plaintiffs' argument as clarifying an aspect of "the Complaint 18 in its entirety." 19 The Court may in unusual cases infer scienter solely because the alleged 20 wrongdoing involves a company's "core operations," or when the complaint alleges the 21 individual defendants actually knew of the disputed core documents. City of Dearborn 22 Heights Act 345 Police & Fire Retirement System v. Align Technology, Inc., 856 F.3d 605, 23 620 (9th Cir. 2014). Generally, allegations about "management's role in a corporate 24 structure and the importance of the corporate information about which management made 25 false or misleading statements" create a strong inference of scienter only "when made in 26 conjunction with detailed and specific allegations about management's exposure to factual 27 information within the company." Id. (citing S. Ferry LP, No. 2 v. Killinger, 542 F.3d 776, 28 785 (9th Cir. 2008)). But occasionally, in the "exceedingly rare" case where misconduct is

35

1 "patently obvious" and it would be "absurd" to suggest that management was without 2 knowledge of it, the Court may infer scienter based solely on the fact that the allegations 3 involve the company's "core operations." S. Ferry LP, No. 2, 542 F.3d at 785 n.3, 786; see 4 also Police Ret. Sys., 759 F.3d at 1063. Alternately, the Court may infer scienter based 5 solely on a core operations theory if the plaintiffs allege that the individual defendants 6 actually knew of the disputed core operations. See, e.g., Daou, 411 F.3d at 1022–23. 7 Plaintiffs argue that because the U.S. government was Raytheon's biggest and most 8 important customer, and because the alleged misconduct involved multiple U.S. 9 government contracts, and because the Officers admitted that several of these contracts 10 were "tainted with wrongdoing," it would be "absurd to suggest" that the Officers did not 11 know about "the misconduct" during the Class Period.6 (Doc. 43 at 19, citing Doc. 34 ¶¶ 12 35, 41, 270–271).) Plaintiffs' argument is unpersuasive for two reasons. First, "absurdity" 13 is a very high bar not reached in cases with more extreme facts than this one. See, e.g., In 14 re NVIDIA Corp. Sec. Litig., 768 F.3d 1046, 1063–64 (9th Cir. 2014) (affirming no scienter 15 where allegations concerned company's "flagship product" and "two largest customers"). 16 Second, the U.S. government's importance to Raytheon's business does not imply that the 17 Officers oversaw every contract. The government is a large Raytheon customer— 18 constituting more than 60% of Raytheon's business, which involves "tens of thousands" of 19 contracts. In that context, alleging misconduct in "multiple" contracts does not give rise to 20 any inference that the Officers must have known about it, much less a strong inference. 21 Plaintiffs' allegations also do not sufficiently plead that the Officers actually knew of the 22 disputed information. Of course, it would be "absurd to suggest" the Officers did not 23 24 6 Plaintiffs’ reference to “the misconduct” is ambiguous. It could refer to (1) the misconduct 25 the Officers “admitted to,” (Doc. 34 ¶ 10 (citing the April 27, 2021 earnings call remarks)), (2) the misconduct involving “multiple U.S. government contracts,” (Id. ¶¶ 40–49 (CW1), 26 59–60 (CW5)), (3) the “egregious misconduct” involving “several improper practices designed to overcharge the government” that “resulted in a gross overstatement” of 27 Raytheon’s financial statements, (Doc. 34 ¶ 4, 50–57 (CW2 & CW3)), or (4) all of the 28 above. This defect is characteristic of the Complaint, which relies on ambiguity and implication to achieve what its specific allegations cannot.

36

1 actually know of the top-line metrics involved in their financial statements. But Plaintiffs' 2 claim rests on actual knowledge of individual contracts that contributed to top-line 3 reporting errors, not knowledge of top-line metrics. In that respect this case is unlike Daou, 4 for example, where a successful core operations theory involved top executives admitting 5 they were involved in "every detail" of the company, and where the plaintiffs alleged the 6 defendants monitored the specific data in the allegedly false statements. 411 F.3d at 1022– 7 23. This case is more like Zucco Partners, where a core operations theory was unsuccessful 8 because the complaint merely alleged that senior management "closely reviewed the 9 accounting numbers" and discussed a related component. 552 F.3d at 1000. 10 For these reasons, the Court finds that although Raytheon's alleged misbehavior 11 involved its "core operations," that fact is insufficient on its own to give rise to a strong 12 inference of scienter. 13 viii. Tellabs holistic analysis 14 The final question in the scienter analysis is whether the whole of the Complaint is 15 greater than the sum of its parts. The Court considers, on one hand, whether all Plaintiffs' 16 allegations together give rise to the inference that the Officers made false or misleading 17 statements intentionally or with deliberate recklessness. If so, the Court then compares that 18 inference to the competing benign inference that the misconduct was limited to a few 19 employees and a few contracts, and the Officers took steps to address the misconduct when 20 it was discovered. If Plaintiffs' inference is at least as compelling as the benign inference, 21 the Court must deny Motion I as to the scienter element. 22 When viewed in its entirety, the Complaint pleads both too much and too little to 23 establish scienter. The Complaint pleads too much because it does not sufficiently connect 24 its many allegations to create an inference that Raytheon is pervaded by fraudulent 25 behavior. The Complaint asks the Court to infer that Raytheon's Officers—and an unknown 26 but potentially very large number of employees—intentionally concealed systemic, 27 "egregious" misconduct, causing "gross" misstatements of financial metrics and internal 28 financial controls. The Court could only reach that inference through several steps. First,

37

1 the seven confidential witness statements must be read as alleging widespread but loosely 2 defined misconduct. The witnesses, after all, are apparently spread widely throughout 3 Raytheon's business. Generally, they all allege bad behavior of some kind or another, in 4 some part of Raytheon's business or another, affecting some contract or another, and 5 stretching back indefinitely far into the past. To reach the Complaint's widest aperture, the 6 Court must ignore the details of these accounts and instead treat each as symptomatic, and 7 all as indicating a fraud so large it does not fit into any single account. 8 Next, the Court must view the DOJ investigation as linked to this widespread 9 misconduct—not only, as stated in the October 2020 disclosure, limited to Raytheon's 10 missiles and defense business or, as stated in the April 2021 disclosure, focused on three 11 or four contracts, or even limited to the Class Period. Rather, the Court must conclude that 12 the DOJ conducted its investigation "as a result of" all misconduct alleged—and quite a lot 13 more implied—in the Complaint. (Doc. 34 ¶ 8.) 14 Next, the Court must connect the confidential witness accounts (spanning 2009– 15 2020) and the DOJ's 2020 investigation with the termination of Raytheon's Missile Systems 16 CFO in 2018, VP in 2019, and the Officers' stock sales throughout 2016–2020. In this view, 17 the widespread misconduct only partially glimpsed by each witness, and triggering the 18 DOJ's investigation, also permitted the Officers to reap the benefit of Raytheon's 19 improperly inflated value while simultaneously requiring the Officers to terminate the 20 Missile Systems CFO and VP. Were the CFO and VP in on the scheme, but then fired when 21 they threatened to go public? Was hush money involved? The Court can only imagine. 22 Finally, the Court must keep the preceding steps in mind while inferring that 23 because the Officers signed Sarbanes-Oxley certifications, and because the GAAP 24 violations alleged do not occur without intent, and because the U.S. government is 25 Raytheon's biggest customer, that the Officers either must have known or recklessly 26 disregarded the fact that they were defrauding the public by permitting widespread 27 misconduct and improperly inflating revenue. 28 On closer inspection, Plaintiff's allegations do not combine as described above to

38

1 reach Plaintiffs' preferred inference. The confidential witness statements do not all refer to 2 widespread misconduct. CW1 primarily alleges multiple instances of misconduct in a 3 single contract. CW4, CW5, and CW6 allege overhearing issues stemming from the DOJ 4 investigation, several contracts within Raytheon's Missile Systems, and several employees 5 "fudging numbers." The remaining witnesses do not all refer to the same misconduct. CW2 6 alleges that 30% of Raytheon's suppliers were coded green when they shouldn't have been 7 to avoid competitive bidding. CW3 alleges that "almost every project" was slowed down 8 to increase Raytheon's billing. And CW7 alleges "a** covering" and "funny money" related 9 to Raytheon's outside contractors. The disclosure of the DOJ investigation never mentioned 10 widespread misconduct; it was limited to Missiles and Defense, then even more limited to 11 focus on a few Missiles and Defense contracts. Plaintiffs do not allege specific enough 12 facts to tie the timing of any of the Officers stock sales to the Complaint's events or explain 13 how the Officers' alleged complicity in the fraud fits with the termination of the Missile 14 Systems CFO and VP. And Plaintiffs allege no facts connecting the Officers to any specific 15 contract where misconduct was alleged or to any specific GAAP violation. Instead, 16 Plaintiffs ask the Court to resolve these issues for them by inferring widespread fraud from 17 a mess of competing inferences. The Court declines to do so. 18 Even if the Court followed the Plaintiffs' winding path to the inference that 19 Raytheon not only permitted but actively fostered widespread, egregious fraud, the Court 20 must then consider competing inferences. The most obvious—and the one suggested by 21 Raytheon—is that any misconduct involved only a few contracts out of "tens of thousands" 22 annually, only a few employees out of more than 60,000, and the Officers were not aware 23 of the misconduct either until Raytheon's internal controls discovered it or until Raytheon 24 began investigating alongside the DOJ. (Doc. 54 at 38:11–15.) That inference is more 25 compelling than Plaintiffs' because it fits the facts more neatly and resolves the various 26 tensions in Plaintiffs' account, such as the firing of Raytheon's Missile Systems CFO and 27 VP. For those reasons, the Complaint pleads too much when it seeks to infer a widespread 28 fraud theory.

39

1 The Complaint also pleads too little because what allegations it does connect do not 2 state a cause of action. The confidential witnesses, for example, corroborate each other to 3 allege only that Raytheon gave the false appearance of competitive bidding and 4 overcharged certain contracts by slowing them down more than necessary, and that a few 5 employees fudged several contracts. The DOJ investigation says nothing about either 6 theory but might be connected to the contracts CW5 and CW6 overheard were being 7 investigated. The Complaint says nothing specifically connecting those accounts and the 8 investigation, however. Similarly, the Complaint says nothing specifically connecting the 9 Missile Systems CFP and VP terminations with CW5's and CW6's accounts, though it 10 implies that these terminations were related. 11 Granting for the sake of argument that these allegations are in fact all connected, 12 they undermine Plaintiffs' other allegations and their argument for scienter. If the 13 corroborated confidential witness accounts refer to the same contracts that launched the 14 DOJ investigation and caused the Missile Systems CFO's and VP's termination, then the 15 Complaint plausibly alleges only that several contracts worth an unknown amount were 16 manipulated by several employees privately motivated to get their bonuses. (Doc. 34 ¶ 60.) 17 But that theory undermines CW1's allegations that Raytheon's fraud was aided by 18 Raytheon's suppliers, CW2's allegations that Raytheon's fraud extended to 30% of those 19 suppliers, CW3's allegations that Raytheon's fraud extended to every contract CW3 worked 20 on, and CW7's allegations that Raytheon's fraud extended to the entire company. The more 21 limited theory also undermines Plaintiffs' allegations that the Officers were complicit in 22 the fraud because the limited theory instead suggests that the Officers were unaware of the 23 fraud until after the contracts were manipulated, and that the Officers took steps to address 24 the issue when they became aware. What allegations remain—the Sarbanes-Oxley 25 certifications, GAAP violations, and "core operation" theory—do not add anything. 26 As discussed above, Plaintiffs' allegations regarding Sarbanes-Oxley certifications, 27 GAAP violations, and the "core operation" theory are individually insufficient to support 28 a strong inference of scienter. Although the Tellabs holistic analysis may breathe new life

40

1 into these categories generally, it does not here. For example, the "core operation" theory 2 may be successful when combined with "detailed and specific allegations about 3 management's exposure to factual information within the company." S. Ferry LP, 542 F.3d 4 at 785 (scienter established where individual defendants discussed the relevant technology 5 and integrations in detail on several occasions); Dearborn Heights, 856 F.3d at 620 (no 6 scienter where individual defendants' awareness of parent company's financial information 7 did not establish exposure to a subsidiary acquisition's financial information). But here, 8 Plaintiffs do not say the Officers were involved in any of the specific contracts alleged to 9 have contributed to Raytheon's misstatements. Rather, Plaintiffs ask the Court to infer that 10 the Officers must have been aware of these contracts in enough detail either to know of the 11 misconduct or to have recklessly disregarded it because the lifetime value of one contract 12 was $11.5 billion, (see Doc. 43 at 19), and because several contracts involved misconduct 13 by a "Deputy Vice President," "Program Manager," and "Contract Director" in Raytheon's 14 missile systems division, (Doc. 43 at 20). That is insufficient. Without significantly more, 15 Plaintiffs' inference is less compelling than the benign inference that, in a company as large 16 as Raytheon, the Officers were not familiar with the details of each contract to know of or 17 disregard fraud within them. 18 For all these reasons, Plaintiffs allege too little because those few of the Complaint's 19 many allegations that are at least implicitly connected undermine Plaintiffs' other 20 allegations and their argument for scienter. Plaintiffs also allege too much because their 21 theory of widespread or rampant fraud is not supported by their allegations. And either 22 way, Plaintiffs do not advance an inference at least as compelling as Defendants' inference. 23 The Court therefore finds Plaintiffs' allegations do not give rise to a strong inference of the 24 Officers' scienter. Although this is independently sufficient to grant Motion I, the Court 25 considers below the last remaining contested § 10(b) element, loss causation. 26 c. Loss Causation 27 In the Ninth Circuit, Rule 9(b)'s heightened standard requiring particularity "applies 28 to all elements of a securities fraud action, including loss causation." Or. Pub. Emps.

41

1 Retirement Fund, 775 F.3d at 605. Loss causation is "a variant of proximate cause," and 2 turns on "whether the defendant's misstatement, as opposed to some other fact, foreseeably 3 caused the plaintiff's loss." Lloyd, 811 F.3d at 1210 (causation sufficiently plead where 4 share price fell 22% and never recovered). The central inquiry is whether a plaintiff's loss 5 was caused by "the very facts about which the defendant lied." Mineworkers' Pension 6 Scheme v. First Solar, Inc., 881 F.3d 750, 753 (9th Cir. 2018) (per curiam) (citation 7 omitted). This inquiry is naturally "fact-specific," id., but may find loss causation 8 allegations insufficient where a "modest" drop in the stock prices coincides with the 9 disclosure of certain news but then "recover[s] very shortly after." Wochos v. Tesla, 985 10 F.3d 1180, 1197 (9th Cir. 2021) (citing Metzler, 540 F.3d at 1064–65). 11 Metzler is instructive. There, Plaintiff Metzler alleged that Defendant Corinthian's 12 colleges were pervaded by fraudulent practices designed to maximize their federal Title IV 13 funding. Metzler, 540 F.3d at 1055. Metzler further alleged Corinthian violated GAAP 14 principles by improperly recognizing revenue. Id. at 1056. Metzler further alleged that 15 because Corinthian's fraud was pervasive, virtually every class-period financial statement 16 was false. Id. Metzler alleged its losses were caused by two disclosures that purportedly 17 revealed Corinthian's fraudulent practices. Id. at 1059. The first was a newspaper article 18 reporting a Department of Education investigation into one of Corinthian's campuses. Id. 19 The second was a press release about a month later disclosing Corinthian had failed to hit 20 prior earnings estimates and containing a passing reference to one of Metzler's alleged 21 fraudulent practices. Id. After the first disclosure, Corinthian's stock fell 10 percent but 22 rebounded within three trading days. Id. After the second disclosure, Corinthian's stock fell 23 45 percent. Id. Affirming under the more permissive Rule 8(a) pleading requirement, the 24 court held that Metzler failed to plead loss causation. Id. at 1065. The court reasoned it was 25 unwarranted to infer that Corinthian's disclosures revealed systematic fraud because 26 Corinthian's stock recovered quickly after the first disclosure, and the second disclosure 27 "contained a far more plausible reason" for the accompanying drop—missed earnings. Id. 28 Wochos followed Metzler in a similar context. In Wochos, Defendant Tesla's stock

42

1 fell 3.9% from $356.88 after a newspaper article revealed that Tesla was making its new 2 Model 3 cars by hand and not on an automated assembly line. 985 F.3d at 1198. But the 3 stock recovered immediately, rising the next day to $355.59 and trading over the next week 4 between $350 and $360. Id. Citing Metzler, the Wochos court held that plaintiffs could not 5 plead loss causation because "[t]he quick and sustained price recovery after the modest . . . 6 drop refutes the inference that the alleged concealment . . . caused any material drop in the 7 stock price." Id. (also citing In re Oracle Corp. Sec. Litig., 627 F.3d 376, 392 (9th Cir. 8 2010) ("To adequately plead loss causation . . . a plaintiff must allege that the 'share price 9 fell significantly after the truth became known.'") (emphasis added in Wochos)). 10 The facts in this case are similar to Metzler and Wochos. Here, Plaintiffs allege that 11 Raytheon was pervaded by fraudulent practices designed to overstate its revenue, 12 overcharge the government, and defraud investors. (See, e.g., Doc. 34 ¶ 4–6.) Plaintiffs 13 further allege Raytheon violated GAAP principles by improperly recognizing revenue, 14 (see, e.g., Doc. 34 ¶¶ 77, 80), and that virtually every Class Period financial statement was 15 false. (See, e.g., Doc. 34 ¶¶ 81, 82.) Plaintiffs allege that "as a result of its misconduct," 16 Raytheon received a DOJ subpoena investigating "information and documents in 17 connection with an investigation relating to financial accounting, internal controls over 18 financing, and cost reporting regarding [Raytheon's] Missiles & Defense business since 19 2009." (Doc. 34 ¶ 8.) Plaintiffs further allege that "[i]n response to th[e] shocking news" 20 that Raytheon had received the subpoena, "the Company's stock price tumbled $4.19 per 21 share, or approximately 7%, on unusually heavy trading volume, damaging investors." 22 (Doc. 34 ¶¶ 9, 267.) As discussed above, the report disclosing the DOJ subpoena also 23 mentioned the COVID-19 pandemic more than seventy times, describing it as 24 "significantly impact[ing]" Raytheon's business, operations, and industry. (Doc. 41-2 at 25 14.) On an earnings call the same day, Raytheon's CEO said the pandemic would require 26 Raytheon to reduce its commercial aerospace division by 20%, firing 15,000 employees. 27 (Doc. 41-7 at 6.) Raytheon's stock rebounded the day after it dropped, recovered entirely 28 within four trading days and never closed below its October 27, 2020 level again. (Doc.

43

1 41-8 at 5–12.) By March 18, 2022, the stock had grown more than 70 percent. (Id.) 2 As in Metzler, Plaintiffs' inferences that Raytheon's disclosure of the DOJ subpoena 3 revealed widespread fraud are implausible because Raytheon's stock recovered in nearly 4 the same time. As in Metzler, Raytheon's disclosure was accompanied by a far more 5 plausible reason for the stock's decline—significant issues stemming from the COVID-19 6 pandemic. And as in Wochos, Raytheon's stock made a quick and sustained recovery 7 because it never traded below its October 27, 2020 level again, and was substantially higher 8 roughly two years later. Plaintiffs attempt to distinguish Wochos because it lacked "robust 9 briefing on loss causation," but Plaintiffs' preferred case is out of circuit and not on point. 10 (See Doc. 43 at 40.) Plaintiffs attempt to distinguish Metzler as involving "unique facts" 11 amounting to pleading loss causation through "euphemism," and containing a "far more 12 plausible reason" for the stock's drop. (Id.) But Plaintiffs inadvertently emphasize precisely 13 why Metzler is persuasive: this case shares key facts with Metzler, like the presence of a 14 more plausible explanation for the stock drop and a quick stock recovery. 15 Plaintiffs' attempts to bring this case under First Solar and Lloyd are also 16 unpersuasive. First Solar stands only for the proposition that "there are an infinite variety 17 of ways for a tort to cause a loss." 881 F.3d at 753. Far from choosing between competing 18 lines of Ninth Circuit authority, the First Solar court denied the existence of any intra- 19 circuit conflict and certified both "lines" as "variants of the basic proximate cause test." Id. 20 at 754. Where, as here, Plaintiffs' claim is based on a modest drop that quickly recovers, 21 accompanied by a much more plausible explanation, a "basic proximate cause test" leads 22 to the same result as in Metzler and Wochos. Plaintiffs' use of Lloyd is also misplaced 23 because Lloyd involved a much bigger drop, much more clearly connected to that plaintiff's 24 theory. Lloyd also ratifies a rule unhelpful to Plaintiffs: "the announcement of a government 25 investigation, without more, cannot meet the loss causation requirement." Lloyd, 811 F.3d 26 at 1210 (citing Loos v. Immersion Corp., 762 F.3d 880, 890 (9th Cir. 2014). That rule could 27 not save the Lloyd defendant CVB because there "much more [was] alleged." Id. 28 Specifically, CVB's stock fell more than 20% after disclosure of an SEC investigation. Id.

44

1 Analysts explicitly linked the investigation to CVB's loan exposure with its largest 2 borrower. Id. CVB's stock then failed to react when CVB later confirmed that its largest 3 borrower would in fact default. Id. The Lloyd court reasoned that the lack of stock market 4 reaction confirmed that investors understood the SEC announcement as at least a partial 5 disclosure of CVB's predicament. Id. Plaintiffs compare this case with Lloyd, pointing to 6 the lack of stock price reaction after the April 2021 disclosure that the DOJ investigation 7 involved up to four contracts. (Doc. 43 at 29.) But Plaintiffs also allege the October 2020 8 investigation revealed pervasive fraud—if anything, the stock price should have gone up 9 in April 2021 when the investigation turned out to involve only a few contracts. More 10 importantly, Plaintiffs do not allege any facts like in Lloyd, where analysts directly 11 connected the disclosure with concerns about the CVB's biggest borrower. The two 12 October 28, 2020 newspaper articles Plaintiffs cite in this case merely paraphrase 13 Raytheon's disclosure without analyzing it, implying a connection but never articulating it. 14 (See Doc. 34 ¶¶ 265, 266.) For these reasons, Lloyd is an inapt comparison that if anything 15 cuts against Plaintiffs' position. 16 Finally, even setting aside Metzler and Wochos, Plaintiffs do not sufficiently plead 17 loss causation under First Solar because they fail to connect the "very facts" Raytheon 18 allegedly lied about with Plaintiffs' loss. Plaintiffs allege that Raytheon lied in all financial 19 statements during the Class Period, and in all its statements that internal controls were 20 effective. But Plaintiffs' loss allegedly comes from the DOJ disclosure of an investigation 21 that turned out to involve only a few contracts, never resulted in restated earnings or any 22 other financial restatements, never impacted an independent auditor's certification of 23 Raytheon's controls, and which Raytheon repeatedly characterized as immaterial in light 24 of its overall finances. Without specific, particularized allegations connecting Plaintiffs' 25 theory of pervasive fraud and the stock drop after the DOJ investigation disclosure, 26 Plaintiffs fail to plead loss causation even under the broadest proximate cause test. 27 The Court therefore finds that the Plaintiffs' allegations do not give rise to a strong 28 inference of loss causation. Both independently and together with Plaintiffs' failure to

45

1 plausibly allege a strong inference of falsity and scienter, the Court finds ample reason to 2 grant Motion I on Count I and dismiss this case without prejudice. 3 COUNT II 4 Section 20(a) of the SEA makes certain "controlling" individuals also liable for 5 violations of § 10(b) and its underlying regulations. 15 U.S.C. § 78t(a). To plead a claim 6 under § 20(a), a plaintiff must demonstrate "a primary violation of federal securities law." 7 Zucco Partners, 552 F.3d at 990. Here, Plaintiffs' Count I failed to state a claim that 8 Raytheon violated federal securities law. Motion I is therefore also granted on Count II. 9 IV. ORDER 10 For these reasons, 11 IT IS ORDERED GRANTING Motion I (Doc. 41) without prejudice. Plaintiffs 12 have leave to amend their Complaint (Doc. 34) no later than December 19, 2022. 13 Defendants shall respond to any amended complaint no later than January 19, 2023. If 14 Plaintiffs choose to amend, they are instructed to provide chambers and opposing counsel 15 with a redline copy of the Complaint (Doc. 34) clearly identifying the changes made to it 16 by the amended complaint. The redline copy may be emailed in Microsoft Word format to 17 chambers when the amended complaint is filed, at "hinderaker_chambers 18 @azd.uscourts.gov"; 19 IT IS FURTHER ORDERED GRANTING Motion II (Doc. 42). The Court takes 20 judicial notice of ECF Docs. 41-2 through 41-11. 21 Dated this 18th day of November, 2022.