FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20LA289 · Beech A36

27 Aug 2020 · Redding, CA, United States

Beech A36 · Accident: runway excursion during takeoff

From Benton Field (O85) to Pierce County-Thun Field (PLU)

Report a problem

Event

NTSB case
WPR20LA289
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
2 · 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 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
N1550G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Benton Field (O85), Redding, CATo Pierce County-Thun Field (PLU), Puyallup, WA
Aircraft age
About 31 years (built 1989)
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
Runway excursion
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot and three passengers were departing from a 2,420-ft-long runway when the accident occurred. A witness reported that the airplane appeared to be accelerating slowly, and that it suddenly rotated and appeared to lift off slightly before settling back to the ground, which caused the nosewheel to come back down to the runway surface. The airplane rotated abruptly a second time and remained in a nose-high attitude while approaching the departure end of the runway. The witness estimated the airplane’s speed as about 60 to 65 knots as it passed his location in a nose-high attitude. The witness added that, throughout the takeoff roll, the “engine sounded like it was producing full power and the propeller was producing full rpm.”

Review of security camera recordings revealed that the airplane appeared to rotate about 700 ft from the departure end of the runway and remain in a nose-high attitude. The airplane briefly became airborne about 300 ft from the departure end of the runway and remained in a nose-high attitude before it settled back onto the runway surface about 2 seconds later and continued off the departure end of the runway: a post-impact fire ensued.

Postaccident examination of the airplane revealed no evidence of any preexisting mechanical malfunction that would have precluded normal operation. A review of weight and balance information indicated that the airplane was about 23 lbs under its maximum gross weight at the time of the accident. Depending on the passenger seating configuration, which could not be determined, the airplane could have been within its center of gravity (CG) limitations or up to about 2 inches forward or about 1.75 inches aft of the CG envelope limit.

Calculated takeoff performance for an airplane within the CG envelope given the atmospheric conditions and gross weight at the time of the accident showed that the airplane would have required 1,978 ft for a no-flap takeoff with no obstacle, or 3,558 ft for a no-flap takeoff to clear a 50-ft obstacle if takeoff power was applied prior to brake release. The extent of the pilot’s preflight takeoff performance planning and his takeoff technique could not be determined based on the available information.

The circumstances of the accident are consistent with the pilot’s failure to recognize the airplane’s inadequate takeoff performance given the length of the available runway and his subsequent failure to abort the takeoff, which resulted in a runway excursion.

Probable cause

The pilot’s failure to recognize the airplane’s inadequate takeoff performance given the length of the available runway and to abort the takeoff, which resulted in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20LA289
Event ID
20200827X41148
Case number
WPR20LA289
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, cause areas. 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: e9c4bf8639964481a2bbf66768b8d71ee4adc1d94d15d7d93f617da4890a6862; retrieved 2026-09-15T07:18:48.181Z.