FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07FA009 · Beech 95-B55

26 Oct 2006 · Lawrenceville, IL, United States

Beech 95-B55 · Accident: in flight collision with terrain/water on approach

From Indianapolis International Airport (IND) to Lawrenceville Vincennes International Airport (LWV)

Report a problem

Event

NTSB case
CHI07FA009
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
1 · 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 95-B55

Aircraft type
Beechcraft 55
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
N1832N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Indianapolis International Airport (IND), Indianapolis, INTo Lawrenceville Vincennes International Airport (LWV), Lawrenceville, 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
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
In flight collision with terrain/water
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 › Judgment, improper
  • Pilot in command › Minimum descent altitude, below

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 operating on an instrument rules flight plan when it impacted trees and terrain during a non precision approach to the destination airport in night instrument meteorological conditions. About 1 1/2 hours before the accident, the pilot received a weather briefing that indicated expected sky conditions along the route were overcast 300-600 feet above ground level (AGL) and a present sky condition at the destination airport of an overcast ceiling at 400 feet AGL. The pilot did not file an alternate airport as required by Federal Aviation Regulations which require that the ceiling be at least 2,000 feet AGL for at least 1 hour before and for 1 hour after the estimated time of arrival. Sky conditions at the destination airport remained unchanged at the time the airplane was cleared for the approach. The approach minimum, for an aircraft with DME capability, was 410 feet above touchdown elevation. Radar track data for the airplane approach profile was consistent with a controlled approach. The wreckage path through the tree was consistent with a level flight attitude in a direction along the inbound approach course. Additionally, the airplane was configured with the landing gear extended and the flaps extended to 15 degrees, a configuration consistent with an initial approach configuration. No anomalies were noted with the airplane that would have precluded normal operation. Advisory Circular information cites the operation pitfalls in aeronautical decision making of "Get-There-Itis" and Duck-Under Syndrome." The pilot received an Authorization For Special Issuance Of A Medical Certificate, which stipulates the following conditions for its validity, "You must promptly report any adverse changes in your medical condition or medications to the FAA Medical Appeals Section, AAM-313. You are cautioned to abide by Title 14 of the Code of Federal Regulations (CFR's), Section 61.53, relating to physical deficiency, medication, or treatment. Because of your cardiac history, operation of aircraft is prohibited at any time new symptoms or adverse changes occur or if you experience side-effect, or require a change in medication." The pilot was reportedly having palpitations for 20 minutes at a time for the two months prior to the accident and noted being "tired" within a week of the accident, but there is no evidence that he sought medical treatment for the fatigue or palpitations. The investigation could not determine if the pilot's physical condition was a factor in the accident flight.

Probable cause

The improper judgment by the pilot to conduct a flight to, and execute an approach to, an airport with weather conditions that were below the required minimums. Also causal was the pilot's continued descent below the approach minimum descent altitude. Contributing factors were the below approach landing weather minimums, the night light conditions, and the lack of a planned alternate airport by the pilot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07FA009
Event ID
20061030X01572
Case number
CHI07FA009
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2006-10-27.
  • API snapshot SHA-256: 8018d6469ae8b25f7460b109d72e62ad40ee4603eb1470839cd9524674b69a8e; retrieved 2026-09-20T17:00:52.074Z.