# NTSB WPR14LA123: Lake LA 4 200, N1040L, Corona, CA, February 25, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: February 25, 2014, 12:30 local (20:30 UTC) - Place: Corona, CA - Coordinates: 33.891944, -117.601387 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.8919&lon=-117.6014&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern downwind: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report November 3, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA - NTSB case key (mKey): 88847 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14LA123 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88847/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88847 - Page: https://openairdocs.org/ntsb/WPR14LA123 ## Probable cause The loss of engine power during initial climb for reasons that could not be determined because a postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Malfunction (probable cause); cases with it: [Lake LA-4-200, 1 case](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=5110310), [All aircraft, 497 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern downwind: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Lake LA-4-200, 1 case](https://openairdocs.org/ntsb-events/341/sequence.md?model=5110310), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Lake LA-4-200, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=5110310), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that he intended to fly the airplane in the airport traffic pattern and perform several full-stop landings. During the engine run-up before the first takeoff, the engine ran roughly on the right magneto. The pilot leaned the fuel mixture, which resolved the problem. He then completed the pretakeoff checklist, and, subsequently, he took off in the airplane, completed the pattern, and made a full-stop landing. During the second takeoff, the pilot climbed the airplane to about 800 feet above ground level where the engine lost power. After turning the airplane back toward the airport, the pilot determined that the airplane would not reach the runway, so he maneuvered the airplane toward an open grassy area on the airport. During the landing, he side-loaded the left main landing gear, which subsequently collapsed. A postaccident test run of the airplane's engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The reason for the loss of engine power could not be determined. ## Factual narrative On February 25, 2014, about 1230 Pacific standard time, a Lake LA-4-200 airplane, N1040L, sustained substantial damage during an emergency descent and landing at the Corona Airport (KAJO), Corona, California. The airplane was owned and being operated by the pilot as a visual flight rules (VFR), personal local flight, under the provisions of 14 Code of Federal Regulations Part 91. The solo airline transport pilot was not injured. Visual meteorological conditions prevailed at the time of the accident, and no flight plan was filed for the local area flight. During a telephone conversation with the National Transportation Safety Board investigator-in-charge on February 25, the pilot said he had not flown the airplane for about 3 weeks. He stated that his intent was to fly the airplane in the airport traffic pattern, and perform several full stop landings. He said prior to takeoff during the run-up, the engine ran rough on the right magneto. After he leaned the mixture, the problem resolved itself, and he proceeded to complete the pre-takeoff checklist. After the first takeoff and landing, he proceeded to take off again, climbed to about 800 feet above ground level, and the engine lost power. The pilot reported that he turned back toward the airport, but when he determined he would not make the runway he steered toward an open grassy area on the airport, and prepared the airplane for landing. During landing, he side-loaded the left main landing gear, which collapsed, resulting in substantial damage to the fuselage. The pilot said prior to the flight, he had not had any mechanical problems with the airplane. He stated that he did not fuel the airplane prior to the flight, and believed that the tank had been one-quarter full. On March 19, at the direction of the NTSB IIC, and under the supervision of an FAA air safety inspector, the accident airplane's engine was test run. The airplane was first inspected and found in suitable condition for an engine run. No fuel was added. The airplane has a single central main fuel tank. The tank is conical in shape with the taper at the bottom. The tank configuration results in no unusable fuel, and places the engine pickup and fuel sump drain at the lowest point in the tank. The engine was started per the airplane's checklist, and run with the electric auxiliary fuel pump in both the on and off position. No mechanical anomalies were found during the engine run. ## Aircraft - Registration: [N1040L](https://openairdocs.org/deregistered/N1040L-2018-02-27), registration cancelled 2018-02-27, S/N 633, built 1974 (OpenAirDocs) - Reported make and model: LAKE LA 4 200 (200) - Registry model: [Lake LA-4-200](https://openairdocs.org/model/lake-la-4-200) (registry code 5110310) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 633 - Year built: 1974 - Airframe hours: 2573 - Engines: Lycoming IO360-A1B 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 1, 2013 - Departed: KAJO, Corona, CA - Destination: KAJO, Corona, CA - Airport: KAJO, Corona ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: none; airline transport; airplane ratings: multi-engine land, single-engine land, single-engine sea; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review January 14, 2011; seat: left; restraint: 3-point; flight hours: 8,281 total, 377 in this make and model, 6,113 as pilot in command, 2 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F - Observed at: KAJO, 1 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 20140225003019A](https://openairdocs.org/incident/20140225003019A), Feb 25, 2014: Lake LA-4-200, Corona, CA, Substantial damage. The engine malfunctioned at 700 feet, and the pilot tried to land on the grass strip located on the south side of the runway ## Docket (2 files) The files NTSB released with the investigation on April 28, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88847. 558 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 502 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40411591&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Inspector's Statement (item 2, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40411592&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.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.