FTW99FA262 · Beech A36TC
Beech A36TC · Accident: partial loss of engine power (mechanical failure) en route
From Baton Rouge Metropolitan Airport (BTR) to Montgomery Regional (Dannelly Field) Airport (MGM)
Event
- NTSB case
- FTW99FA262
- 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
- 4 · 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 A36TC
- Aircraft type
- Beechcraft 36
- 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
- N206WJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo Montgomery Regional (Dannelly Field) Airport (MGM), Montgomery, AL
- 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
- Partial 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
- Stall; Tree(s)
- 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
- Pilot in command › Stall, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported to ATC that 'he wanted to come down to the nearest airport due to an cylinder overheating problem.' The pilot was vectored to an airport with a 3,000 foot runway. A witness observed the airplane 'high and fast' as it entered the pattern. Witnesses observed the airplane flying over runway 31 with the landing gear extended, at 15 to 35 feet agl. Witnesses reported the airplane assumed a nose high attitude as 'if the airplane was attempting to climb,' and subsequently, they heard the sound of the engine increase. One of the witnesses reported 'the engine sounded as if it was flooded or bogged down.' The pilot lost control of the airplane as he attempted to clear trees at the departure end of the runway. The gear was found in the 'in-transit' position with the wing flaps fully extended. Examination of the engine revealed a hole eroded through the side of the piston for the #2 cylinder. Both spark plugs for the #2 cylinder were found filled with aluminum debris around their electrodes. Examination of the propeller indicated that it was being operated with low power at the time of impact.
Probable cause
The pilot's inadvertent stall while attempting to clear trees during a go-around. Factors were the pilot's misjudgment of the airplane's distance and speed during the precautionary landing and the partial loss of engine power due to a perforated piston.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW99FA262
- Event ID
- 20001212X19755
- Case number
- FTW99FA262
- 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: 0a083415d06e5fb4901a1f9508d0524d5e1b52e13ef090183753d5877f886cf8; retrieved 2026-09-20T21:46:36.112Z.