Correction — September 16, 2026. An earlier version of this article asserted that no federal environmental document for Tracy "exists," described a Baton Rouge noise figure as "the loudest moment" of a delivery, stated that September 26 is the date the national PEA's court-challenge window closes and that the framework would then be "settled law," and linked an unofficial mirror of the Federal Register notice. What is verified is narrower: no Tracy entry appears on the FAA's public environmental page as of September 15; the 92.1 figure is a sound exposure level, not a peak-loudness measurement; the order was issued July 28, 2026 and its text allows petitions "no later than 60 days after the order is issued," but UAVHQ has not verified how that deadline computes in practice or whether any petition has been filed; and the official notice is on GovInfo. The article below has been corrected throughout.

Editor's note — September 16, 2026. This revision also removes reported Tracy launch details — timing, service radius, payload, pricing, community events, and company statements — that UAVHQ could not verify against retained source material. The analysis below is rebuilt around what we verified directly: the FAA's public environmental page and the national Programmatic EA's own text.

On September 11, the FAA posted Zipline's Draft Environmental Assessment for five Texas metros and invited public comments through October 11, 2026. Residents of Houston, San Antonio, Austin, Amarillo, and El Paso can read exactly what is proposed to fly over their homes, at what altitude, how loud, and how often, and they can put objections into a record that the FAA's notice says will receive responses to all substantive comments in the final EA. We covered that filing.

Tracy, California, presents a different picture on the page the public can check. As of UAVHQ's September 15 check of the FAA's public drone-delivery environmental page, California's only entry remains Lockeford, from 2022; Tracy appears nowhere on that page. Be precise about what that observation covers: it establishes that this one public portal was silent on that date, not that no document exists anywhere in the federal government, and not that the site has or has not cleared any particular review.

The July 28 fork in the road

On July 28, 2026, the FAA signed a Finding of No Significant Impact and Record of Decision on its national Programmatic Environmental Assessment for Part 135 drone package delivery, with the Notice of Availability published in the Federal Register on July 30. The mechanism, as we detailed at the time, is substitution: instead of drafting a fresh site-specific environmental assessment for every new delivery market — a process the agency says historically ran six to eight months — the FAA now measures each new Part 135 delivery application against one national study. If the proposal fits inside the programmatic envelope, it may not need its own environmental assessment or public comment window — though the FAA's decision document commits the agency to continue site-specific historic-property and biological analyses until programmatic agreements with the SHPOs and the U.S. Fish and Wildlife Service are in place, so "fits the PEA" does not mean "no review of any kind."

Fitting is a qualified test, not a flat rule. The PEA's evaluated reference case is 1,150 average annual daily deliveries from a hub sited at least 600 feet from noise-sensitive land uses, and the document itself qualifies that in three directions: aircraft generating lower sound exposure levels than the aggregate maximum, or operating far enough from airports, may support higher delivery volumes; hubs flying fewer than 1,150 daily deliveries take shorter setbacks from a table in the noise appendix; and operators wishing to use the PEA must submit vehicle noise data as part of their application, with volume beyond the reference case requiring a noise demonstration. Streamlined does not mean unconditioned.

The site-specific track still exists. As of the same September 15 portal check: Chicago's draft assessment ran a comment period that closed August 14; the Zipline Texas filing posted September 11 with comments due October 11; and Baton Rouge and Omaha both had draft assessments whose comment periods closed July 22, with no finals posted on the public page.

So which lane is Tracy in? Here is the uncomfortable answer: the page the public can check does not say, and UAVHQ has not verified the answer from any other source. The site may have been checked against the national PEA, in which case there may be no further site-specific document to post. A site-specific review may still be in the pipeline. Or the answer may sit in some instrument the public page does not display. Under the programmatic framework, portal silence is a permitted outcome.

What the public record offers instead of a Tracy filing

Numbers from other markets — which do not transfer automatically. Amazon's FAA paperwork in Louisiana, filed under the site-specific process, reports a maximum A-weighted sound exposure level of 92.1 for the delivery phase in the 25-foot row of a table whose distance column reads "Distance to PADDC," with an en route maximum-weight SEL of 63.7 dB at 200 feet. Two cautions before anyone quotes those figures in a Tracy city-council meeting. First, SEL is an energy metric that folds the whole event's duration into one second; it is not the loudest instant a listener hears, which is a different metric (Lmax) the technical report tracks separately. Second, those are Baton Rouge filing values for that proposed operation — they are not measurements of Tracy, and as of our September 15 check, no Tracy-specific figures appeared on the FAA's public environmental page to check anything against. We walked through that Baton Rouge noise filing in September, and the pattern it revealed matters here: the environmental paperwork is where operating numbers get written down by someone other than the marketing department.

