A United Airlines Boeing 737 carrying 111 people came within roughly 100 feet of a drone while descending into Newark Airport on Friday afternoon, forcing the FAA to open yet another investigation into unauthorized drone activity near one of the nation's busiest airports.
The pilot of United flight 1513, arriving from Key West, Florida, radioed air traffic control with a blunt warning at approximately 4:20 p.m.: "We almost hit a drone." The drone, described as circular and about three feet wide, was spotted roughly 100 feet below the aircraft at an altitude of approximately 2,000 feet, well inside the approach corridor where commercial jets are heavy, low, and have almost no room to maneuver.
The flight landed safely, and all 106 passengers and five crew members deplaned without incident. But the near-miss raises a question that federal regulators and lawmakers have been slow to answer: Who is flying these drones near major airports, and why does the enforcement response remain so toothless?
The drone sighting was not limited to a single cockpit. A second pilot flying a separate aircraft into Newark also reported seeing the drone at approximately 2,000 feet, corroborating the account from flight 1513. CNN verified the air traffic control audio containing the pilot's statement.
United Airlines issued a brief statement acknowledging the incident but offered little beyond the basics.
"United flight 1513 reported a potential drone sighting prior to arriving in Newark. The flight landed safely, and customers deplaned normally at the gate."
Note the careful language: "potential drone sighting." Two pilots on two different planes saw the same object at the same altitude. The airline's public relations instinct, minimize, move on, is predictable. The FAA's job is to be less diplomatic.
The FAA confirmed it receives more than 100 drone-sighting reports near airports every month. That figure alone should alarm anyone who flies commercially. The agency warned that unauthorized drone operators face fines and criminal charges, including possible jail time.
Warnings are cheap. Enforcement is what matters. And in this case, the drone operator has not been identified. No arrests have been reported. No fines have been announced. The drone itself has not been reported as recovered or tracked.
This is the pattern. A near-miss occurs. The FAA opens an investigation. A statement goes out reminding drone operators that what they did is illegal. And then the story fades until the next close call, or until someone's luck runs out.
Newark Airport has already had a difficult stretch. Earlier this year, a United Airlines plane carrying 221 passengers struck a pole and a truck while landing at Newark, an incident serious enough to prompt a federal safety investigation.
A three-foot circular drone at 2,000 feet is not a toy. At that altitude and size, a direct strike on a jet engine intake could cause catastrophic damage. Bird strikes, involving objects far softer and lighter than a battery-powered drone packed with metal and electronics, have forced emergency landings and caused fatal crashes.
The physics are simple. A Boeing 737 on approach is traveling at roughly 150 to 180 miles per hour. A drone strike at that speed delivers enormous kinetic energy. The FAA knows this. Airlines know this. Passengers, by and large, have no idea how often these encounters happen.
An NTSB report on the earlier Newark incident revealed that a first officer had warned the captain about a low, slow approach before that plane struck a light pole, a reminder that even small deviations from normal flight parameters can produce serious consequences on the ground. A drone collision at altitude would leave a crew with far fewer options.
Federal law prohibits flying drones near airports without authorization. The FAA has the statutory authority to pursue fines and criminal referrals. Yet the agency's own monthly tally, more than 100 sightings near airports, suggests that deterrence is failing.
Part of the problem is identification. Consumer drones are small, fast, and difficult to track on radar. Many lack the Remote ID transponders that the FAA has been phasing in. Even when a drone is spotted by multiple pilots, as it was Friday, tracing it back to an operator on the ground requires technology and coordination that airports and local law enforcement often lack.
The result is an accountability vacuum. Drone operators who fly recklessly near commercial airspace face theoretical penalties but, in practice, face almost none, because they are rarely caught.
That gap between the law on the books and the law as enforced is exactly the kind of institutional failure that puts ordinary people at risk. The 106 passengers on flight 1513 did nothing wrong. They bought tickets, boarded a plane, and trusted that the airspace around a major American airport would be secure. It wasn't.
The incident also comes amid a broader pattern of alarming aviation events. A United Airlines flight was recently forced back to Newark after a teenager's Fitbit device name triggered a midair security scare, a different kind of threat, but one that underscores how thin the margin of safety can feel for passengers on commercial flights.
The FAA has not said whether the drone spotted Friday was a hobbyist device, a commercial unit, or something else entirely. The description, circular, three feet wide, fits a range of consumer and commercial platforms readily available online for a few hundred dollars.
That accessibility is part of the problem. The barrier to entry for owning a drone capable of reaching 2,000 feet is negligible. The barrier to accountability, once that drone enters restricted airspace, is apparently just as low.
Congress has held hearings. The FAA has issued rules. But the fundamental question remains unanswered: What is the plan for actually stopping unauthorized drones near airports before a collision happens, rather than investigating after one does?
Meanwhile, other aviation emergencies continue to test the system. In a separate recent incident, passengers aboard an Air Canada flight had to physically restrain a pilot who suffered a seizure, forcing an emergency diversion, a reminder that the margin between routine flight and crisis is never as wide as travelers assume.
Friday's near-miss ended safely. The plane landed. The passengers walked off. United issued its statement. The FAA opened its file.
But more than 100 drone sightings near airports each month means this is not a freak event. It is a recurring hazard with a known cause and an inadequate response. The FAA's own numbers prove the scale of the problem. Its enforcement record does not prove it has a solution.
The bakery truck driver struck by a United jet at Newark earlier this year told his family he thought he was going to die. He survived. But his fear was rational, and so is the fear of any passenger who learns that a three-foot drone was 100 feet from their aircraft on approach.
A hundred feet is not a close call. It is a near-catastrophe measured in fractions of a second. And until someone in Washington treats it that way, the next drone will be up there waiting.
