Two Planes Nearly Collide Over JFK Airport

A commercial jet and a small private plane got uncomfortably close over JFK on Monday, May 4. The aircraft were Endeavor Air Flight 5289 and a Cirrus SR22, both lining up for parallel runways during the evening arrival push. The FAA says controllers warned both crews, both pilots reported the other aircraft in sight, and the required separation was maintained. But the reported distance — about 500 feet — is close enough that people immediately read it as another JFK near-miss. (faa.gov) ### Which planes were involved? Endeavor Air Flight 5289 was on final approach to Runway 22L at JFK when a Cirrus SR22 crossed over to land on Runway 22R at about 5:15 p.m. local time on May 4. That matters because this was not two airliners on the same path. It was a regional Delta connection flight and a much smaller general-aviation aircraft converging near touchdown on side-by-side runways. (faa.gov) ### Why is “500 feet” such a big deal? Because the FAA’s own definition of a near midair collision starts at less than 500 feet, or when a pilot reports a collision hazard. So “within about 500 feet” is basically the edge of the line people use to separate a scary close call from a formally defined NMAC. The FAA has not publicly labeled this event that way. It has said required separation was maintained. (faa.gov) ### What did air traffic control do? Controllers issued traffic advisories to both pilots. Both crews said they had the other aircraft in sight. That is important because once pilots visually acquire the conflicting traffic, the situation can be managed with a mix of controller instructions and pilot see-and-avoid judgment. In plain English — the system bent, but it did not break. (faa.gov) ### So was this actually a loss of safety margin? Yes — at least in the common-sense way people mean it. Even if the legal or procedural separation minimum was not breached, two aircraft arriving at JFK and ending up roughly 500 feet apart on parallel approaches is a very thin cushion. Think of it less like a crash narrowly avoided at the last instant and more like a lane-d(faa.gov)mall. That last part is an inference from the FAA’s description and the agency’s 500-foot benchmark. (faa.gov) ### Why does JFK keep showing up in these stories? Because this is the second JFK close-call story in just over two weeks. On April 20, an American Airlines regional flight operated by Republic Airways missed its intended approach path and flew too close to Air Canada Jazz Flight 554 on parallel approach. Both crews got onboard collision alerts and both aircraft went around before landing safely. (patch.com) ### What made the April 20 event worse? That one involved two passenger jets, not a regional jet and a private plane, and the response was more dramatic. Controllers told the Air Canada Jazz flight to climb to 3,000 feet, the crew reported a TCAS resolution advisory, and the American flight also went around. The FAA said it was investigating why the Republic-operated flight deviated from its assigned course. (abc7ny.com) ### What happens next? The May 4 event is in the FAA’s incident log as a preliminary entry, which means details can still change. The likely focus is straightforward — how the parallel approaches were being managed, what each pilot saw, and whether the crossing movement by the Cirrus created a conflict that was ac(abc7ny.com)res in quick succession. (faa.gov) ### Bottom line Nobody got hurt, and the FAA says the required separation was maintained. But two JFK approach events in two weeks — one involving go-arounds and one involving a 500-foot gap — are exactly the kind of warnings the system is supposed to learn from fast. (faa.gov)