CHI84FA054 · Beech 77
Beech 77 · Accident: in flight encounter with weather en route
From James M. Cox Dayton International Airport (DAY) to James M. Cox Dayton International Airport (DAY)
Event
- NTSB case
- CHI84FA054
- 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
- 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 77
- Aircraft type
- Beechcraft 77
- 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
- N37253
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From James M. Cox Dayton International Airport (DAY), Dayton, OHTo James M. Cox Dayton International Airport (DAY), Dayton, OH
- 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
- En route · cruise
- 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
- 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
- Destroyed
Cause areas
- Pilot in command › Flight into known adverse weather, continued
- Wing › Ice
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCREW TOOK OFF ON AN IFR FLT FROM DAYTON TO PIQUA & SIDNEY, OH TO PRACTICE APCH'S, THEN THEY INTENDED TO RETURN TO DAYTON. THE COPILOT STATED THAT THEY ENTERED THE CLOUDS AT 700 TO 800 FT AGL & HE DID NOT SEE THE GROUND AGAIN ON THIS FLT. HE REPORTED THAT ICE BEGAN BUILDING ON THE ACFT UNTIL ON A DESCENT TOWARD PIQUA, WHEN REPORTEDLY, IT BEGAN DISSIPATING. A MISSED APCH WAS MADE AT PIQUA WITHOUT SEEING THE ARPT. THE COPILOT STATED THAT THEY WERE UNABLE TO GET A GOOD RATE OF CLIMB. AT 1258 EST, THE AIRCREW REQUESTED VECTORS BACK TO DAYTON (RATHER THAN TO CONTINUE TO SIDNEY) & ADVISED THAT THEY WERE ENCOUNTERING ICE & TURBULENCE. THEY WERE ISSUED A VECTOR, BUT APRX 30 SEC LATER, THEY ADVISED THAT THEY COULD NOT MAINTAIN THEIR ASSIGNED ALT OF 3000 FT. THEY WERE ADVISED THAT VECTORS COULD NOT BE PROVIDEDBELOW 3000 FT, BUT THE SIDNEY ARPT WAS AT THEIR 2 O'CLOCK POSITION AT LESS THAN A MILE. SHORTLY AFTER THAT, THE ACFT CRASHED IN A WOODED AREA APRX 1 1/2 MI WEST OF THE ARPT. REPORTEDLY, RAIN WAS ENCOUNTERED BETWEEN PIQUA & SIDNEY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI84FA054
- Event ID
- 20001214X45240
- Case number
- CHI84FA054
- 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: d9ccdf2ea8231026df7246c497fa33dd6f7d1dfaef389a7d0c347714a69455dc; retrieved 2026-09-21T05:46:17.800Z.