FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX02LA005 · Aero Commander 690

13 Oct 2001 · Temecula, CA, United States

Aero Commander 690 · Accident: loss of control on ground/water during landing

From Flagstaff Pulliam Airport (FLG) to French Valley Airport (F70)

Report a problem

Event

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

Aero Commander 690

Aircraft type
Aero Commander 690
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
N690JM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo French Valley Airport (F70), Temecula, 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
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 on ground/water
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

  • Other maintenance personnel › Maintenance, adjustment, improper
  • Propeller system/accessories, reversing system › Out of balance
  • Reversers › Incorrect

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 an airport boundary fence during an aborted landing. The pilot made a normal approach following the visual approach slope indicator (VASI) with gear down and full flaps and touched down just past the numbers and began to decelerate. The pilot selected reverse thrust with both engines. As he added power to decelerate, the airplane suddenly veered to the left and off the runway when the right engine did not go into reverse thrust. He deselected reverse thrust and aligned the airplane with the runway. He was approaching the end of the runway at high speed and elected to attempt a takeoff. The airplane went off the end of the runway onto smooth grass. The pilot rotated the airplane, but the airplane collided with an airport boundary fence and came to rest in a field. In a post accident examination, when the power levers were placed in the full reverse position, the left fuel control measured 4 degrees, while the right measured 0 degrees. The left pitch control measured 10 degrees, while the right measured 0 degrees; the controls should have read 0 degrees. A controls engineer determined that during landing, there would be a 10-degree propeller pitch control (PPC) angle mismatch, which would be about 2.5 degrees of BETA angle. With matched levers, there would be asymmetric reverse thrust with the left engine lower in torque. This would result in the airplane turning towards the left if both propellers had gone into reverse pitch.

Probable cause

a misrigging of the engine controls that resulted in an asymmetric reverse thrust condition.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02LA005
Event ID
20011029X02157
Case number
LAX02LA005
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 2001-10-14.
  • API snapshot SHA-256: 658b7a0b52673443ccbc2a43a64afa3ff39e172542acaff8009b67a04860a61e; retrieved 2026-09-21T19:50:01.941Z.