eFlight
Accidents · NTSB ERA23LA132 · Final report

Amateur-built SAVANNAH S accident near Trenton, South Carolina, February 28, 2023

On February 28, 2023 at about 5:49 pm local time, a 2022 amateur-built SAVANNAH S, registered N945HS, was substantially damaged in an accident during approach (VFR pattern final) near Trenton, South Carolina (Edgefield County). It was a flight test under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The loss of control during the base turn to final due to the impingement of the Y-stick control by a notepad.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 28, 2023 · about 5:49 pm local time · cases in 2023
Place
Trenton, South Carolina · Edgefield County · cases near this airport · map
Type
Accident
Injuries
1 person was seriously injured and 1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Amateur-built SAVANNAH S, built 2022
Registration
N945HS · registry record · serial 21-12-54-0832
Damage
Substantial damage
Flight
Flight test · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot/builder in the right seat was on the fifth test flight in his amateur-built airplane with another pilot on board who was assisting. While turning from left base to the final leg of the traffic pattern for landing, with the left-seat pilot at the controls, the Y-stick that controlled both pitch and roll jammed. Both pilots attempted to free the Y-stick with force, but it remained jammed with no control of the flaperons and elevator. The airplane remained in a left, descending turn until it collided with trees and terrain about one mile short of the runway. The airplane sustained substantial damage; the right-seat pilot was seriously injured and the left-seat pilot had minor injuries. An examination of the wreckage, including the flight control system, was conducted after the accident. Flight control continuity was confirmed from the flaperons, elevator, and rudder to the cockpit controls, except for the impact-related overload fractures. No areas of flight control binding or improper installation were found that would have prevented normal operation. An examination of the Y-stick revealed that the lower portion of the stick had minimal clearance with the cockpit floor and surrounding structure by design. The stick-to-floor clearance was smallest when the stick was near neutral (straight up). The clearance increased as bank was increased left or right. According to the kit manufacturer, the smallest Y-stick-to-structure clearance was 4.83mm (roll input neutral with full forward stick). The actual Y-stick pre-accident clearance dimensions of the accident airplane could not be determined because of cockpit floor deformation from impact damage. There was no device installed on the floor that would have prevented a foreign object, such as a note pad, mobile phone, logbook, etc., from rolling or sliding under the Y-stick. Both pilots believed that a note pad used by the right-seat pilot to record flight test data fell to the floor during flight and jammed the control. Examination of photos of the 8.5 inch by 11-inch note pad revealed damage consistent with lower Y-stick impingement. It is likely that the note pad fell to the floor during flight and slid under the Y-stick during to the turn to final; when the stick was moved toward neutral, the jam occurred. The kit manufacturer offered, as an option, a soft boot to cover the lower portion of the Y-stick; however, it is not known if this boot would have prevented the accident scenario.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Flight control sys malf/fail during approach (VFR pattern final) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during approach (VFR pattern final)

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Lateral/bank control › Attain/maintain not possible
  • Aircraft › Aircraft systems › Flight control system › (general) › Malfunction other cases naming the flight controls

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 65 hours in all; 4 in this make and model
  • Last flight review: May 17, 2022
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: rgt
  • Injury: serious injuries

Other crew

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 7,500 hours in all; 0 in this make and model
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 4 hours
  • Last inspection: condition inspection, December 2, 2022; 4 hours since
  • Maximum gross weight: 1,320 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Yamaha Apex (piston); 6 hours total

The flight

  • Flight plan: none
  • Runway 29, 2,640 ft by 85 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 300° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 37°F (3°C)
  • Altimeter: 29.84 inHg
  • Observation at 12:53 pm from KDNL, 20 miles away

Weather report (METAR): METAR KDNL 281753Z AUTO 30008KT 10SM CLR 26/03 A2984 RMK AO2 SLP100 T02610028 10261 20189 58009

Injuries

FatalSeriousMinorNone
Flight crew11

Photographs from the investigation 15 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

12 documents, released by the NTSB on May 2, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA23LA132.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.