FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12FA378 · IAR Brasov IS-28B2

17 Jun 2012 · Wallis, TX, United States

Greater Houston Soaring Association IAR Brasov IS-28B2 · Accident: abrupt maneuver during takeoff

From GHSA-Wallis Glideport (TE71) to GHSA-Wallis Glideport (TE71)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's fatalities. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN12FA378
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
4 · all aircraft and ground Possible conflict
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

IAR Brasov IS-28B2

Aircraft type
Iar Brasov IS-28
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
N6388V
Onboard fatalities
Unknown
Route
From GHSA-Wallis Glideport (TE71), Wallis, TXTo GHSA-Wallis Glideport (TE71), Wallis, TX
Aircraft age
About 13 years (built 1999)
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
Takeoff
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
Abrupt maneuver
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 oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A witness reported that, before launch, the pilot installed the tail dolly on the glider, and the ground crew then assisted him pull the glider near the normal launch position about midfield. Another witness reported that the pilot then assisted the passenger and the lapchild into the front seat of the glider and ensured that the restraints were properly latched and snug. The pilot then got in the rear seat, and he secured his own lap belt and shoulder straps. Several witnesses noticed that, after takeoff, the tail dolly was still attached to the glider, and the glider operations dispatcher made a radio call to "abort...abort...abort." The takeoff continued, and several witnesses observed both the tow plane and the glider lift off normally. When the tow plane was about 50 feet above ground level (agl), the glider suddenly pitched nose up about 45 degrees, and the tow plane disconnected from the glider and turned left. The glider subsequently turned right and continued to climb steeply until it was about 150 to 200 feet agl. The glider then began what appeared to be a controlled left turn with the nose level. While the glider was turning, witnesses saw it suddenly pitch nose down and descend. Wreckage evidence showed that the glider impacted terrain at a 30- to 45-degree nose-down angle. The glider's rapid, near-vertical descent is consistent with the pilot's loss of control of the glider because of an aerodynamic stall. An on-scene examination of the wreckage revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.

Two other pilots reported that they had previously inadvertently made takeoffs in the same model glider with the tail dolly still attached. Both of them reported that the flight characteristics did not change in that condition. A postaccident weight and balance calculation showed that the glider's weight and balance were still within the allowable range with the addition of the tail dolly.

At the time of the accident, the pilot had cardiac hypertrophy and severe coronary artery disease. His physician had examined him 3 days before the accident and had ordered several tests. It is likely that, if the pilot had undergone a stress test, he would have failed it, and further evaluation would likely have led to a coronary artery bypass graft operation in the following few days. The pilot's wife reported that the pilot had spent the day of the accident engaging in strenuous activity, including teaching students and moving the glider around. Given the extent of coronary artery disease found on the pilot's autopsy, it is likely that the pilot's sudden awareness of the emergency situation (takeoff with the tail dolly attached) and physical exertion before the flight led to an acute coronary event and that this event contributed to his loss of control.

Probable cause

The pilot’s failure to maintain adequate airspeed during an emergency situation, which resulted in an aerodynamic stall and subsequent impact with terrain. Contributing to the accident was the pilot’s acute coronary event, which resulted from his severe coronary artery disease, prior physical exertion, and the stress of the emergency situation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12FA378
Event ID
20120618X10736
Case number
CEN12FA378
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. 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: a3abf626f662bfe6af27d2f912fd57d06354e7f5d71dd4df5acaa8e5888be2f1; retrieved 2026-09-13T22:27:06.956Z.