FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW94LA151 · Rolladen-Schneider LS-4

8 May 1994 · ELBERT, CO, United States

Rolladen-Schneider LS-4 · Accident: loss of control in flight during landing

Report a problem

Event

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

Rolladen-Schneider LS-4

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
N4MN
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
Loss of control in flight
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 › Visual lookout, inadequate

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

NTSB narrative

DURING SHORT FINAL FOR LANDING IN A GLIDER, THE PILOT SAW A TOW PLANE TURNING RIGHT JUST OFF HIS RIGHT SIDE AND TOOK EVASIVE ACTION TO THE LEFT TO AVOID WHAT HE INTERPRETED TO BE AN IMMINENT COLLISION. DURING THIS ACTION THE LEFT WING OF THE GLIDER CONTACTED THE GROUND AND THE GLIDER IMPACTED ON THE LEFT WING AND NOSE. THE TOW PLANE MADE A NORMAL LANDING IN THE DESIGNATED TOW PLANE LANDING AREA. THE PILOT WAS UNAWARE THE GLIDER WAS BESIDE HIM. THE GLIDER RUNWAY AND TOW PLANE RUNWAY ARE NEXT TO EACH OTHER AND ARE A RUNWAY AND TAXIWAY USED AS A RUNWAY, AS PUBLISHED IN THE AIRPORT OPERATING INSTRUCTIONS. THE TOW PLANE WAS NOT EQUIPPED WITH A RADIO; THEREFORE, HE DID NOT HEAR THE GLIDER PILOT'S TRANSMITTED INTENTIONS.

Probable cause

INADEQUATE VISUAL LOOKOUT ON THE PART OF BOTH PILOTS. A FACTOR WAS POOR AIRPORT OPERATIONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW94LA151
Event ID
20001206X01283
Case number
FTW94LA151
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: 65e29d2c73d0505e79c095873370597a9195b99befe915dce078dd6afc3d526d; retrieved 2026-09-23T01:07:32.549Z.