FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA051 · Beech S35

6 Jan 2002 · Angola, IN, United States

Beech S35 · Accident: loss of control in flight on approach

From Wexford County Airport (CAD) to Tri State Steuben County Airport (ANQ)

Report a problem

Event

NTSB case
CHI02LA051
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
Unknown
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

Beech S35

Aircraft type
Beechcraft 35
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
N7915K
Operator
Mark A. Thrasher · private individual
Onboard fatalities
Unknown
Route
From Wexford County Airport (CAD), Cadillac, MITo Tri State Steuben County Airport (ANQ), Angola, IN
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
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
Destroyed

Cause areas

  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Stall, encountered

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was destroyed by a post impact fire after it collided with terrain following loss of control while on final approach to land. The pilot reported that he was approximately 500 feet from the runway when the right wing stalled at 130 miles per hour and the aircraft rolled to the right 130 degrees. The pilot stated that he applied full power and rolled the aircraft upright, but it felt like the aircraft was being pushed straight down. He reported that they hit the ground almost flat, bounced, and then slid across the highway before coming to a rest. According to the pilot, he and his two passengers exited the airplane prior to it catching fire.

Probable cause

The pilot 's failure to maintain adequate airspeed and encountered a stall on approach to land. The low altitude on final approach was a factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA051
Event ID
20020110X00059
Case number
CHI02LA051
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, coordinates. 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: 0f3841c3b25428497bbcd472f3efa5122ce705fb3ac7ce60d2c95c7b074a5254; retrieved 2026-09-22T11:12:45.416Z.