LAX01LA038 · Schweizer SGS 1-36
Schweizer SGS 1-36 · Accident: loss of control in flight during an emergency descent
From Skylark Airport (CA89) to an unrecorded destination
Event
- NTSB case
- LAX01LA038
- 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
Schweizer SGS 1-36
- Aircraft type
- Schweizer SGS-1
- 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
- N3621R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Skylark Airport (CA89)To 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
- Emergency descent
- 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
- Pilot in command › Airspeed(vs), not maintained
- Pilot in command › Altitude, not recognized
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After soaring for about 1 hour, the student pilot headed back to the departure airstrip for landing. Approaching the airstrip, the student misread his altimeter by 800 to 1,000 feet and initiated a circle to lose altitude. Midway through the turn the student realized his error and noted that he was, in fact, low whereupon he headed directly back toward the airstrip. The glider continued to lose lift, and the student did not initiate emergency procedures to make an off-site landing in nearby available fields. While attempting to stretch the glide, the glider stalled and collided with tree branches. Thereafter, it impacted the ground hard about 1/2 mile from the airstrip. The glider came to rest in the front yard of a trailer park. Nearly 2 months prior to the accident flight, the student's flight instructor authorized the student to fly the glider in solo flight.
Probable cause
The pilot's misjudged altitude approaching the airstrip and his failure to maintain airspeed resulted in the glider's collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA038
- Event ID
- 20001212X22302
- Case number
- LAX01LA038
- 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: 221d3809a49835df461a473276c69bbc7d9ab40b1e63cfbbea22d61f0c6cf591; retrieved 2026-09-21T10:20:03.101Z.