LAX83LA103 · Beech 95-55
Beech 95-55 · Accident: airframe, component or system failure while standing
From an unrecorded airport to R8G · ROSENBERG, OR
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX83LA103
- 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 95-55 Narrative disagrees
- Aircraft type
- Beechcraft 55
- 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
- N704CC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo R8G · ROSENBERG, OR
- 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
- Standing · engine(s) operating
- 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
- Airframe, component or system failure
- 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
- Landing gear, emergency brake system › Inoperative
- Landing gear, normal brake system › Worn
- Pilot in command › Aircraft unattended/engine(s) running, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS PREPARING TO TAXI WHEN HE NOTICED A LOOSE FUEL CAP ON THE ACFT'S LEFT WING. HE SET THE PARKING BRAKE, EXITED THE ACFT WITH BOTH ENGINES OPERATING, PLACED A CHOCK ON THE RIGHT WHEEL AND WAS SECURING THE LOOSE FUEL CAP WHEN THE ACFT STARTED TO MOVE. HE TRIED TO HOLD THE ACFT BY THE WING BUT IT CONTINUED TO TURN AND STRUCK A PARKED COMMANDER 690C, N155WP. THE PILOT STATED THAT PRIOR TO EXITING THE COCKPIT HE ASKED THE FRONT SEAT PASSENGER TO HOLD THE BRAKES IN CASE THE ACFT MOVED. THE PASSENGER WAS FAMILIAR WITH THE BRAKES. THE PASSENGERS ATTEMPTS TO STOP THE ACFT WERE NOT SUCCESSFUL. POST ACCIDENT EXAMINATION DISCLOSED THAT THE PARKING BRAKE VALVE DID NOT HOLD PRESSURE AND THE LEFT BRAKE LININGS WERE AT MINIMUM THICKNESS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83LA103
- Event ID
- 20001214X42242
- Case number
- LAX83LA103
- 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: 5fe18dd20641a8914fff3b1ae34721ca9b12614a5e7641455c5868949c506320; retrieved 2026-09-23T23:08:04.637Z.