FTW99LA093 · Beech G35
Beech G35 · Accident: airframe, component or system failure en route
From New Braunfels National Airport (BAZ) to F41
Event
- NTSB case
- FTW99LA093
- 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 G35
- 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
- N4662D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Braunfels National Airport (BAZ), New Braunfels, TXTo F41
- 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 · descent
- 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
According to the pilot, the airplane was traveling approximately 180 mph, at 2300 rpm and 20-23 inches of manifold pressure (mp), in a wings level descent. While descending through 2,500 feet, the pilot felt a minor vibration in the yoke and rudder pedals, which persisted between three and five seconds. The pilot reduced power (approximately two or three inches of mp), the airplane decelerated to 160 mph and the vibration ceased. The airplane's never exceed airspeed (Vne) is 202 mph, and the maximum cruise speed (Vno) is 176 mph. Examination of the airplane revealed that the aft fuselage sustained damage between the FS 233.5 and FS 256.9 bulkheads. The lower longerons were buckled. The belly skin located at FS 256.9 bulkhead was separated from the fuselage. The damage was consistent with symmetric downward overload. The ruddervators were checked and determined to be properly balanced.
Probable cause
Flutter of the empennage for an undetermined reason, which resulted in damage to the aft fuselage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW99LA093
- Event ID
- 20001204X00063
- Case number
- FTW99LA093
- 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: 660866a056acfc332e191c358ff6aec7390edc3856dd84f7317f3b9e170a74d7; retrieved 2026-09-22T15:59:28.220Z.