American Federation of Government Employees v. Hawley

543 F. Supp. 2d 44, 27 I.E.R. Cas. (BNA) 1240, 2008 U.S. Dist. LEXIS 25308, 2008 WL 835856
CourtDistrict Court, District of Columbia
DecidedMarch 31, 2008
DocketCivil Action 07-00855 (HHK)
StatusPublished
Cited by13 cases

This text of 543 F. Supp. 2d 44 (American Federation of Government Employees v. Hawley) is published on Counsel Stack Legal Research, covering District Court, District of Columbia primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
American Federation of Government Employees v. Hawley, 543 F. Supp. 2d 44, 27 I.E.R. Cas. (BNA) 1240, 2008 U.S. Dist. LEXIS 25308, 2008 WL 835856 (D.D.C. 2008).

Opinion

MEMORANDUM OPINION

KENNEDY, District Judge.

Plaintiffs, four transportation security officers employed by the Transportation Security Administration (“TSA”) and the unions that represent them, bring this action against defendants TSA, Kip Hawley in his capacity as Administrator of the TSA, the Department of Homeland Security (“DHS”), and Michael Chertoff in his capacity as Secretary of the DHS. Plaintiffs allege that defendants violated the Aviation and Transportation Security Act (“ATSA”), 49 U.S.C. §§ 44901 and 44935, and the Privacy Act, 5 U.S.C. § 552a, by failing to establish appropriate safeguards to insure the security and confidentiality of personnel records.

Before the court is defendants’ motion to dismiss [# 3]. Upon consideration of the motion, defendants’ opposition thereto, and the record of this case, the court concludes that the defendants’ motion should be granted in part and denied in part.

I. BACKGROUND

On May 3, 2007, TSA discovered that a hard drive was “missing from a controlled area at the TSA Headquarters Office of Human Capital.” Compl. ¶¶ 28-29. The hard drive contained personnel data for approximately 100,000 individuals employed by TSA between January 2002 and August 2005, including names, social security numbers, birth dates, payroll information, financial allotments, and bank account and routing information. Compl. ¶¶ 28, 29, 31. On May 4, 2007, Administrator Kip Hawley issued a broadcast email to all TSA employees providing notice of the incident and stating that TSA would provide employees with free credit monitoring for one year free of charge. Id.; Defs.’ *46 Mot. Dismiss, Exh. 1 (Decl. of Holmes), Att. 1 at 1 (5/4/2007 TSA Broadcast). 1

II. ANALYSIS

On May 8, 2007, four TSA security officers (“individual plaintiffs”) and their unions (“union plaintiffs”) filed this class action complaint, 2 alleging that defendants violated ATSA and the Privacy Act by failing to ensure the security of the missing hard drive. In their motion to dismiss, defendants argue (1) ATSA does not provide a private right of action; (2) the union plaintiffs lack standing to bring their Privacy Act claim under both the act and the requirements of associational standing; (3) the individual plaintiffs lack standing because they do not allege a cognizable injury; (4) plaintiffs’ Privacy Act claim is unripe; and (5) plaintiffs’ allegations are insufficient to state a Privacy Act claim. To these arguments the court now turns.

I. Plaintiffs’ ATSA Claim

In response to the events of September II, 2001, Congress enacted the Aviation and Transportation Security Act, Pub.L. No. 107-71, 115 Stat. 597 (2001), which created TSA and a federal workforce to screen passengers and cargo at commercial airports. 49 U.S.C. § 114. Among other things, ATSA requires the Administrator to “enforce security related regulations and requirements” and “oversee the implementation, and ensure the adequacy, of security measures at airports.” §§ 114(f)(7), (11). Plaintiffs claim defendants violated ATSA by “failing] to maintain personnel data from loss consistent with security-related regulations” and by “failing] to ensure the adequacy of security measures at airports resulting in the loss of personnel data.” Compl. ¶¶ 45-46.

