# NTSB NYC01LA095: Cessna 150D, N974CA, Slanesville, WV, April 7, 2001 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: April 7, 2001, 14:40 local (18:40 UTC) - Place: Slanesville, WV - Coordinates: 39.375, -78.525001 - Nearby events: https://openairdocs.org/map.md?lat=39.3750&lon=-78.5250&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report August 21, 2001 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 52054 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC01LA095 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/52054/pdf - Page: https://openairdocs.org/ntsb/NYC01LA095 ## Probable cause a loose mixture control cable housing which resulted in an intermittent running engine, and the pilot's subsequent decision to perform a precautionary landing. A factor was the soft terrain. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(partial) - nonmechanical, cruise - normal - precautionary landing - performed, pilot in command - mixture control,cable - loose (cause) - Nose over, landing - roll - terrain condition - soft (contributing factor) ## Analysis The pilot purchased the airplane in Tulsa, Oklahoma, and was destined for Woodbine, New Jersey. On the second day of his trip, while in cruise flight over West Virginia, the engine momentarily lost power and then returned to cruise rpm. This intermittent condition continued and the pilot was unable to return the engine to normal operation. He elected to perform a precautionary landing in an open field below him. After main wheel touchdown, the nose wheel touched down, and dug into the soft ground. The airplane nosed over, and came to rest inverted. Examination revealed that the mixture control cable housing had come loose, which allowed it to move toward the idle cut-off position. The engine ran satisfactorily after the mixture control cable housing was properly secured. ## Factual narrative On April 7, 2001, about 1440 Eastern Daylight Time, a Cessna 150D, N974CA, was substantially damaged during a precautionary landing in Slanesville, West Virginia. The certificated private pilot received minor injuries. Visual meteorological conditions prevailed for the personal flight. No flight plan had been filed for the flight that was conducted under 14 CFR Part 91. The pilot reported that he had purchased the airplane, and taken delivery of it in Tulsa, Oklahoma, on April 6, 2001. He left Tulsa in the afternoon, destined for Woodbine, New Jersey. At his first fuel stop, he replaced the nose landing gear tire and bearings due to dry rot and a flat spot on the tire. He spent the night in Mount Vernon, Illinois. On April 7th, he resumed his eastward flight. After he departed Mt. Vernon, he made two additional stops to refuel during the day. His last refueling stop prior to the accident was Fairmont, West Virginia, which he departed from about 1400. The pilot said that he was in cruise flight at 5,500 feet, operating above some scattered clouds, with an outside air temperature of about 55 degrees Fahrenheit. He further stated: "...About 50 minutes into the flight I developed a sudden power reduction from 2500 to 1000 RPM for about 5 to 7 seconds then with no pilot input engine regained full power. I proceeded to check fuel selector, carb heat, mags, throttle and mixture positions...At no time did any of my inputs seem to effect to resolve the problem. The engine would at times run rough and then loose power regaining same at different intervals." The pilot reported that he checked his GPS for the closest airport, which he observed was 20 nautical miles away. Based upon the condition of the engine, and the distance to the nearest airport, he elected to perform a precautionary landing in a field below him. He positioned the airplane over the field, and set up for the landing. The pilot further stated: "...During my rapid descent the engine ran rough at times but settled during the base and final leg to the field. So as not to be high on short final I flew low and slow through a break in the tree line which bordered the field. Flaps were fully extended and I touched down at a relatively low speed. At 250 to 300 ft into the roll out the nose gear touched down and dug into the soft ground causing the plane to nose in and flip on its back. After the accident, the airplane was removed to a local airport for further examination. According to the report from the inspector with the Federal Aviation Administration (FAA), who conducted the examination: "The engine started immediately, but would not remain running. If the primer was repeatedly pushed, the engine would continue to run...." "The carburetor bowl was drained and some sediment was found in the fuel. Inspection of the carburetor revealed that the mixture control sheath had slipped out of the retaining clamp. When the mixture control was moved, the cable flexed but the mixture valve did not move. The mixture valve [was] in idle cut off all the time. The cable was reattached and the engine ran normally, reaching approximately 2,400 static rpm....The clamp system was metal to metal; The Cessna 150 Parts catalog shows that a rubber lined Adel type clamp is required. In a follow-up telephone interview, the FAA inspector reported that the contamination in the carburetor bowl was loose and in an area from where fuel was supplied to the main carburetor jet. However, no contamination was found in the main fuel strainer, and the source of the contamination in the carburetor bowl was not determined. There were no marks on the mixture control cable housing to indicate it was forced from the clamp. The looseness of the mixture control cable housing allowed the mixture control valve to move towards the idle cut-off position. The airplane had accumulated 38 hours since its last annual inspection on May 24, 2000. The pilot also reported that the airplane had not flown for period of time prior to him taking delivery of it. ## Aircraft - Registration: [N974CA](https://openairdocs.org/deregistered/N974CA-2007-06-21), registration cancelled 2007-06-21, S/N 15060194, built 1963 (OpenAirDocs) - Reported make and model: Cessna 150D - Registry model: [Cessna 150D](https://openairdocs.org/model/cessna-150d) (registry code 2071810) (OpenAirDocs) - Registry engine: [Continental 0-200 series](https://openairdocs.org/engine/continental-0-200-series) (registry code 17020, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 15060194 - Airframe hours: 3890.23 - Engines: Continental O-200A 100 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Utility - Last inspection: Annual, May 24, 2000, 37.59 hours before - Departed: 4G7, Fairmont, WV - Destination: FDK, Frederick, MD ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 45; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--no waivers/lim.; last flight review June 10, 2000; seat: left; flight hours: 700 total, 300 in this make and model, 650 as pilot in command, 25 in the last 90 days, 7 in the last 30 days, 5 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 110° at 10 knots - Visibility: 4 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 63 °F - Altimeter: 30.07 inHg - Observed at: OKV, 22 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 20010407039039A](https://openairdocs.org/incident/20010407039039A), Apr 7, 2001: Cessna 150D, Slanesville, WV, Substantial damage. (.4) The pilot purchased the airplane in tulsa, Oklahoma, and was destined for woodbine, new jersey. On the second day of his trip, while in cruise flight over… 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.