NYC90LA114 · Rolladen-Schneider LSIF SAILPLANE LSIF SAILP
Rolladen-Schneider LSIF SAILPLANE LSIF SAILP · Accident: loss of control in flight while maneuvering
Event
- NTSB case
- NYC90LA114
- 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
- 0
- 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
Rolladen-Schneider LSIF SAILPLANE LSIF SAILP
- Aircraft type
- Rolladen Schneider LSIF SAILPLANE
- 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
- N17EW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Maneuvering
- First occurrenceThe 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Flight control, aileron › Jammed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD BEEN AIRBORNE FOR OVER TWO HOURS AND WAS MANEUVERED IN A LEFT TURN, IN A THERMAL WITH SOME TURBULENCE WHEN THE CONTROL STICK WENT FULL LEFT AND HE WAS UNABLE TO PULL THE STICK FREE AND REGAIN CONTROL OF THE GLIDER. HE JETTISONED THE CANOPY, EXITED THE GLIDER, AND DEPLOYED HIS PARACHUTE. THE GLIDER COLLIDED WITH TREES DURING ITS UNCONTROLLED DESCENT TO THE GROUND. POST CRASH EXAMINATION BY THE FAA DISCLOSED THE AILERON PUSH ROD ON THE LEFT WING WAS BENT IN AN UPWARD DIRECTION. THIS OCCURRED DURING DISASSEMBLY WHEN THE WINGS WERE REMOVED FOR STORAGE ON A TRAILER. THE TRAILING EDGE OF THE LEFT WING WAS ALLOWED TO DROP, WHICH BENT THE PUSH ROD UPWARD. WHEN THE CONTROL STICK WAS MOVED TO FULL LEFT, THE RIVET ON TOP OF THE AILERON PUSH ROD MADE CONTACT WITH THE COLLAR AROUND THE AILERON PUSH ROD AND THE AILERON CONTROL JAMMED.
Probable cause
JAMMED FLIGHT CONTROLS IN FLIGHT DUE TO A BENT AILERON PUSH-ROD.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC90LA114
- Event ID
- 20001212X23268
- Case number
- NYC90LA114
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 063dc442a84617061a1a54742a897cf527283b73b4f5134279550854c40121cc; retrieved 2026-09-21T23:52:31.071Z.