Defendants move to dismiss plaintiffs’ ATSA claim, arguing that the statute does not provide a private cause of action, either express or implied. Plaintiffs admit that ATSA contains no express grant of a private cause of action, but contend that the court should find the act contains an implied cause of action because it “was enacted specifically to create a secure workforce of TSA screeners such as the Plaintiffs” and “protecting screeners’ personnel data is vital to the protection of a secure workforce and security at the airports.” Pis.’ Opp’n to Defs.’ Mot. Dismiss (“Opp’n”) at 4. Plaintiffs further argue that “[tjhere can be no doubt that the Plaintiffs ... are within the zone of interests created by the ATSA” because “the main purpose of the ATSA was to create this federal, security screening workforce.” Id. The court agrees with defendants and finds that ATSA does not provide plaintiffs with a cause of action.

“[Pjrivate rights of action to enforce federal law must be created by Congress.” Alexander v. Sandoval, 532 U.S. 275, 286, 121 S.Ct. 1511, 149 L.Ed.2d 517 (2001) (citing Touche Ross & Co. v. Redington, 442 U.S. 560, 578, 99 S.Ct. 2479, 61 L.Ed.2d 82 (1979)). “The judicial task is *47 to interpret the statute Congress has passed to determine whether it displays an intent to create not just a private right but also a private remedy.” Id. (citing Transamerica Mortgage Advisors, Inc. v. Lewis, 444 U.S. 11, 15, 100 S.Ct. 242, 62 L.Ed.2d 146 (1979)). The court’s analysis “must begin with the language of the statute itself.” Touche Ross & Co. v. Redington, 442 U.S. at 568, 99 S.Ct. 2479. Absent statutory language that expressly grants a private right of action, the court must determine whether the statute contains an implied right of action. Anderson v. USAir, Inc., 818 F.2d 49, 54 (D.C.Cir.1987). Four factors are relevant to discerning congressional intent to provide a private remedy:

(1) [Wjhether the plaintiff is one of the class for whose benefit the statute was enacted;
(2) whether some indication exists of legislative intent, explicit or implicit, either to create or to deny a private remedy; (3) whether implying a private right of action is consistent with the underlying purposes of the legislative scheme; and (4) whether the cause of action is one traditionally relegated to state law, such that it would be inappropriate for the court to infer a cause of action based solely on federal law.

Tax Analysts v. IRS, 214 F.3d 179, 185— 186 (D.C.Cir.2000) (citing Cort v. Ash, 422 U.S. 66, 78, 95 S.Ct. 2080, 45 L.Ed.2d 26 (1975)). Of the four factors, “the most important consideration is whether the legislature intended to create a private right of action.” Dial A Car, Inc. v. Transportation, Inc., 132 F.3d 743, 744 (D.C.Cir.1998).

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

Related

Hammond v. Department of Defense
District of Columbia, 2021
Kelley v. Federal Bureau of Investigation
67 F. Supp. 3d 240 (District of Columbia, 2014)
Dick v. Holder
67 F. Supp. 3d 167 (District of Columbia, 2014)
Jones v. ROSSIDES
657 F. Supp. 2d 167 (District of Columbia, 2009)
Nat'l Treasury Employees Union v. Whipple
636 F. Supp. 2d 63 (District of Columbia, 2009)
Jones v. Rossides
256 F.R.D. 274 (D.C. Circuit, 2009)
SAE Productions, Inc. v. Federal Bureau of Investigation
589 F. Supp. 2d 76 (District of Columbia, 2008)

Cite This Page — Counsel Stack

Bluebook (online)
543 F. Supp. 2d 44, 27 I.E.R. Cas. (BNA) 1240, 2008 U.S. Dist. LEXIS 25308, 2008 WL 835856, Counsel Stack Legal Research, https://law.counselstack.com/opinion/american-federation-of-government-employees-v-hawley-dcd-2008.