FlightFollower69 Y/O pilot goes rogue at JFK, almost causes a mid air, gets intercepted by NYPD 🚁
A Wrong Turn Became an Airspace Emergency
The incident began as a navigation error, not an intentional incursion. A 69-year-old pilot flying his home-built Vans RV-7A, N5025G, toward Republic Airport on Long Island turned too early and entered the busy airspace around John F. Kennedy International Airport.
Accident Facts
- Incident
- 2009 JFK airspace incursion
- Aircraft
- Vans RV-7A, N5025G
- Pilot
- 69-year-old retired Navy pilot, according to contemporary reporting
- Outcome
- EVA Air 747 sent around;
- Public investigation status
- FAA investigation reported at the time;
The aircraft was not communicating with the relevant controllers. It continued circling near the eastern end of JFK while arriving traffic was operating in the same airspace.
At one point, the RV-7A was directly in the path of an inbound EVA Air Boeing 747. JFK Tower responded by sending the airliner around, while an NYPD helicopter moved to identify and contact the unknown aircraft.
The Aircraft Was Not Flying a Normal ATC Profile
The most important operational fact is that the RV-7A was not communicating with the controllers responsible for the airspace it had entered. That left ATC trying to identify an aircraft whose intentions and position were not available through normal two-way communication.
The controller's comment that the aircraft was “going everywhere” reflected the uncertainty created by the track. The risk was not simply that one airplane had crossed a boundary. The risk was that the unknown aircraft was moving through a high-density arrival environment without the normal communication and separation mechanisms.
The NYPD helicopter provided the missing link. Once PD15 established contact, the situation changed from an unidentified traffic hazard into a controllable coordination problem.
The NTSB Record Is Not About the JFK Incursion
The source audit associates ERA12LA293 with this video, but the NTSB report for that number concerns a separate 2012 forced-landing accident involving the same registration, N5025G, in West Virginia. That report found an engine lubrication problem caused by an oil-hole alignment issue following engine work.
The JFK event occurred in 2009 and is therefore not the ERA12LA293 accident. This distinction is critical. video and contemporary reporting establish the JFK incident, but the NTSB number in the audit should not be presented as the investigation number for this airspace event.
ERA12LA293 is therefore not the identifier for this event.
Why This Incident Matters
The event demonstrates how quickly a navigation error can become a traffic emergency near a major airport. Once the aircraft entered JFK's airspace without communication, the system had to create separation around an aircraft whose intentions were unknown.
The successful resolution depended on several layers: the tower recognized the conflict, the airliner responded to the go-around instruction, the NYPD helicopter located the RV-7A and the pilot ultimately followed the escort to Republic Airport.
Evidence and Findings
The incident-specific evidence comes from contemporary reporting and contemporary reporting rather than the NTSB case number listed in the old audit. The video identifies the aircraft as N5025G and describes the RV-7A entering the JFK TCA, the tower sending an EVA Air 747 around and NYPD15 making contact with the homebuilt aircraft.
The difference between accounts is significant enough to state explicitly. ERA12LA293 is a 2012 N5025G accident in West Virginia in which the same aircraft suffered an engine seizure and forced landing. It is not the 2009 JFK airspace event. Using that report as the JFK investigation would create a false chain of evidence.
The 2009 incident itself is well documented in contemporary aviation reporting. The aircraft entered the JFK area after a navigation error, remained without normal radio contact and came into conflict with an inbound airliner. The NYPD helicopter then became the practical communication bridge.
The incident demonstrates that an airspace incursion does not always end with an enforcement action or collision. Controllers and other aircraft can create separation around the unknown traffic while another agency attempts to establish communication. The successful landing at Republic Airport shows how quickly the situation improved once the pilot could be contacted and directed.
What Could Have Broken the Chain
The first barrier was navigation. The pilot's planned route toward Republic Airport required a turn that would keep him outside the JFK traffic environment. Once that turn was made too early, the next barrier was communication. Because the aircraft was not in normal contact with the relevant controllers, the airspace system had to identify it as unknown traffic.
The final barrier was intervention by other agencies. JFK Tower protected the inbound EVA 747 by sending it around, while NYPD15 established contact with N5025G and escorted it to Republic.
The event therefore shows why multiple layers matter. A navigation mistake need not become a collision if communication, surveillance and traffic separation remain effective. But when several layers are simultaneously weakened, a single wrong turn can put an aircraft directly into the path of a heavy airliner.
The Final Safety Margin
The event also shows the value of an aircraft being identifiable even when its pilot is not talking to ATC. Surveillance allowed controllers to recognize the unknown target, while the helicopter provided the close-in identification and communication that radar alone could not provide. Once the pilot was contacted, the emergency became manageable.
- Navigation errors near major airports can become immediate traffic conflicts.
- Loss of communication makes an airspace incursion much harder for controllers to manage.
- Aerial law-enforcement assets can provide an important identification and communication bridge.