> ## Content Index
> Fetch the complete content index at: https://machina.mmalc.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What the law offers a community under a changed flight path
- URL: https://machina.mmalc.com/changed-flight-path-law/
- Published: 2026-07-30T21:11:33.000Z
- Updated: 2026-07-30T21:11:33.000Z
- Author: mmalc Crawford
- Tags: law, flight path, Noise pollution, FAA, NEPA

A single FAA order can turn a quiet community into something resembling the sonic equivalent of an air force base — no local vote, no visible decision-maker, and often no warning beyond the noise itself. This piece addresses what that community — or any other in the same position — can do, legally, when the FAA changes a departure procedure and routes low-altitude traffic over homes that weren't under it before.

> "[Three weeks against REDHEAD](https://machina.mmalc.com/bohemian-grove/)" looked at one airport, one procedure, and one three-week stretch during which the FAA's own conduct undercut its stated justification for a low-altitude departure route it had introduced two years previously.

This article focuses on the effects of increased noise. Other issues such as wildlife impacts and air-quality harm come up regularly in these fights too, and they're real concerns — but they rarely hold up as a standalone legal theory. A recent case outside the airport context makes the pattern clear: conservation groups sued the FAA over expanded rocket launches next to a national wildlife refuge in South Texas, citing noise, light pollution, and harm to endangered ocelots, jaguarundis, and nesting sea turtles. A federal judge dismissed the suit in 2025, finding the FAA had adequately studied the effects — the same threshold problem every claim below runs into. Air-quality litigation against aviation is real too, but it targets the EPA's national aircraft-emissions standards, not a single airport's departure procedure, so it isn't a lever available to a community contesting one route change. Both categories can strengthen a broader argument under the National Environmental Policy Act (NEPA) as one more documented gap in the agency's review; neither typically holds up as a claim on its own.

## Two different lawsuits, two different defendants

The first thing to get straight is that "sue over the noise" describes two entirely different pieces of litigation, aimed at two different defendants, in two different court systems, governed by two different bodies of law. Knowing which situation applies determines which court a case belongs in, and conflating the two is a common way for well-intentioned advocacy to go nowhere.

One path runs against the airport's owner — typically a city, county, or joint authority, not the FAA. This is a state-law claim: nuisance, or inverse condemnation, or both. It asks a state court to award damages for the harm the airport's proprietor has allowed to continue, on the theory that operating an airport is a proprietary activity a public entity can be held responsible for, distinct from the federal government's authority over the airspace itself. For example, a resident whose property has lost value because of continuous overflight noise has a claim against the airport's owner even if the FAA's decision-making was procedurally spotless.

The other path runs against the FAA directly, in federal court, challenging the agency's own order adopting or modifying the procedure. This is administrative law: the claim is not that anyone was harmed in the tort sense, but that the FAA violated a duty — under NEPA, its own noise-evaluation standards, or a specific statute — when it made the decision. For example, a city whose historic districts were never properly studied before a route change has a claim against the FAA even if the airport itself did everything a proprietor is required to do.

## Suing the airport: what Baker actually settled, and what it didn't

The case most often cited for the first path is *Baker v. Burbank-Glendale-Pasadena Airport Authority*, decided by the California Supreme Court in 1985\. Homeowners near what's now Hollywood Burbank Airport sued the airport authority for inverse condemnation and nuisance over noise, smoke, and vibration. The authority argued it couldn't be liable in inverse condemnation because, unlike a true condemning agency, it had no power of eminent domain — and that the nuisance claim was barred by the statute of limitations that applies to permanent injuries.

The court rejected both arguments. Lacking eminent domain power doesn't immunize a public entity from inverse condemnation, because the underlying right comes from the state constitution's ban on taking or damaging property for public use without compensation, not from the entity's own condemnation authority. And airport noise, the court held, is the textbook example of a *continuing* nuisance rather than a permanent one — because it stems from an ongoing use rather than a fixed structure — which meant residents could keep suing for accruing harm rather than being time-barred by a single old filing deadline.

