Comment deadline: October 11, 2026 (official; snapshot September 15, 2026). The FAA's drone-environmental page instructs: review the Draft EA and submit comments by October 11, 2026, by email to 9-FAA-Drone-Environmental@faa.gov, referencing the Zipline Texas Draft EA in the email subject line. The page as retrieved did not state an hour or time zone. Recheck the FAA page for current instructions before filing — and note this is a NEPA comment invitation, not an operating authorization or a permission decision.

On Friday, September 11, the FAA posted a document worth an hour of any operator's time. The Draft Environmental Assessment for Zipline's proposed operations in multiple Texas metropolitan areas covers Houston, San Antonio, Austin, Amarillo, and El Paso, and the proposed ceiling numbers in Table 2.2-1 (printed page 2-2) are worth reading twice: up to 220 charging towers, 4,400 pickup kiosks, 220,000 deliveries per day, and — because each delivery involves three flight legs — as many as 660,000 aircraft transits per day across the five metros, at 330 feet AGL and 70 mph. To be exact about what those numbers are: they are the maximums the draft asks the FAA to assess, not counts of anything currently flying and not volumes anyone has been authorized to fly.

If history is a guide, almost nobody will use the comment window. When the FAA ran the same process for Zipline's Dallas–Fort Worth expansion, the final EA records that the agency received exactly one public comment during that EA's comment period (which ran June 18 to July 18, 2025) before a Finding of No Significant Impact was signed that December.

One comment, on an assessment that evaluated a potential maximum of 30,000 flights a day across roughly 10,904 square miles of North Texas. The Texas five-metro proposal's envelope is substantially larger — the documents state their maximums in different units (DFW in flights, this one in deliveries and transits), so we won't put a multiplier on it, but the direction is not in doubt. That asymmetry between the scale of what is being decided and the attention it gets is the story, and it cuts differently depending on which side of the industry you sit on.

What the filing actually asks for

Strip away the NEPA structure and the mechanics are familiar. Zipline holds a standard Part 135 air carrier certificate and a Section 44807 exemption that together let it carry property for hire beyond visual line of sight with its Platform 2 aircraft. What actually turns that authority on in a given city is the Operations Specifications, the OpSpecs, which name the geographic areas where the certificate holder may operate. Amending OpSpecs to add five metro areas is a major federal action under NEPA, which is why this environmental assessment exists and why the public gets a say at all.

The proposed architecture, per the Draft EA's Table 2.2-1 and Section 2:

If Zipline ever wants to exceed those allocations, the document is explicit that a new NEPA review is required. The numbers in this EA are the proposed envelope, not the forecast and not the grant; for comparison, the DFW final EA describes a planned gradual scale-up in which Zipline would begin its operational program at five sites with 20 daily flights per site, growing over 18 months — a plan as documented, not a report of operations flown. But envelopes are what get approved, and this is the envelope the FAA is being asked to sign.

The bottleneck is not Part 108, and this filing shows why

There is a persistent belief in this industry that scaled drone delivery is waiting on the proposed Part 108 BVLOS rule. This filing is a useful corrective. Zipline is not waiting for Part 108. Neither is Amazon, whose Prime Air Texas expansion cleared its own FONSI in February. The scaling machinery that exists today is Part 135 plus a 44807 exemption plus OpSpecs amendments, and the pacing item in that machinery is environmental review: study areas, endangered-species consultation, Section 106 historic-property findings, noise modeling, tribal consultation, and a public comment period.

For operators building delivery or BVLOS programs, that has two practical implications. First, your regulatory roadmap should treat NEPA as a schedule line item, not a formality. DFW went from draft-EA comment stage to a signed FONSI in about six months; this five-metro filing is bigger and touches more consultation tracks, and the FAA's notice states that all substantive comments received will be responded to in the final EA. Second, these documents are the closest thing you will get to a published playbook for how the FAA thinks about siting scaled UAS infrastructure. The Texas draft describes setback distances between Chargers and noise-sensitive areas determined by planned daily delivery volume, route planning that avoids known high-air-traffic areas, airspace restrictions, and known venues for open-air assemblies of people, and the per-location overflight cap noted above. If you are drafting a ConOps for anything that scales, those constraints preview the questions you will eventually be asked. We saw the same dynamic in Amazon's Baton Rouge noise filing: the environmental paperwork is where proposed operating limits get written down in public.

