# NTSB WPR25LA039: Piper PA32-300, N617ET, Pomona, CA, November 17, 2024 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Class 3 · Limited · Final report - Date: November 17, 2024, 11:11 local (19:11 UTC) - Place: Pomona, CA · Fairplex parking area - Coordinates: 34.09148, -117.77164 - Nearby events: https://openairdocs.org/map.md?lat=34.0915&lon=-117.7716&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) - Highest injury: Serious injuries - Injuries: 1 serious, 3 minor - Status: Completed, report September 23, 2026 - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Lycoming Engines, Piper Aircraft, Inc, Federal Aviation Administration - NTSB case key (mKey): 195504 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR25LA039 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195504/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=195504 - Page: https://openairdocs.org/ntsb/WPR25LA039 ## Probable cause A total loss of engine power during final approach for reasons that could not be determined. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible; cases with it: [Piper PA-32-300, 10 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=7103212), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md) - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Unknown/Not determined (probable cause); cases with it: [Piper PA-32-300, 8 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=7103212), [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 final: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) (defining event); cases with it: [Piper PA-32-300, 6 cases](https://openairdocs.org/ntsb-events/000/sequence.md?model=7103212), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) ## Analysis The pilot and three passengers were on final approach to land after a 31-minute flight when the engine exhibited a total loss of power. The pilot attempted to restore engine power by switching fuel tanks and checking the electric fuel boost pump, but the engine did not restart. The pilot retracted the wing flaps in an unsuccessful attempt to extend the airplane’s glide to a road; however, the airplane descended into a raceway parking lot and struck multiple unoccupied vehicles. Postaccident examinations of the airframe and fuel-injected engine revealed no evidence of a preaccident mechanical malfunction or failure. Although the airplane was equipped with an engine data monitor, the most recent flight-related data was dated March 18, 2024; the unit did not record data from the accident flight. Therefore, the reason for the total loss of engine power could not be determined. ## Factual narrative A review of the airplane’s maintenance records showed that the most recent annual inspection was completed on May 1, 2024. The most recent major overhaul was completed on October 24, 2017, and the engine was installed on the airframe on November 22, 2017. On November 17, 2024, about 1111 Pacific standard time, a Piper PA-32-300 airplane, N617ET, was substantially damaged when it was involved in an accident near Pomona, California. The pilot and two passengers sustained minor injuries, and one passenger sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The airplane departed Apple Valley Airport (APV), Apple Valley, California, about 1040 for Brackett Field Airport (POC), La Verne, California. The pilot reported that the airplane departed APV with full fuel tanks and the left main fuel tank selected. When the airplane was about 10 miles from POC, the pilot contacted the airport traffic control tower, and the controller instructed him to enter the right downwind leg of the traffic pattern for runway 26R. Shortly after, the controller instructed the pilot to enter the traffic pattern on the right base leg for runway 26R. While on the base leg, the pilot completed a pre-landing check and noted no anomalies. The controller cleared the airplane to land on runway 26R. Immediately after the airplane turned onto the final approach leg, the engine lost total power. The pilot switched fuel tanks and checked the fuel boost pump but was unable to restore engine power. He retracted the wing flaps, hoping to extend the airplane’s glide, and attempted to land on a road west of the Pomona Fairplex; however, the airplane descended into a parking lot, where it struck multiple unoccupied vehicles before coming to rest upright about 1,000 ft from the approach end of runway 26R. The engine was separated from the fuselage and remained attached to the engine mount. The engine mount displayed multiple areas of fracture and buckling, consistent with impact damage. Fuel recovered from the fuel selector filter bowl was clean, clear, and blue in color. Water detecting paste confirmed that there was no water present in the fuel. The airplane was equipped with two main fuel tanks and two wing tip fuel tanks. All four fuel tanks were breached. Low pressure air was applied to all fuel lines, vent lines, and finger screens, and no blockages were observed. Fuel selector valve continuity was established to the selector handle in the forward cabin. Fuel selector valve detent function was confirmed, and valve function was confirmed via air applied to each fuel line selected, individually. Examination and flow testing of the fuel servo revealed no evidence of mechanical anomalies, malfunction or failure that would have precluded normal operation. The left and right magnetos remained secure at their respective mounting pads. Both magnetos produced spark at all spark plug leads during hand rotation of theirrespective drive. The impulse coupler drive was found to be intact and safety wired. The upper spark plugs were removed observed to display coloration consistent with normal operation, according to the Champion Spark Plug “Check-A Plug” chart AV-27. The No. 2 spark plug was oil soaked, consistent with postaccident engine positioning. The cylinder valve covers were removed; no anomalies were noted with the rocker assemblies. The crankshaft was rotated by hand using the propeller. Mechanical continuity was established throughout the rotating/reciprocating group, valvetrain and accessory section during hand rotation of the crankshaft. Thumb compression was obtained on all cylinders. Each cylinder was examined with a borescope; the combustion chamber deposits were consistent with normal operation. No anomalies were noted with intake or exhaust valves. Postaccident examination of the airframe and engine revealed no evidence of a preaccident mechanical malfunction or failure that would have precluded normal operation. The airplane was equipped with a JPI EDM-830 engine data monitor. The unit’s data was downloaded by the NTSB Vehicle Recorder Division. The downloaded data contained no flight information recorded after March 18, 2024. ## Aircraft - Registration: [N617ET](https://openairdocs.org/aircraft/N617ET), registered now, S/N 32-40205, built 1967 (OpenAirDocs) - Reported make and model: PIPER PA32-300 - Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs) - Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 32-40205 - Year built: 1967 - Airframe hours: 6204 - Engines: Lycoming IO-540-K1A5 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 1, 2024, 100 hours before - Departed: KAPV, Apple Valley, CA - Destination: KPOC, Laverne, CA - Flight plan: VFR - Airport: KPOC, Brackett Field Airport, runway 26R, 3,661 × 75 ft, asphalt - Equipment: Electronic flight bag or handheld device, Auto-pilot, ADS-B, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 79; injuries: minor; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: basicmed, with waivers/limitations; seat: left; restraint: 4-point; flight hours: 1,765.2 total, 155.4 in this make and model, 1,700.5 as pilot in command, 55.4 in the last 90 days, 17.5 in the last 30 days, 0.8 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 63 °F, dew point 25 °F - Altimeter: 29.99 inHg - Observed at: KPOC, 1 nm away - METAR: METAR KPOC 171847Z 00000KT 10SM CLR 17/M04 A2999= ## 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 20241117020859A](https://openairdocs.org/incident/20241117020859A), Nov 17, 2024: Piper PA-32-300, Pomona, CA, Substantial damage. On November 17, 2024, about 1110 pacific standard time, a Piper PA-32-300, [privacy data omitted], was substantially damaged when it was involved in an… ## Docket (9 files) The files NTSB released with the investigation on September 23, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=195504. 14.1 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 11 pages, 4.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18348161&FileExtension=pdf&FileName=pilot%206120_flat_Redacted-Rel.pdf - Memorandums for record (item 2, PDF, 4 pages, 201 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20851747&FileExtension=pdf&FileName=MOR%20-%20pilot%20and%20family%20member_Redacted-Rel.pdf - Maintenance records excerpt (item 3, PDF, 4 pages, 5.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20857827&FileExtension=pdf&FileName=mx%20excerpt%20-%20last%20annual%20and%20engine%20OH_Redacted-Rel.pdf - Airframe and engine exam summary (item 4, PDF, 14 pages, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20955585&FileExtension=pdf&FileName=Airframe%20and%20Engine%20Exam%20Summary-Rel.pdf - Component examination (item 5, PDF, 7 pages, 188 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20852880&FileExtension=pdf&FileName=Component%20Exam%20%20Fuel%20Flow%20Bench%20Test-Rel.pdf - Engine data monitor (item 6, PDF, 1 page, 294 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20956201&FileExtension=pdf&FileName=Engine%20Data%20Monitor%20No%20Data%20Email%20Report-Rel.pdf - Piper party form (item 7, PDF, 1 page, 598 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20830975&FileExtension=pdf&FileName=Party%20Form%20Piper_Redacted-Rel.pdf - Lycoming party form (item 8, PDF, 1 page, 98 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20831219&FileExtension=pdf&FileName=Party%20Form%20Lycoming_Redacted-Rel.pdf - Wreckage release (item 9, PDF, 1 page, 438 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20831867&FileExtension=pdf&FileName=Wreckage%20release%20form%20N617ET%20signed_Redacted-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.