By John Q. Hosedrinker 
A JetBlue Airways passenger jet reported striking a drone while on final approach to John F. Kennedy International Airport. The pilot of Flight 948 communicated the collision with a drone at approximately 3,000 feet, and the aircraft subsequently landed safely. Although the plane underwent a post-flight inspection that found no damage, the FAA is investigating the incident, which could represent one of the first confirmed drone-aircraft collisions in the U.S. commercial airspace.
Read the original article here
A JetBlue pilot reported what they believed to be a drone strike while on approach to landing at JFK International Airport, a statement that has sparked considerable discussion and raised concerns about the growing presence of unmanned aerial vehicles in sensitive airspace. While the pilot’s account pointed towards a drone, the subsequent post-flight inspection by the airline revealed no physical evidence of such a collision. This discrepancy leaves open the possibility that something did occur, but it also means a definitive confirmation of a drone impact isn’t possible based on the physical findings.
The idea of a drone collision causing absolutely no damage to a commercial airliner strains credulity for those involved in aviation maintenance. Aircraft undergoing such an incident would typically be subjected to an extremely rigorous inspection, with even the slightest surface scratches meticulously documented and addressed. This leads to the question of whether we are waiting for a catastrophic event before implementing stricter measures, highlighting the critical need for robust enforcement of no-drone zones around airports globally. The carelessness of some drone operators, potentially endangering aircraft, is a serious issue that could lead to significant future regulations for drones, especially considering the evolving landscape of drone technology and its potential applications.
The advancements in drone capabilities, particularly the ability to reach considerable altitudes, raise questions about their perceived limitations. There’s a speculative notion of drone users facing legal repercussions, perhaps even suing airlines for drone destruction and inadvertently revealing their ownership of a drone flown illegally. The idea of a drone reaching such heights, coupled with the absence of damage, makes one wonder if other, perhaps more unusual, explanations might be at play.
A personal anecdote from an airline pilot illustrates the complexities of such reports. During a landing, a first officer was convinced they had hit a drone, citing a loud noise, a sharp thud, and even describing it as white. Air traffic control initiated protocols, but the pilot urged a more measured approach until reaching the gate. Upon inspection, it turned out to be a bird, not a drone. This experience underscores the importance of distinguishing between assumption and established fact, particularly when communicating over sensitive air traffic frequencies. The advice given was to report that something was hit and investigate further upon landing, rather than making immediate, unverified claims.
The feasibility of a collision with a consumer-grade drone at significant altitudes, especially at landing speeds, is also being debated. Many commercially available drones are designed with built-in limitations that prevent them from flying into restricted airspace. This suggests that if a drone was indeed involved, it might have been a custom-built or modified unit. The physical possibility of a very small, lightweight drone causing no discernable damage exists, though the likelihood of such a tiny drone being visible from the cockpit is considered exceptionally low.
From an aviation maintenance perspective, the absence of any visible damage after a reported impact is difficult to reconcile with the physics of a collision. Even a relatively soft, lightweight drone would likely leave some trace upon impact with a high-speed aircraft. This leads to the contemplation that the reported incident might have been a misidentification, with a bird strike being a more probable explanation in the absence of physical evidence.
The conversation also touches upon the technological aspects of drones and their compliance with airspace regulations. While many drones are programmed with geofencing capabilities to prevent them from entering no-fly zones, it’s acknowledged that these restrictions can sometimes be bypassed or circumvented, particularly with a determined individual. The ease with which drone restrictions can be modified raises concerns about the reliability of these safety measures, especially when pilots report potential threats.
The escalating use of drones in various capacities, including unfortunately in potentially dangerous situations like flying over active wildfires, has drawn significant attention. These incidents highlight the need for stricter oversight and enforcement to prevent individuals from endangering critical operations and public safety. The potential for drones, even seemingly small ones, to cause significant damage to aircraft engines or other critical components cannot be overlooked, especially given the high relative speeds involved in flight.
While some might dismiss the possibility of a drone strike due to the lack of damage, others acknowledge that numerous factors contribute to such events. The relative speed between an aircraft and a drone, while significant, doesn’t necessarily dictate the outcome of a collision in terms of visible damage. A very light drone, moving at a similar direction and speed as the aircraft, could theoretically cause minimal impact. However, the practicalities of achieving such precise relative speeds are challenging.
The discussion also delves into the concept of “mistaken identity” in aviation. Pilots are highly trained, but situations can arise where what is perceived as one thing might actually be another. The anecdote of the bird strike serves as a prime example of how initial assumptions, even with strong sensory input, can be inaccurate. The focus on factual evidence and thorough inspection remains paramount in such scenarios.
The inherent capabilities of commercially available drones are also a point of contention. Many consumer drones have limitations that prevent them from reaching the altitudes reported in some of these discussions, making a collision with such a device at 3,000 feet less likely. This further fuels the debate about the nature of the object that the JetBlue pilot encountered.
Ultimately, while the pilot’s report of a drone strike at JFK is a significant event, the absence of physical evidence complicates the definitive conclusion. The incident serves as a stark reminder of the evolving challenges posed by drone technology in aviation and underscores the ongoing need for vigilance, robust regulations, and a commitment to safety protocols to prevent future occurrences. The debate surrounding this event highlights the complexity of identifying and responding to potential threats in the airspace, where perception and physical evidence must align for a conclusive understanding.