CEN10LA559 · Beech A36TC
Beech A36TC · Accident: collision during takeoff/landing
From Snook, TX (no airport) to Lakeway Airpark (3R9)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10LA559
- 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
- Unknown
- 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
- N468SG
- Operator
- Guy E.Knolle, Jr
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Snook, TX (no airport)To Lakeway Airpark (3R9), Austin, 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
- Defining eventThe 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
- Collision during takeoff/landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the wind had been from the north between 5 and 10 knots for most of the afternoon. He elected to make a downhill takeoff, and as the airplane neared the end of the runway it failed to gain sufficient airspeed to become airborne. The airplane continued off the runway and struck a pipe and then a fence, resulting in substantial damage to the fuselage and wing. Upon exiting the airplane, the pilot estimated that the wind had increased to 25 knots. The pilot stated there were no preimpact mechanical malfunctions or anomalies with the airplane.
Probable cause
The pilot's failure to recognize the change in wind velocity and his decision to make a downwind takeoff from the grass airstrip, which led to the airplane's degraded climb capability.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10LA559
- Event ID
- 20100926X10010
- Case number
- CEN10LA559
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 73532edd781cf6c9130b8ffa47b4f176588d42a99ca7f99a9d6221c98428ecd2; retrieved 2026-09-15T15:21:16.028Z.