Aviation Accident Summaries

Aviation Accident Summary NYC07FAMS1

Westhampton, NY, USA

Aircraft #1

N5067T

PIPER PA-32-260

Analysis

The pilot was conducting a visual flight rules (VFR) flight when he contacted an airport tower controller and asked if the field was VFR. The controller stated that it was. The pilot advised the controller that he was 15 miles north of the airport, and the controller subsequently cleared him for a straight-in approach, instructing him to report a 3-mile final. About 2 minutes later, the controller asked the pilot for his position, and the pilot stated that he was proceeding to a navigational aid to attempt another approach. The controller then asked the pilot if he would like a contact approach, and the pilot responded that he would. After the controller provided the pilot with the approach control frequency, no further transmissions were received from the pilot. The airplane and the pilot were not located, and were presumed lost at sea.

Factual Information

On August 25, 2007, about 1415 eastern daylight time, a Piper PA-32-260, N5067T, went missing near Westhampton, New York. The airplane and the certificated private pilot were not located, and were presumed lost at sea. Both visual and instrument meteorological conditions were present in the area. No flight plan had been filed for the flight that originated at Spadaro Airport (1N2) East Moriches, New York. The local personal flight was conducted under 14 CFR Part 91. A review of radio transmissions between the airplane and the control tower at Francis S. Gabreski Airport (FOK), Westhampton, New York, revealed that the pilot first contacted the tower controller at 1339, and asked if the airport was "VFR". The controller responded that it was, which the pilot acknowledged. At 1356, the pilot reported that he was 15 miles, "directly north" of the airport, VFR. The tower controller cleared the pilot for a straight-in approach to runway 19, and requested that he report a 3-mile final. The controller then provided an altimeter setting of 29.89 inches of mercury and winds 220 degrees at 9 knots. The pilot confirmed "straight in for one nine." At 1358, the tower controller asked the pilot for his position, and the pilot responded, "I'm gonna go back to Calverton V-O-R and start all over again. I can't find you. Okay?" After the controller's acknowledgement that the pilot was headed back to the VOR, the pilot confirmed that he would "try it again." The controller then asked the pilot if he would like to contact approach control for vectors, and the pilot responded that he would. The controller then provided the pilot with the approach control frequency, which the pilot read back. The tower controller subsequently contacted approach control, and advised that controller to expect the pilot to contact him. He then repeated the approach control frequency over the tower frequency, but did not receive a response from the pilot. After several minutes, the approach controller advised the tower controller that the pilot never contacted him. He also noted, "I think he's headed eastbound, in the wrong direction." The tower controller subsequently made multiple radio calls to the airplane without receiving any responses from the pilot. He also continued to coordinate with approach control, and later contacted search and rescue. Gabreski Tower did not have a radar repeater in the tower cab. Weather, reported at the airport at 1353, included clear skies. However, news reports indicated fog in the area. According to Federal Aviation Administration (FAA) records, the pilot held a private pilot certificate. He did not hold an instrument rating. On his latest FAA third class medical application, dated February 14, 2006, the pilot indicated he had 2,000 hours of flight time. According to Civil Air Patrol press releases, the search area included Long Island, Long Island Sound and the Atlantic Ocean south of Long Island. On August 28, 2007, the search was terminated with no wreckage recovered.

Probable Cause and Findings

Undetermined. The airplane remains missing.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports