eFlight
Accidents · NTSB CEN11LA077 · Final report

Amateur-built Rans S-6S accident near St. Cloud, Minnesota, November 17, 2010

On November 17, 2010 at about 10:30 pm local time, a amateur-built Rans S-6S, registered N280JH, was substantially damaged in an accident during approach (VFR pattern final) near St. Cloud, Minnesota (St. Cloud Regional Airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The airplane kit manufacturer’s recommended use of an improper nut type for securing the door hinge.

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

What the record shows

Date
November 17, 2010 · about 10:30 pm local time · cases in 2010
Place
St. Cloud, Minnesota · St. Cloud Regional Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Rans S-6S
Registration
N280JH · registry record · serial 12051716
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The pilot reported that while practicing touch-and-go landings he noticed that the nut from the forward door hinge of the left cabin door was missing. He decided to make a full stop landing to inspect further. During final approach, the door separated from the fuselage; the pilot was able to complete the landing without further incident. A postaccident examination confirmed that the forward door hinge bolt/nut assembly had backed-off during flight, which precipitated the door separating from the airplane. The airplane kit manufacturer guidance indicated that a shear stop nut was to be used in the gull-wing (upward opening) door hinge assemblies. However, the Federal Aviation Administration (FAA) advises (in Advisory Circular 43.13-1B) that self-locking nuts, such as the type used on the accident airplane door, are not recommended for use on parts subject to rotation. The FAA further advises that the use of self-locking castellated nuts with cotter pins or lockwire is a more suitable method to secure rotating parts. According to the kit manufacturer, the accident flight was the first documented instance where a door separated during flight.

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. Part(s) separation from AC during approach (VFR pattern final) defining event

The NTSB's findings

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 399 hours in all; 163 in this make and model; 76 in the last 90 days; 18 in the last 30 days; 379 as pilot in command
  • Last flight review: June 24, 2009
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Flight instructor

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 1,024 hours in all; 3 in this make and model; 45 in the last 90 days; 22 in the last 30 days; 921 as pilot in command; 368 on instruments
  • Last flight review: March 2, 2009
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 219 hours
  • Last inspection: condition inspection, April 23, 2010
  • Maximum gross weight: 1,100 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 912 ULS (piston); 0 hours total
  • Operator: Airflight, LLC.

The flight

  • Departed from: KSTC St. Cloud MN at 9:30 pm
  • Destination: KSTC St. Cloud MN
  • Flight plan: none
  • Runway 31, 7,000 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 320° at 9 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 2,600 ft
  • Temperature: 32°F (0°C), dew point 23°F (-5°C)
  • Altimeter: 30.22 inHg
  • Observation at 10:53 pm from KSTC, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew2

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

5 documents, released by the NTSB on November 18, 2011. 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/CEN11LA077.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.