GAA17CA325 · Cessna 182 A
Connecticut Parachutists Cessna 182 A · Accident: landing area overshoot
From Ellington Airport (7B9) to Ellington Airport (7B9)
Event
- NTSB case
- GAA17CA325
- 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 182 A
- 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
- N6193B
- Operator
- Connecticut Parachutists
- Onboard fatalities
- Unknown
- Route
- From Ellington Airport (7B9), Ellington, CTTo Ellington Airport (7B9), Ellington, CT
- Aircraft age
- About 60 years (built 1957)
- 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
- Defining eventThe 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
- Landing area overshoot
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he landed the airplane on the 1,800-ft-long asphalt runway in the rain at 70 mph with full flaps. He reported that, on final, he had considered conducting a go-around due to wind and weather, but "we were low, slow, and 130 pounds below maximum gross weight with very dynamic wind conditions at the time and …apartment buildings about 400 yards beyond the end of runway 19." During the landing, he touched down with a right crosswind, about 600 ft beyond the runway threshold.
He recalled that he retracted the flaps and pulled the control wheel all the way aft to put as much weight as possible on the main wheels, but he "felt our ground speed was fast and we must have a tailwind." He applied heavy braking, and as the end of the runway approached, he applied full left rudder to avoid a gully that was just beyond the end of the runway. The airplane exited the end of the runway and veered left. The airplane entered the gully and impacted vegetation.
The airplane sustained substantial damage to the right-wing spar and aileron.
The nearest METAR was 10 nautical miles east of the accident site, and it reported that the wind was from 270° at 13 knots, gusting to 20 knots. The visibility was 10 statute miles with light rain.
The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Per the National Transportation Safety Board Pilot Aircraft Accident Report, the pilot noted that the accident could have been prevented by initiating a go-around after he realized that he could not land in the first third of the runway. He noted that the approaching rain and wind conditions added personal pressure to land before conditions deteriorated. Additionally, he reported that under normal, dry conditions, heavy braking was required to prevent an overrun.
Probable cause
The pilot’s unstabilized approach and failure to go around in rainy, gusting crosswind conditions, which resulted in a runway overrun. Contributing to the accident was the pilot’s self-induced pressure to land due to the deteriorating weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA325
- Event ID
- 20170601X53523
- Case number
- GAA17CA325
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 5aee6665416d7dbacb3913cdc2217d540a2f6999cc7f3c9c64852efd21b3dc14; retrieved 2026-09-16T05:21:21.802Z.