I.C.A.-Brasov (Romania) IS 29D accident near Avenal, California, May 19, 2018
On May 19, 2018, a 1974 I.C.A.-Brasov (Romania) IS 29D (glider), registered N38ES, was destroyed in an accident during prior to flight near Avenal, California. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper installation of the wings onto the glider, which resulted in an in-flight wing separation. Contributing to the accident were the pilot's limited familiarity with the design and a lack of reliable assembly guidance.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 19, 2018
- Place
- Avenal, California · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- I.C.A.-Brasov (Romania) IS 29D D, built 1974
- Registration
- N38ES · no longer on the register · serial 38
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot of the glider and his co-owner had jointly purchased the 44-year-old Romanian-manufactured glider, which was last flown about 7 years before the sale. About 3 months after purchase, the pilot completed an annual inspection of the glider. About 2 months later, the glider was moved to the soaring club's home airport, where the pilot and co-owner, with help from a third club member, assembled the glider for the first time. The pilot held a mechanic certificate with airframe, powerplant, and inspection authorization ratings, and was said by colleagues to be a competent and thorough mechanic. The accident flight was the first flight since assembly. About 1 hour after being towed aloft and released, the pilot indicated via radio that all was well and that he planned to continue flying. There was no further communication from the pilot. When he had not returned about 5 hours later, two club pilots departed to conduct an aerial search and subsequently located the wreckage. Examination of the accident site revealed that both wings separated from the fuselage in-flight and that the pilot had unsuccessfully attempted to parachute to safety. No location or tracking data was available to determine the flight track or altitude history for the flight. Examination and analysis of the wing attach mechanism revealed that the wings had not been properly installed and secured before the flight. Email and witness information indicated that, during the wing installation, the pilot had some doubt whether he had properly secured the wings and had called the previous owner of the glider to obtain his input. The pilot's conclusion from that conversation was that the wings were secured properly and that no additional action was needed. Although some of the attach hardware did not appear to be in accordance with the manufacturer's parts catalog, which may have interfered with the installation of the wings, the effect of this hardware on the installation process could not ultimately be determined. Access to the attach mechanism during wing installation was via an approximate 2-inch diameter cutout in the fuselage skin, which provided a partial view of the assembly when installed. With basic knowledge of the wing securing design and mechanism, the pilot should have been able to readily discern whether proper wing security had been achieved. Both individuals who assisted with the wing installation reported that they did not recall any abnormalities or indications of significant difficulty with the process. They both reported that a post-installation functional check of the flight controls was satisfactory; however, the flight control system design was such that the fuselage-to-wing control link connections could be successfully made despite the improper installation of the wings. This likely provided the pilot a false positive indication of the integrity of the wing installation, reinforcing his conclusion that the wings were properly installed. Despite the incomplete and incorrect assembly, the friction resulting from the partial engagement of the attach mechanism was sufficient to hold the wings in place for at least an hour of flight. Several factors decreased the potential for ensuring that the wings were properly installed and secured; the manufacturer no longer produced or supported any gliders, precluding any direct assistance to the pilot/co-owner; the only written assembly guidance available was of poor visual and technical quality and provided only generic assembly information in poorly-translated text; and the previous owner did not live nearby and there were only two other of the manufacturer's gliders registered in the US, which significantly limited alternate information sources for the pilot. Despite the scarcity of accessible, quality assembly guidance, with the wings uninstalled, a person could access and operate the attach mechanism to determine proper assembly indications. There was no evidence that the pilot or either of the other two persons who helped install the wings ever conducted such an exercise. Additionally, the pilot's chronic back pain restricted his ability to physically examine, manipulate, and work on the glider. However, the simplicity of the design, combined with the pilot's mechanic certification and his reported mechanical skills, should have enabled him to readily determine and accomplish the procedures for the proper installation of the wings as well as to accurately verify their proper installation. In addition, despite the criticality of proper wing installation, and his explicitly-expressed uncertainty as to whether he had properly accomplished that task, the pilot did not remove the wings and re-examine the hardware and structure in order to develop a better understanding of the design, and then re-attempt the process, in order to ensure that the wings were properly installed. The pilot's toxicology test results revealed the presence of hydrocodone, an opiate (narcotic) pain relief medication. While the use of the medication would not have resulted in the wing separation, it could not be determined the effect on his ability to successfully escape the failing glider. Whether he used the medication during the period when he inspected and assembled the glider could not be determined. The wing separation altitude and sequence the resulting glider dynamics, and the effects of these factors on the pilot's ability to execute an escape could not be determined.
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
- Aircraft maintenance event during prior to flight
- Aircraft inspection event during prior to flight
- Part(s) separation from AC during unknown defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incomplete action › Pilot
- cause Aircraft › Aircraft structures › Wing structure › Attach fittings (on wing) › Incorrect use/operation
- factor Personnel issues › Experience/knowledge › Knowledge › Knowledge of equipment › Owner/builder
- factor Organizational issues › Support/oversight/monitoring › Documentation/record keeping › (general) › Manufacturer
Pilot
- Certificate: private
- Ratings: single-engine land; rotorcraft: glider
- Flight time: 601 hours in all; 1 in this make and model
- Medical certificate: BasicMed
- Seat: sngl
- Injury: fatal
The aircraft
- Seats: 1
- Landing gear: fixed
The flight
- Departed from: CA69 Avenal CA at 8:37 pm
- Destination: CA69 Avenal CA
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
17 documents, released by the NTSB on December 10, 2019. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Metars | PDF, 1 page | View Download |
| 3 | Record of Multiple Conversations | PDF, 2 pages | View Download |
| 4 | Record of Communication Co-owner | PDF, 2 pages | View Download |
| 5 | Co-owner Assembly Statement | PDF, 2 pages | View Download |
| 6 | Assembly Statememt - Assistant | PDF, 1 page | View Download |
| 7 | Record of Conversation - Owner of Other Lark | PDF, 2 pages | View Download |
| 8 | Record of Communication - Pilot's Wife | PDF, 1 page | View Download |
| 9 | NTSB Assembly Q&a | PDF, 4 pages | View Download |
| 10 | Site and On-scene Information | PDF, 24 pages | View Download |
| 11 | Airframe Examination | PDF, 18 pages | View Download |
| 12 | Owners' Sailplane Tools | PDF, 5 pages | View Download |
| 13 | Flight Manual Excerpts | PDF, 6 pages | View Download |
| 14 | Aircraft Documents | PDF, 3 pages | View Download |
| 15 | Pilot Logbook Excerpts | PDF, 6 pages | View Download |
| 16 | Toxicological Report | PDF, 1 page | View Download |
| 17 | Partial Wreckage Release | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
