# NTSB ERA16LA251: Tumbling Goose 12S, N867TG, Zellwood, FL, July 11, 2016 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: July 11, 2016, 12:50 local (16:50 UTC) - Place: Zellwood, FL - Coordinates: 28.760278, -81.605834 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=28.7603&lon=-81.6058&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report December 14, 2017 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 93588 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA16LA251 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93588/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93588 - Page: https://openairdocs.org/ntsb/ERA16LA251 ## Probable cause A total loss of engine power during descent for reasons that could not be determined because impact damage precluded a complete examination of the fuel servo. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: lateral/bank control](https://openairdocs.org/ntsb-findings/01062023): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Tumbling Goose 12S, 1 case](https://openairdocs.org/ntsb-findings/01062023/cases.md?model=05634EP), [All aircraft, 390 cases](https://openairdocs.org/ntsb-findings/01062023/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Tumbling Goose 12S, 1 case](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=05634EP), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Tumbling Goose 12S, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=05634EP), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Tumbling Goose 12S, 1 case](https://openairdocs.org/ntsb-events/341/sequence.md?model=05634EP), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Tumbling Goose 12S, 1 case](https://openairdocs.org/ntsb-events/380/sequence.md?model=05634EP), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) ## Analysis The private pilot reported that this was his second flight in his newly manufactured, experimental exhibition airplane. Earlier in the morning, the pilot flew the airplane for 30 minutes over the airport to become familiar with the airplane and noted no anomalies. Several hours later, the pilot departed again to perform aerobatics. While returning to the airport, he reduced power to descend, and once the airplane was at the desired altitude, he advanced the throttle, but the engine did not respond. He then looked at the engine monitor and noted that the engine had lost total power. The pilot noticed a positive indication of fuel pressure, and he used the primer switch, which bypassed the fuel servo, to restart the engine. Once he released the switch, the engine again lost power. The pilot added that, when the airplane was over the airport, he set up for landing, but he believed that the airplane was going too fast to land, so he used the primer switch to develop engine power and perform a go-around maneuver. During the next approach, the pilot slowed the airplane, and once over the runway, he flared for landing. The airplane continued to fly about 10 ft above ground level (agl) down the length of the runway. The pilot tried using the primer switch again to perform another go-around maneuver, but about 200 ft agl, the engine lost total power. He then tried to perform a forced landing to a clearing but impacted trees and terrain before the clearing. Postaccident examination of the engine confirmed engine control and fuel system continuity up to the fuel servo. The fuel servo could not be tested due to impact damage; therefore, the cause of the loss of engine power could not be determined. ## Factual narrative On July 11, 2016, about 1250 eastern daylight time, an experimental exhibition Tumbling Goose LLC, 12S, N867TG, was substantially damaged during a forced landing following a loss of engine power while approaching Tangerine Airport (FL97), Zellwood, Florida. The pilot incurred serious injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal, local flight. The airplane was operated under the provisions of 14 Code of Federal Regulations Part 91.According to the pilot, this was his second flight in the newly manufactured experimental exhibition airplane. His first flight was earlier that morning, and he flew for approximately 30 minutes over the airport to get familiar with the new airplane. The flight was uneventful and he made two practice approaches before landing and debriefing with the airplane builders on the handling characteristics of the airplane. Several hours later, the pilot departed again to perform aerobatics in the airplane with a sufficient amount of fuel for the planned flight. About 1 hour into the flight, while flying at 4,000 feet above ground level (agl), the pilot reduced the engine power in order to descend towards the airport for landing. At 2,000 feet agl, the pilot advanced the throttle with no response from the engine. He looked at the engine monitor and discerned that the engine had lost total power, though the propeller continued to rotate. The pilot turned the fuel boost pump on and noticed positive fuel pressure, and he moved the mixture and throttle controls with no effect on the engine. The pilot then toggled the spring loaded fuel primer switch, the engine restarted, and appeared to go to full power. Once the pilot released the fuel primer switch, the engine again ceased producing power. The airplane was now over the airport, so the pilot set up for a landing on the grass runway. The pilot noticed he was still high and flying "very fast" for landing, so he performed a go-around maneuver by using the primer switch to start the engine and fly around the traffic pattern to set up for another landing. On the next landing approach, the pilot slowed the airplane, and once over the runway, he attempted to flare for landing. The airplane continued to fly about 10 feet agl for the length of the runway. The pilot tried to perform another go-around by toggling the fuel primer switch again. The engine restarted, but lost total power shortly after and did not restart. At the time, the airplane was about 200 feet agl. The pilot then attempted to perform a forced landing to a clearing. The airplane was "too low and slow," and impacted trees and terrain prior to the clearing. According to the Federal Aviation Administration (FAA) the single seat, bi-wing, fixed landing gear, experimental airplane, serial number 353, was manufactured in 2016. It was powered by a Barrett Performance, Vedeneyev M14P, 430 horsepower engine, equipped with a 3-blade MT propeller. The airplane's mostrecent100-hour inspection was completed on March 16, 2016, and it had accumulated 7 hours of total hours of flight time since that date. The airplane was equipped with an engine primer system for starting purposes, which injected an unregulated fuel supply directly from the fuel boost pump into the supercharger, which bypassed the fuel/air servo controller. Examination of the wreckage by the Federal Aviation Administration inspector revealed that it came to rest upright with the nose and engine buried in the ground. Both wings were substantially damaged, and the tail section fractured just behind the pilot's seat. The fuselage was crushed by the impact with the tree. The engine controls all appeared to be intact from the cockpit to the engine. The fuel system was clear of blockages up to the fuel servo. Operation of the fuel servo could not be confirmed due to impact damage. The induction system was free of blockages. The original ignition system had been replaced after the engine's most recent overhaul with an experimental electronic system, and the original carburetor was replaced with an experimental fuel injection system, also after the last overhaul. ## Aircraft - Registration: [N867TG](https://openairdocs.org/deregistered/N867TG-2018-05-24), registration cancelled 2018-05-24, S/N 353, built 2016 (OpenAirDocs) - Reported make and model: TUMBLING GOOSE LLC 12S - Registry model: [Tumbling Goose 12S](https://openairdocs.org/model/tumbling-goose-12s) (registry code 05634EP) (OpenAirDocs) - Registry engine: [Vedeneyev M14P](https://openairdocs.org/engine/vedeneyev-m14p) (registry code 63601, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 353 - Year built: 2016 - Airframe hours: 7 - Engines: Barrett Performance Engine Vedeneyev M14 430 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: 100 hour, March 16, 2016, 7 hours before - Departed: FL97, Zellwood, FL - Destination: FL97, Zellwood, FL - Airport: FL97, Tangerine, runway 09, 2,600 × 100 ft, grass/turf - Equipment: Electronic multifunction display, Data recorder, Auto-pilot, ADS-B, Onboard weather, Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review July 4, 2014; seat: single; restraint: 5-point; flight hours: 1,486 total, 3 in this make and model, 1,445 as pilot in command, 40 in the last 90 days, 22 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 93 °F, dew point 72 °F - Altimeter: 30.13 inHg - Observed at: LEE, 11 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 20160711012009A](https://openairdocs.org/incident/20160711012009A), Jul 11, 2016: Tumbling Goose LLC 12S, Zellwood, FL, Destroyed. Interview date: July 13, 2016 Interview location: (FL97) Tangerine Airport Zellwood FL Pilot name: [privacy data omitted] Pilot certificate type/no: [privacy… ## Docket (5 files) The files NTSB released with the investigation on October 19, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93588. 6.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40457142&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - FAA Inspector's Statement (item 2, .PDF, 26 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40457143&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.PDF - FAA Inspector Statement - Engine Examination (item 3, .PDF, 26 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40457144&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement%20-%20Engine%20Examination-Master.PDF - Memorandum for Record - Telephone Interview, Pilot (item 4, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40457145&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Telephone%20Interview,%20Pilot-Master.PDF - Photo Array (Courtesy of FAA) (item 5, .PDF, 3 photos, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40457146&FileExtension=.PDF&FileName=Photo%20Array%20(Courtesy%20of%20FAA)-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.