LAX82DA182 · Beech 77
Mendocino Aviation Beech 77 · Accident: loss of control on ground/water during landing
From 048 · LITTLE RIVER, CA to 048 · LITTLE RIVER, CA
Event
- NTSB case
- LAX82DA182
- 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
- 0
- 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 77
- Aircraft type
- Beechcraft 77
- 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
- N1805Z
- Operator
- Mendocino Aviation
- Onboard fatalities
- Unknown
- Route
- From 048 · LITTLE RIVER, CATo 048 · LITTLE RIVER, CA
- 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
- Landing · landing roll
- 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
- Loss of control on ground/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Altitude, not attained
- Pilot in command › Clearance, inadequate
- Pilot in command › Directional control, not maintained
- Pilot in command › Go-around, attempted
- Pilot in command › Ground loop/swerve, uncontrolled
- Pilot in command › Level off, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ON THE SECOND ATTEMPT TO MAKE A TOUCH AND GO LANDING, THE PILOT BOUNCED THE AIRCRAFT HARD ON THE RUNWAY IMMEDIATELY FOLLOWED BY A SHARP LEFT TURN. FULL POWER WAS APPLIED AND THE FLAPS WERE RAISED IN AN ATTEMPTED GO-AROUND. THE AIRCRAFT FAILED TO CLEAR TREES ON THE SOUTH SIDE OF THE RUNWAY AND CAME TO REST NOSE DOWN IN A DRAINAGE DITCH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82DA182
- Event ID
- 20020917X03533
- Case number
- LAX82DA182
- 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. 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: 49332b1ae5d1278757ab6297ec35babb99bffebda357bf6afea20b6a7afd5fd5; retrieved 2026-09-22T03:04:15.525Z.