LAX07CA154 · Burkhart Grob G103 Twin II
Burkhart Grob G103 Twin II · Accident: loss of control in flight on approach
From Minden-Tahoe Airport (MEV) to Minden-Tahoe Airport (MEV)
Event
- NTSB case
- LAX07CA154
- 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
Burkhart Grob G103 Twin II
- Aircraft type
- Grob G103
- 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
- N49443
- Operator
- Soar Minden
- Onboard fatalities
- Unknown
- Route
- From Minden-Tahoe Airport (MEV), Minden, NVTo Minden-Tahoe Airport (MEV), Minden, NV
- 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
- Approach · VFR pattern final
- 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/mush
- 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 › Stall/mush, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot stalled the glider and impacted the ground hard about 100 feet short of the 5,300-foot-long runway. The accident occurred while the certified flight instructor (CFI) observed his student perform the 4th landing following her initial solo flight. The CFI reported that his student's first three landings had been somewhat long. Before the student departed on her 4th flight, she stated to him that she would try to land shorter. The CFI reported that the glider appeared to be descending slowly, and when it was about 100 feet short of the approach end of runway 30 it stalled, rapidly descended, and impacted the ground. The wind was light and variable.
Probable cause
The pilot's failure to maintain an adequate airspeed, which led to an inadvertent stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA154
- Event ID
- 20070705X00880
- Case number
- LAX07CA154
- 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: 3ef9136ecab2ce32af6e4a1f38e22010e8b59a76ed44646462f9aef88eb3b6e8; retrieved 2026-09-21T18:31:16.562Z.