By Wesley Alexander • July 28, 2026 • 8 min read

Tactical Summary

On July 15, 2026, the FAA published a Draft Environmental Assessment for Amazon Prime Air's proposed commercial drone package delivery service across the Chicago, Illinois metro area, and opened a 30-day public comment period that closes August 14, 2026 at 5:00 p.m. Central Time. Comments go to 9-FAA-Drone-Environmental@faa.gov with "Prime Air Chicago Draft EA" in the subject line. The responsible FAA official is Derek Hufty, Manager of the General Aviation and Commercial Branch in the Emerging Technologies Division, Office of Safety Standards.

The framing that matters for operators is in the notice language. Amazon is not asking permission to start flying. It is seeking to amend its air carrier Operations Specifications and other FAA approvals so it can integrate the MK30 drone and stand up three new delivery hubs in the Chicago area. The FAA has determined that approving that OpSpecs amendment is a major federal action requiring a NEPA review. The EA is the environmental gate between a Part 135 drone carrier and the footprint it wants, and this comment window is the only formal point where anyone outside Amazon and the FAA gets to shape the record.

What the EA Actually Proposes

The scale is the story. Amazon proposes three new Prime Air Drone Delivery Centers, referred to in the document as PADDCs and identified as IGQ1, ORD5, and SIL3, each sited on or adjacent to an existing Amazon warehouse property. From each of those three hubs, Amazon proposes to operate up to 1,000 MK30 delivery flights per operating day, seven days a week, over 365 operating days a year. That works out to roughly 365,000 annual delivery operations at each PADDC, and three PADDCs running that cadence stacks toward roughly a million delivery flights a year across the Chicago metro.

Each hub carries a potential operating area of 174 square miles, set by the MK30's 7.5-mile range from the launch point. The drone itself weighs about 78 pounds, has a maximum takeoff weight of 83.2 pounds including a 5-pound payload, and flies up to 400 feet above ground level at a maximum cruise speed of 73 mph. A typical mission runs launch, en route outbound, delivery, en route inbound, and landing, with the drone cruising between roughly 205 and 370 feet AGL and descending only to drop the package.

One detail in the flight schedule deserves an operator's attention. Deliveries run from 6:00 a.m. to 10:30 p.m., and the EA states that up to 100 of the 1,000 daily flights at each hub, ten percent, are expected in the shoulder windows of 6 to 7 a.m. and 10 to 10:30 p.m. Those are the hours that carry the heaviest NEPA weight, because the FAA's day-night noise metric applies a 10-decibel penalty to events between 10 p.m. and 7 a.m. Amazon is proposing to fly during precisely the period the regulation treats as most sensitive.

Why Approval Does Not Equal Launch Readiness

This is the recurring trap in delivery-expansion coverage, and it is worth stating plainly. An EA that ends in a Finding of No Significant Impact does not flip a switch. It clears one federal hurdle, the NEPA hurdle, on the path to amended OpSpecs. Amazon still has to hold the operational approvals, airspace authorizations, and per-site arrangements that let it fly each route, and it still has to satisfy state and local land-use and zoning requirements for each hub. The FAA is explicit that it does not select operator locations and that community engagement runs as a parallel process to the federal review.

A favorable EA removes the environmental objection to expansion. It does not certify that airspace deconfliction, ground-risk mitigation, or community notification for every route is solved. That distinction is exactly what we drew out when Flytrex and Wing flew thousands of overlapping deliveries with zero conflicts. As we argued in what UTM actually solved, and what it did not, shared low-altitude airspace works today because a small number of cooperative operators coordinate deliberately. Dropping three high-volume delivery hubs into a single metro raises the coordination burden for everyone else flying there, including the Part 107 operator who never signed up for a UTM handshake and still has to sort out right-of-way at 200 feet over a residential street.

The Noise Methodology Is the Contested Ground