The airspace question the EA does not answer for you

Here is the part that should interest every operator who is not Zipline. The 330-foot cruise altitude sits squarely inside the band where Part 107 operations live under the 400-foot ceiling, where DFR programs launch and recover, where helicopter EMS and law enforcement work low, and where agricultural and inspection flights spend their days. An environmental assessment evaluates noise, wildlife, and historic properties. It is not the venue that deconflicts your survey flight from a delivery corridor that could, at the proposal's Houston maximum, carry 195,000 transits a day.

That deconfliction burden lands on operating rules, Remote ID, strategic separation in Zipline's OpSpecs, and, frankly, on you. A test pilot's read of these numbers: if anything near this density is eventually approved, the low-altitude environment in these five metros stops being empty by default. Preflight planning that assumes nothing else is out there at 300 feet was already lazy; in a city with authorized delivery corridors it becomes a genuine hazard assumption. Know where the proposed operating areas are, treat published delivery infrastructure like you treat a heliport, and log your own position and altitude discipline accordingly. If your program depends on predictable access to that band, this comment window is a formal, on-the-record opportunity to raise concerns — the FAA's notice states that substantive comments will be responded to in the final EA, though an environmental review is not the venue that decides airspace procedures. Per the FAA page as of September 15, comments go to 9-FAA-Drone-Environmental@faa.gov by October 11, 2026, with the Zipline Texas Draft EA referenced in the subject line.

It is also worth saying plainly: scale changes the safety math. A proposed ceiling of 660,000 daily transits — if it were ever reached — would be a different exposure regime than the operations these documents describe today, and the EA does not analyze fleet-scale contingency rates; NEPA is not a safety case. The safety determination lives in the FAA's Part 135 and OpSpecs machinery, which runs on its own track from the NEPA comment process — which means the environmental docket is where a member of the public can most easily put a concern in writing.

What to do with this if you are building toward scale

If you run or are planning a delivery, DFR, or infrastructure BVLOS program, spend an hour with this document and the DFW final EA side by side. Extract the siting standoffs, the phasing tables, the keep-out logic, and the consultation tracks, and map them onto your own concept of operations before a regulator does it for you. Approval is a paperwork architecture, and the operators who scale are the ones who build the readiness file before they need it. The UAVHQ BVLOS Playbook includes ConOps and planning templates structured around these questions — a planning aid, not a promise of approval — and the UAVHQ dispatch on Substack is where we plan to track this docket through the final EA and whatever the FAA decides.

A status note for readers arriving later: this article describes the docket as it stood on September 15, 2026, inside an open comment window. After October 11, check the FAA page for the final EA and decision documents rather than relying on the deadline framing above.

The last time the agency asked Texas what it thought about tens of thousands of daily drone flights, one person answered. Whether the record stays that quiet this time is up to the people who actually use this airspace.

Sources

  1. FAA, "Draft Environmental Assessment for Zipline International Inc. Proposed Drone Package Delivery Operations in Multiple Texas Metropolitan Areas," September 2026 — proposed maximums at Table 2.2-1, PDF p. 10 / printed p. 2-2
  2. FAA, "Public Involvement and Environmental Review for Drone Operations" (NEPA and drones portal) — comment instructions and October 11, 2026 due date, checked September 15, 2026
  3. FAA, "Final Environmental Assessment for Zipline International Inc. Proposed Drone Package Delivery Operations in Dallas–Fort Worth, Texas," December 2025 — one public comment recorded at PDF p. 9 / printed p. 1-3
  4. FAA, "Finding of No Significant Impact and Record of Decision, Zipline Dallas–Fort Worth," December 23, 2025