10 Nov 2017: SOCATA TB200 XL — 1World Aero, LLC

10 Nov 2017: SOCATA TB200 XL (N207GT) — 1World Aero, LLC

No fatalities • Annapolis, MD, United States

Probable cause

A loss of engine power for undetermined reasons after the disconnection of the propeller governor control due to inadequate securenment during maintenance.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn November 10, 2017, about 1520 eastern standard time, a Socata TB200, N207GT, operated by Tipton Tampico LLC, was substantially damaged during a forced landing near Annapolis, Maryland. The commercial pilot and the two passengers were not injured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the flight that departed Tipton Airport (FME), Fort Meade, Maryland, about 1430.

The pilot was conducting a sightseeing flight with his two children around the eastern shore of Maryland. About 45 minutes after departure, the airplane was at an altitude of 1,500 ft and about 25 miles southeast of FME, when the pilot felt a very light and subtle vibration from the engine. Shortly thereafter, the propeller rpm increased to 2,700 rpm uncommanded and remained "pegged at the redline."

The pilot followed the emergency checklist and reduced engine power to remain below redline rpm, but it had little effect. The airplane was 11 miles southeast of FME when the engine vibration increased, and the cockpit started filling-up with smoke, so he diverted to Lee Airport (ANP) Annapolis, Maryland. The pilot reported that the engine gauges were all "indicating green" during this time, but once the situation started deteriorating rapidly, he focused on flying the airplane and did not recall reading the gauges again.

Immediately after turning south towards ANP at around 1,400 feet, the engine experienced a total loss of power. The pilot realized that the airplane would not be able reach the airport and he made a forced landing on a road.

The airplane struck a light pole, spun around, and impacted a guardrail before coming to rest. The impact sheared off the left wing and the horizontal stabilator. The engine remained attached to the fuselage but separated from the top engine mounts and came to rest in a vertical, nose down position.

A postaccident examination of the engine revealed the propeller governor linkage was not connected to the propeller governor. The bolt and cotter key that is needed to secure the linkage to the propeller governor was missing. Further examination of the engine revealed that the fuel filter contained some debris, but it was not obstructed. No other mechanical deficiencies were found with the fuel system or engine that would have precluded normal operation of the engine.

A review of the engine's maintenance logbook revealed that five months before the accident, on June 24, 2017, the propeller assembly was removed and reinstalled for a starter ring gear, alternator belt and crankshaft seal replacement.

The engine's last annual inspection was conducted on October 24, 2017, at a total time of 1,496.53 hours. During that inspection, no anomalies were identified and logged. The airplane and engine then accrued about 13 hours since the annual inspection at the time of the accident.

The pilot held a commercial pilot certificate with ratings for airplane single-engine land instrument airplane and powered lift, instrument airplane. His most recent Federal Aviation Administration (FAA) second-class medical certificate was issued on June 13, 2017. The pilot reported 730 total hours of flight experience, with 13 hours in the accident airplane make and model.

The weather conditions reported at FME, 12-miles northeast of the accident site, at 1524, included wind from 350° at 12 knots gusting to 17 knots, visibility 10 miles, clear skies, temperature 3° C, dew point -9° C, and an altimeter setting of 30.38 inches of mercury.

Contributing factors

  • Not serviced/maintained

Conditions

Weather
VMC, wind 350/12kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.