NYC84LA242

NTSB accident investigation · Schweizer SGS 2-33A · Thomaston, CT · July 15, 1984

Accident · No injuriesLimited investigationFinal report
Date
July 15, 1984, 16:30 local (21:30 UTC)
Place
Thomaston, CT
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N65805Schweizer SGS 2-33A
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
FAA report
19840715070279A
Case key
35707

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

In flight encounter with weatherCruise - normal
Weather condition - unfavorable windFactor
Compensation for wind conditions - not possiblePilot in command(cfi)Cause
Forced landingLanding - flare/touchdown
Directional control - not maintainedPilot in commandCause

Analysis

The glider made an off-arpt landing after encountering unexpected strong head winds in a rapidly changing flow of marineair. The acft cleared obtacles on final but yawed and landed in a crab condition damaging the fuselage and wing tip wheel.

Aircraft

Registration
N65805
Reported as
Schweizer SGS 2-33A
Category
Glider
Engine
unknown
Damage
Substantial damage
Flight
Instructional · Part 91
Registered owner
Connecticut Soaring Club
Airworthiness certificate
Standard, Normal
Departed
Waterbury, CT

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Certificate
Flight instructor
Medical
Unknown, Unknown
Seat
Rear
Flight hours
1,200 total · 600 in this make and model · 1,150 as pilot in command · 40 in the last 90 days · 3 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
180° at 20 knots, gusting 30
Visibility
5 statute miles
Lowest ceiling
None

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.