# Accident 20011121032329A: Gulstm 500S, Eagleville, CA, November 21, 2001 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: November 21, 2001, 11:26 local time - Place: Eagleville, CA - Damage: No damage - Operating rules: General operating rules (Part 91) - Location: 41.2858° N, 120.1947° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=41.2858&lon=-120.1947&mi=10 - Aircraft: N900RA, a cancelled registration (https://openairdocs.org/deregistered/N900RA-2002-04-29) (OpenAirDocs) - Registry model: Aero Commander 500 S (registry code 0141107, https://openairdocs.org/model/aero-commander-500-s) (OpenAirDocs) - Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs) - Reported make and model: GULSTM 500S - People aboard: 5 - Fatal injuries: 5 - NTSB investigation: [NTSB LAX02FA031](https://openairdocs.org/ntsb/LAX02FA031) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20011121032329A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (.19) ON NOVEMBER 21, 2001, AT 1126 HOURS PACIFIC STANDARD TIME, AN AERO COMMANDER 500S, N900RA, COLLIDED WITH MOUNTAINOUS TERRAIN ON EAGLE PEAK NEAR EAGLEVILLE, CALIFORNIA. COMMANDER NORTHWEST LIMITED WAS OPERATING THE AIRPLANE UNDER THE PROVISIONS OF 14 CFR PART 91. THE AIRLINE TRANSPORT CERTIFICATED PILOT-IN-COMMAND, COMMERCIAL CERTIFICATED COPILOT, AND THREE PASSENGERS SUSTAINED FATAL INJURIES; THE AIRPLANE WAS DESTROYED. THE PERSONAL CROSS-COUNTRY FLIGHT DEPARTED RENO, NEVADA, ABOUT 1045, EN ROUTE TO WENATCHEE, WASHINGTON. WHILE VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE CLOSEST AVIATION WEATHER REPORTING STATION, THE WEATHER CONDITIONS AT THE ACCIDENT SITE ARE UNKNOWN. AN IFR FLIGHT PLAN HAD BEEN FILED. ACCORDING TO PRELIMINARY INFORMATION SUPPLIED BY OAKLAND AIR ROUTE TRAFFIC CONTROL CENTER, THE PILOT REQUESTED 12,500 FEET MSL AS A CRUISE ALTITUDE. THE SECTOR CONTROLLER INFORMED THE PILOT THAT HE WAS UNABLE TO CLEAR THE FLIGHT TO THAT ALTITUDE BECAUSE THE MINIMUM EN ROUTE ALTITUDE (MEA) FOR THE ROUTE SEGMENT WAS 14,000 FEET. THE PILOT THEN CANCELLED HIS INSTRUMENT FLIGHT PLAN AND STATED THAT HE WAS VFR ON TOP AT 10,500 FEET. SHORTLY AFTER THAT AT 1126, THE CONTROLLER LOST RADIO AND RADAR CONTACT. WHEN NO FURTHER CONTACT WAS MADE WITH THE FLIGHT, OAKLAND CENTER ISSUED AN ALERT NOTICE AT 1230. THE LAST MODE C RADAR SECONDARY BEACON TARGET OCCURRED AT 41 DEGREES 17 MINUTES 09 SECONDS NORTH LATITUDE BY 120 DEGREES 11 MINUTES 41 SECONDS WEST LONGITUDE. THIS POSITION WAS DETERMINED TO BE ABOUT 1/2-MILE EAST OF EAGLE PEAK (ELEVATION 9,920 FEET). SEARCH AND RESCUE PERSONNEL DISCOVERED THE WRECKAGE NEAR THE CREST OF EAGLE PEAK ON NOVEMBER 23. (-23) ON NOVEMBER 21, 2001 AT 10:45 AM, LOCAL TIME THOMAS R. BLAESING DEPARTED RENO, NV IN AERO COMMANDER N900RA ENROUTE IFR TO WENATCHEE, WA. PRELIMINARY INFORMATION FROM OAKLAND ARTCC SAID THE PILOT REQUESTED 12,500 FOR A FINAL ALTITUDE. THE SECTOR CONTROLLER INFORMED THE PILOT THAT THE MINIMUM ENROUTE IFR ALTITUDE WAS 14,000 MSL. THE PILOT THEN CANCELLED HIS IFR FLIGHT PLAN AND SAID HE WAS VFR ON TOP AT 10,500 MSL. AT 11:26 AM LOCAL TIME, OAKLAND ARTCC LOST RADIO AND RADAR CONTACT. THE AIRCRAFT COLLIDED WITH MOUNTAINOUS TERRAIN ON EAGLE PEAK NEAR EAGLEVILLE, CA. (EAGLE PEAK IS 9,920 FEET MSL) THE PILOT AND FOUR PASSENGERS SUSTAINED FATAL INJURIES AND THE AIRPLANE WAS DESTROYED. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB LAX02FA031](https://openairdocs.org/ntsb/LAX02FA031), Nov 21, 2001: Aero Commander 500S (N900RA), Eagleville, CA, destroyed, 5 fatal. 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… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.