NYC97LA063 · Piper PA-32-260
Piper PA-32-260 · Accident: in flight collision with object on approach
From Orange County Airport (MGJ) to Lincoln Park Airport (N07)
Event
- NTSB case
- NYC97LA063
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-32-260
- Aircraft type
- Piper PA-32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3604W
- Operator
- Walter C Corocco · private individual
- Onboard fatalities
- Unknown
- Route
- From Orange County Airport (MGJ), Montgomery, NYTo Lincoln Park Airport (N07)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › Diverted attention
Approximate · Estimated position: the centre of Lincoln Park, NJ, the place the record names. Not the accident site.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA063
- Event ID
- 20001208X07618
- Case number
- NYC97LA063
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1997-03-25.
- API snapshot SHA-256: 11ba28dceed0bc196c90672778880cf81a8eae206f8ffdbb792d85443f0082f1; retrieved 2026-09-21T21:29:13.481Z.