# NTSB CEN10LA494: Cessna 310F, N6762X, LaGrange, IN, August 19, 2010

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: August 19, 2010, 11:30 local (15:30 UTC)
- Place: LaGrange, IN
- Coordinates: 41.641175, -85.41547 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=41.6412&lon=-85.4155&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Defining event: [Enroute-cruise: Miscellaneous/other](https://openairdocs.org/ntsb-events/900)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report May 3, 2012
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: Federal Aviation Administration, Teledyne Continental Motors
- NTSB case key (mKey): 77061
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN10LA494
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77061/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77061
- Page: https://openairdocs.org/ntsb/CEN10LA494

## Probable cause

The pilot did not maintain altitude due to his distracted attention to a vibration of unknown origin.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Action: incorrect action selection](https://openairdocs.org/ntsb-findings/02041010): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 310F, 1 case](https://openairdocs.org/ntsb-findings/02041010/cases.md?model=2074216), [All aircraft, 397 cases](https://openairdocs.org/ntsb-findings/02041010/cases.md)
- [Performance/control parameters: climb rate](https://openairdocs.org/ntsb-findings/01062035): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 310F, 1 case](https://openairdocs.org/ntsb-findings/01062035/cases.md?model=2074216), [All aircraft, 265 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md)
- [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Cessna 310F, 1 case](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=2074216), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Enroute-cruise: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) (defining event); cases with it: [Cessna 310F, 1 case](https://openairdocs.org/ntsb-events/900/sequence.md?model=2074216), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Enroute-descent: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 310F, 1 case](https://openairdocs.org/ntsb-events/060/sequence.md?model=2074216), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md)
- [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 310F, 1 case](https://openairdocs.org/ntsb-events/440/sequence.md?model=2074216), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md)
- [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 310F, 2 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2074216), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot stated that, during cruise flight, he noticed a sudden airplane vibration, decreased controllability, and a loss of altitude. He initially thought that the vibration was coming from the empennage but later thought it was from the left engine. He stated that the engine instrument indications for both engines were normal. He elected to shut down the left engine, but the vibration and altitude loss continued. The pilot performed an off-airport landing to a pasture, and the airplane collided with obstacles. During postaccident examination, no airframe anomalies that would have induced a vibration were noted. Testing of the right engine did not reveal any anomalies that would have induced a vibration or precluded normal operation. The airplane owner's manual performance information indicated that the airplane was capable of climbing at a rate of about 500 feet per minute with one engine inoperative at the conditions that were present at the time of the accident. Given that no anomalies were found with the airframe or the right engine and that the airplane had climb performance capability even with one engine inoperative, it is likely that the pilot was distracted by the vibration and did not maintain altitude.

## Factual narrative

On August 19, 2010, at 1130 eastern daylight time, a Cessna 310F, N6762X, received substantial damage on impact with terrain during a forced landing to a pasture near LaGrange, Indiana. Visual meteorological conditions prevailed at the time of the accident. The 14 CFR Part 91 personal flight was not operating on a flight plan. The pilot and passenger were uninjured. A horse was injured when it was struck by the airplane and later euthanized. The flight originated from Wauseon, Ohio, at 1100 and was en route to Wahpeton, North Dakota. The airplane was in cruise flight at 3,500 feet above mean sea level (MSL)(LaGrange, Indiana, is about 932 feet MSL) and at an airspeed of 155 knots when the pilot reportedly noticed a sudden vibration, decreased controllability, and a loss of altitude. Both sets of engine instruments indicated normal manifold pressure, engine speed, and temperature. The pilot also heard a repetitive loud beeping, which he thought was either a stall or gear warning. The pilot thought that the vibration was from the left engine/propeller so he decided to shut down the left engine and feather the left propeller. He advanced the right engine to full power but did not notice a change in the vibration. The pilot stated the airplane continued to lose altitude while at the airplane's single-engine best rate of climb speed. The pilot then performed a forced landing to a pasture where the airplane struck a wire fence and a horse. A post crash fire ensued. The horse was later euthanized due to its injuries. According to the on-scene Federal Aviation Administration inspector, the pilot initially stated that the vibration was emanating from the tail. There were no ground scars in the pasture consistent with the landing gear being extended but only of the fuselage. The landing gear handle was in the up or retracted position. The flaps were extended. The inspector's examination of the airplane noted that all of the control surfaces were attached and there was no evidence of repetitive contact of the control surfaces to any of the adjacent surfaces. The control surfaces were attached and control continuity from the control surfaces to the cockpit controls was confirmed. The fuel selector was positioned to the right fuel tank. The left fuel tank contained fuel. The right propeller blades exhibited S-shaped bending and twisting consistent with engine power, and the left propeller blades were relatively straight. The airplane sustained substantial damage, which included a left wing separation and a buckled empennage. Examination of the airplane revealed no anomalies that would have induced an aircraft vibration. The right engine was a Continental Motors IO-470-D, serial number CS105283-D-R. The engine's last major overhaul was dated March 26, 1998, at a Hobbs time of 1,504.1 hours. The engine underwent its last inspection during a 100-hour inspection dated April 8, 2010, at an airplane total time of 2,153 hours, an engine total time of 5,519.8 hours,and a time since major overhaul of 648.9 hours. The right engine was removed from the airplane and shipped to Teledyne Continental Motors, Mobile, Alabama, where it underwent an engine run under the supervision of the National Transportation Safety Board Investigator-in-Charge for the accident investigation. Prior to the engine run, the fuel control unit screen was removed and noted to contain contaminants that were consistent with cloth/fabric fibers. The fuel servo screen was reinstalled without removal of the fuel control unit screen contaminants. A test club propeller was installed onto the engine for the test. During the test, the engine throttle was set to the following speeds for 5-minute intervals: 1,260 rpm, 1,630 rpm, 2,100 rpm, and 2,450 rpm. The throttle was then advanced to the full open position for 5 minutes and advanced 6 times from idle to full throttle. No interruption or hesitation in power was noted. The pilot reported that the airplane weight at the time of the accident was 4,000 pounds. The Kirsch Municipal Airport (IRS) Sturgis, Michigan, automated weather observing system, located about 12 miles north of the accident site and at an elevation of about 924 feet MSL, recorded: temperature - 81 degrees Fahrenheit(F) and an altimeter setting - 29.98 inches of mercury. The Cessna 310F Owner's Manual provides the following climb data based upon the flaps and landing gear retracted, the inoperative propeller feathered, wing banked 5 degrees toward the operating engine, full throttle, propeller speed at 2,625 rpm, and the mixture leaned at the recommended leaning schedule. The rate of climb is to be decreased 10 feet/minute for each 10 degrees F above standard temperature for the particular altitude. At a gross weight of 4,000 pounds, at 2,500 feet and 50 degrees F, the rate of climb is 545 feet at a best climb speed of 106 knots indicated airspeed.

## Aircraft

- Registration: [N6762X](https://openairdocs.org/deregistered/N6762X-2010-09-21), registration cancelled 2010-09-21, S/N 310-0062, built 1961 (OpenAirDocs)
- Reported make and model: CESSNA 310F
- Registry model: [Cessna 310F](https://openairdocs.org/model/cessna-310f) (registry code 2074216) (OpenAirDocs)
- Registry engine: [Continental I0-470 series](https://openairdocs.org/engine/continental-i0-470-series) (registry code 17027, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 310F-0062
- Airframe hours: 5500
- Engines: Continental IO-470 260 horsepower reciprocating
- Damage: Substantial damage
- Fire: On-Ground
- Flight: Personal, Part 91
- Operator: Pilot
- Registered owner: Pilot
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, April 1, 2010
- Departed: USE, Wauseon, OH
- Destination: BWP, Wahpeton, ND

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 53; injuries: none; private; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; seat: left; flight hours: 1,600 total, 300 in this make and model, 1,500 as pilot in command

## Weather

- Conditions: Visual (VMC), Day
- Wind: 230° at 8 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 81 °F, dew point 64 °F
- Altimeter: 29.97 inHg
- Observed at: IRS, 20 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20100819046459A](https://openairdocs.org/incident/20100819046459A), Aug 19, 2010: Cessna 310F, Lagrange, IN, Destroyed. Pilot stated that during cruse flight at 3500 feet aircraft began to vibrate / shutter and he could not maintain altitude. Pilot felt that the vibration…

## Docket (5 files)

The files NTSB released with the investigation on March 30, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77061. 1.3 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 509 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40364716&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Record of Conversation - FAA (item 2, .PDF, 79 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40364775&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20FAA-Master.PDF
- Weather Reports and Records - KIRS AWOS (item 3, .PDF, 100 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40364741&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records%20-%20KIRS%20AWOS-Master.PDF
- Maintenance Records - Excerpt (item 4, .PDF, 553 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40364732&FileExtension=.PDF&FileName=Maintenance%20Records%20-%20Excerpt-Redacted.PDF
- Statement of Party Representatives to NTSB Investigation (item 5, .PDF, 90 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40364734&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
