# NTSB WPR22LA242: Cessna 120, N2056V, San Carlos, CA, June 28, 2022 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: June 28, 2022, 11:46 local (18:46 UTC) - Place: San Carlos, CA - Coordinates: 37.511861, -122.24953 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.5119&lon=-122.2495&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 105433 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR22LA242 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/105433/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=105433 - Page: https://openairdocs.org/ntsb/WPR22LA242 ## Probable cause The total loss of engine power for undetermined reasons. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Cessna 120, 7 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=2071402), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) (defining event); cases with it: [Cessna 120, 2 cases](https://openairdocs.org/ntsb-events/000/sequence.md?model=2071402), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) - [Initial climb: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 120, 10 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2071402), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 120, 13 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2071402), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The accident pilot reported that, 2 days before the accident, the airplane was flown uneventfully by another pilot to the destination airport using the right fuel tank. The pilot who previously flew the airplane reported that he had refueled the airplane with 15 gallons of fuel before that flight, which lasted about 1 hour and 40 minutes; he used the right tank for that flight. He did not indicate that the tanks had been completely filled, noting that 15 gallons was all he needed for the flight. As he approached the destination, he switched to the left fuel tank and landed uneventfully. According to the accident pilot, after conducting a preflight inspection on the day of the accident, he taxied the airplane out to the runway using the right fuel tank. He recalled that the right tank was full of fuel, which would be inconsistent with the right tank’s fuel state if the previous flight had been flown using the right tank. Following an engine runup, he departed. As the airplane was about 400 ft above ground level, the engine rpm decayed to about 1,800 rpm. The pilot performed a 180° turn but was unable to make it to the runway and landed on an airport perimeter road. The airplane bounced, impacted the fence, and came to rest upright on the airport transient parking ramp. The pilot stated that, after the accident, he observed the right fuel line was “severed” with “pouring out fuel.” Postaccident examination of the airplane revealed that the right fuel line from the lower door frame structure had separated from the fuel fitting. Examination of the recovered airframe and engine revealed no evidence of any preexisting mechanical malfunction that would have precluded normal operation. Although the investigation did not identify performance information for the O-200-A engine installed on the Cessna 120 specifically for fuel burn, given the fuel burn of the O-200-A, and estimated flight time, the previous flight would have used about 10 gallons of fuel. This would place the fuel level in the fuel tank below 1/4 tank, which would prohibit takeoff according to the airplane owner’s manual. Although the pilot may have inadvertently used the wrong fuel tank for takeoff, which could have unported the fuel tank and interrupted the subsequent fuel delivery to the engine, the investigation could not determine the position of the fuel selector valve at the time of the accident. The reason for the total loss of engine power could not be determined. ## Factual narrative On June 28, 2022, about 1146 Pacific daylight time, a Cessna 120, N2056V, was substantially damaged when it was involved in an accident near San Carlos, California. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The accident pilot reported that 2 days before the accident the airplane was flown, uneventfully, by another pilot from Anderson, California, to San Carlos Airport (SQL), San Carlos, using the right fuel tank. The pilot who previously flew the airplane reported that he had refueled the airplane with 15 gallons of fuel and flew it back to SQL using the right fuel tank; he estimated the duration of that flight as about 1 hour and 40 minutes. He did not indicate that the tanks had been completely filled, noting that 15 gallons was all he needed for the flight. As he approached SQL, he switched to the left fuel tank and landed uneventfully. On the day of the accident, the accident pilot reported he had 14 gallons of fuel onboard. He taxied out to the runway using the right fuel tank, which he recalled was full of fuel. Following an engine runup, he departed runway 30. As the airplane was about 400 ft above ground level, the engine rpm decayed to about 1,800. The pilot performed a 180° turn to runway 12 but was unable to make it to the runway and landed on the airport perimeter road. The airplane bounced, impacted the fence, and came to rest upright on the airport transient parking ramp. The pilot stated that, after the accident, the right fuel line was “severed” with “pouring out fuel.” He reported that he attempted to turn the fuel selector off but instead turned it in the wrong direction before leaving the wreckage. The accident airplane is equipped with two 12.5-gallon fuel tanks, both of which have float-type sight gauges. The fuel selector valve has three positions: LEFT, RIGHT, and OFF. The airplane owner’s manual states in part “…Set fuel tank selector to fullest tank. (Do not take off on less than 1/4 tank).” Postaccident examination of the airplane by a Federal Aviation Administration inspector revealed that the fuselage was substantially damaged. Examination of the recovered airframe and engine revealed no evidence of any preexisting mechanical malfunction that would have precluded normal operation. The position of the fuel selector valve at the time of the accident was unable to be determined. The investigation did not identify any specific performance information for the O-200-A engine installed on the Cessna 120 specifically for fuel burn. However, the Fuel Flow Limits vs RPM chart from the O-200-A overhaul manual indicated that fuel burn rates vary between 4.5 and 9 gallons per hour (GPH) at 2,050 and 2,750 rpm respectfully. Fuel burn at 2,350 rpm would be about 6 gph. ## Aircraft - Registration: [N2056V](https://openairdocs.org/deregistered/N2056V-2024-09-03), registration cancelled 2024-09-03, S/N 14269, built 1947 (OpenAirDocs) - Reported make and model: CESSNA 120 - Registry model: [Cessna 120](https://openairdocs.org/model/cessna-120) (registry code 2071402) (OpenAirDocs) - Registry engine: [Continental C85 series](https://openairdocs.org/engine/continental-c85-series) (registry code 17008, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 14269 - Year built: 1947 - Engines: Continental Motors O-200-A 100 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Airport: SQL, San Carlos, runway 12, 2,621 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 68; injuries: none; flight instructor, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review May 19, 2022; seat: left; restraint: 4-point; flight hours: 26,200 total, 800 in this make and model, 20,000 as pilot in command, 25 in the last 90 days, 10 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 360° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 55 °F - Altimeter: 30.09 inHg - Observed at: KSQL - METAR: KSQL 281747Z 36008KT 10SM CLR 19/13 A3009 ## 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 20220628011479A](https://openairdocs.org/incident/20220628011479A), Jun 28, 2022: Cessna 120, San Carlos, CA, Destroyed. San Carlos, CA (sql): [privacy data omitted] C120, departed rwy 30, the pilot stated that at about 150-200 feet the engine started running rough and he started… ## Docket (9 files) The files NTSB released with the investigation on April 10, 2024, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=105433. 11.7 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 11 pages, 5.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15627346&FileExtension=pdf&FileName=6120_Redacted-Rel.pdf - Memorandum of record - conversation with the pilot (item 2, PDF, 1 page, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15595993&FileExtension=pdf&FileName=MOR%20Pilot-Rel.pdf - FAA record of conversation - passenger (item 3, PDF, 1 page, 57 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15595837&FileExtension=pdf&FileName=FAA%20Passenger%20phone%20conversation_Redacted-Rel.pdf - FAA record of conversation - previous pilot (item 4, PDF, 1 page, 53 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15596003&FileExtension=pdf&FileName=FAA%20ROC%20Previous%20Pilot-Rel.pdf - NTSB airframe and engine examination report (item 5, PDF, 4 pages, 2 photos, 485 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15595648&FileExtension=pdf&FileName=airframe%20and%20engine%20examination%20summary-Rel.pdf - Cessna 120 - 140 owners manual (item 6, PDF, 52 pages, 3.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15595441&FileExtension=pdf&FileName=Operation%20Manual%20for%20Cessna%20120%20140-Rel.pdf - O-200-A fuel burn vs RPM chart - from O-200-A overhaul manual (item 7, PDF, 1 page, 506 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16049951&FileExtension=pdf&FileName=O200%20performance-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 8, PDF, 1 page, 147 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15595847&FileExtension=pdf&FileName=wreckage_releasedocs%20N2056V_Redacted-Rel.pdf - Photo array (item 9, PDF, 2 pages, 2 photos, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15595179&FileExtension=pdf&FileName=Photo%20array-Rel.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.