Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

March 25, 1997 · Piper PA-32-260 · N3604W

Lincoln Park, NJ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 25, 1997
Injury Outcomes
1 injury (1 minor injury)
Location
Lincoln Park, NJ
Aircraft
Piper PA-32-260
Tail Number
N3604W
Operator
Walter C Corocco
Injuries
Minor
Aircraft Damage
Destroyed
NTSB Number
NYC97LA063

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.

NTSB 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.

Full 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. .

Flight

Event TypeAccident
Event Time19:30 EST
Nearest AirportLincoln Park (0nm)
Runway1
Runway Length2942 ft
Runway Width40 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32-260
Tail NumberN3604W
Aircraft CategoryAir
DamageDestroyed
OperatorWalter C Corocco
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-540-E4B5 · Reciprocating · 260
Seats6

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 69 · Third Class

Conditions

ConditionsVMC
LightDark Night
Wind3 kt
Visibility20 sm
CeilingNone
Temperature / Dew Point36 C / 12 C
Altimeter30.00 inHg
Observation Time23:45
Weather SourceWFAC

Appendix: Source Data