The U.S. aircraft register, updated daily
Accidents · NTSB GAA17CA325 · Final report

Cessna 182 accident near Ellington, Connecticut, June 1, 2017

On June 1, 2017 at about 1:45 pm local time, a 1957 Cessna 182, registered N6193B, was substantially damaged in an accident during landing (landing roll) near Ellington, Connecticut (Ellington airport). It was a skydiving flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 1, 2017 · about 1:45 pm local time
Place
Ellington, Connecticut · Ellington · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 182 A, built 1957 · all 182s on the register
Registration
N6193B · registry record · serial 34193
Damage
Substantial damage
Flight
Skydiving flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Abnormal runway contact during landing (landing roll)
  2. Landing area overshoot during landing (landing roll) defining event
  3. Loss of control on ground during landing (landing roll)
  4. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Rain › Effect on equipment
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Aircraft capability › Landing distance › Capability exceeded
  • factor Personnel issues › Psychological › Personality/attitude › Motivation/respond to pressure › Pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Effect on operation
  • Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land
  • Flight time: 944 hours in all; 14 in this make and model; 39 in the last 90 days; 16 in the last 30 days; 832 as pilot in command
  • Last flight review: September 22, 2016
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 12,792.5 hours
  • Last inspection: annual inspection, July 27, 2016
  • Maximum gross weight: 2,950 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Cont Motor O-470 (piston); 1,420 hours total
  • Operator: Connecticut Parachutists INC

The flight

  • Departed from: 7B9 Ellington CT at 1:45 pm
  • Destination: 7B9 Ellington CT
  • Flight plan: none
  • Runway 19, 1,800 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 270° at 13 knots, gusting 20
  • Visibility: 10 statute miles
  • Sky: broken clouds at 7,000 ft; a few clouds at 5,000 ft
  • Temperature: 70°F (21°C), dew point 52°F (11°C)
  • Altimeter: 29.87 inHg
  • Observation at 5:51 pm from KBDL, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on December 5, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.