NTSB CAROL · Event
Event CEN23LA318
Registry · N365B
FAA Aircraft Registry record.
Make / Model
BEECH H35
Year of manufacture
1957 · 66 years old at event
Engine
CONT MOTOR O-470 SERIES (230 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19570305
ADS-B equipped
Yes — Mode-S A41EF8
Registrant of record
MILES BARRINGTON K
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
A loss of engine power for reasons that could not be determined.
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 specified for 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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Not determined-Not determined-(general)-(general)-Unknown/Not determined
Verbatim from NTSB's published report. Source file
NTSB_2023_CEN23LA318.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