Cessna 182Q accident near Groton, Connecticut, June 27, 2005
On June 27, 2005 at about 5:20 pm local time, a Cessna 182Q, registered N5155N, was destroyed in an accident near Groton, Connecticut (Groton - New London Airport). It was a personal flight under general aviation rules (Part 91). 4 people were killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain aircraft control while executing an ILS (Instrument Landing System) approach to minimums.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 27, 2005 · about 5:20 pm local time
- Place
- Groton, Connecticut · Groton - New London Airport · map
- Type
- Accident
- Injuries
- 4 people were killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Cessna 182Q · all 182Qs on the register
- Registration
- N5155N · no longer on the register · serial 18267548
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane impacted water during its second ILS (Instrument Landing System) approach to runway 5. Review of recorded radar data revealed that during the first approach, the airplane made several excursions to the right and left of the inbound course centerline. A tower controller observed the airplane "break out" of the clouds at 200 feet, left of the runway centerline. The airplane appeared to be headed straight for the control tower when the flight radioed a request to conduct a "circle to land." The airplane then continued into a cloud layer, and the controller instructed the pilot to "execute the published missed approach." The last radar target recorded prior to initiation of the missed approach placed the airplane at a Mode C altitude of 100 feet msl, about 1/2 mile from the runway threshold and 1/2 mile left of the course centerline. The flight was instructed to contact approach control and then received vectors for a second ILS approach. About 30 minutes later, the airplane was again established on the ILS Runway 5 approach. The tower controller cleared the flight to land, which was acknowledged. The tower controller then observed a target on his radar scope, identified as the accident airplane, that appeared to be left of the final approach course. The controller informed the flight that the airplane was left of course; however, no response was received. Radar data for the second approach showed a track similar to the first approach with several excursions to the right and left of the inbound course centerline. The last recorded radar hit placed the airplane at a mode C altitude of 400 feet msl, about 1 and 1/2 miles from the runway threshold and slightly left of course. Several witnesses in the area of the accident site recalled hearing an airplane about the time of the accident. The engine sounded normal, until rpm increased, followed by the sound of an impact. None of the witnesses observed the airplane due to the low visibility in the area. About 8 minutes after the accident, a floating debris field was located about 1.15 miles from the approach end of runway 5, on a 051-degree bearing. Pilots who had conducted approaches to runway 5, both prior to and after the accident airplane's first approach to the runway, recalled breaking out of the cloud layer around 200 to 250 feet above the ground. None of the pilots recalled any abnormalities with the ILS while conducting an approach to runway 5. Damage observed on the recovered wreckage was consistent with the airplane impacting the water in an uncontrolled descent. Examination of the recovered wreckage revealed no evidence suggesting mechanical malfunction or failure.
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
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 1,407 hours in all; 67 in the last 90 days; 25 in the last 30 days
- Last flight review: October 1, 2004
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: fatal
Co-pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 544 hours in all; 25 in the last 90 days; 13 in the last 30 days
- Last flight review: October 1, 2004
- Medical certificate: Class 3
- Seat: rgt
- Injury: fatal
The aircraft
- Airframe total time: 2,393 hours
- Last inspection: annual inspection, May 1, 2004; 198 hours since
- Maximum gross weight: 2,960 lb
- Seats: 4
- Landing gear: fixed
- Engine: Teledyne Continental O-470-U (piston); 0 hours total
The flight
- Departed from: PWM Portland ME at 3:30 pm
- Destination: GON Groton CT
- Flight plan: IFR
- Runway 5, 5,000 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 5 statute miles
- Sky: overcast at 200 ft
- Temperature: 73°F (23°C), dew point 70°F (21°C)
- Altimeter: 30.25 inHg
- Observation at 5:27 pm from GON, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 2 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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.