That 1985 ruling didn't award anyone damages; it reversed a dismissal and sent the case back for trial. The follow-up matters more than the headline case, because it shows what actually happened once these claims were tried — and it isn't a clean win for property claims. By the time of trial, the airport's predecessor had operated the same flight pattern continuously since 1965, well past California's five-year threshold for acquiring an easement by prescription. The appellate court relied directly on a related 1989 ruling, *Institoris v. City of Los Angeles*: once an airport operator has acquired that kind of easement — meaning the noise went unchallenged in court for five straight years — a resident no longer holds the property interest a nuisance or inverse-condemnation claim depends on. That's what happened here: the trial court denied the property claims outright, and the appellate court affirmed the denial.

Emotional-distress damages actually fared better at trial — several plaintiffs won them — before being reversed on appeal, for two separate reasons. First, that kind of damage requires a *public* nuisance with a special injury "different in kind" from what the general public suffers, and the court found these plaintiffs differed only in degree. Second, and more decisively, the same prescriptive easement that barred the property claims covered the underlying noise and vibration however the harm was framed, so it barred the emotional-distress claims too.

The generalizable lesson isn't that property claims beat personal-injury claims. It's that a nuisance nobody sues over for five years can calcify into a legal right to keep causing it — an avigation easement, acquired the same way a footpath becomes a public right of way. That's bad news for residents near an airport who have endured decades of noise but never taken legal action. It's better news for anyone dealing with a new procedure: a departure route adopted in 2024 hasn't (at the time of writing) had five years to become fully established, which means a property claim could still be feasible in a way a claim over a 1965 flight pattern could not.

## Challenging the FAA directly: the model, and the mechanics

The second path — going after the FAA's order itself — has its own landmark, and it's more recent. In *City of Phoenix v. Huerta*, decided by the D.C. Circuit in 2017, the city and a coalition of historic-neighborhood associations challenged a 2014 FAA order that had rerouted departures over previously unaffected neighborhoods. The court agreed the FAA had violated the National Environmental Policy Act, the National Historic Preservation Act, and Section 4(f) of the Department of Transportation Act, largely because the agency hadn't properly documented or disclosed the route change's effects, or given the city a real opportunity to object before the decision was finalized. The court vacated the FAA's order and sent it back for a proper process.

The mechanism for bringing that kind of challenge is a petition for review under 49 U.S.C. § 46110, filed directly in a federal court of appeals. It has to be filed within 60 days of the FAA order being challenged — a short window for a community that may not learn what changed, or why, until long after the fact. The statute allows a court to excuse a late filing only where there are "reasonable grounds" for the delay, and *Phoenix* is the case that shows a petition filed months — not days — after the deadline can still be allowed once new evidence of what the FAA actually knew, and when, surfaces later. That exception is fact-specific and not a guarantee; it depends on convincing a court the delay itself was reasonable, not just that the underlying grievance is serious.

## Most challenges since Phoenix have failed — and the reasons are the real lesson

*Phoenix* reads, on its own, like a template. Applied since, it has mostly not worked that way. Several communities have tried variations of the same challenge against departure-procedure changes elsewhere, and the pattern in how those cases were resolved is more instructive than the *Phoenix* result taken in isolation.

The City of Scottsdale sued the FAA over the same Phoenix-area NextGen changes, seeking to force a reroute; in 2022 the D.C. Circuit dismissed the case for lack of standing, finding no cognizable injury before it. Howard County, Maryland, petitioned over NextGen changes at Baltimore-Washington International; the Fourth Circuit dismissed that petition in 2020\. A coalition of D.C. residents challenged flight-path changes near Reagan National; the D.C. Circuit dismissed that petition in 2018 as untimely, finding the operative order had actually issued years earlier and that no reasonable grounds excused the delay. And when the City of Los Angeles petitioned over a "southerly shift" in departures from Hollywood Burbank Airport, the Ninth Circuit dismissed it in 2021 on the narrower and more technical ground that the FAA's letter to the city wasn't a reviewable final order at all — it announced no new policy and represented no change from what air traffic controllers had already been doing.

That last point deserves emphasis, because it's the threshold question every one of these cases turns on before a court ever reaches the merits: whether there's an identifiable FAA *order* to challenge, issued on a specific date, rather than an ongoing practice with no single decision point a court can point to. *Phoenix* worked partly because the FAA's 2014 order was a discrete, datable agency action. Cases that couldn't point to an equivalent order — only to a letter, a continuation of existing practice, or a change nobody could pin to a specific document — have tended to lose on jurisdiction before any judge examines whether the underlying environmental review was adequate.

