# NTSB WPR25LA082: Cessna 172K, N79910, Columbia, CA, January 23, 2025 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Class 3 · Limited · Final report - Date: January 23, 2025, 15:15 local (23:15 UTC) - Place: Columbia, CA · wooded pasture - Coordinates: 38.015813, -120.41977 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.0158&lon=-120.4198&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) - Highest injury: Serious injuries - Injuries: 2 serious - Status: Completed, report September 23, 2026 - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Lycoming Engines, Textron Aviation, Federal Aviation Administration - NTSB case key (mKey): 199593 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR25LA082 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199593/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=199593 - Page: https://openairdocs.org/ntsb/WPR25LA082 ## Probable cause A partial loss of engine power for undetermined reasons. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Power plant](https://openairdocs.org/ntsb-findings/01057100): Aircraft › Aircraft power plant · Unknown/Not determined (probable cause); cases with it: [Cessna 172K, 2 cases](https://openairdocs.org/ntsb-findings/01057100/cases.md?model=2072430), [All aircraft, 198 cases](https://openairdocs.org/ntsb-findings/01057100/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) (defining event); cases with it: [Cessna 172K, 3 cases](https://openairdocs.org/ntsb-events/000/sequence.md?model=2072430), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) ## Analysis The pilot stated that the airplane was too high on landing approach and he applied full power to initiate a go-around. Shortly thereafter, the engine rpm began to decrease. He verified that the mixture, throttle, and carburetor heat controls were all fully forward and confirmed that the fuel selector was set to both tanks. When he moved the throttle aft and forward, the engine briefly surged, and the rpm increased. As he searched for a suitable forced landing site, the engine then lost rpm again. With limited options, he made a 180° turn in an attempt to return to the runway. The airplane collided with trees and impacted the ground in a nose-down attitude. A postaccident examination revealed no evidence of mechanical malfunction or failure. The reason for the partial loss of power could not be determined. ## Factual narrative Examination of the airplane’s documentation indicated that the most recent maintenance performed was an annual/100-hour inspection on January 9, 2025. At the time of inspection, the tachometer reading was recorded as 2,774.6 hours. The tachometer reading at the time of the accident was 2,799.52 hours, indicating that the airplane was operated 24.92 hours since the inspection. The last documented fueling occurred on January 22, 2025, the day before the accident, with the addition of 20.968 gallons. On January 23, 2025, about 1515 Pacific standard time, a Cessna 172K airplane, N79910, was substantially damaged when it was involved in an accident near Columbia, California. The pilot and passenger sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that, on final approach for landing, he noted that the airplane was high and performed a forward slip in an attempt to descend faster. As the airplane approached the runway, it was still too high, and the pilot determined there was not enough available distance to land safely. The pilot initiated a go-around and pushed the throttle fully forward to increase engine power and turned the carburetor heat on. Shortly thereafter, the engine rpm began to decrease. He verified that the mixture, throttle, and carburetor heat controls were all fully forward and confirmed that the fuel selector was set to both tanks. When he moved the throttle aft and forward, the engine briefly surged, and the rpm increased. As he searched for a suitable off-airport landing site, he observed that the surrounding terrain was hilly with trees and brush. The engine then lost rpm again. With limited options, he turned left 180° in an attempt to return to the runway. While transmitting a radio call to report the engine failure, he noticed that the radios had gone blank. The airplane collided with trees and impacted the ground in a nose-down attitude. The pilot had a GoPro camera inside the cockpit that recorded the accident sequence. The recording showed that, about ten seconds after initiating the go-around, the engine began to sputter. Based on comparisons with local landmarks, the airplane traveled about 2.55 miles from the airport before turning back toward runway 35. The final recorded position placed the airplane about 1,592 feet from the accident site. The camera position obstructed most of the instrument panel and throttle quadrant. No gauges or displays were visible. The engine cylinders’ combustion chambers were examined through the upper spark plug holes with a lighted borescope. The combustion chambers remained mechanically undamaged, and there was no evidence of foreign object ingestion or detonation. There was no evidence of valve-to-piston face contact observed. The gas path and combustion signatures observed at the spark plugs, combustion chambers, and exhaust system components displayed coloration that was consistent with normaloperation. There was no oil residue observed in the exhaust system gas path. Investigators achieved manual rotation of the crankshaft by rotating the propeller by hand. Thumb compression was established in all cylinders. Valve train continuity was observed, with approximately equal lift action at each rocker assembly. The accessory gears were undamaged and had a light residue of oil. The muffler assembly was removed from the engine; one header pipe was detached, and internal examination revealed no obstructions to exhaust gas flow. The intake tubes at each cylinder were removed, and the induction plenum was internally inspected, revealing no obstructions. The ignition system was intact, with all spark plug leads secured at their respective spark plugs. Both magnetos were secure at their respective mounting pads. Both magnetos were removed, their drives were intact and undamaged, and both produced spark upon manual rotation. The carburetor remained securely attached to the engine with mixture and throttle controls connected. Carburetor control cable continuity could not be fully verified due to impact damage at the firewall. The carburetor was removed and opened for examination. The fuel bowl was clean, without visible contamination. The composite floats and the float arm were intact and undamaged. The fuel inlet filter at the carburetor was free of visible contamination, the main jet was unobstructed, and the venturi was secure and intact. The accelerator pump plunger gasket appeared somewhat dry yet pliable. The carburetor airbox was removed along with the air filter element; both were free of foreign objects or airflow obstructions. The foam filter element was intact and unobstructed. The propeller remained securely attached to the crankshaft flange, with both blades intact from tip to hub. The propeller blades exhibited minor leading edge nicking. Fuel System The pilot reported that he had 38 gallons of 100LL AvGas onboard the airplane at the time of impact. The fuel selector functioned normally in all positions (Left, Right, Both, and Off). The gascolator was removed and contained about one-quarter pint of clean, blue-colored fuel; the internal gascolator screen was clean, though minor corrosion was noted in the bottom of the bowl. The gascolator drain remained attached to its bracket, which was broken free from the gascolator itself. Continuity was confirmed by blowing air backward from the gascolator through the fuel selector valve with no obstructions noted. Fuel lines from the fuel selector were individually disconnected and continuity verified with no obstructions. Disassembly of the fuel selector revealed all poppet balls in place and moderate wear on the cam, though it still functioned properly with distinct detents. The linkage between the fuel selector handle and valve was bent, consistent with impact damage; the surrounding floorboard was buckled. The fuel line connecting the gascolator to the fuel selector was disconnected forexamination, revealing no internal obstruction or significant deterioration, although there was a slight imperfection of metal observed inside the ferrule clamp. Approximately two tablespoons of fuel, containing sediment, were recovered from this fuel line. A jar of fuel recovered from the left wing during aircraft recovery appeared cloudy yellow with sediment observed at the bottom. The jar had been sitting outside and exposed to sun. The amount of fluid was not enough to be tested. The examination revealed no evidence of mechanical malfunction or failure. ## Aircraft - Registration: [N79910](https://openairdocs.org/deregistered/N79910-2025-05-04), registration cancelled 2025-05-04, S/N 17258243, built 1969 (OpenAirDocs) - Reported make and model: CESSNA 172K - Registry model: [Cessna 172K](https://openairdocs.org/model/cessna-172k) (registry code 2072430) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17258243 - Year built: 1969 - Airframe hours: 2799 - Engines: LYCOMING O-320-E2D 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 9, 2025, 24.92 hours before - Departed: 1O3, Acampo, CA - Destination: Same as departure - Flight plan: VFR - Airport: O22, Columbia, runway 17/35, 4,673 × 75 ft, asphalt - Equipment: ADS-B, Stall warning system, Video recording device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 44; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review January 17, 2025; seat: left; restraint: 3-point; flight hours: 91 total, 54 in this make and model, 25 as pilot in command, 14 in the last 90 days, 8 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 18 °F - Altimeter: 30.32 inHg - Observed at: KO22, 1 nm away - METAR: KO22 232315Z AUTO 00000KT 10SM CLR 19/M08 A3032 RMK A01 ## 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 20250123000969A](https://openairdocs.org/incident/20250123000969A), Jan 23, 2025: Cessna 172K, Columbia, CA, Substantial damage. The aircraft was flown from lodi, CA airport to the Columbia, CA airport for recreational purposes. The airplane fuel tanks were reported by the pilot to be… ## Other investigations on N79910 (2) 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 DEN86LA251](https://openairdocs.org/ntsb/DEN86LA251), Sep 7, 1986: Cessna 172K (N79910), Monte Vista, CO, substantial damage - [NTSB IAD74DLJ37](https://openairdocs.org/ntsb/IAD74DLJ37), Apr 6, 1974: Cessna 172 (N79910), Oxford, NC, substantial damage ## Docket (8 files) The files NTSB released with the investigation on September 23, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=199593. 5.3 MB in all. - Onboard image recorder - specialist's factual report (item 1, PDF, 13 pages, 4 photos, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20972440&FileExtension=pdf&FileName=Onboard%20Image%20Recorder%20-%20Specialist%27s%20Factual%20Report-Rel.pdf - Onboard image recorder - specialist's factual report - ATTACHMENT1 - tabular data (item 2, CSV, 2 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19796306&FileExtension=csv&FileName=Onboard%20Image%20Recorder%20-%20Specialist%27s%20Factual%20Report%20-%20Attachment1%20-%20Tabular%20Data-Rel.csv - Supplemental investigative material (item 3, PDF, 10 pages, 212 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20696935&FileExtension=pdf&FileName=25LA082-%20C172%20Columbia%20Engine%20Supplemental%20Material_Redacted-Rel.pdf - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 4, PDF, 10 pages, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20696541&FileExtension=pdf&FileName=Z%20-%20Attachment%2002%20-%206120_Redacted-Rel.pdf - Record of conversation (item 5, PDF, 2 pages, 143 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20696852&FileExtension=pdf&FileName=Z%20-%20Attachment%2003%20-%20Record%20of%20Conversation%2025LA082_Redacted-Rel.pdf - Record of conversation (from the FAA) (item 6, PDF, 3 pages, 158 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20696945&FileExtension=pdf&FileName=Z%20-%20Attachment%2003%20-%20Record%20of%20Conversation%20from%20FAA%2025LA082_Redacted-Rel.pdf - Statement of party representatives to NTSB investigation (item 7, PDF, 2 pages, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20696955&FileExtension=pdf&FileName=Z%20-%20Attachment%2005%20-%20Party%20Forms_Redacted-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 8, PDF, 1 page, 218 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20696733&FileExtension=pdf&FileName=WPR25LA082_Wreckage_Release_N79910_REDACTED_REVISED-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.