CEN12LA265 · Jonker Sailplanes CC JS 1B
Jonker Sailplanes CC JS 1B · Accident: system/component malfunction/failure (non-power) en route
From Moriarty Municipal Airport (0E0) to Moriarty Municipal Airport (0E0)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN12LA265
- 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
Jonker Sailplanes CC JS 1B
- Aircraft type
- Jonker Sailplanes CC JS-1
- Category
- Glider
- 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
- N555AP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Moriarty Municipal Airport (0E0), Moriarty, NMTo Moriarty Municipal Airport (0E0), Moriarty, NM
- 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
- En route · cruise
- 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
- System/component malfunction/failure (non-power)
- 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 systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While in soaring flight, the pilot heard a loud metallic sound come from the area near the rudder pedals and subsequently lost contact between his feet and the pedals, which resulted in a temporary loss of glider control. Although the pilot regained control of the glider, it was descending. When the glider had descended to about 10,000 feet mean sea level, the pilot chose to bail out with a parachute due to the descent rate and the unfavorable terrain for landing. The glider subsequently impacted a mesa and sustained substantial damage. Subsequent examination of the adjustable rudder pedal system revealed that the right rudder cable had fractured at the forward opening of the S-tube on the right rudder pedal. Examination of the rudder pedal design configuration revealed that full-forward deflection of the rudder pedal forced the cable to sharply bend at the point where it exited the forward opening of the S-tube, which was confirmed by a corresponding wear pattern on the accident glider’s S-tube. The repeated bending during normal operation resulted in the fatigue failure of 92 percent of the individual right rudder cable wires and, subsequently, final overstress failure of the remaining wires. After the accident, the owner of another glider of the same design examined the rudder cable on his glider and found similar damage to the cable. Subsequently, he conducted ground testing, which confirmed that repeated operation of the rudder pedals resulted in further damage to the rudder cables, indicating a progressive failure. Therefore, it is likely that the right rudder cable failed during the flight and resulted in the loss of rudder control. The glider manufacturer subsequently issued service bulletins and service letters to address the rudder pedal system deficiencies discovered during the accident investigation. Flight testing conducted by the manufacturer in an exemplar glider confirmed that the glider would have been controllable if the pilot had not chosen to bail. However, the flight testing was conducted under controlled conditions, and the test pilot was fully aware of the modifications made to the exemplar glider to simulate the cable failure. Further, despite these modifications, the test pilot was still able to fully control the rudder, if necessary, during the flight test. Since the accident pilot did not have knowledge of the nature of the control problem and did not have the ability to gain full rudder control, his decision to bail out of the airplane was understandable.
Probable cause
The fatigue failure of the rudder cable due to the inadequate design of the rudder pedal system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA265
- Event ID
- 20120501X72635
- Case number
- CEN12LA265
- 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: c6454ed033d62a415fdf165b909f8e602e19d5fc788936c294d9e5050bf428ce; retrieved 2026-09-15T17:57:04.964Z.