FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC95FA105 · Beech BE60

9 May 1995 · Olney, IL, United States

Beech BE60 · Accident: in flight collision with terrain/water on approach

From Dixon Municipal Charles R. Walgreen Field (C73) to an unrecorded destination

Report a problem

Event

NTSB case
NYC95FA105
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
2 · 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
Instrument Meteorological Cond

Beech BE60

Aircraft type
Beechcraft 60
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
N81TS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Dixon Municipal Charles R. Walgreen Field (C73), Dixon, ILTo 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 · IFR final 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
Destroyed

Cause areas

  • Pilot in command › IFR procedure, improper
  • Pilot in command › Minimum descent altitude, not complied with
  • Pilot in command › Missed approach, not performed

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

NTSB narrative

THE PILOT WAS CLEARED FOR THE LOCALIZER RUNWAY 11 APPROACH. THE AIRPLANE IMPACTED IN AN OPEN FIELD APRX 1 MILE NE OF THE AIRPORT AND APRX 600 FT LEFT OF THE EXTENDED CENTERLINE OF THE DEPARTURE END OF THE RUNWAY. A WITNESS SAW THE AIRPLANE AT A LOW ALTITUDE, AND STATED 'IT WAS FOGGY,' AND HE DID NOT SEE THE AIRPLANE UNTIL IT WAS DIRECTLY OVER HIS HEAD. THE WITNESS STATED THAT HE SAW THE AIRPLANE FOR ABOUT '3 SECONDS,' AT AN ALTITUDE OF 'BETWEEN 50 AND 100 FEET ABOVE THE GROUND,' AND IT DID NOT SOUND LIKE IT WAS HAVING 'MECHANICAL DIFFICULTY.' THE AIRPLANE TURNED LEFT (NORTH), AND STRUCK THE GROUND WITH THE LEFT WING. THE PUBLISHED MISSED APPROACH CALLED FOR A CLIMBING 'RIGHT TURN.' THE OLNEY AIRPORT AUTOMATED WEATHER OBSERVING SYSTEM (AWOS) WAS OPERATING AND CURRENT AT THE TIME OF THE ACCIDENT, BUT COULD ONLY BE OBTAINED BY TELEPHONE; HENCE ATC COULD NOT PROVIDE THE PILOT WITH THE CURRENT AWOS INFORMATION. THE PILOT WAS PROVIDED THE EVANSVILLE, INDIANA (EVV) WEATHER; 1,200 SCATTERED, MEASURED 4,500 OVERCAST, VISIBILITY 5 MILES, LIGHT RAIN AND FOG. EVANSVILLE WAS LOCATED APRX 20 MILES SE OF OLNEY. THE LOCAL (AWOS) WEATHER WAS; PARTIAL OBSCURATION, 100 FEET OVERCAST, VISIBILITY 3/4 MILE.

Probable cause

The pilot's improper IFR procedures by descending below the minimum descent altitude and not executing the published missed approach procedures. A factor in thE accident was the low overcast and fog conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC95FA105
Event ID
20001207X03521
Case number
NYC95FA105
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: 45dcd89c6eecf8e9ad320135d88b22a403374ac5cd56b3fd921ab29f1054124c; retrieved 2026-09-20T23:47:07.530Z.