ASN Wikibase Occurrence # 96
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: | Wednesday 5 December 2007 |
| Time: | 18:55 |
| Type: |  Piper PA-28R-200 |
| Owner/operator: | Pheonix Air |
| Registration: | N43274 |
| MSN: | 28R-7435259 |
| Year of manufacture: | 1974 |
| Total airframe hrs: | 2704 hours |
| Engine model: | Lycoming IO-360 |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Augusta, GA -
 United States of America
|
| Phase: | Unknown |
| Nature: | Executive |
| Departure airport: | Charleston, SC (CHS) |
| Cartersville, GA (VPC) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
While enroute to the destination airport, the pilot reported to air traffic control that he had a "rough running engine,"and asked where the nearest airport was. He was given vectors for an airport and subsequently reported that the airplane's engine lost power and that he would attempt to land on a road. The airplane touched down in a parking lot and continued to travel for about 50 feet, until it impacted a building and caught fire. A witness reported that the engine sounded as if "all the cylinders weren't firing." Examination of the engine revealed that the number 2 cylinder was displaced from the crankcase and the associated connecting rod was separated from the crankshaft. Examination of the studs used to attach the cylinder to the crankcase revealed that they were fractured due to fatigue. Additionally, continued operation of the engine after the separation of the cylinder fractured the associated connecting rod to produce mechanical damage inside of the crankcase. According to maintenance records, 22 months prior to the accident the engine case was repaired when a crack was noted. The engine was reinstalled and the airplane returned to service two months later, at 977 hours since major overhaul. The most recent 100-hour inspection was performed one month prior to the accident with no anomalies noted. At that time, the engine had accumulated 1409 hours since major overhaul. The investigator could not determine if a specific maintenance action initiated and allowed the fatigue crack.
Probable Cause: A loss of engine power due to the fatigue fracture of the number 2 cylinder attach studs, and the subsequent separation of the number 2 cylinder.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20071227X01997&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 20-Jan-2008 12:55 | JINX | Added |
| 21-Dec-2016 19:12 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:13 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:14 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:16 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:20 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 04-Dec-2017 19:04 | ASN Update Bot | Updated [Cn, Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation