# NTSB ERA23LA041: Rhinehart Stolp Sdtr TOO SA300, N160JR, Lordstown, OH, October 23, 2022 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Class 3 · Limited · Final report - Date: October 23, 2022, 14:12 local (18:12 UTC) - Place: Lordstown, OH - Coordinates: 41.1665, -80.81437 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.1665&lon=-80.8144&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-descent: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Serious injuries - Injuries: 2 serious - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA FSDO - NTSB case key (mKey): 106205 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA23LA041 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/106205/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=106205 - Page: https://openairdocs.org/ntsb/ERA23LA041 ## Probable cause The pilot’s exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall and loss of airplane control. Contributing to the accident was the improper installation of the elevator trim tab control, which created control feedback that likely distracted the pilot during the precautionary landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Rhinehart Gerald A JR STOLP SDTR TOO SA300, 1 case](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=05601NO), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Rhinehart Gerald A JR STOLP SDTR TOO SA300, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05601NO), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Maintenance: installation](https://openairdocs.org/ntsb-findings/02062035): Personnel issues › Task performance · Owner/builder (probable cause); cases with it: [Rhinehart Gerald A JR STOLP SDTR TOO SA300, 1 case](https://openairdocs.org/ntsb-findings/02062035/cases.md?model=05601NO), [All aircraft, 371 cases](https://openairdocs.org/ntsb-findings/02062035/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Rhinehart Gerald A JR STOLP SDTR TOO SA300, 1 case](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=05601NO), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-descent: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Rhinehart Gerald A JR STOLP SDTR TOO SA300, 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=05601NO), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) ## Analysis The pilot reported that shortly after takeoff, the control stick started shaking violently fore and aft. A witness video confirmed that upon liftoff the airplane’s elevator and elevator trim surfaces began to oscillate. The pilot stated that he continued the takeoff because insufficient runway remained on which to abort, and that he had full control authority, but flew the traffic pattern 10 mph slower than normal due to the feedback on the flight controls. The video showed that the airplane flew the downwind leg at a constant altitude but appeared low based on its position relative to trees and structures in the foreground. The sound of the engine was smooth and continuous through the takeoff roll, the initial climb, and the crosswind and downwind legs of the left traffic pattern. At a point consistent with the base leg of the traffic pattern, the airplane decelerated and entered a left turn. The airplane banked steeply, the nose pitched downward, and the angle of descent steepened. The airplane’s descent appeared to shallow before it disappeared behind trees and the sounds of impact were heard. The pilot’s son, who was a passenger in the airplane, said, “He tried to turn it back, but our airspeed was so low [the plane] just started falling.” Flight control continuity was confirmed from the cockpit to the flight control surfaces. The elevator trim tab cable was intact, but free from its attachment hardware on the trim tab cable mount. Examination of the cable and its associated hardware revealed that the cable was not properly secured and pulled free of its mount. Because the maintenance records for the airplane were burned in the post-crash fire, the history of the assembly could not be determined after the airplane’s airworthiness date. It is likely that the pilot’s decision to fly at a lower airspeed and his distraction due to the fluttering elevator trim tab led to his exceedance of the airplane’s critical angle of attack during the downwind-to-base-leg turn, which resulted in an aerodynamic stall and a subsequent loss of control. ## Factual narrative On October 23, 2022, at 1412 eastern daylight time, an experimental, amateur-built Stolp SDTR Too SA300, N160JR, was destroyed when it was involved in an accident near Lordstown, Ohio. The private pilot and passenger were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. In an interview with law enforcement after the accident, the pilot, who was also the owner and builder of the two-place biplane, explained he had just departed his home airstrip with his son in the front seat; the airplane was about 50 ft into the initial climb when he felt, and then saw, “the elevator shaking on the tail.” The pilot stated that he attempted to return to the runway, but “lost all control and [the plane] went down.” A witness located across the street from the airstrip said that the airplane departed to the south and circled around, heading north when he heard the engine “start to cut out.” The witness saw the airplane then bank left and nose-dive into the pasture. When interviewed, the pilot’s son stated that at takeoff “something seemed off” and his father announced there was something wrong with the elevator. He said, “He tried to turn it back, but our airspeed was so low [the plane] just started falling.” Another witness was standing on the pilot’s property and made a video recording of the flight. The airplane appeared to use nearly the full length of the grass strip and climbed at a shallow angle. At liftoff, the airplane’s elevator and elevator trim surfaces fluttered. The airplane flew the downwind leg at a constant altitude but appeared low based on its position relative to trees and structures in the foreground. The sound of the engine was smooth and continuous through the takeoff roll, the initial climb, and the crosswind and downwind legs of the left traffic pattern. At a point consistent with the base leg of the traffic pattern, the airplane decelerated and entered a left turn. The airplane banked steeply, the nose pitched downward, and the angle of descent steepened. The airplane’s descent appeared to shallow before it disappeared behind trees and the sounds of impact were heard. The pilot reported to a Federal Aviation Administration (FAA) aviation safety inspector that, at liftoff, the control stick began “shaking violently” fore and aft. He continued the takeoff and climb due to inadequate runway remaining to abort the takeoff. The pilot reported that he had elevator authority, but limited his movements of the control stick and flew the traffic pattern “10 mph slower than normal.” The pilot held a private pilot certificate with a rating for airplane single-engine land. The pilot completed the requirements for operation under BasicMed on March 23, 2022. He reported 1,100 total hours of flight experience on that date. According to FAA records, the airplane was manufactured by the pilot/owner in 1996. The airplane’s records were destroyed in the postcrash fire, so its maintenance historycould not be reviewed. The wreckage was examined and photographed at the accident site by FAA aviation safety inspectors. The tube-and-fabric airplane was consumed by postcrash fire. The tail section appeared structurally intact but was thermally damaged. The horizontal stabilizer, elevator, and rudder retained their fabric covering. Flight control continuity was confirmed from the cockpit to the flight control surfaces. The elevator trim tab cable was intact but free from its attachment hardware on the trim tab cable mount. Score marks on the underside of the elevator trim tab were of the same dimension and aligned with the disconnected cable end. The trim tab cable, its mount, and attachment hardware were retained for further examination at the National Transportation Safety Board Materials Laboratory in Washington, DC. Examination of the hardware revealed that the attachment bolt displayed a through-hole in the shank for the control cable, and a hat-shaped spacer beneath the nut. When tightened, the nut provided a clamping force to the cable in the through-hole between the spacer and the head of the bolt. Sliding contact marks were observed on the cable and the spacer beneath the nut on the attachment bolt. Hardware and cable dimension, torque, and thread-engagement measurements of the hardware revealed the nut reached the limit, or was bottomed-out, on the bolt grip. The nut reached the limit of its travel before adequate clamping force could be applied on the cable, which was consistent with cable movement and the sliding contact marks. ## Aircraft - Registration: [N160JR](https://openairdocs.org/aircraft/N160JR), registered now, S/N 2364, built 1996 (OpenAirDocs) - Reported make and model: RHINEHART Stolp SDTR TOO SA300 (NO SERIES) - Registry model: [Rhinehart Gerald A JR STOLP SDTR TOO SA300](https://openairdocs.org/model/rhinehart-gerald-a-jr-stolp-sdtr-too-sa300) (registry code 05601NO) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 2364 - Year built: 1996 - Engines: Lycoming O-360-A1A 180 hp reciprocating - Damage: Substantial damage - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Departed: Warren, OH - Destination: Same as departure - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: serious; private; airplane ratings: single-engine land; medical: basicmed, with waivers/limitations; seat: rear; restraint: 4-point; flight hours: 1,800 total, 795 in this make and model, 18 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Temperature: 72 °F, dew point 39 °F - Altimeter: 30.21 inHg - Observed at: KYNG, 8 nm away - METAR: KYNG 231751Z 00000KT 10SM FEW065 SCT180 SCT250 22/04 A3021 RMK AO2 SLP229 T02170044 10217 20083 58008 ## 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 20221023020439A](https://openairdocs.org/incident/20221023020439A), Oct 23, 2022: Rhinehart Gerald A Jr STOLP SDTR TOO SA300, Lordstown, OH, Destroyed. During takeoff at approximately 20'- 30' the control stick started shaking violently fore and aft. Pilot decided to continue the flight vice putting it back on… ## Docket (5 files) The files NTSB released with the investigation on June 20, 2024, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=106205. 204 MB in all. - Materials laboratory factual report 23-031 (item 1, PDF, 8 pages, 6 photos, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15304475&FileExtension=pdf&FileName=23-031-Rel.pdf - Pilot/operator aircraft accident report, NTSB form 6120.1 memorandum for record (item 2, PDF, 1 page, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17217187&FileExtension=pdf&FileName=Memorandum%20For%20Record%20NTSB%20Form%206120.1-Rel.pdf - Pilot's interview summary (FAA) (item 3, PDF, 1 page, 120 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16248463&FileExtension=pdf&FileName=Pilot%20Interview%20Summary%20FAA_Redacted-Rel.pdf - Ohio state highway patrol accident report (item 4, PDF, 12 pages, 5.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17218059&FileExtension=pdf&FileName=2_Plane%20Crash%2078-133_Redacted-Rel_Redacted-Rel.pdf - Video file of accident flight (item 5, MOV, 197 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16247953&FileExtension=MOV&FileName=IMG_2371-Rel.MOV 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.