# NTSB ERA25LA053: Beech A36, N8152R, Doylestown, PA, November 18, 2024 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Class 3 · Limited · Final report - Date: November 18, 2024, 12:23 local (17:23 UTC) - Place: Doylestown, PA - Coordinates: 40.33305, -75.122338 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.3331&lon=-75.1223&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) - Highest injury: Serious injuries - Injuries: 2 serious, 1 minor - Status: Completed, report August 26, 2026 - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: Textron Aviation, FAA/FSDO, Continental Aerospace Technologies - NTSB case key (mKey): 195529 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25LA053 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195529/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=195529 - Page: https://openairdocs.org/ntsb/ERA25LA053 ## Probable cause The pilot’s failure to maintain control of the airplane during an attempted go-around, which resulted in an aerodynamic stall and impact with terrain and a parked airplane. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Beech A36, 43 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=1151604), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Beech A36, 9 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=1151604), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/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: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) (defining event); cases with it: [Beech A36, 10 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=1151604), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) ## Analysis The purpose of the flight was to demonstrate the airplane’s flight characteristics to the pilot-rated passenger, who was interested in purchasing a share of the airplane. Both the pilot and the pilot-rated passenger reported that the preflight, takeoff, and local flight were uneventful. When returning to the departure airport, the pilot extended the landing gear, and fully extended the flaps. During the landing attempt, when the airplane was about 3 ft above the runway, the pilot reported the airplane suddenly ballooned about 20 ft into the air. The pilot decided to perform a go-around and applied full throttle, retracted the landing gear, and partially raised the flaps. The pilot then reported that he felt the airplane “drop out from under me.” The airplane then impacted the ground to the left of the runway and slid into a parked airplane before coming to rest, resulting in substantial damage to the accident airplane’s left wing and fuselage. The accident was partially captured by video surveillance. The airplane was first seen in a shallow climb. Shortly after, it began to descend, and the wings began to rock back and forth. As the airplane neared the ground, the airplane pitched up, and then impacted the ground near the runway. The wings rocking back and forth were consistent with the airplane nearing an aerodynamic stall, and when the airplane pitched up, it resulted in a full aerodynamic stall. Postaccident examination of the airframe, and an examination and test run of the engine, revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Examination of the propeller showed signatures that were consistent with the high rotational energy at the time of impact. The airplane was equipped with an engine data monitor that recorded the accident flight; however, due to the low recording frequency, it did not capture at least the last 8 seconds of the flight. Shortly before the data stopped recording, the engine rpm and manifold pressure rose sharply to 2,606 rpm and 22.9 inches of manifold pressure. While this is not the maximum rpm or a manifold pressure expected for full power; since the engine run showed the engine was capable of reaching full power, it is likely that the data recording did not capture the engine accelerating to full power. ## Factual narrative On November 18, 2024, at about 1223 eastern standard time, a Beechcraft A36, N8152R, was substantially damaged when it was involved in an accident near Doylestown, Pennsylvania. The pilot received minor injuries, the pilot-rated passenger and the back seat passenger were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulation Part 91 personal flight. According to the pilot rated passenger, he was interested in purchasing a share of the airplane and the purpose of the flight was to demonstrate the airplane’s characteristics. During the preflight inspection, takeoff, and flight, the airplane performed normally with no anomalies noted by the pilot or the pilot-rated passenger. After performing some maneuvers in the local area, the they elected to return to the Doylestown Airport (DYL), Doylestown, Pennsylvania. The pilot reported that they entered the traffic pattern at 1,400 ft mean sea level (msl), before the pilot then put the landing gear down and extended one “notch” of flaps. After turning from the base leg of the traffic pattern to final approach, the pilot ensured that the landing gear was down, he set the flaps to fully extended, and ensured that the mixture and propeller controls were full forward. During the landing flare, about 3 ft above the runway, the pilot reported the airplane ballooned to about 20 ft in the air. The pilot decided to perform a go-around and he pushed in for full throttle and began to retract the flaps and the landing gear. Shortly after beginning the go-around, the pilot felt the airplane “drop out from under me.” The airplane descended and impacted the ground to the left of the runway and continued to slide onto the ramp where an unoccupied airplane was parked. The accident airplane impacted the parked airplane’s right wing and the right side of the fuselage. The accident resulted in substantial damage to the fuselage and left wing of the accident airplane. An airport surveillance video showed the accident sequence. As the airplane came into view, it was in a shallow climb and the landing gear was retracting. The airplane started to descend, and the wings rocked back and forth while the airplane started to deviate to the left of the runway. As the airplane neared the ground, the airplane’s nose pitched up and then the airplane impacted the median between the runway and the taxiway. The airplane was equipped with an engine data monitor capable of storing the flight data. The engine monitor was set to record at a very low rate, and only captured a snapshot of engine data once every 5 seconds. When compared with the surveillance video of the accident, the data also did not record the last 8 seconds of the flight prior to the airplane impacting the ground. The data revealed that between 25 to 30 seconds prior to the accident, the engine rpm, fuel flow, manifold pressure (MAP), and the exhaust gas temperatures (EGT) were all decreased to a level consistent with the engine being at idle.About 20 seconds before the accident, the rpm, fuel flow, MAP, and EGTs all started to increase. The last data datapoint (about 8 seconds prior to impact) indicated the engine was at 2,606 rpm, the MAP was 22.9 inches of mercury, and the fuel flow was reading 20.3 gallons per hour. The engine data also recorded the fuel levels of both main fuel tanks. According to the last datapoint, the left fuel tank still contained 27.1 gallons, and the right fuel tank contained 34.2 gallons. A postaccident examination of the airplane established flight control continuity for all primary and secondary flight controls from their flight control surfaces to their respective cockpit controls through disconnects from recovery. The flap position was determined to be set to 15°, and the landing gear motor was in the retracted position. All of the fuel caps remained secure, intact, and had pliable seals. The fuel tank outlet screens were examined and were clear of any contamination or blockages. Continuity of the fuel lines was verified by blowing low pressure air through the fuel lines to the firewall outlet fitting; there were no obstructions in any of the fuel lines. Both wing fuel tank vents were inspected and were found to be clear of obstructions. The fuel selector was found in the “OFF” position at the time of the examination., Photographs taken of the airplane immediately after the accident by FAA inspectors showed that the “LEFT” fuel tank was selected. The fuel selector was moved to each position and had noticeable detents for each selected position and the fuel selector operated normally in each position. The fuel strainer contained a small amount of residual fuel that had the color and odor consistent with 100LL Avgas. There were no contaminants or signs of water within the fuel sample. The fuel strainer screen was removed and was clear of any contaminants. Control continuity for the engine controls was verified by moving the cockpit control and observing its respective control on the engine. The throttle, propeller, and mixture controls worked from stop to stop with no anomalies. The propeller remained attached to the engine and displayed impact damage. One blade displayed aft bending and twisting deformation, polishing of the cambered end, and the face side. Another blade displayed aft bending and twisting deformation, polishing of the cambered end, and the face side. A portion of the blade’s tip was missing. The remaining propeller blade displayed aft bending with tip curling. The engine’s top spark plugs were removed. The electrodes displayed normal operating and wear signatures. The cylinders were inspected using a lighted borescope; the cylinder walls, piston faces, and valve heads displayed normal operating and combustion signatures. Continuity was established between the crankshaft, camshaft, connecting rods, and associated components by rotating the crankshaft 720°. All six cylinders displayed thumb pressure and suction during crankshaftrotation. The engine throttle and fuel metering inlet screen contained light debris; however, it was not obstructed. There were no signs of leaks in the fuel system between the firewall and the engine injector nozzles. Due to impact damage, the engine was sent to the manufacture for a test run. Prior to the engine run, the impact damaged components were repaired or replaced. The magneto to engine timing was checked, and the left magneto was found to be 25° before top dead center (BTDC), and the right magneto was found to be 26° BTDC. The magneto timing specifications for the engine was 22° BTDC. The engine was placed on a test stand, and a test club propeller was installed on the crankshaft. The engine started on its first attempt without any stumbling or hesitation. The engine rpm was advanced in steps for warm-up and preparation for full power operation. While at 2,100 rpm, a magneto check was performed, when running on the left magneto, the rpm drop was 50 rpm. When the magneto was switched to the right magneto, the rpm dropped by 220 rpm, and the No. 5 cylinder EGT level dropped to levels consistent with combustion no longer occurring in the cylinder. The magneto switch was put back into the both position and the No. 5 cylinder EGT levels indicated normal combustion within the cylinder. The engine run continued, the throttle was then advanced to full throttle, and the engine rpm increased to approximately 2,620 rpm, and the engine continued to run smoothly without any stumbling or hesitation. After the engine was shut down, the engine was troubleshot to determine the cause of the high rpm drop during the right magneto check. The No. 5 top spark plug was found to have the outer and center electrodes contacting each other, resulting in a short that would have prevented a spark from forming between the gap. The spark plug electrode gap was compared with the photographs taken of the spark plug prior to the engine run. The photographs showed a clear gap between the electrodes during the examination. This is consistent with the spark plug being damaged during engine preparation for the engine run. A new spark plug was installed into the No. 5 cylinder top position, and another engine run was performed. At 2,100 rpm, another magneto check was performed; the engine rpm only dropped approximately 50 rpm, and the No. 5 cylinder EGTs were normal. Another full power check was performed, and the engine rpm increased to 2,700 rpm without any stumbling or hesitation. While at full power, it was observed that the unmetered fuel pressure was higher than specifications; however, it did not prevent the engine from operating normally at full throttle. The engine was then brought back to idle rpm, and multiple throttle bursts from idle to full power were performed. The engine accelerated normally during each throttle burst and would reach 2,700 rpm during each throttle burst. ## Aircraft - Registration: [N8152R](https://openairdocs.org/aircraft/N8152R), registered now, S/N E-2778, built 1993 (OpenAirDocs) - Reported make and model: BEECH A36 - Registry model: [Beech A36](https://openairdocs.org/model/beech-a36) (registry code 1151604) (OpenAirDocs) - Registry engine: [Continental TSIO-550 series](https://openairdocs.org/engine/continental-tsio-550-series) (registry code 17043, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: E-2778 - Year built: 1993 - Airframe hours: 2952.9 - Engines: Continental IO-550-B 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 11, 2024, 36.8 hours before - Airport: DYL, Doylestown, runway 23, 3,002 × 60 ft, asphalt - Equipment: Onboard weather, Handheld GPS, Auto-pilot, ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 75; injuries: minor; commercial, private; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review October 28, 2023; seat: left; restraint: 3-point; flight hours: 1,510 total, 750 in this make and model, 1,260 as pilot in command, 6 in the last 90 days, 5 in the last 30 days, 1 in the last 24 hours - Pilot-rated passenger; age 26; injuries: serious; flight instructor, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review October 25, 2024; seat: right; restraint: 3-point; flight hours: 1,537 total, 0 in this make and model, 1,390 as pilot in command, 48 in the last 90 days, 48 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 320° at 7 knots, gusting 16 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 45 °F - Altimeter: 29.86 inHg - Observed at: DYL - METAR: METAR KDYL 181754Z AUTO 32007G16KT 10SM CLR 18/07 A2986 RMK AO2 SLP112 T01830067 10183 20072 58024= ## 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 20241118020619A](https://openairdocs.org/incident/20241118020619A), Nov 18, 2024: Beech A36, Doylestown, PA, Substantial damage. The pilot approached runway 23 at Doylestown Airport, entering the traffic pattern at 1,400’ MSL. On downwind, he lowered the landing gear, confirmed three… ## Docket (17 files) The files NTSB released with the investigation on August 26, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=195529. 59.7 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 - pilot (item 1, PDF, 11 pages, 4.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19785872&FileExtension=pdf&FileName=Pilot%206120%20Form_Redacted-Rel.pdf - Pilot/operator aircraft accident report, NTSB form 6120.1 - pilot rated passenger (item 2, PDF, 2 pages, 2.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19786559&FileExtension=pdf&FileName=6120%20Pilot%20Rated%20Passenger_Redacted-Rel.pdf - Pilot rated passenger statement (item 3, PDF, 1 page, 230 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19786680&FileExtension=pdf&FileName=8152R%20Statement%20of%20Events%20(Pilot%20Rated%20Passenger)-Rel.pdf - Surveillance video (item 4, MOV, 32.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19787126&FileExtension=MOV&FileName=20241204_134520000_iOS-Rel.MOV - Maintenance logbook excerpts (item 5, PDF, 1 page, 643 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19928596&FileExtension=pdf&FileName=20240311_N8152R_2024_Annual_Redacted2-Rel.pdf - ADS-B data (.kmz file) (item 6, KMZ, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19786603&FileExtension=kmz&FileName=20241118_AB1E9D_571954691-Rel.kmz - ADS-B data (.csv file) (item 7, XLSX, 6.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19786197&FileExtension=xlsx&FileName=20241118_AB1E9D_571954691_ADSB-Rel.xlsx - On scene FAA photographs (item 8, PDF, 7 pages, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19787081&FileExtension=pdf&FileName=On%20Scene%20Photo%20Array-Rel.pdf - Wreckage examination report (item 9, PDF, 10 pages, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19928137&FileExtension=pdf&FileName=N8152R%20Initial%20Wreckage%20Examination%20Report-Rel.pdf - Engine run report (item 10, PDF, 6 pages, 777 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19928067&FileExtension=pdf&FileName=ERA25LA053%20Engine%20Run%20Report-Rel.pdf - Engine run screenshots (item 11, PDF, 3 pages, 387 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19787226&FileExtension=pdf&FileName=Engine%20Run%20Screenshots-Rel.pdf - Continental engine run paperwork (item 12, PDF, 10 pages, 4.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19787136&FileExtension=pdf&FileName=Continental%20Engine%20Run%20Paperwork_Redacted-Rel.pdf - Electronic devices - specialist's factual report (item 13, PDF, 10 pages, 5 photos, 815 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18944062&FileExtension=pdf&FileName=ERA25LA053%20final-Rel.pdf - Attachment 1 to electronic devices - specialist's factual report (item 14, CSV, 47 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18942415&FileExtension=csv&FileName=attachment%201-Rel.csv - Statement of party representatives to NTSB investigation - Continental aerospace technologies (item 15, PDF, 1 page, 931 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19786950&FileExtension=pdf&FileName=Continental%20Party%20Form_Redacted-Rel.pdf - Statement of party representatives to NTSB investigation - Textron aviation (item 16, PDF, 1 page, 137 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19787273&FileExtension=pdf&FileName=Textron%20Aviation%20Party%20Form_Redacted-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 17, PDF, 1 page, 663 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20152760&FileExtension=pdf&FileName=Wreckage%20Release_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.