# NTSB NYC97LA063: Piper PA-32-260, N3604W, Lincoln Park, NJ, March 25, 1997 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: March 24, 1997, 19:30 local (Mar 25, 1997, 00:30 UTC) - Place: Lincoln Park, NJ - Location: 40.9476° N, 74.3145° W: Placed by OpenAirDocs at LINCOLN PARK (N07), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=40.9476&lon=-74.3145&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report February 2, 1998 - Report: Approved by Office Director - NTSB case key (mKey): 39334 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC97LA063 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/39334/pdf - Page: https://openairdocs.org/ntsb/NYC97LA063 ## Probable cause The pilot's failure to maintain adequate obstacle clearance due to his diverted attention in attempting to re-illuminate the runway lights, which resulted in an inflight collision with a tree. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, approach - vfr pattern - final approach - light condition - dark night - clearance - not maintained, pilot in command (cause) - diverted attention, pilot in command (cause) - object - tree(s) ## Analysis The pilot reported that when he entered the traffic pattern at an uncontrolled airport, the runway lights were illuminated. On final approach, the runway lights extinguished. He clicked the microphone 5 times, and the runway lights reappeared. He remembered nothing else until he woke up in the airplane and climbed out of the wreckage. The airplane had struck a tree about 83 feet high, and 1,306 feet from the displaced threshold of the landing runway. A check of the pilot controlled lighting found that although the lights would stay illuminated longer than the required minimum of 15 minutes, it was possible to extinguish the lights if an attempt was made to reset the timer. According to the FAA publications (Airman Information Manual) and (Advisory Circular 150/5340-27A), the cycle of illumination, once initiated, should not be able to be interrupted. The pilot reported in a telephone interview that he should have gone around rather than attempt to get the runway lights illuminated again. ## Factual narrative On March 24, 1997, about 1930 eastern standard time, a Piper PA-32-260, N3604W, struck trees while on approach to the Lincoln Park Airport, Lincoln Park, New Jersey. The airplane was destroyed, and the certificated private pilot received minor injuries. Visual meteorological conditions prevailed for the local personal flight which departed Orange County Airport, Montgomery, New York, about 1900. No flight plan was filed for the flight which was conducted under 14 CFR Part 91. The pilot had departed earlier in the day from Lincoln Park Airport, and flew to Orange County Airport. He then flew back to Lincoln Park Airport where the accident occurred. In the NTSB Pilot/Operator Aircraft Accident Report, the pilot stated: "...Entered downwind for runway 1. Runway lights were on. Several other aircraft were in pattern. On final approach about 1/2 mile from displaced runway, runway lights went out. (They are on a timer). I pressed transmitter the obligatory five times and runway lights reappeared. That is all I remember until I woke up, climbed out of wreckage and walked to the airport restaurant." Inspectors from the Federal Aviation Administration (FAA) and the New Jersey Department of Aeronautics examined the airplane at the accident site. They reported that the airplane first struck the top of tree about 83 feet AGL. It then traveled an 289 feet, and came to rest in a wooded area, 177 feet from the approach end of the runway. Both wings were separated from the fuselage and the cabin area was opened up. Emergency personnel reported that fuel was leaking from the ruptured fuel tanks. In a telephone interview, the pilot told the Safety Board Investigator-In-Charge (IIC) that he should have gone around rather than attempt to get the runway lights illuminated again. A check of FAA records revealed that runway 1 was 2,942 feet long, 40 feet wide, and had an asphalt surface. The runway edge lights were medium intensity, and were equipped with pilot controlled lighting. The landing threshold was displaced 840 feet. Trees about 80 feet tall were located about 330 feet prior to the approach end of the runway. A Visual Approach Slope Indicator (VASI) was installed on runway 1; however, a Notice to Airmen was issued that the VASI status as "Out of service indefinitely." The airport manager told the Safety Board IIC, that there were no plans to make the VASI operational. On the night of April 2, 1997, the Safety Board IIC checked the pilot controlled runway lights using a hand held radio. The runway edge lights would stay illuminated for 18 minutes, 30 seconds when activated on. They would flash 3 times in the last few seconds of their illumination. With the runway edge lights illuminated, an attempt to reset the timer for a full 15 minutes would sometimes extinguish the runway lights. According to the Aeronautical Information Manual \ Chapter 2 - Aeronautical Lighting and Other Airport Visual Aids \ Section 1 - Airport Lighting Aids \ 2-1-7 PILOT CONTROL OF AIRPORT LIGHTING, and Advisory Circular AC 150/5340-27A - AIR TO GROUND RADIO CONTROL OF AIRPORT LIGHTING SYSTEMS, you should not be able to extinguish the runway lights prior to the end of the 15 minute cycle. The investigation found that the runway lights would extinguish under two conditions; reaching the end of the timer cycle; clicking five times on the frequency to reset the timer. . ## Aircraft - Registration: [N3604W](https://openairdocs.org/deregistered/N3604W-1997-11-19), registration cancelled 1997-11-19, S/N 32502 (OpenAirDocs) - Reported make and model: Piper PA-32-260 - Registry model: [Piper PA-32-260](https://openairdocs.org/model/piper-pa-32-260) (registry code 7103206) (OpenAirDocs) - Category: Airplane - Serial number: 32-502 - Airframe hours: 3965 - Engines: Lycoming O-540-E4B5 260 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Operator: Walter C Corocco - Registered owner: Ronald Saglimbene - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: Annual, September 27, 1996, 77 hours before - Departed: MGJ, MONTGOMERY, NY - Destination: N07 - Airport: N07, Lincoln Park, runway 1, 2,942 × 40 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 69; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 3,510 total, 45 in this make and model, 3,510 as pilot in command, 44 in the last 90 days, 8 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night/dark - Wind: variable at 3 knots - Visibility: 20 statute miles - Lowest ceiling: none - Temperature: 36 °F, dew point 12 °F - Altimeter: 30.00 inHg - Observed at: CDW, 4 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 19970325003539A](https://openairdocs.org/incident/19970325003539A), Mar 25, 1997: Piper PA32260, Lincoln Park, NJ, Substantial damage. Aircraft struck trees on approach and crashed into woods. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.