FTW97LA146 · Beech G33
Beech G33 · Accident: total loss of engine power (mechanical failure) en route
From Tulsa Riverside Airport (RVS) to Bill & Hillary Clinton National Airport/Adams Field (LIT)
Event
- NTSB case
- FTW97LA146
- 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 G33
- Aircraft type
- Beechcraft 33
- 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
- N166B
- Operator
- David H. Laughrey · private individual
- Onboard fatalities
- Unknown
- Route
- From Tulsa Riverside Airport (RVS), Tulsa, OKTo Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, AR
- 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
- Total loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- 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
- Engine assembly, connecting rod bolt › Failure, total
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he had just leveled off at 7,500 feet on a cross-country flight to Little Rock, Arkansas, when the engine started to 'shake violently.' The pilot attempted to return to his departure point, but the engine failed totally. The pilot performed a forced landing, but the airplane impacted a wire on final approach, which subsequently delayed the gear extension, causing the airplane to land with its gear in transit. Postcrash examination of the engine revealed that the number two rod bolt head was in 'relatively undamaged condition.' An FAA Inspector assigned to the accident stated that he believed that the rod bolt was 'either over torqued or under torqued during engine assembly which led to the bolt failure and the number two rod failure well before TBO.' According to the airplane's engine logbook and the pilot's flight log book, the engine had run approximately 604 hours, since being overhauled in August of 1991.
Probable cause
failure of a number two connecting rod bolt, possibly from being either over-torqued or under-torqued during installation, and failure of the pilot to see-and-avoid the transmission line, while performing a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97LA146
- Event ID
- 20001208X07550
- Case number
- FTW97LA146
- 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: ca4b9ee897a723210b09a880c9993e13909a75c52d2eb40253d7e4da0abb9b51; retrieved 2026-09-22T20:06:19.864Z.