LAX92LA344 · Cessna 320A
Cessna 320A · Accident: airframe, component or system failure during landing
From Salt Lake City International Airport (SLC) to an unrecorded destination
Event
- NTSB case
- LAX92LA344
- 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
Cessna 320A
- Aircraft type
- Cessna 320
- 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
- N3014R
- Operator
- Craig, Michael · private individual
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC), Salt Lake City, UTTo not recorded
- 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
- 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, normal brake system › Locked
Approximate · Estimated position: the centre of Novato, CA, the place the record names. Not the accident site.
NTSB narrative
THE PILOT WAS CONCLUDING A VISUAL FLIGHT RULES PERSONAL FLIGHT WHEN THE AIRPLANE SWERVED TO THE LEFT ON TOUCHDOWN. THE PILOT APPLIED OPPOSITE RUDDER AND POWER BUT TO NO AVAIL. THE AIRPLANE EXITED THE RUNWAY ENVIRONMENT AND COLLIDED WITH A GULLY. LEFT TIRE SKID MARKS BEGAN AT THE TOUCHDOWN POINT. EXAMINATION OF THE LEFT BRAKE ASSEMBLY DISCLOSED THAT THE BRAKE DISK PARTIALLY CAME OUT OF ITS ATTACH POINT AND JAMMED AGAINST THE HOUSING EFFECTING A LOCKED BRAKE. THE EXAMINATION ALSO REVEALED THAT ALL BUT ONE OF THE BRAKE CLIPS WERE MISSING.
Probable cause
THE LOCKED LEFT BRAKE ASSEMBLY DUE TO THE MISSING BRAKE RETAINING CLIPS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX92LA344
- Event ID
- 20001211X15443
- Case number
- LAX92LA344
- 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 1992-08-09.
- API snapshot SHA-256: 3043fac47349c2261f40999b7a856cd91092840403fb94f08011fa02a1e1dab4; retrieved 2026-09-23T02:47:14.666Z.