LAX04CA270 · Pdps PZL-Bielsko SZD-50-3
Pdps PZL-Bielsko SZD-50-3 · Accident: in flight collision with object during landing
From Lone Pine/Death Valley Airport (O26) to Lone Pine/Death Valley Airport (O26)
Event
- NTSB case
- LAX04CA270
- 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
Pdps PZL-Bielsko SZD-50-3
- Aircraft type
- Pdps PZL Bielsko SZD-50
- 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
- N19SZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lone Pine/Death Valley Airport (O26), Lone Pine, CATo Lone Pine/Death Valley Airport (O26), Lone Pine, CA
- 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
- Landing
- 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
- In flight collision with object
- 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 › Clearance, misjudged
- Pilot in command › Proper alignment, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The glider collided with a tree during landing, and the right wing was torn from the fuselage. After clearing a set of power lines, the glider was 15 feet agl. The pilot saw a tree, and the glider drifted to the right of the runway centerline. He misjudged the clearance between the tree and the wing, and a collision occurred. The glider spun 270 degrees from its original flight path before coming to rest. The pilot recommended flying a higher approach to prevent future accidents. The pilot noted no mechanical malfunctions with the glider prior to the accident.
Probable cause
the pilot failed to maintain runway alignment, and misjudged the clearance between the tree and the wing resulting in a collision with the tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04CA270
- Event ID
- 20040730X01116
- Case number
- LAX04CA270
- 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: 47fc6d2e57a64537695a9f498c435d04b5a187f241554d396c4fb834ef5a50db; retrieved 2026-09-22T07:02:56.610Z.