FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI98LA018 · Bellanca 7GCBC

18 Oct 1997 · Rapid City, SD, United States

Bellanca 7GCBC · Accident: loss of control in flight on approach

Report a problem

Event

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

Bellanca 7GCBC

Aircraft type
Bellanca 7
Category
Airplane
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
N88119
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
Approach · VFR pattern final
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
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(vso), not maintained
  • Pilot in command › Stall, inadvertent
  • Weather condition › Windshear

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

NTSB narrative

The pilot said that the winds at the destination airstrip 'appeared to be light on the ground and out of the north- northwest, judging by the windsock. I entered a normal traffic pattern, rolled out on final and flew final at my normal approach speed with full flaps. At approximately 100-120 feet, I hit a windshear. The wind either stopped or abruptly became a tailwind. The aircraft quickly settled.' The pilot said that he rapidly applied power, but hit the ground before it could take effect. A witness on the ground, near the location of the accident, noticed that the wind was changing directions, 'sometimes from the northwest, west, and east.' The witness said that about 100 feet above the ground, 'the airplane appeared to almost stop then drop nearly vertical.' The witness said that he heard the power being added before the airplane struck the ground. Examination of the wreckage revealed no anomalies.

Probable cause

the windshear, the pilot's inability to maintain the airplane's landing approach speed, and the inadvertent stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI98LA018
Event ID
20001208X08976
Case number
CHI98LA018
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: d4614c205b0a9361f09629b229fe0b90ee993820a26fd1f3c6d7a0b9edad8414; retrieved 2026-09-21T21:06:26.608Z.