# NTSB ERA19LA232: Vans RV7, N849GS, Ocean City, MD, July 19, 2019

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Class 3 · Limited · Final report
- Date: July 19, 2019, 12:10 local (16:10 UTC)
- Place: Ocean City, MD
- Coordinates: 38.314445, -75.127777 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=38.3144&lon=-75.1278&mi=10
- Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping)
- Defining event: [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342)
- Highest injury: Minor injuries
- Injuries: 1 minor
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 99901
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA19LA232
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99901/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99901
- Page: https://openairdocs.org/ntsb/ERA19LA232

## Probable cause

The disconnection of the propeller governor control arm from the propeller governor due to a missing attachment bolt, which resulted in a partial loss of engine power during takeoff when the governor control vibrated to a high pitch, low rpm setting.

## Findings

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

- [Propeller system: propeller controlling system](https://openairdocs.org/ntsb-findings/01046120): Aircraft › Aircraft propeller/rotor · Failure (probable cause); cases with it: [Threet Richard L VANS RV-7A, 1 case](https://openairdocs.org/ntsb-findings/01046120/cases.md?model=05617CS), [All aircraft, 25 cases](https://openairdocs.org/ntsb-findings/01046120/cases.md)
- [Propeller system: propeller governor](https://openairdocs.org/ntsb-findings/01046122): Aircraft › Aircraft propeller/rotor · Not specified (probable cause); cases with it: [Threet Richard L VANS RV-7A, 1 case](https://openairdocs.org/ntsb-findings/01046122/cases.md?model=05617CS), [All aircraft, 16 cases](https://openairdocs.org/ntsb-findings/01046122/cases.md)
- [Maintenance: scheduled/routine maintenance](https://openairdocs.org/ntsb-findings/02062010): Personnel issues › Task performance · Maintenance personnel; cases with it: [Threet Richard L VANS RV-7A, 1 case](https://openairdocs.org/ntsb-findings/02062010/cases.md?model=05617CS), [All aircraft, 320 cases](https://openairdocs.org/ntsb-findings/02062010/cases.md)

## Sequence of events

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

- [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [Threet Richard L VANS RV-7A, 1 case](https://openairdocs.org/ntsb-events/342/sequence.md?model=05617CS), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md)
- [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Threet Richard L VANS RV-7A, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=05617CS), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Threet Richard L VANS RV-7A, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=05617CS), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The pilot reported that, during takeoff, the airplane was about 500 ft above ground level when the engine lost partial power. The pilot verified that the throttle, mixture, and propeller were in the full forward position and chose to stay in the airport traffic pattern and land on the runway. The pilot noted that, during short final on approach, the airplane was "high and fast," but he still wanted to land on the runway to avoid landing in the water beyond the runway. The airplane landed hard, continued into the grass, and then nosed over and came to rest inverted, which resulted in substantial damage to the rudder. A postaccident engine examination was conducted. The propeller governor control arm was found disconnected from the propeller governor, and the control arm locking bolt was missing. In addition, the secondary control arm/spacer and spring were not located. No other anomalies were noted with the engine. The propeller governor control arm was reattached (without the missing parts), and fuel was plumbed into the engine; the engine started and ran smoothly. The propeller lever was operated with no anomalies noted. Then, the governor control arm was positioned in the low pitch, high rpm position to simulate takeoff conditions, and the governor control arm was disconnected. The engine was restarted and the throttle was advanced, but the engine rpm would not rise above 1,400 at maximum power, which was similar to the accident flight data downloaded from the engine information system on board the airplane. After the engine was shut down, examination of the governor control revealed that it had vibrated/turned to a high pitch, low rpm setting. It is likely that the absence of the control arm locking bolt that secured the propeller governor control arm to the propeller governor resulted in the control arm separating from the governor and then the governor control vibrating/rotating into a high pitch, low rpm setting, which resulted in a partial loss of engine power. The investigation could not determine if the bolt was not installed during the engine overhaul 28.5 flight hours before the accident or if the bolt backed out of the propeller control arm.

## Factual narrative

On July 19, 2019, about 1210 eastern daylight time, an experimental, amateur-built Vans RV-7A, N849GS, was substantially damaged after it experienced a partial loss of engine power during the initial climb after takeoff from Ocean City Municipal Airport (OXB), Ocean City, Maryland. The commercial pilot sustained minor injuries. The airplane was registered to and operated by the pilot as a Title 14 Code of Federal Regulations Part 91 flight. Visual meteorological conditions prevailed at the time of the accident and a visual flight rules flight plan was filed for the personal flight destined for Manassas Regional Airport (HEF), Manassas, Virginia. According to the pilot, he performed a preflight inspection of the airplane and an engine run-up with no anomalies noted. He taxied the airplane onto runway 20, applied full power, then, about 500 ft above ground level, the engine experienced a partial loss of power. The pilot verified that the throttle, mixture, and propeller were in the full forward position, and elected to stay in the airport traffic pattern and land on runway 14. He radioed on the UNICOM frequency and reported that he was landing on runway 14. On approach, the pilot noted that an airplane was entering runway 14 for departure. He radioed the pilot of the other airplane on the UNICOM frequency and asked him to abort the takeoff. The airplane exited the runway and the pilot continued his approach to runway 14. During short final on approach, the pilot noted that the airplane was "high and fast," but he still wanted to land on the runway in order to prevent landing in the water. He landed the airplane "hard," about 1,000 ft from the end of the runway and continued for about 150 ft into the grass. The airplane nosed over and came to rest inverted, which resulted in substantial damage to the rudder. An examination of the engine by a Federal Aviation Administration inspector revealed that compression was confirmed on all cylinders, fuel was noted in the fuel lines, and that there were no holes in the crankcase. According to FAA airworthiness records, the airplane was manufactured in 2004. It was equipped with a Superior Air Parts IO-360-B1A3, 180 hp engine. The most recent condition inspection was performed on August 8, 2018, at an airframe time of 431.0 hours, and the most recent overhaul of the engine was performed at that time. The time on the Hobbs meter when the airplane engine was examined was 459.5 hours. During an examination of the engine with an NTSB investigator, the engine cowling was removed to facilitate further engine examination. The governor control arm was found disconnected from the propeller governor and the control arm locking bolt was missing. In addition, the secondary control arm/spacer was not located, nor was the spring. Furthermore, the governor control arm pin that slid into the secondary control arm/spacer was not sheared and remained intact. No other anomalies were noted with the engine. The governor controlarm was re-attached (without the missing parts), fuel was plumbed into the engine, the engine started and operated without anomalies. The engine throttle was advanced and the engine ran smoothly. The propeller lever was operated and the propeller moved from low pitch, high RPM, to high pitch, low RPM multiple times without anomaly. The propeller control was returned to low pitch, high RPM setting and the engine was shut down. Then, the governor control arm was positioned in the low pitch, high RPM position to simulate takeoff conditions. Furthermore, the governor control arm was disconnected since that was how it was initially found by investigators. The engine was restarted, the throttle was advanced, and the engine RPM would not rise above 1400 RPM at maximum power. After the engine was shutdown, the governor control had vibrated/turned and was observed in a high pitch, low RPM setting. A Grand Rapid Technologies Model 4000 Engine Information System was installed in the instrument panel. It was downloaded and the data was reviewed. The most recent flight data indicated that the RPM increased to about 2,600 RPM about 8 minutes and 15 seconds into the recording. Then about 450 ft in the air, and 8 minutes and 30 seconds into the recording, the tachometer decreased to about 1,500 RPM and maintained that RPM over the next one minute and 12 seconds until the engine power reduced to about 800 RPM and finally to 0 RPM.

## Aircraft

- Registration: [N849GS](https://openairdocs.org/aircraft/N849GS), registered now, S/N 71000, built 2004 (OpenAirDocs)
- Reported make and model: VANS RV7 (A)
- Registry model: [Threet Richard L VANS RV-7A](https://openairdocs.org/model/threet-richard-l-vans-rv-7a) (registry code 05617CS) (OpenAirDocs)
- Registry engine: [Lycoming O-360-A1A](https://openairdocs.org/engine/lycoming-o-360-a1a) (registry code 41594, 4 cycle) (OpenAirDocs)
- Category: Airplane, amateur-built
- Serial number: 71000
- Year built: 2004
- Airframe hours: 459.5
- Engines: Superior Air Parts IO-360-B1A3 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Condition, August 8, 2018, 28 hours before
- Departed: OXB, Ocean CIty, MD
- Destination: HEF, Manassas, VA
- Flight plan: VFR
- Airport: OXB, Ocean City Muni, runway 14, 4,074 × 75 ft, asphalt
- Equipment: ADS-B, Angle of attack indicator, Auto-pilot, Data recorder

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 69; injuries: minor; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review December 3, 2018; seat: left; restraint: 5-point; flight hours: 2,500 total, 48 in this make and model, 2,285 as pilot in command, 48 in the last 90 days, 4 in the last 30 days, 0 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 180° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 90 °F, dew point 77 °F
- Altimeter: 29.95 inHg
- Observed at: OXB

## 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 20190719022919A](https://openairdocs.org/incident/20190719022919A), Jul 19, 2019: Threet Richard L VANS RV-7A, Berlin, MD, Substantial damage. The pilot stated that prior to takeoff he performed a preflight inspection, including sumping the fuel tanks. After engine start up he taxied to runway 20 and…

## Docket (7 files)

The files NTSB released with the investigation on November 18, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=99901. 19.1 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 5.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478069&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Pilot Interview Summary (item 2, .PDF, 141 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478070&FileExtension=.PDF&FileName=Pilot%20Interview%20Summary-Master.PDF
- Engine Maintenance Log Excerpts (item 3, .PDF, 960 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478071&FileExtension=.PDF&FileName=Engine%20Maintenance%20Log%20Excerpts-Master.PDF
- Pilot Log Excerpts (item 4, .PDF, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478072&FileExtension=.PDF&FileName=Pilot%20Log%20Excerpts-Master.PDF
- Engine Examination Report (item 5, .PDF, 2 photos, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478073&FileExtension=.PDF&FileName=Engine%20Examination%20Report-Master.PDF
- Grand Rapids Technology - Engine Information System - 4000 Accident Flight Data (item 6, .PDF, 8.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478074&FileExtension=.PDF&FileName=Grand%20Rapids%20Technology%20-%20Engine%20Information%20System%20-%204000%20Accident%20Flight%20Data-Master.PDF
- Investigative Photographs (item 7, .PDF, 3 photos, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40478075&FileExtension=.PDF&FileName=Investigative%20Photographs-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.
