FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD02LA009 · Schleicher ASW-19

3 Nov 2001 · Jersey Shore, PA, United States

Schleicher ASW-19 · Accident: in flight encounter with weather en route

From Ridge Soaring Gliderport (79N) to an unrecorded destination

Report a problem

Event

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

Schleicher ASW-19

Aircraft type
Schleicher ASW-19
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
N19KH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ridge Soaring Gliderport (79N), Unionville, PATo 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
En route · cruise
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 encounter with weather
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

  • Weather condition › Downdraft

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 returning from a cross country glider flight when the glider encountered a downdraft. The pilot was unable to maintain altitude, and could not reach the nearest airport. The pilot elected to land on a "canopy" of trees beneath the glider. The glider collided with the tree tops, and fell to the ground. The pilot reported that an annual inspection of the glider was completed on the day of the accident, and that there were no mechanical deficiencies. The weather reported at an airport about 20 miles east of the accident site, included clear skies with the wind from 270 degrees at 8 knots, gusting to 15 knots.

Probable cause

The pilot's in-flight encounter with weather, which led to a forced landing to unsuitable terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD02LA009
Event ID
20011204X02349
Case number
IAD02LA009
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: 00bb3c7803a7f27501cf8ee2400a194c6f367d025dfb674c2e8fab7718c06e82; retrieved 2026-09-22T11:27:15.104Z.