FTW96LA002 · Beech A36
Beech A36 · Accident: overrun during takeoff
From an unrecorded airport to West Houston Airport (IWS)
Event
- NTSB case
- FTW96LA002
- 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 A36
- 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
- N7247W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo West Houston Airport (IWS), Houston, TX
- 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
- Takeoff · rejected takeoff
- 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
- Overrun
- 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
- Pilot in command › Aborted takeoff, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE IMPACTED TREES AFTER IT OVERRAN THE DEPARTURE END OF THE 2,200-FOOT GRASS STRIP DURING TAKEOFF. THE PILOT STATED THAT INITIALLY THE AIRPLANE ACCELERATED NORMALLY FOR THE SHORT FIELD TAKEOFF UNTIL ROTATION SPEED WAS ATTAINED. SOON AFTER LIFTOFF THE AIRPLANE NEVER GAINED MORE AIRSPEED 'LIKE IF SOMETHING WAS HOLDING THE AIRPLANE DOWN.' THE PILOT FURTHER STATED THAT WHEN HE REALIZED THAT HE WAS NOT GOING TO BE ABLE TO CLEAR THE TREES AT THE DEPARTURE END OF THE STRIP, HE ELECTED TO ABORT THE TAKEOFF. HE DETERMINED THAT THE AIRPLANE WAS WITHIN WEIGHT AND BALANCE LIMITS, AND HE CALCULATED THE TAKEOFF DISTANCE AND DETERMINED THAT 'THEY HAD AMPLE TAKEOFF DISTANCE.' A REVIEW OF THE TAKEOFF DISTANCE CHARTS IN THE PILOT'S OPERATING HANDBOOK REVEALED THAT TO CLEAR A 50-FOOT OBSTACLE REQUIRED 2,350 FEET WITH THE FLAPS DOWN, AND 2,950 FEET WITH THE FLAPS UP.
Probable cause
THE PILOT'S DELAY IN ABORTING THE TAKEOFF. A FACTOR WAS THE PILOT'S IMPROPER USE OF THE AIRCRAFT PERFORMANCE DATA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA002
- Event ID
- 20001207X04687
- Case number
- FTW96LA002
- 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: d1d483de5003788ee9ca7916d5be6a46597c0cd830279b9946c5f0ac5ee4ce35; retrieved 2026-09-22T23:12:15.377Z.