# NTSB LAX02LA124: Cessna 152, N69000, Lake Elsinore, CA, April 4, 2002 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: April 3, 2002, 21:05 local (Apr 4, 2002, 05:05 UTC) - Place: Lake Elsinore, CA - Coordinates: 33.680328, -117.370582 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.6803&lon=-117.3706&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 2 minor - Status: Completed, report November 25, 2003 - Report: Approved by Office Director - Parties: FAA FSDO - NTSB case key (mKey): 54465 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX02LA124 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54465/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54465 - Page: https://openairdocs.org/ntsb/LAX02LA124 ## Probable cause The pilot lost awareness of his location and collided with trees. Factors in the accident were the mountainous terrain and night conditions. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, cruise - terrain condition - mountainous/hilly - light condition - night (contributing factor) - became lost/disoriented - inadvertent, pilot in command (cause) - object - tree(s) ## Analysis The airplane collided with terrain while in cruise flight. The pilot completed three takeoff and landings at Long Beach, and departed for the French Valley Airport at Murrieta, California. He pilot followed the 91 Freeway eastbound and turned southbound to follow Interstate 15. As he started to climb from 2,600 feet, he obtained the Automated Weather Observation System (AWOS) information for French Valley. He noticed that he was off course, but was unable to see any ground visual references. He turned on the landing and taxi lights and tuned in two VOR (very high frequency omni-directional radio range) stations to try and determine his position. He was scanning for ground references and suddenly noted trees in his flight path. He applied full forward throttle and started a climb; however, the airplane collided with trees on mountainous terrain. The occupants were rescued the following morning. ## Factual narrative On April 3, 2002, about 2105 Pacific standard time, a Cessna 152, N69000, collided with terrain while in cruise flight near Lake Elsinore, California. The private pilot/owner was operating the airplane under the provisions of 14 CFR Part 91. The pilot and one pilot rated passenger sustained minor injuries; the airplane sustained substantial damage. The personal cross-country flight departed Long Beach, California, about 2000. Night visual meteorological conditions prevailed, and no flight plan had been filed. The pilot stated that he stayed in the landing pattern at Long Beach, and completed three takeoff and landings. He departed for the French Valley Airport at Murrieta, California, and then he planned to return to Long Beach. The pilot said he followed the 91 Freeway eastbound and turned southbound to follow Interstate 15. As he started to climb from 2,600 feet, he obtained the Automated Weather Observation System (AWOS) information for French Valley. He noticed that he was off course, but was unable to see any ground visual references. The pilot turned on the landing and taxi lights and tuned in two VOR (very high frequency omni-directional radio range) stations to try and determine his position. He was scanning for ground references and suddenly noted trees in his flight path. He applied full forward throttle and started a climb; however, the airplane collided with trees on mountainous terrain. The occupants were rescued the following morning. ## Aircraft - Registration: [N69000](https://openairdocs.org/deregistered/N69000-2005-09-20), registration cancelled 2005-09-20, S/N 15282423, built 1978 (OpenAirDocs) - Reported make and model: Cessna 152 - Registry model: [Cessna 152](https://openairdocs.org/model/cessna-152) (registry code 2071835) (OpenAirDocs) - Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 15282423 - Airframe hours: 8070 - Engines: Lycoming O-235-N2C 108 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Dariush Javadi - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 3, 2001, 90 hours before - Departed: LGB, LONG BEACH, CA - Destination: F70, MURRIETA, CA ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 43; injuries: minor; private; airplane ratings: single-engine land; medical: class 2, valid medical--no waivers/lim.; last flight review April 14, 2001; seat: left; flight hours: 284 total, 274 in this make and model, 150 as pilot in command, 64 in the last 90 days, 12 in the last 30 days ## Weather - Conditions: Visual (VMC), Night - Wind: 300° at 3 knots - Visibility: 4 statute miles - Lowest ceiling: none - Temperature: 52 °F, dew point 46 °F - Altimeter: 30.04 inHg - Observed at: RAL, 13 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20020403004959A](https://openairdocs.org/incident/20020403004959A), Apr 3, 2002: Cessna 152, Lakeelsinore, CA, No damage. (.19) On April 3, 2002, about 2105 pacific standard time, a Cessna 152, N69000, collided with terrain while maneuvering near lake elsinore, California. The… ## Docket (1 files) The files NTSB released with the investigation on August 19, 2003, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54465. 326 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 326 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40422926&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF 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. --- 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.