LAX02LA206 · Beech BE76
Beech BE76 · Accident: overrun during takeoff
From Prescott Regional Airport - Ernest A. Love Field (PRC) to Prescott Regional Airport - Ernest A. Love Field (PRC)
Event
- NTSB case
- LAX02LA206
- 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 BE76
- Aircraft type
- Beechcraft 76
- 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
- N6627U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZ
- 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 · roll/run
- First occurrenceThe 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
- Overrun
- 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
- Dual student › All available runway, not used
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During an aborted takeoff due to an open door, the airplane impacted a dirt berm at the departure end of the runway. While conducting touch-and-go takeoffs and landings, the student pilot's door popped open. The student retarded the throttles and applied brakes. The CFI assessed the situation, and decided that they could not safely continue the takeoff due to low airspeed and no remaining runway. She then assisted the student with directional control and braking action. The airplane departed the runway and collided with a dirt berm. There were no discrepancies noted with the airplane by the CFI or student pilot.
Probable cause
The student pilot's decision to abort the takeoff with insufficient runway remaining, resulting in a runway overrun and collision with a berm. A factor was the cabin door opening during the takeoff roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA206
- Event ID
- 20020701X01005
- Case number
- LAX02LA206
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 6e2abb7050fb8a4f06759ca746fd6e1e245e5cc18444dff2323d9e3e4e424571; retrieved 2026-09-22T10:51:00.556Z.