NYC96LA185 · Cessna 182
Cessna 182 · Accident: overrun during landing
From Worcester Regional Airport (ORH) to an unrecorded destination
Event
- NTSB case
- NYC96LA185
- 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 182
- Aircraft type
- Cessna 182
- 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
- N737MD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Worcester Regional Airport (ORH), Worcester, MATo 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 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 › Go-around, not performed
Approximate · Estimated position: the centre of Stow, MA, the place the record names. Not the accident site.
NTSB narrative
The pilot was practicing a short field landing on a 1600 foot long turf runway. He reported that his first approach was high, and he made a go-around. He described the second approach as a little fast and long. He was unable to stop by the end of the runway, and the airplane went off the departure end and into a pond. During the occurrence, the nose landing gear was bent rearward, and the firewall was wrinkled. The pilot also reported that he was not aware that the grass was wet or that he had a tailwind of 2 to 3 mph during touchdown.
Probable cause
the pilot's misjudgment of speed and distance during the landing, and his failure to go around while there was sufficient runway remaining, which resulted in a runway overrun and an encounter with a soft terrain at the edge of a pond. Wet grass on the runway was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA185
- Event ID
- 20001208X06801
- Case number
- NYC96LA185
- 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: dcaceb637b98d44e333536ba4d00628c65f126dcad7156dde5c4320b23bb96e9; retrieved 2026-09-22T21:08:42.568Z.