CEN11LA077 · Halbrook Rans S-6S
Airflight Halbrook Rans S-6S · Accident: part(s) separation from aircraft on approach
From Saint Cloud Regional Airport (KSTC) to Saint Cloud Regional Airport (KSTC)
Event
- NTSB case
- CEN11LA077
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Halbrook Rans S-6S
- Aircraft type
- Halbrook RANS S-6S
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N280JH
- Operator
- Airflight
- Onboard fatalities
- Unknown
- Route
- From Saint Cloud Regional Airport (KSTC), St. Cloud, MNTo Saint Cloud Regional Airport (KSTC), St. Cloud, MN
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Part(s) separation from aircraft
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft structures
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The airplane kit manufacturer’s recommended use of an improper nut type for securing the door hinge.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11LA077
- Event ID
- 20101118X52720
- Case number
- CEN11LA077
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b63e7e89bd5d9e87d05cc7de136d10cfe26dd379fedc64a452bb791a1bf9c5aa; retrieved 2026-09-15T15:34:28.615Z.