FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03LA063 · Davis YAK-3 UR-2000

9 Jan 2003 · Parker, AZ, United States

Davis YAK-3 UR-2000 · Accident: propeller failure/malfunction during initial climb

From Chino Airport (CNO) to Avi Suquilla Airport (P20)

Report a problem

Event

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

Davis YAK-3 UR-2000

Aircraft type
Davis YAK-3
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
N498SD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chino Airport (CNO), Chino, CATo Avi Suquilla Airport (P20), Parker, AZ
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
Initial climb
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
Propeller failure/malfunction
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

  • Propeller system/accessories, prop control unit › Failure

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

NTSB narrative

The airplane collided with terrain during an off airport forced landing after the failure of the propeller pitch change control during initial climb after an aborted landing. The propeller blades remained in the high-pitch, low-rpm setting, and did not provide sufficient power to sustain flight. The pilot landed the airplane about 1.5 miles from the airport in open desert terrain. The pilot felt that the propeller shaft extension mechanism failed prior to his landing approach at the airport, resulting in a loss of propeller control.

Probable cause

failure of the propeller shaft extension mechanism resulting in a loss of power, and the pilot's failure to attain the proper touchdown point.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03LA063
Event ID
20030117X00079
Case number
LAX03LA063
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-01-10.
  • API snapshot SHA-256: 73ad552250cc78ba2ea8e8805e9337ea4675b692c849851f41f669c586d30249; retrieved 2026-09-21T09:32:00.643Z.