FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD96LA143 · Cessna T210N

2 Sept 1996 · Wadsworth, OH, United States

Cessna T210N · Accident: overrun during landing

From Wadsworth Municipal Airport (3G3) to Weltzien Skypark Airport (15G)

Report a problem

Event

NTSB case
IAD96LA143
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

Cessna T210N

Aircraft type
Cessna 210
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
N6614Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wadsworth Municipal Airport (3G3), OHTo Weltzien Skypark Airport (15G), 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
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 › Distance/speed, misjudged
  • Pilot in command › Proper touchdown point, not attained

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

NTSB narrative

The pilot completed touch-and-go landings at one airport, then flew to another local airport within 5 miles. After entering the downwind leg of the traffic pattern, the pilot observed a windsock indicating calm winds. He configured the airplane for a short field landing with 30 degrees of flaps, and used an approach airspeed of 75 knots. The pilot stated the airplane touchdown long, but he felt he could still stop the airplane on the remaining runway. Also, he said he used heavy braking, but the airplane went off the runway, crossed a state road, and came to rest in a ditch. After exiting the airplane, the pilot observed that the windsock indicated a direct tailwind for his landing runway.

Probable cause

the pilot's misjudgment of distance and speed, and his failure to attain a proper touchdown point, during the landing. Factors related to the accident were: dusk light conditions, and a tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD96LA143
Event ID
20001208X06752
Case number
IAD96LA143
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: 3c9afe9ee3d6f260d538521d6c11688564f0145d76efcef2c5fa2b09c790115e; retrieved 2026-09-22T21:16:45.973Z.