FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA00LA148 · Schweizer SGS 2-33

6 May 2000 · Jacksonville, FL, United States

Schweizer SGS 2-33 · Accident: loss of control in flight during landing

From 23J to an unrecorded destination

Report a problem

Event

NTSB case
MIA00LA148
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-33

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
N5738S
Operator
Unknown
Onboard fatalities
Unknown
Route
From 23JTo 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
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
Loss of control in flight
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
Stall/mush; 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 › Airspeed(vs), not maintained
  • Pilot in command › Distance/altitude, misjudged

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot stated that he was performing steep turns to dissipate altitude and land, but ended up being low, with wires impeding his path of flight. The student further stated that as he maneuvered to avoid the wires, the glider lost lift, and fell towards the ground. The student said he then lowered the nose to avoid landing empennage first, but during the landing the glider was damaged. An FAA inspector examined the accident aircraft, and stated that during the landing the left wing hit a tree and the spar was damaged.

Probable cause

the student pilot's misjudgment of the aircraft's altitude and subsequent maneuver to avoid an obstacle, that resulted in a loss of airspeed, an inadvertent stall, and an inflight loss of control, which resulted in damage to the aircraft during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00LA148
Event ID
20001212X21063
Case number
MIA00LA148
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: c9836da761b30c134d5ef3d6276d4c4f10b3bbbc39fbd2ce26091a9970019c24; retrieved 2026-09-22T12:55:12.873Z.