ASN Wikibase Occurrence # 134849
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: | Saturday 20 August 2005 |
Time: | 14:20 |
Type: | Piper PA-18-105 |
Owner/operator: | Van Wagner Aerial Media LLC |
Registration: | N294T |
MSN: | 18-2408 |
Total airframe hrs: | 12589 hours |
Engine model: | Lycoming O-360-A1A |
Fatalities: | Fatalities: 0 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Palos Verdes, CA -
United States of America
|
Phase: | En route |
Nature: | Banner and glider towing |
Departure airport: | Long Beach Airport, CA (LGB/KLGB) |
Destination airport: | |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:During a banner towing flight over the ocean along the coast, the engine lost power and the airplane ditched in the water. While in cruise flight, the engine began to run rough and lose a significant amount of power. The pilot attempted corrective measures (applying and removing carburetor heat and releasing the banner), but the airplane continued to lose power. The engine was not producing enough power for continued flight and the pilot landed in the water short of the beach. When the airplane hit the water, it nosed over and came to rest inverted. Post accident examination revealed that the number 4 piston had fractured around the circumference of the piston just above the connecting rod pin and had beach mark signatures consistent with cyclic fatigue. Fractured pieces of the piston were found in the oil sump. The aft piston pin end cap was worn and burnished. The forward piston pin end cap separated from the piston pin, with fracture surface signatures consistent with overload. The rod journal bearing was also worn and burnished. The number 4 connecting rod journal of the crankshaft was cracked and the connecting rod cheek on the crankshaft was fractured perpendicular to the rod journal. The journal cheek fracture exhibited beach marks consistent with cyclic fatigue. The fracture had an irregular shape that provided a "key" that maintained rotational continuity of the crankshaft during operation; however, the fracture also allowed the crankshaft to flex. Flexing of the crankshaft induced a rotational misalignment of the connecting rod, which in turn induced the cyclic fatigue failure of the piston. This condition was likely on-going for some time prior to the final fatigue failure. Copious amounts of small metal debris and flakes were retrieved from the oil pressure filter screen that were consistent with the rod end cap bearing material and should have been apparent if the screen and filter were being checked for contaminants on a regular basis. Lycoming Mandatory Service Bulletin (SB) No. 480E recommends an oil change, pressure screen cleaning and oil sump screen check at 25-hour intervals. The SB continues that observation of abnormal metal content during the service may indicate additional service is required. Examination of maintenance records revealed that it had been 112 hours since the last 100-hour inspection at the time of the accident. The aircraft and engine logbooks contained no record of the operator following the recommended procedures as set forth in SB 480E.
Probable Cause: a loss of engine power due to the cyclic fatigue failure and separation of the number 4 piston.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | LAX05LA273 |
Status: | Investigation completed |
Duration: | |
Download report: | Final report |
|
Sources:
NTSB:
https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20050901X01370&key=1
History of this aircraft
Other occurrences involving this aircraft Location
Revision history:
Date/time | Contributor | Updates |
21-Dec-2016 19:26 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
06-Dec-2017 10:51 |
ASN Update Bot |
Updated [Operator, Other fatalities, Departure airport, Source, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation