NTSB CAROL · Event
Event NYC97LA063
Aircraft involved
Probable cause & findings
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.
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. . 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_NYC97LA063.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
- arXiv 2022 · arXiv preprint
Enhanced Prediction of Three-dimensional Finite Iced Wing Separated Flow Near Stall
Icing on three-dimensional wings causes severe flow separation near stall. Standard improved delayed detached eddy simulation (IDDES) is unable to correctly predict the separating reattaching flow due…
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Analysis on the Negative Emotional, Physiological, and Cognitive Responses Elicited from of the Activation of a Stall Alarm
Failing to identify an aerodynamic stall can lead to the inability of an aircraft to sustain flight. To warn pilots of an impending or fully-developed stall, many aircraft have safety devices installe…
Browse the full corpus — academia portal ↗