FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR15LA183 · Beech E33A

11 Jun 2015 · Tucson, AZ, United States

Beech E33A · Accident: system/component malfunction/failure (non-power) during landing

From La Cholla Airpark (57AZ) to La Cholla Airpark (57AZ)

Report a problem

Event

NTSB case
WPR15LA183
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 E33A

Aircraft type
Beechcraft 33
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
N8401N
Operator
Unknown
Onboard fatalities
Unknown
Route
From La Cholla Airpark (57AZ), Tucson, AZTo La Cholla Airpark (57AZ), Tucson, AZ
Aircraft age
About 47 years (built 1968)
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
Landing · landing roll
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
System/component malfunction/failure (non-power)
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane touched down smoothly with the power nearly off. During the landing roll, the commercial pilot applied gentle pressure to the brakes to slow down; however, there was no left braking action, but there was right braking action. The pilot was unable to maintain directional control of the airplane, and it departed the narrow runway and subsequently collided with a drainage ditch and cement wall.

During postaccident examination of the brake system, the hydraulic system was found almost empty because the bleeder valve on the brake caliper had sheared off due to impact damage. The examination revealed no evidence of any preimpact mechanical failures or malfunctions that would have precluded normal operation. The reason for the lack of left braking action could not be determined.

Probable cause

A loss of left braking action for reasons that could not be determined because postaccident examination did not reveal any evidence of preimpact mechanical failures or malfunctions that would have precluded normal operation, which resulted in a loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR15LA183
Event ID
20150614X35207
Case number
WPR15LA183
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: 8a0045aa287a02b9e1613ea0df7d9bafc7b06dd80c43c6bb7e3e8005d2b836c3; retrieved 2026-09-16T02:25:09.524Z.