ERA17LA246 · Costruzioni Aeronautiche Tecna P92 Eaglet
Costruzioni Aeronautiche Tecna P92 Eaglet · Accident: loss of engine power (total) on approach
From Shoestring Aviation Airfield (0P2) to Bay Bridge Airport (W29)
Event
- NTSB case
- ERA17LA246
- 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
- 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
Costruzioni Aeronautiche Tecna P92 Eaglet
- Aircraft type
- Tecnam P92
- 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
- N561TU
- Operator
- Chesapeake Sport Pilot
- Onboard fatalities
- Unknown
- Route
- From Shoestring Aviation Airfield (0P2), Stewartstown, PATo Bay Bridge Airport (W29), Stevensville, MD
- Aircraft age
- Built the same year (2017)
- 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
- Approach · VFR pattern final
- 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
- Loss of engine power (total)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
**This report was modified on December 4, 2022. Please see the public docket for this accident to view the original report.** While in the airport traffic pattern for landing at the conclusion of a cross-country flight, the airplane experienced a total loss of engine power, and the pilot performed a forced landing during which the airplane sustained substantial damage. The airplane had recently been purchased and the Rotax 912 ULS engine had 13.2 hours total operating time. Review of onboard data indicated that the fuel pressure, cylinder head temperature, and oil temperature remained relatively steady until the loss of power occurred, which indicated that the engine failure likely did not involve the fuel system, cooling system, or lubrication system. Examination of the engine revealed that there was no oil in the oil line between the oil thermostat and oil pump. The oil pump drive pin also displayed excessive wear in relation to the operating hours of the engine, and the magnetic plug was covered in metallic particles, although the oil filter was clean. Further examination of the engine revealed that the No. 1 cylinder was substantially damaged, and evidence of bluing was present. The cylinder’s exhaust valve spring retainer was fractured in half, and one half of the cotter was fractured. A small ridge could be felt on the exhaust valve spring retainer and galling (a rough surface) was visible on the exhaust valve bore in the cylinder head. The hydraulic lifter for the exhaust valve displayed a small indentation on the edge of the lifter, and when the hydraulic lifters were manually depressed, the lifter for the exhaust valve was easier to depress than the lifter for the intake valve. The pushrod for the exhaust valve was straight, but displayed a ridge on the rocker arm side of the pushrod, and the rocker arm displayed impact damage on the valve connection face. The exhaust valve was found in the combustion chamber. It was chipped, and bent, and deformed into an “S” shape. A hole was visible in the piston as the result of the piston face striking the exhaust valve after it dropped into the cylinder.
A small amount of oil captured from the hydraulic tappets indicated that the oil contained significantly elevated levels of nickel, which could have come from manganese-containing alloys, as they occur in high-alloy hardened steels, e.g. for camshafts, valves or valve shafts. Examination of the fractured surface on the exhaust valve spring retainer revealed the presence of fatigue with pronounced vibration stripes when viewed with an electron microscope; however, the heat treatment corresponded to the target specifications, as did the statistical process control value. Between 2 and 3 years after this accident, four more cases of broken valve spring retainers on Rotax 900 engine series occurred in the United States. All the engines had differing hours of operation. Extensive metallurgical examination of the engine components from these four engines revealed that they met their specifications, and the fractured surfaces on the valve spring retainers revealed the presence of fatigue with pronounced vibration stripes, which was the same pattern that was observed on the valve spring retainer from this accident. Review of the engine manufacturer’s published guidance revealed that air could be introduced into the oil lubrication system through several means, including exceedance of the maximum bank angle of 40°, poorly or insufficiently vented hydraulic valve tappets, lack of proper oil system purging, spinning the propeller in the reverse direction from normal rotation, or opening portions of the oil system during maintenance or servicing. Testing of an exemplar engine with air introduced into the lubrication system revealed that with air trapped in the hydraulic tappets, it took about 6.5 minutes of engine operation at 2,538 rpm for air to be purged from the tappets, allowing them to work as designed. This indicated that with air trapped in the hydraulic tappets, the valve train could be overloaded, which could lead to a fatigue crack and breakage of a valve spring retainer; this was likely the reason for the fatigue cracking of the valve spring retainers in this accident and in the other four failures identified.
Probable cause
The fatigue failure of an exhaust valve spring retainer due to air trapped in the lubrication system, which resulted in a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17LA246
- Event ID
- 20170716X40924
- Case number
- ERA17LA246
- 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. 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: f5daf933ba845b493402abd345db881dee17f7684fde00e3f40fee0c7a283017; retrieved 2026-09-16T05:32:53.627Z.