IAD00LA046 · Schweizer SGS 2-33A
Schweizer SGS 2-33A · Accident: overrun during landing
From Sterling Airport (3B3) to an unrecorded destination
Event
- NTSB case
- IAD00LA046
- 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 2-33A
- Aircraft type
- Schweizer SGS-2
- 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
- N1225S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sterling Airport (3B3)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
- Landing · flare/touchdown
- 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
- Overrun
- 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 › Proper touchdown point, not attained
Approximate · Estimated position: the centre of Sterling, MA, the place the record names. Not the accident site.
NTSB narrative
The pilot entered a right traffic pattern for Runway 16. At the midfield point, on the downwind leg of the traffic pattern, the glider was 1,000 feet above the ground, and the pilot extended the spoilers. The base leg of the traffic pattern was performed about 700 feet above the ground. When the glider was turned onto the final approach, the right wing was kept down and left rudder was applied to initiate a slip. The pilot determined the slip was ineffective, rolled the glider level for a moment, and then entered the slip again. The glider touched down '90% down the runway,' and traveled off the end. The glider became airborne again, turned to the right, and touched down a second time on a road. The glider impacted several road signs with both wings, before turning 180 degrees and coming to rest. The pilot stated that the reason for the accident was an 'ineffective slip.'
Probable cause
The pilot's failure to attain a proper touchdown point.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD00LA046
- Event ID
- 20001212X21022
- Case number
- IAD00LA046
- 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: 645d2d34c8a0b11e35fb2910ceb45e3ead1b41570dd479f06944d00c5b902b82; retrieved 2026-09-22T12:51:25.655Z.