NYC97FA013 · Piper PA-34-200T
Piper PA-34-200T · Accident: airframe, component or system failure en route
From Boston Logan International Airport (BOS) to North Central West Virginia Airport (CKB)
Event
- NTSB case
- NYC97FA013
- 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-34-200T
- Aircraft type
- Piper PA-34
- 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
- N5671V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boston Logan International Airport (BOS), Boston, MATo North Central West Virginia Airport (CKB), Clarksburg, WV
- 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
- Fuselage, cargo compartment › Undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was 90 minutes into the flight, level at 10,000 feet mean sea level, on a southwest heading, when air traffic control lost radio and radar contact with the flight. ATC observed primary radar targets only continue in a northerly direction, followed by a northeasterly direction. The cockpit, right wing and engine were found impaled on a tree near the point where radar contact was lost. The left wing and engine were within 200 feet east of the right wing. Debris was scattered northeast of the main wreckage for about 10,500 feet. Examination of the wreckage revealed that the fiberglass nose assembly had failed due to an undetermined reason. Airworthiness directives had been complied with that applied to the forward baggage compartment door.
Probable cause
The failure of the forward fuselage nose assembly for an undetermined reason, which resulted in an in-flight breakup of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97FA013
- Event ID
- 20001208X07101
- Case number
- NYC97FA013
- 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: 5c9ebe3ea44e483903220ad173f96addc51a5758b8b201ac53eed341c9e8eb15; retrieved 2026-09-20T23:08:12.326Z.