CHI95LA184 · Beech B23
Beech B23 · Accident: loss of control in flight during initial climb
From 4V9 to Montevideo Chippewa County Airport (MVE)
Event
- NTSB case
- CHI95LA184
- 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech B23
- Aircraft type
- Beechcraft 23
- 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
- N7632R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 4V9To Montevideo Chippewa County Airport (MVE), Montevideo, MN
- 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
- Initial climb
- 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
- 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
- Stall
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT PRIOR TO DEPARTING ON RUNWAY 30 HE OBSERVED THE WINDSOCK INDICATING WINDS FROM ABOUT 190 DEGREES AT 15 GUSTING TO 19 KNOTS . HE BELIEVED HE WOULD HAVE 'A LEFT FRONT QUARTERING WIND.' HE STATED THAT IN RETROSPECT 'THIS WAS NOT THE CASE.' HE INITIATED THE DEPARTURE WITH TEN DEGREES OF FLAPS WITHOUT USING THE ADDITIONAL RUNWAY AVAILABLE IN THE DISPLACED THRESHOLD. WHEN THE AIRPLANE BECAME AIRBORNE, IT VEERED RIGHT. THE PILOT ATTEMPTED TO ACCELERATE AT A LOW ALTITUDE TO NO AVAIL. HE ELECTED TO ATTEMPT TO LAND THE AIRPLANE. IT IMPACTED THE TERRAIN SUSTAINING SUBSTANTIAL DAMAGE TO THE FORWARD FUSELAGE, LEFT WING, AND EMPENNAGE. HE REPORTED THAT THE ENGINE WAS RUNNING NORMALLY THROUGHOUT THE ACCIDENT SEQUENCE.
Probable cause
the pilot's selection of the wrong runway for takeoff, and his failure to compensate for the tailwind. A factor was the tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA184
- Event ID
- 20001207X03666
- Case number
- CHI95LA184
- 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: 097b9c08de6d8ded60188ab39f5c1d2d144719ffdd7d15a76cdb38c0bc5bf661; retrieved 2026-09-21T13:14:00.388Z.