By Wesley Alexander • September 10, 2026 • 8 min read

Tactical Summary

Amazon's Prime Air operations lead in Baton Rouge told a Rotary Club audience last week that the company's delivery drones are quieter than an idling delivery truck.[1] The FAA's environmental filing for that same hub puts the loudest moment of a Baton Rouge delivery at a sound exposure level of 92.1 decibels, measured 25 feet from the aircraft while it hovers about 13 feet over the drop point.[2] The agency's own reference for that figure is a diesel truck at 50 feet, or a noisy urban street in daytime, at roughly 80 to 90 decibels.[3]

Both characterizations come from the same program, and in a narrow sense both are defensible. That is exactly why this story matters beyond Louisiana. The gap between the cruise number and the doorstep number, and between today's flight volumes and the permitted ceiling, is where community acceptance for drone delivery will be won or lost. The data that decides the argument is already public, in the operator's own regulatory filings, and residents are learning to read it.

Two Numbers, Both True

The FAA's draft environmental assessment for the Baton Rouge Prime Air Drone Delivery Center contains two headline acoustic figures for the MK30.[2]

En route, at about 200 feet above ground and roughly 67 mph, the maximum sound exposure level on the ground is about 63.7 dB. The agency compares that to an air conditioning unit heard from 100 feet.[3] Quieter than an idling truck is a fair gloss of that number. If a drone transits overhead and keeps going, most people will register it briefly, if at all.

At the delivery point, the profile changes. The MK30 descends to about 13 feet above the drop location and hovers while it releases the package through its payload doors.[2] That hover is the 92.1 dB SEL figure, measured at 25 feet. Takeoff and landing at the hub measure 90.5 and 91.8 dB SEL at 20 feet.[3] The FAA's comparison for those is a household vacuum cleaner at 10 feet, running in your front yard for the better part of a minute.

So the truck comparison holds while the aircraft is passing overhead and inverts at the doorstep. Neither Amazon nor the FAA is fabricating anything. They are describing different phases of the same 61-second delivery profile.[2] The operator lesson is that a single noise talking point cannot honestly summarize a flight profile with a 28-decibel spread, and audiences eventually notice.

The Floor and the Ceiling

The second gap is volumetric. Residents of the Broadmoor neighborhood under the outbound flight paths from the Cortana Place hub told WAFB they see a drone roughly every two to five minutes, and an Amazon spokesperson confirmed the site currently operates 20 drones with up to 10 airborne at a time.[1]

The filing authorizes far more. Prime Air asked to operate up to 1,000 MK30 flights per day from Baton Rouge, up to 365 days a year, between 6 a.m. and 10:30 p.m., across a 7.5-mile radius and roughly 174 square miles.[2] Spread over the operating window, that is on the order of 60 departures an hour, each a round trip. The FAA's noise analysis conservatively estimates that any single location could see up to 500 delivery overflights a day at the maximum, plus returns.[3]

Amazon has said it will ramp gradually with demand, and the Texas experience suggests the ramp is real: DroneXL notes the Richardson-area hub was reported filling about 150 orders a day against a permitted 1,000.[4] But the permit is the permit. What Broadmoor hears today is closer to the floor than the ceiling, and every future complaint cycle will be litigated against the authorized maximum, not the current tempo.

We covered the same structural issue when Amazon requested 1,000 flights a day from each Chicago hub: the environmental assessment is where the real operating envelope is defined, long before the neighborhood feels it.

The Paperwork Loose End

There is also a process wrinkle worth watching. According to DroneXL's review of the FAA's public NEPA docket, Baton Rouge commercial service began on July 7, while the public comment period on the draft environmental assessment ran until July 22, and as of the FAA page's August 20 update no final assessment or Finding of No Significant Impact for the site appeared in the completed-reviews section.[4] The identically dated Omaha filing sits in the same state. Neither the agency nor the company has published anything reconciling those dates.

Meanwhile, the FAA has moved the goalposts for everyone who comes next. The agency's new national Programmatic Environmental Assessment for Part 135 drone delivery lets future markets be checked against a standing document, with no site-specific review and no comment period if they fit inside it. Fitting is largely a noise calculation: up to 1,150 deliveries a day per hub, with high-volume hubs kept at least 600 feet from homes. We broke down that framework and its September 26 court-challenge deadline in our analysis of the national programmatic EA's setback and delivery cap. Baton Rouge came in under the old site-specific system; the noise numbers in its filing are effectively the calibration data for the national one.

Why Operators Outside Amazon Should Care

If you run or are planning any delivery, DFR, or infrastructure program that flies over homes, Baton Rouge is a preview of your community meeting. Four takeaways:

  1. Your EA is your deposition. Every acoustic claim you make in public will be checked against your own filing. Brief your spokespeople on the SEL table, not the marketing sheet. The safest public statement is the one that quotes the filing directly, ugly numbers included.
  2. Describe the profile, not the average. Cruise, approach, and hover are different acoustic events. Tell neighbors the honest version: mostly a faint pass at altitude, briefly a vacuum cleaner in the yard during the drop. People forgive noise they were told about; they organize against noise they were promised away.
  3. Route design is noise policy. WAFB asked Amazon whether it had considered routing over roads instead of homes; the answer was that it had not, and that altitude changes are the FAA's call.[1] That is technically true and rhetorically costly. Operators who proactively bring routing and altitude options to the FAA, rather than pointing at the agency, will own the narrative in their markets. Wing's approach in its Houston expansion filings shows how siting choices get scrutinized well before scale.
  4. Plan against the ceiling. Community sentiment measured at 150 flights a day tells you little about life at 1,000. If your business case needs the full permitted volume, your acceptance strategy has to survive the full permitted volume. Amazon's Richardson apartment strike showed how fast goodwill decays when incidents meet an already-irritated population.

Noise is not a PR problem to be phrased around. It is a siting, routing, and flight-profile engineering problem, and it is rapidly becoming the binding constraint on drone delivery in populated areas. The operators who treat acoustic data as core airworthiness-style documentation, disclosed and defended like any other performance number, are the ones who will still be flying at scale in five years.

For continuing coverage of how delivery noise, siting rules, and the national programmatic framework evolve, the weekly UAVHQ dispatch on Substack tracks this beat. If your own program's authorization package needs to hold up in front of both regulators and a city council, the Part 108 BVLOS Readiness Playbook covers the documentation and safety-case discipline that makes those meetings survivable.

Sources

  1. Amazon drones draw noise complaints in area neighborhoods (WAFB, Sept. 9, 2026)
  2. FAA Draft Environmental Assessment: Amazon Prime Air Package Delivery Operations in Baton Rouge (faa.gov)
  3. FAA Baton Rouge EA, Appendix D: Noise Analysis (faa.gov)
  4. Amazon Says Quieter Than a Truck. Its FAA Filing Says 92 Decibels (DroneXL, Sept. 9, 2026)