WPR16LA105 · Beech B24R
Beech B24R · Accident during takeoff
From Pine Mountain Lake Airport (E45) to Pine Mountain Lake Airport (E45)
Event
- NTSB case
- WPR16LA105
- 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 B24R
- Aircraft type
- Beechcraft 24
- 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
- N2052L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pine Mountain Lake Airport (E45), Groveland, CATo Pine Mountain Lake Airport (E45), Groveland, CA
- Aircraft age
- About 40 years (built 1976)
- 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
- Miscellaneous/other
- 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
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The passenger, who was a student pilot, recently purchased the airplane in an estate sale. He and the airline transport pilot, both of whom lived in Mississippi, had traveled to California to retrieve the airplane and fly it back to Mississippi. Before the purchase, the airplane had not been maintained, operated, or flown in almost 11 years. Following the purchase, the owner contracted with a mechanic in California to ensure the airplane was in airworthy condition, which the mechanic reportedly did. The day before the accident, the pilot and owner took the airplane for its first flight after its dormant period and flew one uneventful circuit in the airport traffic pattern, as planned. The following day, the pilot and owner planned to fly the airplane for some systems evaluations. During that takeoff attempt from runway 9, the airplane became airborne but failed to climb and struck trees and terrain beyond the runway end. Although the pilot believed that he was taking off into the wind, witness statements and other evidence indicated that the takeoff was attempted with an approximate 5-knot tailwind. The first 1,000 ft of the runway was level, but the remaining 2,000 ft was sloped uphill. Although the Pilot's Operating Handbook specified using 15° flaps for takeoff, and the pilot reported that he used that setting and did not alter the flap position during the flight, the flaps were found to have been fully retracted at impact.
Surveillance camera imagery captured about 2 seconds of the flight, when the airplane was about midfield and 4 ft above ground level (agl). Review of that imagery and audio data indicated that the ground speed was about 68 knots and that the engine speed was about 2,640 rpm; both values were consistent with normal takeoff values. However, the exact winds (and thus airspeed) were unknown, and because the propeller was a constant-speed model, nominal takeoff rpm could be achieved even if the engine was not developing full-rated power.
Detailed examination of the airplane, including the engine, revealed that, although its condition was not in accordance with Federal Aviation Administration and manufacturer guidance, none of the observed deficiencies could have caused or contributed to the loss of climb performance, except for one magneto that was found to be mistimed to the engine by 7°. Evidence suggested that this was likely a result of the accident but that could not be determined with certainty. Performance calculations conducted by the airplane manufacturer, which accounted for most of the known takeoff conditions, including fully retracted flaps, indicated that the distance to 50 ft agl was slightly more than the available runway. The estimated airplane takeoff weight was about 300 lbs (11%) below the maximum takeoff weight that was used in the calculations, which would yield better performance than the calculated results. However, those calculations did not account for off-nominal values of the many other variables that could adversely affect takeoff performance, including pilot technique, airframe and engine deterioration, and inaccurate or improperly set instrumentation and controls. Thus, although a successful downwind takeoff with no flaps was unlikely, it might have been possible, but there were too many other unknowns to determine its likelihood with greater certainty.
The reason(s) for the retracted flaps could not be determined. It is possible that the pilot forgot to extend them or that they were inadvertently and unknowingly retracted. Given the location of the flap control switch and its design (momentary, paddle-type), it is possible that the pilot extended the flaps to the proper takeoff setting of 15° but that they were subsequently retracted when the nonpilot passenger inadvertently contacted and actuated the flap control. The size and location of the flap position indicator gauge, combined with the location of the flaps (behind the pilot on the low-wing airplane), minimized the possibility that the pilot would notice that they had been retracted.
Probable cause
The pilot's decision to conduct an upslope, downwind takeoff combined with an improper flap setting, which resulted in the airplane's inability to clear trees beyond the runway end. The reason for the improper flap setting could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16LA105
- Event ID
- 20160511X13324
- Case number
- WPR16LA105
- 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, coordinates. 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: 52486eca3a3ab158fa956ea7da09e4a40d104c77ef202f83baf3805ad535c768; retrieved 2026-09-16T03:22:40.071Z.