# NTSB ERA10LA349: Beech F33A, N350NW, Mooresville, NC, July 6, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 6, 2010, 18:30 local (22:30 UTC) - Place: Mooresville, NC - Coordinates: 35.608055, -80.892776 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.6081&lon=-80.8928&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern base: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 27, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 76535 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10LA349 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76535/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76535 - Page: https://openairdocs.org/ntsb/ERA10LA349 ## Probable cause A loss of engine power for undetermined reasons. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Beech F33A, 8 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=1151425), [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. - [Approach-VFR pattern base: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Beech F33A, 14 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=1151425), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Beech F33A, 8 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=1151425), [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: [Beech F33A, 21 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=1151425), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis Because the airplane had not flown for an extended period of time, the pilot elected to fly the airplane to his home in order to run the engine. During the preflight inspection, the pilot removed trace amounts of water and contaminants by draining fuel samples from the fuel tanks several times. The pilot subsequently departed and the flight proceeded uneventfully. Upon entering the traffic pattern at the destination airport, the pilot activated the fuel boost pump according to the airplane's before-landing checklist. Immediately after the fuel pump activated, the engine began to lose power, and after turning off the fuel boost pump the pilot attempted to restart the engine. The pilot subsequently performed a forced landing to a lake, resulting in substantial damage to the fuselage and left wing tip. Postaccident inspection revealed no evidence of any obvious mechanical deficiencies of the engine, though an attempted test run of the engine was unsuccessful. ## Factual narrative On July 6, 2010, about 1830 eastern daylight time, a Beech F33A, N350NW, was substantially damaged during a forced landing to a lake following a loss of engine power while in the traffic pattern at Lake Norman Airpark (14A), Mooresville, North Carolina. The certificated private pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight, which originated from Piedmont Triad International Airport (GSO), Greensboro, North Carolina, about 1800. The flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. During a telephone interview, the pilot stated that the airplane was being brokered for sale, and had not flown for an extended period. He elected to fly the airplane to his home located near 14A in order to "exercise" it. During the prefight inspection, the pilot noted that all of the fuel tanks contained fuel, and that he "sumped" the main fuel tanks several times to verify that the trace amount of water and contaminants, he observed in the first sample, were removed. The pilot attempted to start the engine but discovered the battery voltage was too low due to the airplane's extended period of inactivity. It was subsequently started with assistance from an external power supply. During the engine run-up, prior to takeoff, the pilot reported that there were indications of "fouled [spark] plugs which did clean up after [the] leaning procedures." He did not note any other abnormalities with the airplane before takeoff. After departing from GSO, the pilot climbed the airplane to the planned cruise altitude of 6,500 feet mean sea level. During the descent, the pilot reviewed the supplemental before landing checklist, and maneuvered the airplane to enter the traffic pattern. During the downwind to base turn, about 500 feet above ground level, the pilot began the final checklist for landing and activated the fuel boost pump. Immediately after the fuel pump activated, the engine began to "sputter" and lose power. The pilot quickly turned off the fuel boost pump and performed the emergency procedures checklist to restart the engine. He elected to land in Lake Norman and attempted to restart the engine several times before impacting the water. A Federal Aviation Administration (FAA) inspector examined the airplane after it was recovered from the lake. The airplane exhibited substantial damage along the right side of the fuselage and the left wing tip fuel tank. The fuselage was buckled aft of the right cabin door and the left wing fuel tip tank was dented along the aft outboard section of the tank. According to FAA records, the airplane was manufactured in 1977, and most recently registered to in 2003. It was equipped with a 350-horsepower, Lycoming TIO-540 series engine, which was installed under the provisions of a supplemental type certificate. It was a four-place, all-metal, low-wing, single-engine, monoplane with retractable tricycle landing gear. According to thepilot, the airplane had accumulated approximately 2,740 hours of total time in service as of last annual inspection, which was performed on November 17, 2009. The FAA inspector examined the engine in Clayton, Georgia on July 29, 2010. The engine crankshaft was rotated by hand at the propeller and continuity of the crankshaft and valvetrain to the accessory section of the engine was confirmed. Thumb compression was confirmed on all cylinders. The spark plugs were removed and exhibited normal wear. Examination of the magnetos revealed water in the housing, and rotation of the magneto failed to produce spark. The water was drained, but neither produced any spark. The turbo charger moved freely with no blockage or oil contamination noted. The inspector attempted to initiate a test run of the engine, but was unsuccessful. The pilot held a private pilot certificate with ratings for airplane single-engine land, multiengine land, and instrument airplane. His most recent FAA second class medical certificate was issued on May 26, 2009. The pilot reported 3,757 total hours of flight experience, of which, 25 hours were in the accident airplane make and model. The 1952 recorded weather at Statesville Regional Airport, located about 9 miles north of the accident location, included calm winds, scattered clouds at 9,000 feet, 10 miles visibility, temperature 31 degrees C, dewpoint 14 degrees C, and an altimeter setting of 30.10 inches of mercury. ## Aircraft - Registration: [N350NW](https://openairdocs.org/aircraft/N350NW), registered now, S/N CE-753, built 1977 (OpenAirDocs) - Reported make and model: BEECH F33A - Registry model: [Beech F33A](https://openairdocs.org/model/beech-f33a) (registry code 1151425) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: CE-753 - Airframe hours: 2740 - Engines: Lycoming TIO-540 350 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Utility - Last inspection: Annual, November 17, 2009 - Departed: GSO, Greensboro, NC - Destination: 14A, Mooresville, NC - Flight plan: Unknown - Airport: 14A, Lake Norman Airpark ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: none; private; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review August 5, 2009; seat: left; flight hours: 3,757 total, 25 in this make and model, 3,700 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 190° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 90 °F, dew point 55 °F - Altimeter: 30.10 inHg - Observed at: SVH, 9 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 20100706037379A](https://openairdocs.org/incident/20100706037379A), Jul 6, 2010: Beech F33A, Mooresville, NC, Minor damage. Aircraft enroute from gso (greensboro, NC) to 14A (Lake Norman air park). While attempting to land at 14A on base to final, pilot cut on placarded boost pump… ## Other investigations on N350NW (2) 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. - [NTSB CHI02LA071](https://openairdocs.org/ntsb/CHI02LA071), Jan 26, 2002: Beech F33A (N350NW), Bloomington, IN, substantial damage. Probable cause: The pilot's inadequate recovery from a bounced landing which resulted in a hard contact with the runway. Factors associated with the accident were the improper flare and the crosswind condition. - [NTSB CHI98LA276](https://openairdocs.org/ntsb/CHI98LA276), Jul 25, 1998: Beech F33A (N350NW), Delavan, WI, substantial damage. Probable cause: the pilot's failure to maintain aircraft control during the takeoff roll. Factors contributing to this accident were the pilot's inadequate preflight, his operation of an airplane with a known… ## Docket (6 files) The files NTSB released with the investigation on April 22, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76535. 902 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 461 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40345134&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Pilot Interview Summary (item 2, .PDF, 45 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40345135&FileExtension=.PDF&FileName=Pilot%20Interview%20Summary-Master.PDF - Memorandum of Record - FAA Inspector (item 3, .PDF, 83 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40346790&FileExtension=.PDF&FileName=Memorandum%20of%20Record%20-%20FAA%20Inspector-Master.PDF - Weather Reports: SVH METARs (item 4, .PDF, 39 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40345137&FileExtension=.PDF&FileName=Weather%20Reports%3A%20SVH%20METARs-Master.PDF - Airplane Checklist (item 5, .PDF, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40346795&FileExtension=.PDF&FileName=Airplane%20Checklist-Redacted.PDF - Accident Photographs (3) (item 6, .PDF, 3 photos, 206 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40345139&FileExtension=.PDF&FileName=Accident%20Photographs%20(3)-Master.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.