Drone & Aerial
Zipline Arizona FAA Draft EA: 130,000 Daily Drone Deliveries
Zipline's November 2026 FAA draft EA proposes up to 130,000 daily drone deliveries in Phoenix and Tucson. Caps, Platform 2 specs, and comment deadlines.

TL;DR
The FAA posted Zipline's November 2026 draft EA for Phoenix and Tucson: up to 65 chargers and 65,000 daily deliveries per metro (130,000 combined at max), Platform 2 up to eight-pound payloads, 24/7 ops, and public comments due early December 2026.
Update: what new details emerged on November 20–21, 2026?
Update — November 21, 2026: DroneXL published a November 20, 2026 deep read of the same draft environmental assessment (EA), adding several details beyond our November 13 summary. Tucson would see about 117 deliveries per square mile per day at the stated ceiling versus 42 in the larger Phoenix footprint, because both metros are capped at 65 Chargers despite very different land areas. The FAA sent Endangered Species Act consultation materials to the U.S. Fish and Wildlife Service on November 5, 2026, one day before the public comment window opened. On noise, DroneXL reports 170-foot (52-meter) minimum setbacks for Chargers and 50-foot (15-meter) setbacks for Dropboxes at maximum throughput, using Zipline sound studies attached to the draft—shorter than the 600-foot hub distance in the FAA’s national delivery assessment DroneXL references. Zipline’s Zach Hill told 12News (via DroneXL) that Arizona service could begin in early 2027 if the EA path completes. DroneXL also flags template leftovers from the Texas EA (appendix titles, wildlife flight counts, and species-name typos), which commenters may cite because Arizona joined litigation challenging the FAA’s national delivery finding. None of this changes the legal status: the EA remains a draft until the FAA signs a final decision.
On November 6, 2026, the Federal Aviation Administration (FAA) opened a 30-day public review of a draft environmental assessment (EA) for Zipline International Inc. package delivery in the Phoenix and Tucson metropolitan areas (FAA NEPA and drones listing). Trade coverage on November 12 highlighted the scale: up to 130,000 deliveries per day across both metros at maximum capacity, 24-hour operations, and infrastructure counts that dwarf earlier pilot networks (DroneLife). For enterprise teams, the Zipline Arizona FAA draft EA is the primary document: it states what Zipline is requesting, what the caps mean, and how NEPA fits before any Part 135 operating specification change is finalized.
What did the FAA publish in November 2026?
The FAA posted Draft Environmental Assessment for Zipline International Inc. Proposed Drone Package Delivery Operations in Multiple Arizona Metropolitan Areas (PDF on FAA.gov). The notice inside that draft states the review runs from Friday, November 6, 2026 through Monday, December 7, 2026, with comments due by 5:00 p.m. Central Time on that date.
The FAA's companion webpage summarizes the proposed action in plain language and invites comments by December 9, 2026 (FAA environmental review page). DroneLife notes the two deadline dates; teams submitting input should treat the draft EA notice as the formal comment window and still aim for the earliest stated cutoff.
The draft is not an approval. NEPA requires the FAA to evaluate environmental effects before deciding whether to amend Zipline's air carrier operation specifications. Until the responsible FAA official signs a finding of no significant impact or orders further review, Arizona expansion remains a proposed federal action.
What maximum scale does the draft EA describe?
The FAA's public summary and DroneLife's reporting align on headline numbers. Under the proposed action for each metropolitan area:
| Element | Per metro area (maximum) | Both metros combined |
|---|---|---|
| Zipline Chargers | 65 | 130 |
| Dropboxes (pickup kiosks) | 1,300 | 2,600 |
| Deliveries per day | 65,000 | 130,000 |
| Operating hours | 24 hours per day, 7 days per week, including holidays | Same |
DroneLife adds that the draft ties up to 1,000 deliveries per day to each Charger when running at cap, and that each delivery involves three flight segments (charger to pickup, pickup to customer, return), so 390,000 transit segments per day could occur across Phoenix and Tucson at those maximums (DroneLife).
These figures are capacity ceilings, not forecasts. The FAA page states that actual flights would vary with customer demand and weather. That distinction matters for noise, wildlife, and community commenters, and for operators modeling flight log volume: a network might run far below cap for years while still holding approved maximums.
What aircraft and payloads does Platform 2 carry?
The FAA's November 2026 summary names Zipline Platform 2 (referred to as the Zipline UA in the draft). It lists:
-
Maximum takeoff weight of about 63 pounds, including payload.
-
Maximum payload weight of eight pounds.
DroneLife repeats that Platform 2 is the delivery aircraft in the Arizona proposal. The draft EA's technical sections (in the PDF) describe charger docks (up to 72 per Charger, with most sites around 36) and Dropboxes where partners load parcels that the aircraft retrieves autonomously.
None of those specs change how you search footage after a flight, but they set how often cameras on docks, partner sites, and aircraft might record descent paths over neighborhoods—the same tension that surfaced when Amazon Prime Air won UK SAIL 4 approval and expanded BVLOS corridors over more households.

