CHI98LA125 · Beech B35
Beech B35 · Accident: airframe, component or system failure en route
From ASC · Springdale, AR to Nhon Co Airfield (HOO)
Event
- NTSB case
- CHI98LA125
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
- Visual Meteorological Cond
Beech B35
- 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
- N5246C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From ASC · Springdale, ARTo Nhon Co Airfield (HOO)
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Empennage › Flutter
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the airplane was just leveling off after a descent of 700 feet. The wind was light in smooth air. The airplane was in a 15 degree angle of bank right turn, 1 to 2 degrees nose down attitude, and at 180 mph. The airspeed was in the middle of the yellow arc. The pilot reported the airplane began to shake violently like a rivet gun hitting against the fuselage, or like a machine gun. He said the vibrations reverberated throughout his body. He did not feel any vibrations in the controls. He pushed over on the control column after about three seconds of vibration. The vibration stopped. An uneventful landing was made. The aircraft inspection revealed cracks in the upper two corners of the FS 256.9 bulkhead. The forward spar of the right ruddervator was broken. A crack had proceeded through the top spar flange and had worked its way down to the bottom flange but stopped about 1/4 inch prior to reaching a rivet hole. The center hinge had broken and a 8.5 inch skin tear was evident on the top surface of the ruddervator. The ruddervators were properly balanced. The inspection revealed no maintenance anomalies. The FAA issued an Airworthiness Directive 98-13-02 on July 7, 1998, restricting the airspeed to 144 mph on Beech 35, A35,and B35 airplanes. The aircraft manufacturer issued a Service Bulletin 27-3358 in February 2000, which required an extensive inspection of empennage components, and it changed the ruddervator underbalance from 16.8 to 19.8 inch pounds to 16.8 to 18.0 inch pounds in order to lift the speed restriction.
Probable cause
the damage to the empennage was due to flutter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA125
- Event ID
- 20001211X09820
- Case number
- CHI98LA125
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 67b7a750b439790b443cb6fe8ed01c6dcf783fb9c43baf739a9d4746a2c4eb81; retrieved 2026-09-22T17:53:25.298Z.