CHI83LA271 · Beech E18S
Beech E18S · Accident: in flight encounter with weather on approach
From 77D · Big Rapids, MI to an unrecorded destination
Event
- NTSB case
- CHI83LA271
- 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
- Charter & commuter
- 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 E18S
- Aircraft type
- Beechcraft 18
- 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
- N995H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 77D · Big Rapids, MITo 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 135: Air Taxi & Commuter
- 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 encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Tree(s)
- 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 › Distance, misjudged
- Pilot in command › Go-around, delayed
- Pilot in command › VFR flight into imc, continued
Approximate · Estimated position: the centre of Youngstown, OH, the place the record names. Not the accident site.
NTSB narrative
THE PLT HAD NOT OBTAINED A WX BRIEFING, BUT HAD GOTTEN INFO FROM ANOTHER COMPANY PLT WHO HAD FLOWN INTO THE DESTINATION ARPT EARLIER. DURING ARRIVAL, HE COULD SEE THE ROTATING BEACON & RWY LIGHTS THRU SOME FOG & ELECTED TO MAKE A VISUAL APCH. AT APRX 75 FT AGL ON FINAL APCH, THICKER FOG WAS ENCOUNTERED, BUT THE RWY LIGHTS WERE STILL IN SIGHT. THE PLT CONTINUED THE APCH UNTIL HE SAW HE WAS PASSING THE OPERATIONS BUILDING, THEN HE KNEW THERE WAS INSUFFICIENT RWY REMAINING TO STOP SAFELY, SO HE INITIATED A GO-AROUND. HOWEVER, HE WAS UNABLE TO CLEAR TREES OFF THE DEPARTURE END OF THE RWY. AFTER COLLIDING WITH THE TREES, THE ACFT WAS LANDED IN A FIELD WHERE IT SKIDDED APRX 150 YARDS TO A STOP WITHOUT INJURY TO THE PLT OR CARGO HANDLER.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI83LA271
- Event ID
- 20001214X43269
- Case number
- CHI83LA271
- 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: 0f9e35ee432810a91d6945c47c00d71e46491296debcec4f5aaff854279f114b; retrieved 2026-09-18T20:57:39.640Z.