FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA95LA069 · Scheibe Flugzeugbau BERGFALKE II-55 BERGFALKE

18 Mar 1995 · Bozeman, MT, United States

Scheibe Flugzeugbau BERGFALKE II-55 BERGFALKE · Accident: undershoot on approach

Report a problem

Event

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

Scheibe Flugzeugbau BERGFALKE II-55 BERGFALKE

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
N5924
Operator
Stradley, Roger · private individual
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
Approach · VFR pattern base
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
Undershoot
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 › Distance/altitude, misjudged

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

NTSB narrative

WHILE IN THE TRAFFIC PATTERN FOR LANDING, THE PILOT STATED THAT HE RELIED ON THE ALTIMETER TO DETERMINE ELEVATION, EVEN THOUGH HE FELT THAT HE WAS LOW. WHILE TURNING BASE TO FINAL APPROACH, THE PILOT REALIZED THAT HE WAS TOO LOW AND WAS NOT GOING TO MAKE THE RUNWAY. DURING A LEFT TURN TO MANEUVER TO AN ACCESS ROAD, THE LEFT WING CONTACTED THE GROUND AND THE GLIDER SPUN AROUND BEFORE COMING TO REST. AFTER THE ACCIDENT, THE PILOT STATED THAT HE DID NOT GET THE CURRENT ALTIMETER SETTING FROM THE FSS BEFORE LANDING, AND NOTED THAT THE ALTIMETER READING WAS 170 FT HIGHER THAN FIELD ELEVATION.

Probable cause

THE PILOT MISJUDGED HIS ALTITUDE AND DISTANCE FROM THE RUNWAY. A FACTOR WAS THE PILOT'S FAILURE TO OBTAIN THE CURRENT ALTIMETER SETTING.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA95LA069
Event ID
20001207X03200
Case number
SEA95LA069
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: 6b9a3127a695e4804b3e87a5087db3c3fa0f60a62f822ea428055c8988ce36c6; retrieved 2026-09-23T00:08:35.566Z.