eFlight
Accidents · NTSB ERA13FA227 · Final report

Newgent, Barry S6S accident near Suffolk, Virginia, May 4, 2013

On May 4, 2013 at about 5:00 pm local time, a Newgent, Barry S6S, registered N388KB, was destroyed in an accident during approach (VFR pattern base) near Suffolk, Virginia (Suffolk Executive Airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain airspeed while turning from the downwind to the base leg of the traffic pattern, which resulted in a subsequent aerodynamic stall, spin, and impact with terrain. Contributing to the accident were the pilot's lack of currency and proficiency in controlling the airplane and his decisions to forego recurrent training and to land on the nontraditional runway.

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

What the record shows

Date
May 4, 2013 · about 5:00 pm local time · cases in 2013
Place
Suffolk, Virginia · Suffolk Executive Airport · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Newgent, Barry S6S
Registration
N388KB · no longer on the register · serial 04011413
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot, who was the owner/builder of the accident airplane, flew his airplane with a group of three other airplanes of the same make and model to a fly-in event located about 115 nautical miles from their home airport. The flight made two intermediate stops during the trip due to adverse weather, and, each time, witnesses reported observing the accident pilot having difficulty controlling the airplane at low speed and while landing. The other airplanes landed without incident. When one of the other pilots in the group asked the accident pilot about his difficulty during the previous two landings, the accident pilot stated that he was having difficulty controlling the airplane with a passenger onboard and that the additional weight was "throwing him off." The pilots subsequently took off. The weather conditions at the final destination airport included wind aligned within 20 degrees of the runway heading at 11 knots, gusting to 19 knots. One of the pilots chose to land on the airport's 5,000-foot-long paved runway and did so without incident. The accident pilot and two of the other pilots chose to land on a 2,000-foot-long auxiliary turf runway in use exclusively for the fly-in event. Due to space constraints, pilots were advised to avoid overflying areas with aircraft and personnel, which required a traffic pattern that was closer than customary to the auxiliary runway. The other two pilots landed their airplanes without incident; however, the accident pilot made two aborted approaches. Witnesses reported that, during the two aborted approaches, the airplane appeared to enter an aerodynamic stall as it turned onto the final approach to the runway. During the third and final attempted landing, the airplane appeared to enter a stall while turning from the downwind to the base leg of the traffic pattern and subsequently entered a spin and descended into terrain. The pilot's logbook showed that he had not logged the required number of takeoffs and landings for carrying passengers before departing on the morning of the accident flight. In addition, the pilot had not logged the completion of a flight review in nearly 5 years. Witness observations of the pilot's flying performance on the day of the accident indicate that he also was not proficient in the airplane's operation, particularly with a passenger aboard. The pilot missed several opportunities to avoid or mitigate the outcome of the accident. He could have taken additional recurrent flight training offered to him before and on the day of the accident flight. Additionally, upon recognizing his difficulties with the initial two diversionary landings, the pilot could have chosen to perform some additional practice with a flight instructor who was traveling with the group, or return home, rather than continuing the flight to the more demanding environment of a fly-in event. Further, upon recognizing his difficulties while unsuccessfully attempting to land the airplane twice with the nontraditional, constrained traffic pattern offered by the auxiliary turf runway, the pilot could have chosen to land on the longer, paved runway.

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. Aerodynamic stall/spin during approach (VFR pattern base) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Experience/knowledge › Experience/qualifications › Recent experience › Pilot
  • factor Personnel issues › Experience/knowledge › Training › Recurrent instruct/training › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 244 hours in all; 45 in this make and model; 141 as pilot in command
  • Last flight review: May 24, 2008
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 57 hours
  • Last inspection: inspection type not recorded
  • Maximum gross weight: 1,200 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 912S (piston); 0 hours total

The flight

  • Departed from: JGG Williamsburg VA at 4:30 pm
  • Destination: SFQ Suffolk VA
  • Flight plan: none
  • Runway 07, 2,010 ft by 90 ft

Weather at the time

  • Light: daylight
  • Wind: from 050° at 11 knots, gusting 19
  • Visibility: 10 statute miles
  • Sky: overcast at 1,200 ft; ovct at 1,200 ft
  • Temperature: 57°F (14°C), dew point 54°F (12°C)
  • Altimeter: 30.20 inHg
  • Observation at 4:55 pm from SFQ, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

11 documents, released by the NTSB on March 27, 2014. 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/ERA13FA227.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.