How would day versus night operations split?
Zipline is requesting permission to fly around the clock, but the FAA summary states an expected split:
-
Roughly 95 percent of flights between 7:00 a.m. and 10:00 p.m.
-
Roughly 5 percent between 10:00 p.m. and 7:00 a.m., depending on demand.
Night operations are politically sensitive. DroneLife connects the Arizona filing to community noise debates elsewhere, including Amazon Prime Air proposals that drew local opposition in Massachusetts. The draft EA's noise chapters (in the PDF) are what commenters will challenge or support; they are Zipline-prepared analysis under FAA supervision, not final FAA findings.
For video operations teams, night share affects which incidents trigger after-hours review. A five percent night slice of a 130,000-delivery cap is still thousands of low-light clips per day at full utilization—enough to overwhelm a manual review team if QA sampling is not automated.
What regulatory path must Zipline complete beyond NEPA?
DroneLife notes Zipline already holds a Part 135 air carrier certificate and exemptions supporting certain BVLOS operations, but amended operating specifications and other FAA approvals are still required for Arizona metros.
The FAA webpage stresses a parallel truth local governments already know from FCC and FAA coordination on drone communications: federal airspace authorization does not pick store locations. Zipline must site Chargers and Dropboxes in commercial areas consistent with local zoning—retail, warehouses, laboratories, and partner facilities according to the FAA summary.
That split of responsibilities mirrors DFR programs where flight legality and post-flight transparency are different workstreams. Our write-up on Evolver DFR and video review after the flight shows how often the bottleneck moves to finding the right clip once flights scale.
How does this compare with other drone delivery NEPA filings?
The same FAA index hosts draft and closed EAs for Zipline Texas metros, Amazon Prime Air Chicago, Baton Rouge, and other proposals. Placing Arizona next to those filings clarifies trend lines:
| Operator / region (FAA draft or closed EA) | Illustrative daily flight cap in filing | Aircraft named in FAA summary |
|---|---|---|
| Zipline Arizona (Nov 2026 draft) | Up to 65,000 deliveries per metro; 130,000 combined | Platform 2, ~63 lb MTOW, 8 lb payload |
| Amazon Prime Air Chicago (closed comment period) | Up to ~1,000 MK30 flights per day per center | MK30, electric, up to 83.2 lb MTOW in FAA text |
| Zipline Texas metros (comment closed Oct 2026) | 30,000–65,000 deliveries per day per metro depending on area | Platform 2 |
The Arizona proposal is notable for paired large metros and 24/7 authorization at the maximum level, not for inventing a new aircraft class.
What should compliance and security video teams watch?
NEPA comments focus on environmental impact, but operators still produce recorded evidence unrelated to the EA:
-
Onboard or dock cameras used for package verification, obstacle monitoring, or maintenance.
-
Partner facility CCTV covering Dropbox loading bays.
-
Incident exports when a flight aborts, a parachute deploys, or a citizen complaint arrives.
The draft EA does not standardize retention periods or public disclosure of those recordings. Each operator sets policy. When daily segments approach hundreds of thousands at cap, the cost of manual incident review rises linearly unless teams index exports and search by timecode, scene, or spoken radio calls.
The video review cost calculator turns hours of footage into labour estimates; what is video indexing explains why storage alone does not make those hours searchable.
How does an honest Ceptory angle fit?
Ceptory is a video intelligence platform: you upload recorded video or add it by URL through the REST API, then search in natural language across scenes, speech, and on-screen text. It does not operate Zipline Chargers, negotiate Part 135 amendments, or replace an operator's safety management system.
Where Ceptory fits is after capture: QA teams reviewing sampled descent clips, legal staff validating community complaint windows, or auditors proving checklist steps on a Dropbox loading video. See drone monitoring for how aerial workflows map to indexing, and how to review drone inspection footage faster for narrowing windows before upload.
Pricing is $0.042 per minute indexed plus $0.0015 per minute infrastructure, $4 per 1,000 search queries, with the first 10 minutes of indexing free (/pricing). Indexing every segment at 130,000 deliveries per day would be uneconomic; teams should export incident and QA samples, not entire raw archives.
What should readers do now?
-
Read the primary PDF on FAA.gov and the FAA summary page, not only press summaries.
-
Note whether your organization is a local government, retail partner, or competitor with overlapping Part 135 plans; compare caps to your own NEPA filings on the same index.
-
If you are affected, draft a substantive comment by December 7, 2026 (Central Time) to [email protected] with Zipline Arizona Draft EA in the subject line, as the draft notice specifies.
-
Inside your company, align retention, privacy, and incident review SLAs with the 24/7 proposal—even if realized demand stays far below cap.
-
Pilot search on a single exported clip if manual scrubbing already slows QA; use Ceptory search on a short file before committing to a full integration.
What changes for search if Arizona approves at scale?
Approval—if it comes—would normalize metro-scale BVLOS logistics with documented environmental baselines. It would not, by itself, give retailers or cities searchable video of those flights.
The operational lesson from other high-volume aerial programs is unchanged: regulators set flight rules, communities scrutinize noise, and investigators still need timestamps when something goes wrong. Whether the aircraft carries a burrito or a thermal sensor, the review bottleneck is finding the moment in the recording. Teams preparing for that workload can start with enterprise video search in natural language and the beyond manual video review playbook.
For platform context across delivery and inspection, see Ceptory and the drone monitoring feature page.
Frequently asked questions
What is Zipline asking the FAA to approve in Arizona?
Zipline seeks amended Part 135 operation specifications and related approvals for commercial package delivery in the Phoenix and Tucson metropolitan areas. The November 2026 draft EA describes chargers, dropboxes, and daily delivery maximums for each metro.
Does the draft EA approve 130,000 deliveries per day?
No. The document is a draft under NEPA review, not a final authorization. One hundred thirty thousand deliveries per day is the combined maximum capacity across both metros if every charger ran at its daily cap; the FAA must complete review before any approval.
What aircraft would Zipline fly in Arizona?
The FAA's public summary names Zipline Platform 2, with about 63 pounds maximum takeoff weight and up to eight pounds of payload per the draft EA materials posted on FAA.gov.
When can the public comment on the Zipline Arizona draft EA?
The draft EA notice in the PDF sets comments through 5:00 p.m. Central Time on Monday, December 7, 2026, while the FAA's environmental review webpage also lists December 9, 2026. Submit to [email protected] with Zipline Arizona Draft EA in the subject line.
Would round-the-clock drone delivery change video retention for operators?
NEPA review does not set retention rules, but 24/7 proposed operations multiply flight and descent-phase recordings. Compliance teams still need policies for incident review, privacy, and how long onboard or ground video is kept.
Can Ceptory index Zipline or other drone delivery flight video?
Ceptory indexes recorded video you upload or add by URL through its API. It does not operate aircraft or chargers. Exported QA, incident, or compliance clips can be searched in natural language after your team ingests them.
How close can a Zipline Charger sit to homes in the Arizona draft?
DroneXL reports Nov 20, 2026 that a Charger at the 1,000-deliveries-per-day maximum would sit at least 170 feet (52 meters) from homes and other noise-sensitive sites, with Dropboxes at least 50 feet (15 meters), based on Zipline sound measurements in the draft EA.
When does Zipline hope to start Arizona deliveries?
Zipline community engagement lead Zach Hill told 12News in November 2026 that the company hopes to start serving Arizona customers in early 2027, per DroneXL's Nov 20 recap. The FAA has not issued a final finding yet.
Ceptory
Search your own footage in plain language. The free tier indexes 60 minutes of video.
Related reading


