SEA04LA079 · SZD Jantar 42-1
SZD Jantar 42-1 · Accident: forced landing during an emergency descent
From Ken Jernstedt Airfield (4S2) to 4S2
Event
- NTSB case
- SEA04LA079
- 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
SZD Jantar 42-1
- Aircraft type
- SZD JANTAR 42
- 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
- N272AS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ken Jernstedt Airfield (4S2), Hood River, ORTo 4S2
- 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
- Forced landing
- 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 › In-flight planning/decision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was beginning to work his way north toward his destination landing site, when he encountered an area where there was not sufficient lift to keep the glider at an altitude that would allow him to continue along his intended route. As the glider descended, the pilot headed toward an area where he knew there was a small airstrip that he would be able to land on. Once the aircraft descended to a height of about 300 feet above the ground, the pilot realized that he could not safely continue en route, so he made the decision that he should commit to the best nearby landing area he could find. Since he was at that time over terrain that was almost completely covered by trees, he selected an area of young/small trees, and flew the glider onto them at a very slow airspeed in an attempt to execute a controlled crash landing. After impacting the trees, the glider slid to the ground, and the pilot exited in a normal manner.
Probable cause
The glider pilot's inadequate en route planning, which resulted in a forced landing in an area without suitable landing terrain. Factors include no suitable landing terrain in the area where the pilot found it necessary to execute a forced landing, and trees at the location where the aircraft came in contact with the terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04LA079
- Event ID
- 20040505X00558
- Case number
- SEA04LA079
- 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: c84379ed081ea3c185f4731b4a3c7548a2596df0893a678ec9260cf69454fe53; retrieved 2026-09-22T07:37:26.623Z.