Whatever community-facing work a company does in a new market, it is not a substitute for a public record. A company presentation answers a fixed list of questions on the company's schedule. An environmental assessment sits in a federal docket where a county supervisor can read it years later. Lockeford — still California's only entry on the FAA's public environmental page — had one from 2022, which means anyone can still read what was analyzed for that site.

The judicial-review clock is running, but read it carefully

The national FONSI/ROD is a final agency order, and its own Right of Appeal section says any party with a substantial interest may petition the appropriate United States Court of Appeals "no later than 60 days after the order is issued," under 49 U.S.C. § 46110. The order was issued July 28, 2026. What UAVHQ has verified stops there. We have not verified how that 60-day period computes into an actual calendar filing deadline — court filing rules and applicable exceptions are questions for counsel — and we have not verified whether any petition has been filed. Earlier UAVHQ coverage stated a specific September 26 cutoff and treated the framework as effectively settled once it passed; both statements went beyond the record, and we are not replacing the retracted date with another one.

The comment record behind the order was real, if modest: the FAA received 241 written comment submissions on the draft PEA, extended the comment period at the public's request to January 23, 2026, and published the submissions and its responses in Appendix E. (An earlier version of this article characterized specific commenters and their arguments; UAVHQ could not verify those characterizations against retained sources and has removed them.) Whether anyone petitions for review is exactly the kind of fact that will not announce itself — if no challenge materializes, the two-lane structure simply continues operating, and the paperwork question for each future market gets answered lane by lane, often invisibly from the outside.

The operator read

I spent years on the flight-test side of getting unmanned aircraft approved to fly over people who did not ask for them, and this is the part of the Tracy story I would flag for anyone building or advising a program:

If you are a delivery operator, the programmatic lane is a genuine schedule gift, but it is conditional. The no-impact finding holds only if you implement the mitigation, and the envelope is qualified: the setback varies with volume per the appendix table (in DNL-equivalent units that weight nighttime deliveries tenfold), quieter aircraft change the math, and your application still carries a vehicle-noise-data obligation. Exceed the envelope and additional review follows, potentially a full impact statement. Build your site-selection screen around the PEA's actual conditions now, and keep a documented conformity file for every site you stand up under it. If the finding is ever challenged and modified, that documentation is what you will argue from — though what happens to any operation then would depend on the decision and the remedy, not on the quality of anyone's files.

If you run a DFR or public-safety program, note what can disappear with the comment window: a formal, documented channel for putting airspace-integration concerns in front of the FAA during a site's environmental review. A new delivery site in your jurisdiction may now appear with little or no advance public paperwork for you to read. Get ahead of it. Track the FAA's environmental page and your regional operators' announcements, and open the deconfliction conversation with the operator directly, because nobody is going to convene it for you.

If you advise a city or county, this is your preview: assurances may arrive from a company before, or instead of, any federal filing appearing on the public page. The productive move is not outrage, it is a specific ask. Request the operator's siting analysis against the national PEA's setback and volume conditions, and ask which NEPA lane the site cleared under. Those are answerable questions with documents behind them, whichever lane applies.

The PEA itself anticipates that package delivery would move to the proposed Part 108 framework once that rule is implemented — the FAA's estimate, which it labels unknown, is that Part 108 delivery may commence one to two years after rule issuance, pending consensus standards and other prerequisites. Until then, the Part 135 machinery plus this programmatic bridge is the structure, and if the framework holds, future markets may produce exactly as much advance public paperwork as Tracy has so far shown on the page we checked: none.

We will track the petition docket and whatever appears, or does not appear, in the FAA's public record for Tracy in the UAVHQ dispatch on Substack. And if your program's expansion plan depends on the programmatic lane, the UAVHQ BVLOS Playbook includes ConOps and general planning templates you can use as a starting point for organizing your own program documentation; it is a planning aid, not a guarantee of any regulatory outcome.

Sources