The pilot's words went on the radio. The post flight inspection told a different story. The Federal Aviation Administration has opened a probe to figure out which is right.
JetBlue Flight 948 was on final approach to New York's John F. Kennedy International Airport on Monday morning when its pilot keyed the radio and told air traffic control something controllers do not hear every day. "We collided with a drone," the pilot said, according to ATC audio published by ABC7 New York and Fox News. The controller asked the pilot to confirm. The pilot confirmed.
An hour or so later, the Airbus landed safely, the passengers deplaned normally, and a post-flight inspection of the aircraft found no damage and no evidence of any impact, according to JetBlue's statement to the BBC and the Federal Aviation Administration.
That gap is the actual story: a direct pilot claim on the radio, alongside a clean post-flight inspection.
The flight had taken off from Las Vegas the night before and was descending through roughly 3,000 feet over Queens on its way to runway 22L when the pilot made the report, at about 7:15 a.m. local time on June 29, according to AP News. The aircraft was withdrawn from service so technicians could look for what the pilot said he had hit. JetBlue and the FAA both said the inspection turned up nothing.
The contradiction sits in the structure of the report itself. A pilot on final approach has direct sensory information: a visual cue, a sound, a vibration, an unexpected flash. Post-flight inspection by a technician walking the fuselage with a flashlight and a checklist is good at finding damage that breaks the skin, dents aluminum, smears composite, or leaves residue. It is not built to confirm the absence of something the size of a small bird, in flight, at several hundred knots of closure speed, where even a confirmed strike might leave only a faint mark that gets filed under "unknown."
That is why the FAA has opened an investigation even though there is nothing on the plane to investigate in the physical sense. The agency's job, in cases like this, is to take the pilot's report seriously enough to look, and to acknowledge openly when the aircraft tells a different story than the cockpit did.
CNN reported on Monday that a separate helicopter crew operating near JFK the same day reported a near-miss with a model aircraft, an incident that is not the same event and does not share an aircraft, a pilot, or an operator with Flight 948. It does illustrate a wider pattern of small unmanned aircraft showing up where they should not be, in airspace where a commercial jet is descending toward a runway at a major airport.
NBC News and the BBC both noted that the FAA has not, as of Monday afternoon, identified a drone operator or filed any enforcement action tied to the JetBlue report. Without a recovered device, a witness on the ground, or radar returns consistent with a small drone in the approach path, the federal investigation will lean heavily on the pilot's account, the maintenance log, and whatever the agency can pull from the JFK tower recordings.
For now, the public record holds two facts that have not been reconciled. A JetBlue captain told controllers, on a recorded frequency, that he hit something. Mechanics who spent the next several hours with the airplane say there is nothing to show for it.
The next thing to watch is the FAA docket. The agency typically publishes a final report on pilot-reported collision cases, including ones that close without finding an object. That report will not retroactively create damage on the aircraft, but it will determine whether the incident is logged as a confirmed drone strike, an unconfirmed drone strike, or an unconfirmed impact of unspecified origin, three different categories that tell different stories about what was actually flying near JFK at 7:15 on a Monday morning.