ASN Wikibase Occurrence # 134120
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Monday 24 March 1997 |
Time: | 19:30 |
Type: | Piper PA-32-260 |
Owner/operator: | Walter C Corocco |
Registration: | N3604W |
MSN: | 32-502 |
Total airframe hrs: | 3965 hours |
Fatalities: | Fatalities: 0 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Lincoln Park, NJ -
United States of America
|
Phase: | Approach |
Nature: | Private |
Departure airport: | MGJ |
Destination airport: | N07 |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
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. .
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.
Sources:
NTSB id 20001208X07618
Revision history:
Date/time | Contributor | Updates |
15-Feb-2015 20:53 |
Anon. |
Updated [Narrative] |
21-Dec-2016 19:26 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation