1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 ANA MARIA MARCELA TAVANTZIS, et Case No. 23-cv-05607-BLF (SVK) al., 8 Plaintiffs, ORDER RE DISCOVERY DISPUTE 9 v. Re: Dkt. No. 78 10 AMERICAN AIRLINES, INC., 11 Defendant. 12 The Parties present the Court with a relatively workaday discovery dispute—a request to 13 compel further discovery from Defendant American Airlines, Inc. (“AA”)—with an added twist: 14 the Transportation Security Administration (the “TSA”). See Dkt. 78 (the “Joint Letter”). 15 Specifically, Plaintiffs seek to compel AA to provide further responses and documents in 16 connection with three discovery requests: 17 • Interrogatory 3. A request for AA to “[i]dentify and describe” its internal policies and 18 procedures for handling passengers’ medical complications that arise while on one of AA’s 19 aircraft. See id. at 1. 20 • Request For Production (“RFP”) 19. A request for AA to produce its policies and 21 procedures concerning passengers’ medical complications that arise “at any time before, 22 during, or after a flight,” including those documents identified in response to Interrogatory 23 3. See id. 24 • RFP 27. A broad request for “[a]ny document” used by AA in responding to Plaintiffs’ 25 first five interrogatories. See id. 26 In response to these requests, AA disclosed that it possesses two responsive documents but insists 27 that it cannot produce them without approval from the TSA. It points to federal regulations 1 restricting the disclosure of “Sensitive Security Information” (“SSI”), arguing that until the TSA 2 determines in the first instance whether the responsive documents consistute SSI, AA’s hands 3 remain tied, lest it disclose potential SSI to Plaintiffs in violation of the regulations. See 49 C.F.R. 4 § 1520.1 et seq. 5 The regulations broadly define SSI as “information obtained or developed in the conduct 6 of security activities, . . . the disclosure of which TSA has determined would” violate privacy, 7 reveal trade secrets or other confidential information or “[b]e detrimental to the security of 8 transportation.” See id. § 1520.5(a). They go on to enumerate 15 categories of particularly 9 described SSI (see id. §§ 1520.5(b)(1)-(15)) and one catch-all category for any other information 10 “that TSA determines is SSI” under 49 U.S.C. Section 114(r) (see id. § 1520.5(b)(16)).1 Relying 11 on this catch-all category, AA reached out to the TSA for a determination of whether the 12 documents in question constitue SSI.2 That process remains pending, and until it concludes, AA 13 refuses to produce the documents. 14 AA cannot resist discovery on this basis. While the Court respects the SSI regime and the 15 disclosure restrictions it imposes on AA, the regulations do not create an impenetrable privilege 16 that AA may unilaterally invoke with zero evidentiary support for its potential application. AA 17 provides barely any description of the documents in question and offers no explanation as to why 18 it believes those documents may contain SSI. Were such bare efforts sufficient, AA and all other 19 entities subject to the SSI restrictions could invoke the catch-all category—and the plodding 20 bureaucracy that comes with it—to grind civil litigation to a halt. AA offers no legal authority 21
22 1 The catch-all category actually refers to 49 U.S.C. Section 114(s) and not Section 114(r). That appears to be error. Congress amended the statute in 2007, resulting in recodification of former 23 Section 114(s) at Section 114(r). See Consolidated Appropriations Act, 2008, Pub. L. No. 110- 161, 121 Stat. 1844, 2092 (2007). The TSA promulgated the catch-all category prior to that 24 amendment, and its language currently remains the same as it did at the time of promulgation, including its reference to Section 114(s). Compare Protection of Sensitive Security Information, 25 69 Fed. Reg. 28066, 28084 (May 18, 2004), with 49 C.F.R. § 1520.5(b)(16). The language of the statute confirms the error; Section 114(r) empowers the TSA to prescribe regulations concerning 26 the disclosure of SSI, while Section 114(s) concerns entirely different subject matter. 27 2 AA implicitly concedes that none of the other enumerated categories of SSI applies. See Joint 1 (beyond its interpretation of the regulations) to support that result, and the Court will not sanction 2 it. Indeed, Congress foreclosed application of the SSI regime to information not properly within 3 its scope: 4 Nothing in this subsection, or any other provision of law, shall be construed to 5 authorize the designation of information as sensitive security information (as 6 defined in section 1520.5 of title 49, Code of Federal Regulations) . . . to prevent or delay the release of information that does not require protection in the interest of 7 transportation security . . . . 8 9 49 U.S.C. § 114(r)(4) (emphasis added). 10 In light of such limited applicability, the Court will require AA to provide evidentiary 11 support for its position that the documents in question potentially contain SSI. See, e.g., UPS Co. 12 v. DNJ Logistic Grp., Inc., No. 16-cv-00609, 2018 WL 3199475, at *16 (W.D. Ky. Apr. 16, 2018) 13 (“To the extent that the TSA-related documents may partially contain SSI, or sensitive security 14 information, under 49 C.F.R. §§ 15 and 1520, an appropriate privilege log along with the careful 15 redaction of such putative SSI from the documents produced by DNJ will more than adequately 16 address any concerns . . . .”); Slaven v. Spirit Airlines, No. 08-cv-10705-ADT, 2009 WL 17 10713213, at *2-4 (E.D. Mich. July 7, 2009) (court conducted in camera review of documents 18 before agreeing that they contained SSI and accordingly directed defendants to initiate 19 administrative process with TSA concerning disclosure of documents). 20 The foregoing discussion of the SSI regime implicates primarily Interrogatory 3 and RFP 21 19. RFP 27 bears further discussion. Plaintiffs seek the production of AA’s communications with 22 the TSA concerning this action through that broad RFP. But they do not explain the relevance of 23 those communications to the claims or defenses in this action. See Fed. R. Civ. P. 26(b)(1) 24 (“Unless otherwise limited by court order, the scope of discovery is as follows: Parties may obtain 25 discovery regarding any nonprivileged matter that is relevant to any party’s claim or defense . . . 26 .”). Further, “[d]iscovery into another party’s discovery process is disfavored.” Ashcraft v. 27 Experian Info. Sols., Inc., No. 16-cv-02978-JAD, 2018 WL 6171772, at *2 n.2 (D. Nev. Nov. 26, ] 2014 WL 4547039, at *2 (S.D.N.Y. Sept. 12, 2014) (“[R]equests for such ‘meta-discovery’ should 2 || beclosely scrutinized ... .” (citation omitted)).
Free access — add to your briefcase to read the full text and ask questions with AI
1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 ANA MARIA MARCELA TAVANTZIS, et Case No. 23-cv-05607-BLF (SVK) al., 8 Plaintiffs, ORDER RE DISCOVERY DISPUTE 9 v. Re: Dkt. No. 78 10 AMERICAN AIRLINES, INC., 11 Defendant. 12 The Parties present the Court with a relatively workaday discovery dispute—a request to 13 compel further discovery from Defendant American Airlines, Inc. (“AA”)—with an added twist: 14 the Transportation Security Administration (the “TSA”). See Dkt. 78 (the “Joint Letter”). 15 Specifically, Plaintiffs seek to compel AA to provide further responses and documents in 16 connection with three discovery requests: 17 • Interrogatory 3. A request for AA to “[i]dentify and describe” its internal policies and 18 procedures for handling passengers’ medical complications that arise while on one of AA’s 19 aircraft. See id. at 1. 20 • Request For Production (“RFP”) 19. A request for AA to produce its policies and 21 procedures concerning passengers’ medical complications that arise “at any time before, 22 during, or after a flight,” including those documents identified in response to Interrogatory 23 3. See id. 24 • RFP 27. A broad request for “[a]ny document” used by AA in responding to Plaintiffs’ 25 first five interrogatories. See id. 26 In response to these requests, AA disclosed that it possesses two responsive documents but insists 27 that it cannot produce them without approval from the TSA. It points to federal regulations 1 restricting the disclosure of “Sensitive Security Information” (“SSI”), arguing that until the TSA 2 determines in the first instance whether the responsive documents consistute SSI, AA’s hands 3 remain tied, lest it disclose potential SSI to Plaintiffs in violation of the regulations. See 49 C.F.R. 4 § 1520.1 et seq. 5 The regulations broadly define SSI as “information obtained or developed in the conduct 6 of security activities, . . . the disclosure of which TSA has determined would” violate privacy, 7 reveal trade secrets or other confidential information or “[b]e detrimental to the security of 8 transportation.” See id. § 1520.5(a). They go on to enumerate 15 categories of particularly 9 described SSI (see id. §§ 1520.5(b)(1)-(15)) and one catch-all category for any other information 10 “that TSA determines is SSI” under 49 U.S.C. Section 114(r) (see id. § 1520.5(b)(16)).1 Relying 11 on this catch-all category, AA reached out to the TSA for a determination of whether the 12 documents in question constitue SSI.2 That process remains pending, and until it concludes, AA 13 refuses to produce the documents. 14 AA cannot resist discovery on this basis. While the Court respects the SSI regime and the 15 disclosure restrictions it imposes on AA, the regulations do not create an impenetrable privilege 16 that AA may unilaterally invoke with zero evidentiary support for its potential application. AA 17 provides barely any description of the documents in question and offers no explanation as to why 18 it believes those documents may contain SSI. Were such bare efforts sufficient, AA and all other 19 entities subject to the SSI restrictions could invoke the catch-all category—and the plodding 20 bureaucracy that comes with it—to grind civil litigation to a halt. AA offers no legal authority 21
22 1 The catch-all category actually refers to 49 U.S.C. Section 114(s) and not Section 114(r). That appears to be error. Congress amended the statute in 2007, resulting in recodification of former 23 Section 114(s) at Section 114(r). See Consolidated Appropriations Act, 2008, Pub. L. No. 110- 161, 121 Stat. 1844, 2092 (2007). The TSA promulgated the catch-all category prior to that 24 amendment, and its language currently remains the same as it did at the time of promulgation, including its reference to Section 114(s). Compare Protection of Sensitive Security Information, 25 69 Fed. Reg. 28066, 28084 (May 18, 2004), with 49 C.F.R. § 1520.5(b)(16). The language of the statute confirms the error; Section 114(r) empowers the TSA to prescribe regulations concerning 26 the disclosure of SSI, while Section 114(s) concerns entirely different subject matter. 27 2 AA implicitly concedes that none of the other enumerated categories of SSI applies. See Joint 1 (beyond its interpretation of the regulations) to support that result, and the Court will not sanction 2 it. Indeed, Congress foreclosed application of the SSI regime to information not properly within 3 its scope: 4 Nothing in this subsection, or any other provision of law, shall be construed to 5 authorize the designation of information as sensitive security information (as 6 defined in section 1520.5 of title 49, Code of Federal Regulations) . . . to prevent or delay the release of information that does not require protection in the interest of 7 transportation security . . . . 8 9 49 U.S.C. § 114(r)(4) (emphasis added). 10 In light of such limited applicability, the Court will require AA to provide evidentiary 11 support for its position that the documents in question potentially contain SSI. See, e.g., UPS Co. 12 v. DNJ Logistic Grp., Inc., No. 16-cv-00609, 2018 WL 3199475, at *16 (W.D. Ky. Apr. 16, 2018) 13 (“To the extent that the TSA-related documents may partially contain SSI, or sensitive security 14 information, under 49 C.F.R. §§ 15 and 1520, an appropriate privilege log along with the careful 15 redaction of such putative SSI from the documents produced by DNJ will more than adequately 16 address any concerns . . . .”); Slaven v. Spirit Airlines, No. 08-cv-10705-ADT, 2009 WL 17 10713213, at *2-4 (E.D. Mich. July 7, 2009) (court conducted in camera review of documents 18 before agreeing that they contained SSI and accordingly directed defendants to initiate 19 administrative process with TSA concerning disclosure of documents). 20 The foregoing discussion of the SSI regime implicates primarily Interrogatory 3 and RFP 21 19. RFP 27 bears further discussion. Plaintiffs seek the production of AA’s communications with 22 the TSA concerning this action through that broad RFP. But they do not explain the relevance of 23 those communications to the claims or defenses in this action. See Fed. R. Civ. P. 26(b)(1) 24 (“Unless otherwise limited by court order, the scope of discovery is as follows: Parties may obtain 25 discovery regarding any nonprivileged matter that is relevant to any party’s claim or defense . . . 26 .”). Further, “[d]iscovery into another party’s discovery process is disfavored.” Ashcraft v. 27 Experian Info. Sols., Inc., No. 16-cv-02978-JAD, 2018 WL 6171772, at *2 n.2 (D. Nev. Nov. 26, ] 2014 WL 4547039, at *2 (S.D.N.Y. Sept. 12, 2014) (“[R]equests for such ‘meta-discovery’ should 2 || beclosely scrutinized ... .” (citation omitted)). 3 Accordingly, the Court ORDERS as follows: 4 e By August 12, 2024, AA shall submit a supplemental brief, not to exceed three pages in 5 length and with supporting evidence, that: (1) provides legal authority, if any, for AA’s 6 interpretation of the SSI regulations; (2) describes in detail the documents in question; (3) 7 explains why AA believes those documents contain SSI; and (4) explains why AA cannot 8 avoid violation of the SSI regulations by producing redacted versions of the documents, 9 particularly as the disputed requests are limited to documents and information concerning 10 passengers’ medical complications. The Court will permit a modest extension of this 11 deadline pursuant only to stipulation of the Parties. 12 e Plaintiffs’ request to compel AA’s communications with the TSA under RFP 27 is 13 DENIED. SO ORDERED. 3 15 || Dated: August 1, 2024
Sassen yeh SUSAN VAN KEULEN 4 18 United States Magistrate Judge 19 20 21 22 23 24 25 26 27 28