CHI08FA053 · Beech V35B
Beech V35B · Accident: loss of control in flight on approach
From Clermont County Airport (I69) to Abraham Lincoln Capital Airport (KSPI)
Event
- NTSB case
- CHI08FA053
- 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
- 3 · 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
- Instrument Meteorological Cond
Beech V35B
- 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
- N17784
- Onboard fatalities
- Unknown
- Route
- From Clermont County Airport (I69), Batavia, OHTo Abraham Lincoln Capital Airport (KSPI), Springfield, IL
- 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 · IFR initial 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
- 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 › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed on the cross-country flight under visual flight rules and obtained flight following from several air traffic control facilities located along the intended route of flight. While enroute, he obtained an instrument flight rules (IFR) clearance after encountering instrument conditions at 2,500 feet. The accident flight was provided radar vectors to intercept the instrument landing system (ILS) runway 4 approach for the intended destination. Radar track data showed the accident airplane passed through the localizer centerline at 2,400 feet and then it made a rapid right turn back toward the centerline. The airplane then performed a series of rapid descents and climbs, and several course reversals over a period of 75 seconds. During this time period, the pilot reported having an unspecified problem and his last communication was "I can go out now ... flying eastbound." A witness reported seeing the accident airplane flying about 20 feet above the ground before it entered a steep climb. He then heard an increase in engine noise, which was followed by a loud boom. The airplane impacted about 3.5 miles outside the locator outer marker along the localizer centerline. Instrument meteorological conditions prevailed at the destination airport with a ground visibility of 2-1/2 miles in mist and a 500 foot overcast ceiling. Based on available information, the pilot had not recorded an instrument approach in over 6 months and his last flight review was completed more than 24 months before the accident. No additional dual flight instruction or instrument proficiency checks were uncovered during the investigation. A review of the maintenance records found no history of unresolved airworthiness issues. Examination of the recovered wreckage revealed no evidence of a pre-impact mechanical malfunction.
Probable cause
The loss of control during an instrument approach due to spatial disorientation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08FA053
- Event ID
- 20080102X00007
- Case number
- CHI08FA053
- 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: 93d062366696351c0e295de111b00bf70a27952077c415b2b062ca5fb6be329a; retrieved 2026-09-20T16:03:10.966Z.