NYC98FA073 · Piper PA-23-160
Piper PA-23-160 · Accident: airframe, component or system failure en route
From Greenwood Lake Airport (4N1) to 2N8 · Matawan, NJ
Event
- NTSB case
- NYC98FA073
- 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
- 2 · 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-23-160
- Aircraft type
- Piper PA-23
- 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
- N3374P
- Operator
- Lino Fazio
- Onboard fatalities
- Unknown
- Route
- From Greenwood Lake Airport (4N1), West Milford, NJTo 2N8 · Matawan, NJ
- 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
- En route · cruise
- 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
- Airframe, component or system failure
- 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
- Empennage › Separation
Approximate · Estimated position: the centre of Somerville, NJ, the place the record names. Not the accident site.
NTSB narrative
"THIS CASE WAS MODIFIED AUGUST 2, 2006."
The Piper Apache was cruising at about 1,500 feet AGL, when a witness saw the vertical stabilizer start to oscillate and then separate from the airplane. The airplane descended and struck a multiple family dwelling. Examination of the wreckage revealed the outboard wing panels had separated from the airplane in flight due to downward bending forces that occurred after the in-flight separation of the horizontal stabilizer. The horizontal stabilizer was found next to the vertical stabilizer apart from the main fuselage and wing wreckage and had separated, in-flight, in a horizontal twisting motion that pushed the left tip of the horizontal stabilizer rearward. An impact mark on the left outboard leading edge of the horizontal stabilizer was consistent with a soft bodied impact that occurred prior to ground impact. Although one witness reported seeing several birds flying in the area at the time of the accident, examination of the left horizontal stabilizer and elevator failed to find any evidence of blood, feathers, or bird remains. A detailed and comprehensive examination of the accident site area failed to reveal any evidence of a bird carcass, or bird feathers. Aircraft components composed of both aluminum and fiberglass were mounted forward of the empennage, however the impact mark showed no residual evidence of being struck by either material. A determination of the source of the soft bodied impact could not be made. The vertical stabilizer is attached to the horizontal stabilizer, and this assembly is then attached to the fuselage through four attach points. The damage to the vertical stabilizer attach points indicates that they failed toward the left (as viewed from the rear looking forward) and were securely attached to the horizontal stabilizer at the time of failure. Three of the four bolts that attach the horizontal stabilizer to the fuselage were recovered. The forward two attach points were torn out of the horizontal stabilizer during the in-flight separation. Compression damage to the lower skin immediately forward of the aft, left attach point indicates that it was securely attached. No evidence was found to indicate that any of the attach points were unsecured prior to the accident.
Probable cause
in-flight separation of the empennage for undetermined reasons.
"THIS CASE WAS MODIFIED AUGUST 2, 2006."
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC98FA073
- Event ID
- 20001211X09759
- Case number
- NYC98FA073
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ed6ad28798409e028848c21605c25896a99eb5e321c182822fcbbf6a87019b5f; retrieved 2026-09-20T22:40:01.166Z.