LAX02FA031 · Aero Commander 500S
Aero Commander 500S · Accident: in flight encounter with weather en route
From Reno Tahoe International Airport (RNO) to Pangborn Memorial Airport (EAT)
Event
- NTSB case
- LAX02FA031
- 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
- 5 · 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
- Instrument Meteorological Cond
Aero Commander 500S
- Aircraft type
- Aero Commander 500
- 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
- N900RA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reno Tahoe International Airport (RNO), Reno, NVTo Pangborn Memorial Airport (EAT), Wenatchee, WA
- 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
- En route · cruise
- 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
- In flight encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Preflight briefing service, not used
- Weather condition › Icing conditions
- Weather condition › Mountain wave
- Weather condition › Turbulence, terrain induced
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 mountainous terrain during cruise after encountering turbulence and downdrafts associated with mountain wave conditions. According to Federal Aviation Administration (FAA) records, the pilot called the Reno Automated Flight Service Station at 0941 and filed an IFR flight plan, then asked for the winds aloft forecast, which was provided. The pilot did not request any additional weather briefing information for the flight. No other record was found that the pilot obtained additional weather forecast information from any official source associated with the FAA or the National Weather Service. At the time of the pilot's call to the Reno AFSS, several AIRMET weather advisories had been issued hours prior detailing warnings for turbulence and clear icing along the route of flight. The advisories warned of occasional moderate turbulence below 18,000 feet in moderately strong westerly winds especially in the vicinity of mountainous terrain. Clear Air Turbulence (CAT) between 18,000 and 40,000 feet was forecast over the area of the accident site due to jet stream wind shear and mountain wave activity. The pilot departed under visual flight rules (VFR) and picked up his instrument flight rules (IFR) clearance en route and climbed to 14,000 feet. The pilot later asked if he could maintain 12,500 feet. The controller advised him that the minimum IFR altitude on this segment of his route was 14,000 feet, and the pilot cancelled his IFR flight plan. The controller advised the pilot that he had lost radar contact, and instructed the pilot to squawk VFR and the pilot acknowledged the transmission. The last radar target was about 1/2 mile east of Eagle Peak (elevation 9,920 feet) in the Warner Mountains. Rescuers discovered the wreckage near the crest of Eagle Peak on November 23. Investigators found no anomalies with the airframe, engines, or propellers that would have precluded normal operation. The NWS had a full series of AIRMETs current over the proposed route of flight, which included mountain obscuration, turbulence, and icing. Analysis of the weather conditions disclosed a layer between 9,500 and 11,000 feet over the accident site area as having a high likelihood of severe or greater turbulence. A pilot on the same route of flight reported at 1127 that he was in instrument conditions at 11,000 feet, and experiencing light turbulence and light clear icing conditions. He also reported encountering updrafts of 2,000 feet per minute, which was indicative of mountain wave activity. A company pilot was in a second Aero Commander trailing the accident airplane and he reported that at 1147, at a position near the accident site, he encountered a severe downdraft. He applied full climb power, but as the airplane passed over the accident site position, the airplane continued to lose altitude even at maximum power. At 1159, he was able to gain altitude, and return to his assigned cruising altitude of 14,000 feet. The second Aero Commander was turbocharged, the accident airplane was not. Analysis showed that the topography of the area was critical in this case, given that the accident site was at an elevation of 9,240 feet on the eastern slope of Eagle Peak. The accident airplane's flight track was normal along the airway until immediately downwind of the higher terrain. As the flight approached the lee side of the mountain, it came under the influence of the mountain wave and first encountered an updraft and then a downdraft, which increased in amplitude as the flight progressed towards Eagle Peak. Eagle Peak was the tallest point along the Warner Mountain range and the steep slope of this terrain was significant when the mountain wave action was encountered. Such terrain features have been known to enhance the vertical downdrafts and updrafts associated with the most intense mountain wave turbulence.
Probable cause
the pilot's encounter with forecast mountain wave conditions, moderate or greater turbulence, and icing, with downdrafts that likely exceeded the climb capability of the airplane, which was encountered at an altitude that precluded recovery. Also causal in the accident was the failure of the pilot to obtain an adequate preflight weather briefing which would have included a series of Airmets that were in effect at the time.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02FA031
- Event ID
- 20011206X02358
- Case number
- LAX02FA031
- 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, 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: d32b22877cd7091471ea26cbd7a8dc68c60fdac3cfc49e1456111ba692e58076; retrieved 2026-09-20T20:17:12.388Z.