The FAA's noise analysis concludes that levels would stay below the agency's threshold for significance, even in the areas of highest exposure within half a mile of a PADDC. Under FAA Order 1050.1G, a significant noise impact is a DNL increase of 1.5 decibels or more at or above the 65-decibel level. The EA's finding is that Chicago operations would not cross that line.

The methodology behind that conclusion is where the substantive public criticism of drone-delivery review has landed nationally. DNL, the day-night average sound level, was built for continuous airport noise. It averages sound across a 24-hour period. Community groups have formally argued, in comments on the national Draft Programmatic Environmental Assessment for drone package delivery, that averaging understates how people actually experience repeated, intermittent drone passes. A metric that smooths a full day of sound can average away the specific annoyance of a delivery drone crossing the same backyard a dozen times between breakfast and dinner. That is the crux of the comment fight, and it is where a specific, locally grounded comment carries the most weight on the Chicago record.

For an operator, the practical read is that the noise appendix, Appendix E, and the delivery-location DNL table are the pages to open first. If the assumptions about flight distribution, altitude profile, or per-location delivery frequency do not match what you would expect over a dense residential grid, that mismatch is the comment. Vague objections do not move a NEPA record. Specific, technical, sourced observations do.

What Chicago-Area Operators Should Do Before August 14

If you fly commercially anywhere in the north or west Chicago suburbs, the operating areas around IGQ1, ORD5, and SIL3 are about to become a persistent new low-altitude traffic layer. Three concrete moves:

  1. Read the operating-area figures against your own footprint. The EA's Chapter 2 study-area maps and the Table 3-4 list of airports and heliports within each operating area tell you whether your survey, inspection, real-estate, or public-safety corridors overlap Amazon's. If they do, the environment you plan around is about to get denser, and the assumptions behind that density are written down now.

  2. Tighten your Remote ID and traffic-awareness posture. A denser autonomous delivery environment is exactly the case where broadcasting standard Remote ID and having a practical way to detect nearby traffic stops being a compliance checkbox and becomes an operational necessity. This is the same posture we laid out in the BVLOS compliance checklist: compliance is a procedure you run, not a document you file once.

  3. File a comment that counts, or lose the standing to object later. The window closes August 14 at 5 p.m. Central. Comments that cite specific EA sections, specific operating assumptions, and specific local conditions become part of the Final EA record and get a response. Comments filed after the window do not. If the Chicago expansion changes your airspace, this is the one formal moment to say so on the record.

The UAVHQ Read

The easy way to file this is "Amazon expands drone delivery, again." The more useful read is structural. This is the third or fourth metro-scale Prime Air environmental review in a year, and the pattern is now clear: the OpSpecs amendment is the real gate, the EA is the choke point, and the noise methodology is the recurring battleground. The company that masters the NEPA and OpSpecs process at metro scale expands. The one that treats the EA as paperwork stalls.

For independent operators, the takeaway is twofold. Short term, if you fly in the Chicago basin, your low-altitude environment is about to gain three high-volume delivery hubs, so read the operating areas and tighten your traffic posture before the Final EA lands. Long term, the barrier to entry in delivery is migrating toward exactly the competencies this review tests: the air carrier certificate, the operational discipline, and the ability to carry a defensible environmental and safety case through a federal process. As we argued on where the delivery moat actually sits, the airframe is table stakes and the certificate plus the compliance backbone is the product.

If your team is weighing how a metro-scale delivery expansion changes the airspace you already fly, or how to build the compliance and environmental case behind a Part 135 or BVLOS operation, that is exactly the kind of operational and regulatory question UAVHQ works through with operators. The comment window is open. Read the EA, and if it touches your airspace, put your operational judgment on the record before August 14.

Sources

Amazon Prime Air MK30 Chicago Drone Delivery FAA Environmental Assessment NEPA Part 135 OpSpecs BVLOS Remote ID DNL Noise Operating Area Public Comment Commercial Drone Operator Compliance