A UPS cargo jet climbing out of Louisville hit something at 5,000 feet in late July, and the crew told air traffic control it was probably a drone or a balloon. Neither pilot got a good look at it. One of them added that whatever they hit, it definitely was not a bird.
Five days later, UPS said it was a bird. The crew found the remains on the airframe after landing in Milwaukee, and an inspection turned up no damage.
I have spent nine years watching this sequence run. A startled crew reaches for “drone” on the radio, the word travels, and the answer arrives later to a much smaller room. This one resolved faster and more cleanly than most, with physical evidence on the aircraft. It still has not caught up.
UPS Confirmed A Bird Strike Five Days After The Drone Report
UPS Flight 5542, an Airbus A300-600 freighter bound for Milwaukee, struck an object climbing out of Louisville Muhammad Ali International Airport on a Friday in late July. A UPS spokesperson confirmed the following Wednesday that the aircraft had hit a bird and that no damage was found.
The cockpit audio, captured on LiveATC and posted by the aviation channel VASAviation, is undramatic. The crew reported the strike, said neither of them saw it clearly, and offered the drone-or-balloon theory unprompted. Asked about damage indications, they had none. No warning lights, no alarms, pressurization normal. The controller passed them a phone number to call after landing and they continued to Milwaukee.
The pilot later contacted VASAviation with more detail, reported by WHAS11 in Louisville. He had taken bird strikes before, he said, but this one was louder and much higher, and bird remains were visible on the jet at Milwaukee. One detail stuck with him: “this one stayed stationary while we were climbing.”
That is what made him certain it was not a bird, and it cuts the other way. Birds that break late are the ones you notice breaking. A soaring bird riding a thermal does nothing at all while a freighter closes on it at 250 knots. From the flight deck, a motionless object at altitude reads as a machine.
A Drone At That Height Would Have Been Deliberate, Not Accidental
Five thousand feet on the Louisville departure is roughly 4,500 feet above the ground, since the field sits at 501 feet (153 meters) of elevation. No consumer drone reaches that out of the box. DJI caps its aircraft at 500 meters, or 1,640 feet, above the takeoff point.
Open the Safety tab in DJI Fly and the max flight altitude slider starts at 120 meters, the 400-foot default. Push past that and the app throws a dialog telling you that you may be breaking local law and that the consequences are yours. Run the slider to its end and you are at 1,640 feet, still about 2,900 feet below this strike. Getting a Mavic or a Mini to 4,500 feet takes modified firmware, not a fat thumb.
One piece of folklore needs killing here too. There is no five-mile airport rule anymore. That was the old Section 336 notification requirement, repealed in 2018. The Federal Aviation Administration now holds both Part 107 pilots and recreational flyers to 400 feet (122 meters) above ground level, and Louisville sits under Class C airspace where any flight needs LAANC authorization, with ceilings near the field set at zero.
A drone at 4,500 feet is therefore not a hobbyist drifting high. It is someone who overrode their own aircraft and broke several federal rules on purpose. That operator exists, and we have never pretended otherwise: when a JetBlue crew reported striking a drone at 3,000 feet over JFK in June, the same arithmetic applied. It is simply not the likely explanation for an unidentified impact on a summer climb-out.
FAA Data Recorded 24,447 Wildlife Strikes Last Year
The FAA’s National Wildlife Strike Database logged 24,447 reported strikes in 2025, up 9.3 percent from the year before and equal to about 67 a day. Birds accounted for 94 percent of them, and 902 of the total did enough damage to be recorded as damaging.
The altitude numbers are where this story lives. Across 36 years of data in the FAA’s 2025 wildlife strike report, 71 percent of bird strikes with transport aircraft happened at or below 500 feet AGL, and 92 percent at or below 3,500 feet. Above 500 feet, reports fall by about 35 percent for every additional 1,000 feet of height. A bird at 4,500 feet is genuinely uncommon, which is exactly why the crew’s instinct went where it went.
Uncommon is not rare. The record height for a reported bird strike on a U.S. transport aircraft is 32,000 feet AGL, a Wilson’s warbler identified by the Smithsonian’s feather lab. And the high ones are the dangerous ones: strikes above 500 feet make up 29 percent of reports but 46 percent of the damaging ones. The FAA’s own conclusion is that the unsolved part of the bird problem is this exact band, climb and approach beyond the airport fence, where mowing and fencing do nothing.
Set that against the drone column. No U.S. airliner has ever been brought down by a drone. Birds have done it repeatedly, which is why the database exists and why the agency has spent more than $400 million on the problem since Flight 1549 went into the Hudson. We laid out that comparison in full when JetBlue’s JFK report produced no damage and no debris.
Drone Is Now The First Word Pilots Reach For
The FAA receives more than 100 drone sighting reports near airports every month. It publishes them quarterly as raw spreadsheets. They are reports, not findings. Nothing in the file records what the object turned out to be, because in most cases nobody establishes it.
The agency’s own sightings page logs what a pilot, a controller or a member of the public believed they saw. A sighting enters on the strength of one glimpse and stays there whether or not anything is recovered. There is no column for “resolved.” Reports accumulate. Corrections do not.
Louisville shows why that gap matters. This crew got an answer within days because a bird left physical evidence on an airframe that someone inspected. That is the exception. When the JetBlue crew reported a strike at JFK in June, mechanics found no damage, no dented leading edge and no debris, and the FAA confirmed nothing about what the aircraft actually hit. That report is still in the file, and so are hundreds like it.
The pattern predates this year by a decade. The agency determined that an Embraer 175 out of Chicago had collided with a party balloon rather than a drone, and almost nobody who read the first headline saw the second. Danish authorities quietly walked back the sightings that triggered a NATO response last autumn. A former Maryland governor reported dozens of large drones that critics identified as stars. Yesterday a NATO jet was scrambled and Vilnius airport closed over a radar contact that turned out to be birds. The Louisville audio resurfaced today on the aviation channel Captain Steeeve, where the object is still described as officially unconfirmed.
DroneXL’s Take
Give the crew of 5542 their due. At 4,500 feet, watching something hold perfectly still while you climb into it at 250 knots, “drone” is not a stupid conclusion. It is the wrong one, and they reported it as a guess rather than a fact.
The operator they were picturing is real, too. Don’t be that guy. Anyone who overrides their own aircraft to put a Mini at 5,000 feet near a Class C field is the reason the rules keep tightening on the rest of us who fly inside them.
But the reflex is what concerns me. Twenty years ago an unidentified object at altitude was a bird or a balloon, and the crew said so. Today the first word out of the cockpit is “drone,” from professionals with thousands of hours who have never knowingly seen one up there. That shift did not come from the sky changing. It came from five years of headlines teaching everyone what to call a thing they could not identify. Then the guess enters a federal database as a sighting, the sighting gets counted, and the count becomes evidence for the next rule.
Here is the detail I cannot get past. The FAA’s 36-year list of aircraft destroyed by wildlife runs to 89 entries, and one of them is a drone, knocked out of the sky by a bald eagle in 2020 during a shoreline erosion survey over Lake Michigan. In the agency’s own ledger of who has destroyed whom, wildlife is at 89 and drones are at zero. Thirty-five of the 89 were terrestrial mammals, mostly deer on runways. One was a drone.
What I would still like to know is the species. The public reporting has not named one, and the Smithsonian’s feather lab processed 7,408 bird-strike cases last year precisely so this question gets answered instead of guessed at. If the remains from Milwaukee went to that lab, the answer is already sitting in the database. That matters more than it sounds, because “large bird at 4,500 feet over Kentucky in July” is answerable, and answering it is how you stop the next crew from having to guess on an open frequency.
My read is that the reflex has outrun the evidence, and the honest fix is small. A crew that hits something unidentified should say they hit something unidentified. “We struck an object” costs nothing on the radio and puts no word into a database that a rulemaking will later lean on. Save “drone” for the times you actually saw one.
Sources: WHAS11, VASAviation, FAA National Wildlife Strike Database, 1990-2025, FAA UAS Sightings Reports, Captain Steeeve
DroneXL uses automated tools to support research and source retrieval. All reporting and editorial perspectives are by Haye Kesteloo. Read our editorial standards.
