FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10LA173 · Williams Yakovlev YAK 3UPW

22 Mar 2010 · Half Moon Bay, CA, United States

Williams Yakovlev YAK 3UPW · Accident: landing gear collapse

From Half Moon Bay Airport (HAF) to Half Moon Bay Airport (HAF)

Report a problem

Event

NTSB case
WPR10LA173
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

Williams Yakovlev YAK 3UPW

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
N153U
Operator
James A Williams · private individual
Onboard fatalities
Unknown
Route
From Half Moon Bay Airport (HAF), Half Moon Bay, CATo Half Moon Bay Airport (HAF), Half Moon Bay, 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
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
Landing gear collapse
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

  • Aircraft › Aircraft systems

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

NTSB narrative

Prior to landing the pilot observed 3 green lights indicating that the landing gear was down and locked. During the landing roll the left main landing gear collapsed, which resulted in substantial damage to the left wing and aileron. A Federal Aviation Administration inspector reported that a postaccident examination of the left main landing gear's pneumatic actuator revealed that the actuator's down-lock ball track was contaminated with dirt and that the steel down-lock balls were corroded. The combination of dirt in the actuator's down-lock track, the corroded down-lock balls, and the low down-lock pressure likely caused the gear to collapse.

Probable cause

The failure of left main landing gear actuator to lock in the down position due to low down-lock pressure as a result of a contaminated down-lock track and corroded down-lock balls.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10LA173
Event ID
20100322X85943
Case number
WPR10LA173
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: 3733f2a83d1820f2606ec1c36f3fd52979ac866be5d333cec789a4ddb9b48f77; retrieved 2026-09-15T13:46:45.664Z.