LAX84LA056 · Beech A-36
Beech A-36 · Accident: loss of control in flight during landing
From Page Municipal Airport (PGA) to Bermuda Dunes Airport (UDD)
Event
- NTSB case
- LAX84LA056
- 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 A-36
- Aircraft type
- Beechcraft A-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
- N3821Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Page Municipal Airport (PGA), Page, AZTo Bermuda Dunes Airport (UDD), Bermuda Dunes, 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 · flare/touchdown
- 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 in flight
- 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
- Substantial
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › Directional control, not maintained
- Pilot in command › Go-around, initiated
- Pilot in command › Proper alignment, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH A CHAIN LINK FENCE AND SAND DUNES DURING AN ATTEMPTED GO-AROUND AFTER LANDING. THE PLT SAID THAT AFTER LANDING THE BRAKES WERE APPLIED TO NO AVAIL SO AT MIDFIELD THE PLT ELECTED TO GO-AROUND. DURING THE GO-AROUND THE ACFT DRIFTED OFF THE RWY JUST MISSING PARKED ACFT, HIT THE FENCE AND IMPACTED IN THE SAND DUNES OF A VACANT LOT. AFTER THE ACCIDENT AN FAA INSPECTOR FOUND A STREAK OF HYDRAULIC FLUID ON THE MID-SECTION OF THE RWY. IT WAS FOUND THAT RIGHT BRAKE BLEEDER SCREW WAS MISSING HOWEVER THE RIGHT HAND BRAKE ASSEMBLY BLEEDER FITTING PORT HAD TOW THREADS DISTORTED ANDCOMPRESSION DAMAGE NOTED WITH TWO THREADS ON THE OPPOSITE SIDE STRIPPED OUT. THE BRAKE CASTING HAD WHAT APPEARED TO BE RWY SCRAPE MARKS ON THE BLEEDER PORT BOSS. THE RIGHT TIRE WAS FLAT AND LEFT AND RIGHT SKID MARKS WERE NOTED IN THE GRASSAS THE ACFT LEFT THE RWY BEFORE CONTACT WITH THE SAND DUNES. ACCORDING TO THE ARPT MANAGER THERE WAS A LEFT CROSSWIND ATTHE TIME OF THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX84LA056
- Event ID
- 20001214X45114
- Case number
- LAX84LA056
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1983-11-13.
- API snapshot SHA-256: 792021b972a18f14d2d51a5ab4d60190e3b36afdfa3bb34acd0e52f51786d84e; retrieved 2026-09-23T21:07:22.648Z.