Electronic Privacy Information Center v. Federal Aviation Administration

821 F.3d 39, 422 U.S. App. D.C. 222, 2016 U.S. App. LEXIS 8553, 2016 WL 2640535
CourtCourt of Appeals for the D.C. Circuit
DecidedMay 10, 2016
Docket15-1075
StatusPublished
Cited by18 cases

This text of 821 F.3d 39 (Electronic Privacy Information Center v. Federal Aviation Administration) is published on Counsel Stack Legal Research, covering Court of Appeals for the D.C. Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Electronic Privacy Information Center v. Federal Aviation Administration, 821 F.3d 39, 422 U.S. App. D.C. 222, 2016 U.S. App. LEXIS 8553, 2016 WL 2640535 (D.C. Cir. 2016).

Opinion

Opinion for the Court filed by Circuit Judge HENDERSON.

KAREN LECRAFT HENDERSON, Circuit Judge:

Petitioner Electronic Privacy Information Center (EPIC) seeks review of the decision of the Federal Aviation Administration (FAA) not to promulgate certain regulations. EPIC, challenges both the FAA’s dismissal of its petition for rule-making and the FAA’s omission of privacy provisions in the notice of proposed rule-making (NPRM). Regarding its first challenge, EPIC is time-barred; on the second, EPIC’s challenge is premature. Accordingly, we dismiss EPIC’s petition for review. ■

I.

On February 14, 2012 the Congress enacted the FAA Modernization and Reform Act of 2Q12(Act), Pub. L. No. 112-95, 126 Stat. 11 (codified at 49 U.S.C. § 40101 note). The Act was enacted to regulate, inter alia, “unmanned aircraft” — ie., drones. 1 Specifically, the Act directs the FAA to develop, within 270 days of enactment, “a .comprehensive plan to safely accelerate the integration of civil unmanned aircraft systems into the national airspace system,” including regulations to “implement the recommendations of the plan.” Act. § 332(a)(1), (b)(2). The Act prescribes certain safety considerations the plan must contain, including, e.g., provisions to “ensure that any civil unmanned aircraft system includes a sense and avoid capability” and to implement “the best methods to enhance the technologies and subsystems necessary to achievé the safe and routine operation of civil unmanned aircraft systems.” Id. § 332(a)(2). The Act is silent as to any privacy considerations.

On February 24, '2012 EPIC petitioned the FAA to promulgate privacy-specific drone regulations. Thirty-three months later, on November 26, 2014, the FAA denied the petition, stating that it was “dismissing [EPIC’s] petition for rule-making.” Although a petition for review of an FAA-order “must be filed not later than 60 days after the order is issued,” 49 NS.C. § 46110(a),. EPIC did not file its petition until March 31, -2015 — 125 days after the dismissal. 2

*42 II.

The FAA endéd its November 26, 2014 letter denying EPIC’s petition by “dismissing [the] petition for rulemaking in accordance with 14 CFR § 11.73.” Letter from Lirio Liu, Dir., Office of Rulemaking, FAÁ, to Marc Rotenberg,' Exec. Dir., EPIC at 2 (FAA Letter). Despite the FAA’s explicit dismissal, EPIC waited over 60 days to petition for review. EPIC, now makes two arguments to excuse its tardiness. First, it contends that “reasonable grounds” justify its untimely petition. 49 U.S.C. § 46110(a) (“court may allow the petition to be filed after thé 60th day only if there are reasonable grounds”). In thé alternative, EPIC argues that the FAA’s February 23, 2015 NPRM constituted, in effect, the dismissal of its petition, triggering the 60-day clock. We find neither argument availing.'' ’ '

Because EPIC’s arguments turn on the alleged inconsistencies in the FAA’s letter, exposition thereof is necessary. FAA regulations require the Agency to respond to a “petition for rulemaking in one of ... [five] ways,” 14 C.F.R. § 11.73, two of which are relevant here. First, if the FAA has “begun a rulemaking project in the subject area of [the] petition,” it “will consider [the] comments and arguments for a rule change as part of that project. [FAA] will not .treat [the] petition as a separate action.” - Id. § 11.73(c). Second, if the FAA “detennine[s] that thé issues ... identified] in [the] petition may have merit, but do not address an immediate safety concern or cannot be addressed because of other priorities arid resource constraints, [it] may dismiss [the] petition---- [Petitioners’] comments and arguments for a rule change will be placed in'a database, which [the FAA] will examine when ... considering] future rulemaking.” Id. § 11.73(e).

Read against the backdrop , of its regulations, the FAA’s letter does lack clarity. Although the letter contains language consistent with a section 11.73(e) dismissal, see FAA Letter at 1 (“[W]e have determined that the issue you have raised is not an immediate safety concern.”), another statement more closely aligns it with section 11.73(c), see id. at 1 (“[T]he FAA has begun a rulemaking addressing civil operation of small unmanned aircraft systems in the national airspace system. We will consider your comments and argument as part of that project.”). EPIC argues that we should construe the ambiguity against the Agency and that it either provides reasonable grounds for delay — assuming that we believe the letter to represent “a final order,” see Vill. of Bensenville v. FAA, 457 F.3d 52, 69 (D.C.Cir.2006) (jurisdiction under 49 U.S.C. § 46110 is contingent on “a final order”) — or establishes that the Agency’s letter indicated it would *43 consider EPIC’s petition consistent with section 11.78(c). We need not determine whether the letter constitutes a final order/dismissal sufficient to start the 60-day clock because, under either argument, EPIC cannot prevail.

Regarding “reasonable grounds for delay,*’ 49 U.S.C. § 46110(a), EPIC alleges that the FAA letter, if final, is at leást “misleading.” Pet’r Reply Br. 12. We have rarely found “reasonable grounds” under section 46110(a) and, when, we most recently so found, the circumstances were plainly distinguishable. See Safe Extensions, Inc. v. FAA, 509 F.3d 593 (D.C.Cir.2007). There, the FAA affirmatively misrepresented to the petitioner'that the challenged order was to be revised. See id. at 603 (“[W]hen [petitioner’s President] expressed [his] concerns to [the FAA] about how AC-42E dealt with [adjustable products], the FAA responded .that [he] should wait until AC-42F comes out because the FAA was currently revising AC-42E.” (alteration in original) (internal quotations omitted)). Because the Agency told the petitioner “to basically ignore” the order inasmuch as it “would be eliminated and replaced with” another, we reviewed its otherwise untimely challenge when the order was not in fact revised. Id. (internal quotations omitted). Moreover, EPIC’s argument fails even under its preferred authority, a Ninth Circuit, decision. Ame ricopters, LLC v. FAA, 441 F.3d 726 (9th Cir.2006). In Ameñcopters, the Ninth Circuit held that “an attempt to exhaust the wrong remedy is not” reasonable grounds for delay; so too with “procedural missteps ...

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
821 F.3d 39, 422 U.S. App. D.C. 222, 2016 U.S. App. LEXIS 8553, 2016 WL 2640535, Counsel Stack Legal Research, https://law.counselstack.com/opinion/electronic-privacy-information-center-v-federal-aviation-administration-cadc-2016.