The U.S. aircraft register, updated daily
Accidents · NTSB MIA99LA185 · Final report

Beech E-35 accident near Yankeetown, Florida, June 5, 1999

On June 5, 1999 at about 6:30 pm local time, a Beech E-35, registered N3508B, was substantially damaged in an accident near Yankeetown, Florida. It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of maintenance personnel to balance check the ruddervators after painting the airplane and unclear information contained in the compliance section of AD 94-20-04 resulting in the failure of maintenance personnel to balance check the out-of-balance ruddervators and subsequent in-flight flutter and structural damage. Findings in the investigation were 1) improper modification/repair to both propeller blades by unknown person(s) resulting in them being below specification for chord width, and one of the propeller blades being below specification for chord thickness, 2) wrong sized rivets near the trim tab of the right elevator were noted and the skin of both ruddervators was not trimmed correctly, 3) paint drips flowing towards the trailing edge of both ruddervators contrary to shop manual.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 5, 1999 · about 6:30 pm local time
Place
Yankeetown, Florida · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beech E-35 · all E-35s on the register
Registration
N3508B · no longer on the register · serial D-3725
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

While in smooth air in a right descending turn in VMC conditions between 160-170 mph IAS, the pilot encountered what he thought was turbulence. He slowed the airplane and landed uneventfully at an alternate airport. Damage to the empennage was noted. Both elevators/rudders (ruddervators) were out of balance limits and discrepancies pertaining to both ruddervators were noted. The ruddervators were reskinned and rebalanced in October 1982 and the airplane was painted August 1986; no record of balance check was noted after painting (contrary to the shop manual) through the last entry in the maintenance records. Airworthiness Directive (AD) 94-20-04, effective November 28, 1994, requiring in part balance check of the ruddervators, and a stipulation to repeat the balance check if the ruddervators(s) are repaired or painted. The compliance section of the AD states, '...unless already accomplished'. The AD was completed first in October 1995, in July 1997, and last July 1998; no evidence of balance check was annotated in the maintenance records during accomplishment with the AD. The airplane had accumulated at the time of the accident approximately 79 hours since last compliance with AD 94-20-04 and approximately 156 hours since painting. The mechanic who first performed AD 94-20-04 in October 1995 stated that the ruddervators were not balance checked then due to the wording of the compliance section that states not required if previously accomplished. The mechanic also stated that AD 94-20-04 is 'hard to interpret.' Personnel from the FAA ACO stated that because the AD is subject to interpretation in the field, it may be revised. Review and analysis of the manufacturers flight test report pertaining to flutter indicated no critical frequency around 38.3 Hertz, which is the frequency when the propeller is operating at 2,300 rpm. Postaccident, the maximum vibration recorded from the engine/propeller was .6 ips; the propeller had been balanced to .15 IPS, 15 months before the accident. The maximum limit pertaining to attempting to balance the propeller established by the test equipment manufacturer is 1.2 IPS. The properly installed propeller was out of specification for chord width on both blades and for thickness for Blade No. 2. The aircraft's airspeed indicator was indicating 3-5 mph higher than the test unit when tested between 160 and 170 mph.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 111 hours in all; 34 in this make and model; 66 in the last 90 days; 44 in the last 30 days; 38 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 8,012 hours
  • Last inspection: annual inspection, July 6, 1998; 79 hours since
  • Maximum gross weight: 2,725 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Continental E-225-8 (piston); 0 hours total

The flight

  • Departed from: ORL Orlando FL at 5:30 pm
  • Destination: CDK Cedar Key FL
  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 090° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 91°F (33°C), dew point 66°F (19°C)
  • Altimeter: 30.00 inHg
  • Observation at 6:55 pm from OCF

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.