NYC08LA086 · Piper PA-28-R200
Rock Hill Aviation Piper PA-28-R200 · Accident: powerplant system/component malfunction/failure en route
From Rock Hill - York County Airport (UZA) to Asheville Regional Airport (AVL)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC08LA086
- 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
- Unknown
- 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-28-R200
- Aircraft type
- Piper PA-28
- 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
- N1939T
- Operator
- Rock Hill Aviation
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Rock Hill - York County Airport (UZA), Rock Hill, SCTo Asheville Regional Airport (AVL), Ashville, NC
- 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 · climb to cruise
- Defining eventThe 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
- Powerplant system/component malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Shortly after departure, while climbing through 4,000 feet, the airplane experienced a "sudden and violent shuddering," followed by smoke penetration into the cockpit. The pilot performed a forced landing to a field, during which the airplane was substantially damaged. Examination of the engine revealed the number two cylinder had separated from the engine crankcase and the through-bolts that attached the cylinder to the crankcase were fractured due to fatigue. Evidence of welding in the cylinder deck area of the crankcase was observed, which produced a soft condition in the cylinder mounting flanges and subsequent non-standard loading and fatigue fracture of the studs. The engine manufacturer does not allow welding in the critical cylinder deck area of the crankcase. According to the engine maintenance records, the engine was overhauled 2 years prior to the accident and had accumulated 679 hours since then.
Probable cause
Loss of engine power due to improper welding of the crankcase, which resulted in fatigue failure of the through-studs and a subsequent separation of the number two cylinder. Contributing to the accident was the unsuitable terrain for a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08LA086
- Event ID
- 20080210X00161
- Case number
- NYC08LA086
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: cb8fcdf502bb6848156f6614502b94b54aacdcbb99849d6c536338719d149535; retrieved 2026-09-15T09:21:30.056Z.