CEN18LA114 · Beech 77
Beech 77 · Accident: loss of control in flight during initial climb
From Odessa Schlemeyer Field (ODO) to Odessa Schlemeyer Field (ODO)
Event
- NTSB case
- CEN18LA114
- 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 77
- Aircraft type
- Beechcraft 77
- 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
- N6699B
- Operator
- Russ Padgett
- Onboard fatalities
- Unknown
- Route
- From Odessa Schlemeyer Field (ODO), Odessa, TXTo Odessa Schlemeyer Field (ODO), Odessa, TX
- Aircraft age
- About 39 years (built 1979)
- 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
- Initial climb
- 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
- Loss of control in flight
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot had no flight time in the accident airplane make and model before his personal flight in the airplane. He said that he looked over the pilot's operating handbook (POH), performed a preflight inspection with the owner, and then obtained fuel and performed an engine run-up; no anomalies were noted. During the takeoff roll, the pilot began rotation about 1/2 of the way down the 6,200-ft-long runway at 49 knots, which was below the airplane's rotation speed and stall speed. The pilot stated that he continued the takeoff, and upon lift-off, the airplane's "acceleration and power started to disappear." He lowered the airplane's nose to increase airspeed as the airplane approached the departure end of the runway and then raised the nose gradually, but the stall warning horn sounded; he aborted the climb and executed a slight right bank turn to remain over the airport. He indicated that the stall warning horn sounded, and the airplane "dropped from the sky."
Postaccident examination of the airplane revealed that the propeller blade damage was consistent with the engine producing power at the time of impact. There was no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. According to the takeoff performance chart in the POH, at gross weight, the airplane's takeoff distance ground roll and takeoff distance over a 50-ft obstacle were about 900 ft and 1,350 ft, respectively. Thus, sufficient runway remained had the pilot elected to abort the takeoff when the airplane exceeded its takeoff ground distance roll. According to the Federal Aviation Administration Airplane Flying Handbook, before takeoff, pilots should identify a point along the runway at which the airplane should be airborne; if the airplane is not airborne by that point, the pilot should take immediate action to discontinue the takeoff.
Probable cause
The pilot’s improper takeoff procedures and his failure to abort the takeoff, which resulted in an aerodynamic stall and subsequent impact with terrain. Contributing to the accident was the pilot’s lack of experience in the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA114
- Event ID
- 20180305X14504
- Case number
- CEN18LA114
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2018-03-01.
- API snapshot SHA-256: 2152ad22830a1adfa3d3fbbf2769d7a70edd8c4cbe7a3f4c0113f70f6dfa2769; retrieved 2026-09-16T06:34:29.847Z.