WPR20FA072 · Beech B36TC
Beech B36TC · Accident: runway excursion during takeoff
From Corona Municipal Airport (AJO) to Zamperini Field (TOA)
Event
- NTSB case
- WPR20FA072
- 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
- 4 · 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 B36TC
- 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
- N36TT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Corona Municipal Airport (AJO), Corona, CATo Zamperini Field (TOA), Torrance, CA
- Aircraft age
- About 37 years (built 1983)
- 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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane, with two pilots and two passengers onboard, had landed at the airport to refuel, and 78.06 gallons of fuel were added. The airplane departed with a 5-knot tailwind down a 3,200 ft asphalt runway. According to a witness at the airport, the nose raised off the runway surface prematurely during the takeoff roll. Although the investigation could not determine which pilot was at the controls, neither pilot elected to abort the landing and the airplane bounced down the runway unable to become airborne. The airplane continued to accelerate and reached rotation speed as it collided into a fence at the end of the runway.
Onsite examination revealed the elevator trim tabs were in the full-down position (full nose-up trim). It is likely the elevator trim was mistakenly set at full nose-up trim, which enabled the nose to rise off the runway surface prematurely during the takeoff roll. As the airspeed increased, the force required to push the nose down would have become greater.
The right-seated pilot owned the airplane and the left-seated pilot had flown with him before. A review of the left-seated pilot’s personal notebook revealed that he had flown 3.7 hours in the accident airplane and therefore, likely had limited familiarity with it.
Although the airplane was likely at or over the maximum gross weight based on the amount of fuel added to the airplane, the airplane’s performance charts indicate that the runway length was sufficient at the airplane’s maximum gross takeoff weight to complete a takeoff. Both pilots had ample opportunity to abort the takeoff when they realized the airplane was not becoming airborne but continued with the takeoff attempt.
Probable cause
The pilots’ failure to abort the takeoff, which resulted in a collision with a fence at the end of the runway. Contributing to the accident was the airplane being at or over the maximum gross takeoff weight and the inappropriate elevator trim tab setting.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20FA072
- Event ID
- 20200122X05239
- Case number
- WPR20FA072
- 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: d691671859aaf390b18c7908f552d5614c5de0dda0b17c0df5b88831f56c6aea; retrieved 2026-09-15T07:10:49.568Z.