FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA196 · Elan DG 300

7 Jun 2005 · Jean, NV, United States

Elan DG 300 · Accident: loss of control in flight during initial climb

From Jean Airport (0L7) to 0L7

Report a problem

Event

NTSB case
LAX05LA196
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

Elan DG 300

Aircraft type
Elan DG-300
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
N303LV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jean Airport (0L7), Jean, NVTo 0L7
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
Initial climb
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
Stall
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

  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Glider/tow release, delayed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Shortly after takeoff, the glider dragged a wing and collided with the runway. The glider pilot said he discussed the takeoff with the tow plane pilot and requested a climb at 65, though he did not specify whether the speed was in knots or miles per hour. The tow plane departed and climbed at an airspeed that was lower than what was discussed by himself and the glider pilot. The glider pilot realized airspeed was not sufficient and attempted to release from the tow but missed the tow release handle. On the second attempt, the glider pilot released from the tow plane at approximately 100 feet above ground level (agl) with little airspeed remaining. The glider then began a slow roll to the right and the pilot realized that the glider had stalled. He applied forward pressure on the stick in an effort to regain airspeed. Shortly thereafter, the right wing impacted the terrain and was dragged forward. The fuselage then descended and impacted the terrain on the main landing gear. The main landing gear structure failed as result of the impact, and the glider slid across the ground on the fiberglass fuselage. The pilot stated that the glider had no mechanical failures or malfunctions during the flight. A witness to the accident reported that after both the glider and tow plane had lifted off, the tow plane began a very steep climb. The tow plane was considerably higher than the glider with a significant amount of slack in the towrope. The glider then moved slightly to the left, which corrected for the slack. The glider and tow plane flew at a level altitude briefly, but then the tow plane became considerably higher than the glider. The tow plane continued to climb and the glider remained configured in a straight and level attitude. About 100 feet agl, the glider released from the towrope and appeared to be heading straight ahead to land. As the glider descended towards the runway, the right wing dipped down approximately 30 to 40 degrees. The glider continued to descend until the right wing touched the terrain. According to the data retrieved from the recorder installed in the glider, the highest altitude that the glider reached was approximately 130 feet agl; the highest airspeed obtained was approximately 45 knots. The glider's flight manual states that the glider will exhibit certain stall characteristics while in specific attitudes. In level and turning flight, at stall speed, the glider will begin to mush; there is no abrupt stall and the ailerons will remain effective. When following the recommended manufacturer specified procedure stall recovery is possible in less than 65 feet.

Probable cause

the glider pilot's failure to release from the towline in a timely manner, and to maintain adequate airspeed. Contributing to the accident was the glider pilot's failure to recognize and correctly recover from the stall in a timely manner, and the inadequate airspeed flown by the tow plane pilot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA196
Event ID
20050616X00789
Case number
LAX05LA196
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, 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: 4b3b399f6fe0443de7f68df1d7cc8bc202c4c08b1a0de34840fc90ccd9ee984a; retrieved 2026-09-21T19:00:17.078Z.