# NTSB CEN23LA318: Beech H35, N365B, Georgetown, TX, July 23, 2023 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Class 3 · Limited · Final report - Date: July 23, 2023, 11:52 local (16:52 UTC) - Place: Georgetown, TX · unoccupied residence - Coordinates: 30.6619, -97.6871 - Nearby events: https://openairdocs.org/map.md?lat=30.6619&lon=-97.6871&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) - Highest injury: Minor injuries - Injuries: 3 minor - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Central Region - Parties: FAA Flight Standards, Continental Aerospace Technologies, Textron Aviation - NTSB case key (mKey): 192694 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN23LA318 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/192694/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=192694 - Page: https://openairdocs.org/ntsb/CEN23LA318 ## Probable cause A loss of engine power for reasons that could not be determined. ## 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: [Beech H35, 3 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=1151520), [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. - [Approach: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) (defining event); cases with it: [Beech H35, 3 cases](https://openairdocs.org/ntsb-events/000/sequence.md?model=1151520), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Beech H35, 3 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=1151520), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Beech H35, 8 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=1151520), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis After the airplane was fueled, the pilot and two passengers completed an uneventful 33-minute cross-country flight. The airplane was not fueled before beginning the 28-minute return flight. The pilot reported that the run-up, takeoff, climb out, and cruise portion of the return flight proceeded normally. While on left base in the airport traffic pattern and after configuring the airplane for landing, he attempted to increase engine power, but the engine did not respond. His attempt to troubleshoot the problem, which included activating the fuel boost pump and changing fuel tanks, was not successful. The airplane impacted an unoccupied two-story residence about 1 mile south-southwest of the airport. Postaccident examination confirmed continuity of the airframe fuel system. The fuel strainer contained some water, and the screen was partially obstructed with debris. The salvage operator noted that the airplane was stored outside after recovery from the accident site. During an engine test run, the engine speed at full throttle was 2,450 rpm rather than 2,700 rpm as specified for maximum rated power by the manufacturer. The fuel pressure was about 1 psi above the limit. When the fuel mixture to the engine was leaned to within the specification, the engine speed did not change appreciably. Fuel pressure was a field-adjustable parameter, which may account for the finding. The investigation was unable to determine the reason for the loss of engine power. Since the fuel-injected engine performed normally on the initial flight and for most of the return flight, and considering that the wreckage was outside and subjected to the environment during storage, it is unlikely that the debris observed in the fuel screen was present at the time of the accident and likely did not have a role in the loss of engine power. ## Factual narrative On July 23, 2023, about 1152 central daylight time, a Beech H35 airplane, N365B, was substantially damaged when it was involved in an accident near Georgetown, Texas. The pilot and 2 passengers sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that he purchased the airplane about one month before the accident flight. The airplane was flown from California to Texas by a friend of the pilot. About two weeks before the accident, the pilot completed a familiarization flight with the friend who had relocated the airplane to Texas and who was also a flight instructor. According to the pilot, on the morning of the accident flight, he flew from Georgetown Executive Airport (GTU) to Gillespie County Airport (T82) with two passengers. The airplane’s main and auxiliary fuel tanks were full before that flight; the wing tip tanks were not fueled. The pilot and passengers remained at T82 for lunch before the planned return flight to GTU. The airplane was not fueled while at T82. The pilot reported that the run-up, takeoff, climb out, and cruise portion of the return flight proceeded normally. While on left base in the airport traffic pattern at GTU, he attempted to increase engine power after configuring the airplane for landing, but the engine did not respond. His attempt to troubleshoot the problem, which included activating the fuel boost pump and changing fuel tanks, was not successful. He notified the airport tower controller of the loss of engine power and the airplane “impacted seconds later.” ADS-B data revealed that the initial flight departed GTU at 0925 and arrived at T82 about 0959. The accident flight subsequently departed T82 about 1124. The final data point was recorded at 1152 and located in the immediate vicinity of the accident site. The airplane impacted an unoccupied two-story residence about 1 mile south-southwest of the airport. It broke through the roof structure and came to rest on top of the second story. The airplane sustained damage to the fuselage and both wings. A postaccident examination confirmed continuity of the airframe fuel system using compressed air from each wing root fuel line through the fuel selector. The fuel selector operated normally when rotated; however, the detents at each tank position were not pronounced as normally expected. The fuel pump drive coupling was intact. The electric fuel boost pump was tested and operated normally. The fuel strainer contained some water, and the screen was partially obstructed with debris. The recovery operator noted that the airplane was stored outside after recovery from the accident site. The fuel tank vents were unobstructed. An engine test run was conducted following an initial examination and evaluation. The engine started normally, ran smoothly, and responded to throttle inputs promptly. During the test run, the engine speed at full throttle was 2,450 rpm rather than 2,700 rpm as specifiedfor maximum rated power by the manufacturer. The fuel pressure was 18.2 psi, which was above the limit of 17.2 psi. When the fuel mixture to the engine was leaned to a fuel pressure to 16.0 psi, the engine speed measured 2,432 rpm. Airplane maintenance records revealed that, in August 1986, the originally installed Continental O-470-G engine was replaced with a Continental IO-520-B engine under Supplemental Type Certificate SA686CE. The fuel pump was replaced with an overhauled unit about 18 months before the accident flight. The engine had accumulated an additional 29 hours since the fuel pump was replaced. The maintenance records noted a “fuel system adjustment” at that time. Fuel pressure is a field-adjustable parameter. The maintenance records contained no entries after the annual inspection on January 2, 2023. ## Aircraft - Registration: [N365B](https://openairdocs.org/aircraft/N365B), registered now, S/N D-4995, built 1957 (OpenAirDocs) - Reported make and model: BEECH H35 - Registry model: [Beech H35](https://openairdocs.org/model/beech-h35) (registry code 1151520) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: D-4995 - Year built: 1957 - Airframe hours: 6169 - Engines: Continental IO-520-BA10 240 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 2, 2023 - Departed: T82, Fredericksburg, TX - Destination: GTU, Georgetown, TX - Airport: GTU, Georgetown Exec, runway 36, 5,004 × 100 ft, asphalt - Equipment: Stall warning system, ADS-B, Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 51; injuries: minor; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review January 6, 2023; seat: left; restraint: 3-point; flight hours: 4,805 total, 1,203 in this make and model, 4,710 as pilot in command, 22 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 95 °F, dew point 70 °F - Altimeter: 30.06 inHg - Observed at: KGTU, 1 nm away - METAR: METAR KGTU 231656Z VRB05KT 10SM CLR 35/21 A3006 ## 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 20230723010099A](https://openairdocs.org/incident/20230723010099A), Jul 23, 2023: Beech H35, Georgetown, TX, Substantial damage. The pilot started the landing sequence/descent at approximately 10 miles out from gtu. The tracking was high, but the pilot thought it was still ok. The pilot… ## Docket (14 files) The files NTSB released with the investigation on September 11, 2024, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=192694. 343 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 718 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17193003&FileExtension=pdf&FileName=Accident%20Rpt%20--%20CEN23LA318_redacted-Rel.pdf - ADS-B data -- initial flight (item 2, CSV, 3.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17210104&FileExtension=csv&FileName=ADSB%20Data%20File%20--%20Initial%20Flight-Rel.csv - ADS-B data -- initial flight (google earth file) (item 3, KMZ, 104 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17209978&FileExtension=kmz&FileName=ADSB%20Data%20--%20Initial%20Flight%20(Google%20Earth%20File)-Rel.kmz - ADS-B data file -- accident flight (item 4, CSV, 3.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17208702&FileExtension=csv&FileName=ADSB%20Data%20File%20--%20CEN23LA318-Rel.csv - ADS-B data -- accident flight (google earth file) (item 5, KMZ, 84 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17210554&FileExtension=kmz&FileName=ADSB%20Data%20--%20Accident%20Flight%20(Google%20Earth%20File)-Rel.kmz - Investigation photos (item 6, PDF, 7 pages, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17208928&FileExtension=pdf&FileName=Investigation%20Photos%20--%20CEN23LA318-Rel.pdf - Airplane examination summary (item 7, PDF, 8 pages, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17213248&FileExtension=pdf&FileName=Examination%20Summary%20--%20CEN23LA318-Rel.pdf - Maintenance records -- airframe (item 8, PDF, 7 pages, 132 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17206416&FileExtension=pdf&FileName=Maintenance%20Records%20--%20Airframe_redacted-Rel.pdf - Maintenance records -- engine (item 9, PDF, 6 pages, 90.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17207733&FileExtension=pdf&FileName=Maintenance%20Records%20--%20Engine_redacted-Rel.pdf - Maintenance records -- propeller (item 10, PDF, 5 pages, 66.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17207473&FileExtension=pdf&FileName=Maintenance%20Records%20--%20Propeller_redacted-Rel.pdf - Maintenance records -- weight & balance (item 11, PDF, 1 page, 24.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17208304&FileExtension=pdf&FileName=Maintenance%20Records%20--%20Weight%26Balance_redacted-Rel.pdf - FAA major repair & alteration (form 337) -- engine replacement (item 12, PDF, 4 pages, 15.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17208778&FileExtension=pdf&FileName=FAA%20Major%20Repair%20%26%20Alteration%20(Form%20337)%20--%20N365B_redacted-Rel.pdf - Flight manual supplement -- STC engine replacement (item 13, PDF, 2 pages, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17207935&FileExtension=pdf&FileName=Flight%20Manual%20Supplement%20--%20Beech%20H35%20(STC%20SA686CE)_redacted-Rel.pdf - Statement of party representatives to NTSB investigation (item 14, PDF, 2 pages, 693 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17207819&FileExtension=pdf&FileName=Party%20Stmts%20--%20CEN23LA318_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.