FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16FA176 · Beech V35 B

3 May 2016 · Syosset, NY, United States

Beech V35 B · Accident: loss of control in flight en route

From Grand Strand Airport (CRE) to Robertson Field (4B8)

Report a problem

Event

NTSB case
ERA16FA176
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
3 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Beech V35 B

Aircraft type
Beechcraft 35
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N440H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Grand Strand Airport (CRE), North Myrtle, SCTo Robertson Field (4B8), Plainville, CT
Aircraft age
About 43 years (built 1973)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The instrument-rated pilot was conducting a personal cross-county flight and was operating on an instrument flight rules flight plan. While he was flying in visual conditions between cloud layers at 7,000 ft and heading toward the destination airport, he reported to air traffic control that the airplane had experienced a vacuum pump failure and that he had lost the associated gyroscopic instruments and part of the instrument panel. The pilot continued toward the destination airport because it had the best weather conditions compared to alternate nearby airports; however, after accepting radar vectors for the GPS approach to the airport, he reported that the airplane had entered instrument meteorological conditions (IMC) and that he had lost a "little bit" of control. He then reported that more of the instruments had failed and that he was trying to get back to 7,000 ft. Shortly after, the controller provided the pilot with the weather conditions at a closer airport and asked him if he would like to try to land there; however, no further communications were received from the pilot. Review of radar data revealed that the airplane made several course and altitude deviations as it proceeded northeast until the end of the data.

The airplane was found separated in multiple pieces along a 0.4-mile-long debris path. Based on the radar data and debris path, it is likely that the pilot experienced spatial disorientation while maneuvering the airplane in IMC without a full instrument panel, that he subsequently lost airplane control, and that the airplane broke up in flight due to overstress during the ensuing uncontrolled descent.

Review of a vacuum pump manufacturer's service letter (SL) revealed that the mandatory replacement time for the make and model vacuum pump was 500 aircraft hours or 6 years from the data of manufacture, whichever came first. Compliance with the SL was not mandatory for 14 Code of Federal Regulations Part 91 operations. The vacuum pump was manufactured in May 1999, which was 17 years before the accident. Additionally, the airplane was not equipped with a backup/standby vacuum pump.

Metallurgical examination of the vacuum pump revealed that the rotor had separated radially in numerous locations. Three vanes remained intact, and three vanes separated into numerous pieces. Rotational scoring/rubbing marks were observed on the rotor and pump housing.

Additionally, debris was noted in the inlet screen, but the engine had impacted a dirt field. It is likely the rotor's contact with the pump housing caused the failure of the pump rotor and vanes; however, it could not be ruled out that debris ingestion contributed to their failure.

The pilot had severe coronary artery disease, and toxicological testing revealed low levels of diphenhydramine, a sedating antihistamine allergy treatment and sleep aid, and zolpidem, a prescription sleep aid. However, there was no evidence that the pilot's heart disease or sedating medications impaired his performance or incapacitated him.

Probable cause

The pilot's loss of airplane control while operating in instrument meteorological conditions with only a partial instrument panel due to a failure of the airplane's vacuum pump. Contributing to the accident were the pilot's spatial disorientation and the operation of the vacuum pump beyond the 6-year time limit recommended by the vacuum pump manufacturer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16FA176
Event ID
20160503X70529
Case number
ERA16FA176
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: b67ea811fde86ade5811f22da454d6d6ebdaafe3b6b00c65b10fbdc939dc7862; retrieved 2026-09-14T21:45:09.573Z.