ERA10GA320 · Cessna T210L
U.S. Department of Agriculture Forest Service Cessna T210L · Accident: loss of engine power (total) on approach
From AQX · Clarion, PA to William T. Piper Memorial Airport (LHV)
Event
- NTSB case
- ERA10GA320
- 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
- 3 · 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
- Government
- 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
Cessna T210L
- Aircraft type
- Cessna 210
- 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
- N30266
- Onboard fatalities
- Unknown
- Route
- From AQX · Clarion, PATo William T. Piper Memorial Airport (LHV), Lock Haven, PA
- 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
- Public Aircraft
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aerial observation flight was conducted by a 14 CFR Part 135 certificated on-demand air carrier under contract to the U.S. Forest Service. As the flight neared its destination airport, the pilot reported via the airport's common traffic advisory frequency his intent to land. Witnesses reported that, as the airplane overflew them on approach to the airport, it appeared to be in distress, trailing black smoke with the engine "sputtering." The airplane subsequently impacted a light stanchion about 1,300 feet short of the intended landing runway. Before coming to rest, the airplane struck a house and several parked cars, and it was nearly consumed during a post-impact fire. Postaccident examination revealed a catastrophic failure of the airplane's engine, which originated with a fatigue failure of the number 2 cylinder exhaust valve. The fatigue failure was likely due to abnormal loading associated with excessive valve-to-valve guide clearance resulting from valve guide wear. Typically, valve guide wear results from either overall elevated engine operating temperatures or individually elevated valve temperatures due to improper valve seating. The normal wear pattern observed on the number 2 exhaust valve seat suggested that improper valve seating was not an issue in this case.
Significant exhaust valve guide wear was observed on all cylinders, with the valve guides of the generally cooler cylinders near the front of the engine showing less wear than those of the generally hotter cylinders near the rear of the engine. This overall pattern suggested a persistent elevated temperature problem, which could have resulted from either improper engine operation or an undiagnosed maintenance issue.
The investigation revealed that, when performing engine cylinder differential pressure tests during required routine inspections of the airplane’s engine, the contract operator utilized gauges that had not been calibrated since their purchase and did not perform the tests in accordance with the engine manufacturer's recommendations. Also, the engine manufacturer recommended that cylinder borescope inspections be accomplished in conjunction with the differential pressure tests, and there were no notations in the engine maintenance records of any visual borescope inspections of the interior of the cylinders. Further, there was no notation in the records that the fuel injection system had been inspected and adjusted per the engine manufacturer’s recommendations. If properly performed, differential pressure tests and borescope inspections may have detected valve guide wear and prevented the exhaust valve failure, and fuel injection system inspections may have detected and corrected incorrect adjustment of the engine fuel system, which can result in elevated engine cylinder temperatures and lead to valve guide wear. These and other instances of non-compliance with manufacturer service recommendations discovered during the investigation indicated that the contract operator was not maintaining the airplane in a manner consistent with its "Operator's Manual," which dictated that inspections of time-limited components were to be conducted in accordance with the applicable manufacturers' recommendations.
Probable cause
The total loss of engine power resulting from the fatigue failure of the engine's number 2 cylinder exhaust valve. The fatigue failure was due to valve guide wear that led to excessive clearance between the valve and valve guide. Contributing to the accident was the contract operator’s lack of compliance with its own maintenance procedures, which, if followed, would have prevented the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10GA320
- Event ID
- 20100621X53342
- Case number
- ERA10GA320
- 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: 6b3654627c4d5617f467a9439ddda88b642ea7bd342d31cd3de84f72e33fc428; retrieved 2026-09-13T20:53:53.271Z.