ASN logo
ASN Wikibase Occurrence # 37916
Last updated: 6 September 2020
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:29-AUG-2000
Time:11:57
Type:Silhouette image of generic C182 model; specific model in this crash may look slightly different
Cessna 182N
Owner/operator:Private
Registration: N92596
C/n / msn: 18260275
Fatalities:Fatalities: 2 / Occupants: 2
Other fatalities:0
Aircraft damage: Written off (damaged beyond repair)
Category:Accident
Location:Las Vegas, NV -   United States of America
Phase: En route
Nature:Private
Departure airport:LAS
Destination airport:Concord, CA (CCR)
Investigating agency: NTSB
Narrative:
During cruise flight, the airplane collided with rising terrain while operating under visual flight rules. Prior to departure, Clearance Delivery issued a Class B visual flight rules departure to fly a heading of 270 degrees, climb to 4,000 feet msl, and transmit a transponder code of 4205. The ground controller questioned the pilot about the weather to the west, noting the visibility was no more than 4 to 5 miles from his perspective in the tower. The pilot acknowledged. After departure, the airplane was handed off to the Terminal Radar Approach Control (TRACON). The controller identified the airplane and asked the pilot to confirm heading and desired course. The pilot replied 270 heading and "going up V105." A climb to 5,500 feet msl was issued, which the pilot acknowledged. Airway V105 is about 8 nautical miles south of the accident site. The airplane exited Class B airspace to the west. TRACON instructed the pilot to maintain appropriate VFR altitudes, resume own navigation, and contact the west arrival sector. The pilot acknowledged the frequency change only, and continued his climb and heading for about 8 miles. He never contacted the west arrival sector. The west arrival controller accepted the automated handoff. About 10 minutes later, the controller noticed a loss of radar contact with the VFR airplane. The controller had the opportunity and ability to notice that the airplane was approaching high terrain and issued a warning to the pilot. Radar coverage of the airplane was maintained throughout the sector until impact and Mode C altitude returns were continuously received from the airplane. The airplane was dramatically below the minimum vectoring altitude when it entered the 9,200-foot Minimum Vectoring Altitude area about 5,800 feet, however, the controller took no note of this. According to FAA Order 7110.65, Part 2-1-6 Safety Alert, the controller should issue a safety alert to an aircraft if the controller is aware the aircraft is in a position/altitude which, in the controller's judgment, places it in unsafe proximity to terrain, obstructions, or other aircraft. The controller made one radio call to the pilot in the blind. The last radar contact occurred about 7,300 feet msl. The airplane subsequently impacted a vertical rock face in mountainous terrain at an elevation of 7,450 feet.
Probable Cause: The pilot's continued visual flight into instrument meteorological conditions into rising terrain and the air traffic controller's failure to issue a Safety Advisory.

Sources:

NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20001212X21757&key=1


Revision history:

Date/timeContributorUpdates
24-Oct-2008 10:30 ASN archive Added
21-Dec-2016 19:23 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
12-Dec-2017 19:03 ASN Update Bot Updated [Departure airport, Source, Narrative]

Corrections or additions? ... Edit this accident description