FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD01LA103 · Cessna U206G

2 Sept 2001 · Millersburg, OH, United States

Cessna U206G · Accident: overrun during landing

From Beach City Airport (2D7) to Millersburg, OH (no airport)

Report a problem

Event

NTSB case
IAD01LA103
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
Unknown
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

Cessna U206G

Aircraft type
Cessna 206
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
N579LD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Beach City Airport (2D7), Beach City, OHTo Millersburg, OH (no airport)
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
Landing · landing roll
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

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

NTSB narrative

The pilot had no braking effectiveness after landing to the west on a wet 1,000 foot long grass runway. The pilot said he misjudged the distance the airplane needed to stop and went off the runway into a corn field. Weather reported at an airport about 19 nautical miles away included winds from 060 degrees at 4 knots. The pilot reported that the wind was calm at the time of the accident. Interpolation of performance data found in the POH revealed that with the airplane's flaps extended to 40 degrees, power off, and maximum braking applied a on a dry, grass runway, the airplane would have a ground roll of approximately 1,068 feet in calm wind. With a 4-knot tailwind, the airplane 's ground roll would be approximately 1,260 feet. When asked how the accident could have been prevented, the pilot said, "Could have powered up and went around." The pilot also reported that there were no mechanical deficiencies with the airplane.

Probable cause

The pilot's misjudgment of speed and distance, which resulted in an overrun during landing. Factors were the short, wet, grass runway, and his failure to do a go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD01LA103
Event ID
20010914X01945
Case number
IAD01LA103
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: d61e20820f4bdf40397387c45f1cf6754ada3abdd44e8a54e90b95720cf36473; retrieved 2026-09-22T11:35:54.253Z.