CHI00LA203 · Weatherly 201B
Weatherly 201B · Accident: overrun during takeoff
From Private airstrip to an unrecorded destination
Event
- NTSB case
- CHI00LA203
- 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
Weatherly 201B
- Aircraft type
- Weatherly 201
- 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
- N1261W
- Operator
- Don Younglove
- Onboard fatalities
- Unknown
- Route
- From Private airstripTo 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 137: Agricultural
- 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
- Takeoff
- 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
- Overrun
- 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 › Preflight planning/preparation, inadequate
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane overran the runway during takeoff. The pilot reported he was not aware that the wind had shifted prior to takeoff and did not recognize it until it was too late. The takeoff was being made on runway 09 (2,400 feet by 60 feet, paved). The pilot reported the winds had shifted from the east to west to south. Winds reported at Bloomington, Illinois, 45 miles south of the accident site, 15 minutes after the accident, were from 270 degrees at 9 knots. The airplane traveled approximately 300 feet off the departure end of the runway and came to rest in a cornfield.
Probable cause
the pilot's preflight planning was inadequate which resulted in taking off in the wrong direction on the runway. Factors associated with the accident were the tailwind condition and the crop that the airplane contacted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00LA203
- Event ID
- 20001212X21394
- Case number
- CHI00LA203
- 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: 10056d7a8e956b8e320920c8601e213d04ccbb572c6e271eccbbc2a0d5a33698; retrieved 2026-09-22T12:40:50.771Z.