It isn't all one direction. Los Angeles separately succeeded, in a different case over LAX arrival paths, in getting the Ninth Circuit to find a genuine NEPA violation and order a proper environmental review; the city has also had mixed results in a parallel challenge to LAX terminal construction, winning on the environmental-review question while losing on a separate argument that the outcome had been predetermined. The throughline across all of these outcomes: NEPA-based claims can succeed when a community can point to a specific order and a specific documented gap in the FAA's review. Claims that skip past that threshold — that argue from harm alone, without a datable order and a demonstrable procedural failure — tend not to reach a hearing on the merits at all.

## The paperwork builds the case, but doesn't have to precede the filing

Building an evidentiary record — establishing what was actually decided, by whom, on what evidence, and whether alternatives were considered at all — matters for both avenues, and it comes from public-records requests: FOIA to the FAA, and the state-law equivalent — in California, a California Public Records Act request — to the airport's proprietor.

That doesn't resolve neatly against the 60-day filing deadline for an FAA challenge, since FOIA responses routinely take months. The way that tension actually gets handled in practice is that the deadline runs against what's already public, not against what a records request might later reveal. A petition can be — and typically is — filed on the public record alone: the order itself, the absence of an environmental document where the FAA's own rules would require one, a comment docket showing objections the agency didn't address. That's enough to preserve the claim. FOIA and discovery then build out the merits case after filing, not before it.

The "reasonable grounds" exception to the 60-day rule exists for the harder version of this problem — a defect a community genuinely couldn't have known about until FOIA'd records surfaced it well after the fact. That's close to the actual fact pattern *Phoenix* excused a late filing over, though it remains a fact-specific argument a court has to accept, not an automatic extension. The state-law path avoids the timing problem differently: because *Baker* treats airport noise as a continuing rather than a permanent nuisance, there's no single filing deadline racing against a pending records request in the first place.

None of this makes records requests fast or satisfying. They get acknowledged, extended, sometimes narrowed or denied outright, often over a timeline measured in months. A pending request is not evidence of anything until it returns records, and treating an unanswered request as if it already proves a cover-up is a mistake worth avoiding — both because it isn't true yet, and because overclaiming in public undermines the credibility of the record once it does arrive.

## "Corruption" is a word, not a cause of action

It's worth being precise about a distinction that gets blurred in the heat of a real dispute. Calling a decision "corrupt" is a political and rhetorical judgment, and sometimes an entirely fair one — a description of how a decision looks, given who benefited and who didn't. It is not the same thing as a legal claim of corruption, which requires proving specific elements: a bribe, a quid pro quo, a defined ethics-statute violation. None of the avenues described above require any of that. Nuisance, inverse condemnation, and arbitrary-and-capricious administrative review all turn on documented harm and documented process failures — not on anyone's motive. A community doesn't need to prove corruption to win a nuisance claim against a proprietor or force a do-over of an inadequate environmental review. Trying to prove corruption, when the available and provable claims don't require it, risks aiming at the hardest possible target when an easier and equally legitimate one is available.

## What this means for a community facing a new departure procedure

None of the above is legal advice, and the caveats matter more here than in most subjects this newsletter covers. Whether a nuisance claim survives a statute-of-limitations fight; an FAA communication counts as a reviewable order; or a filing delay counts as reasonable are fact-specific questions that turn on details a general-interest article can't resolve for any particular case. Anyone considering litigation over a departure-procedure change should talk to an attorney with aviation or inverse-condemnation experience before relying on any of this.

There are two distinct legal paths. The first, against a proprietor, is strongest early — before unlitigated noise lets a prescriptive easement take hold. The second, against the FAA, has precedent behind it, but a narrow window — a discrete, datable order, a plausible procedural failure, and either a timely filing or a persuasive reason for a late one. And underneath both avenues sits the same basic prerequisite: a documented record of what happened — established promptly from the public record where a deadline is running, built out more slowly through FOIA and discovery afterward, but never skipped.

---

*This article was researched and drafted in collaboration with Claude, Anthropic's AI model.*