# NTSB NYC05FA109: Cessna 182Q, N5155N, Groton, CT, June 27, 2005 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: June 27, 2005, 13:20 local (17:20 UTC) - Place: Groton, CT - Coordinates: 41.303054, -72.050277 - Nearby events: https://openairdocs.org/map.md?lat=41.3031&lon=-72.0503&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 4 fatal - Status: Completed, report November 29, 2007 - Report: Approved by Office Director - Parties: Teledyne Continental Motors, Cessna Aircraft Company, FAA/FSDO - NTSB case key (mKey): 61805 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC05FA109 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61805/pdf - Page: https://openairdocs.org/ntsb/NYC05FA109 ## Probable cause The pilot's failure to maintain aircraft control while executing an ILS (Instrument Landing System) approach to minimums. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - in flight, approach - faf/outer marker to threshold (ifr) - aircraft control - not maintained, pilot in command (cause) - In flight collision with terrain/water, descent - uncontrolled - terrain condition - water ## Analysis 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. ## Factual narrative HISTORY OF FLIGHT On June 27, 2005, at 1320 eastern daylight time, a Cessna 182Q, N5155N, was destroyed when it impacted water following a loss of control while on approach to the Groton/New London Airport (GON), Groton, Connecticut. The airplane was registered to and operated by the pilot. The commercial pilot, pilot-rated passenger, and two other passengers were fatally injured. Instrument meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan was filed for the flight that originated from the Portland International Jetport (PWM), Portland, Maine, about 1130. The personal flight was conducted under 14 CFR Part 91. Review of air traffic control (ATC) transcripts, recordings, and interviews with air traffic controllers from Groton tower revealed that the accident airplane conducted two ILS (Instrument Landing System) approaches to runway 5. On the first approach, approximately 1250, the pilot-rated passenger initially transmitted to the GON tower "…skylane five five november with you." The controller questioned the pilot-rated passenger if they were associated with the Rotarian Club, which the pilot-rated passenger replied "affirmative." The controller subsequently cleared the flight to land. About 2 minutes later, 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 pilot-rated passenger radioed a request to conduct a "circle to land." The airplane then continued into a cloud layer, and the air traffic controller instructed the flight to "execute the published missed approach," which was acknowledged. The flight was instructed to contact Providence Approach Control and then received vectors for a second ILS approach. At 1315:34, the flight was cleared for the ILS Runway 5 approach. The flight was instructed to continue the approach, and then at 1318:27, cleared 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. At 1320:54, the controller informed the flight that the airplane was left of course; however, no response was received. Review of recorded radar data revealed that during the first approach to GON, the airplane made several excursions to the right and left of the inbound course centerline. The last radar target recorded prior to the missed approach at 1252:56 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. 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 at 1320:44 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 began to increase, followed by the sound of an impact. None of the witnesses observed the airplane due to the low visibility in the area. 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. About 8 minutes after the accident, United States Coast Guard personnel and private vessels located a floating debris field about 1.15 miles from the approach end of runway 5, on a 051-degree bearing. The main wreckage, which consisted of the main cabin and empennage, was located on June 29, 2005, about 300 feet southeast of the floating debris field, in 24 feet of tidal water. The engine was separated from the fuselage, and came to rest about 80 feet beyond the main wreckage. The two-bladed propeller assembly was separated from the engine. Both blades remained attached to the hub, and came to rest near the engine. The engine and propeller were recovered on June 30, 2005. The accident occurred during the hours of daylight, at 41 degrees, 18.57 minutes north longitude, 72 degrees, 03.78 minutes west latitude. PERSONNEL INFORMATION The pilot held a commercial pilot certificate for airplane single-engine and multi-engine land, and instrument airplane. The pilot's most recent application for a Federal Aviation Administration (FAA) second class medical certificate was dated September 21, 2004. Review of the pilot's logbook revealed that he had accumulated about 1,407 hours of total flight experience. Additionally, the logbook indicated the pilot had logged 58.2 hours of actual instrument flight time and 48.0 hours of simulated instrument flight time. He successfully completed the flight test for a commercial multi-engine instrument airplane rating on September 29, 2004. Since that flight test, the pilot had logged 9.5 hours of actual instrument flight time. The pilot-rated passenger held a private pilot certificate for airplane single-engine land. She was not instrument rated. The pilot's most recent application for a FAA third class medical certificate was dated on September 21, 2004. Review of the pilot's logbook revealed that she had accumulated about 544 hours of total flight experience. AIRCRAFT INFORMATION According to the logbooks for the airplane, the most recent annual inspection was completed on May 30, 2004. On that date, the tachometer time was recorded as 442.6 hours, and the airplane had accumulated 2,195.3 total hours of operation. In addition, the last documented engine oil and oil filter change was completed on October 8, 2004. On that date, the tachometer time was recorded as 503.5 hours, and the engine had accumulated 310.3 hours since major overhaul. The last maintenance action on the airplane entered in the logbooks was dated on May 23, 2005, at a tachometer time of 536.5 hours, when a landing gear part was removed and replaced. No records of an annual inspection being performed on the airplane in 2005 were located during the investigation. Review of the available maintenance records indicated the airplane's most recent 14 CFR Part 91.411 IFR certification of the altimeter, encoder, and static system took place in July 2001. METEOROLOGICAL INFORMATION The 1256 weather observation reported at GON included wind variable at 5 knots; 10 statute miles of visibility; an overcast cloud layer at 500 feet agl; temperature of 24 degrees Celsius; dew point of 22 degrees Celsius; and an altimeter setting of 30.25 inches of mercury. The 1327 weather observation reported at GON included calm winds; 5 statute miles of visibility; mist; an overcast cloud layer at 200 feet agl; temperature of 23 degrees Celsius; dew point of 21 degrees Celsius; and an altimeter setting of 30.25 inches of mercury. Both of the reports also included a note that the visibility to the south was 1 statute mile. AIRPORT INFORMATION The airport elevation at GON was 9 feet msl. AIDS TO NAVIGATION Review of the approach plate for the ILS Runway 5 approach at GON revealed that the final approach fix (FAF), identified as PINET intersection, was located 6.3 miles from the runway 5 threshold. The minimum crossing altitude at PINET was 1,777 feet msl. The minimums for the straight-in approach were 1/2 statute mile of visibility, and a minimum decision altitude of 208 feet msl (200 feet agl). The missed approach procedure was: climb to 2,000 feet, via the GON 062-degree radial to the BABET intersection, and hold. WRECKAGE AND IMPACT INFORMATION The wreckage was examined at a secured facility on June 28 to 30, 2005, under the supervision of a Safety Board ## Aircraft - Registration: [N5155N](https://openairdocs.org/deregistered/N5155N-2005-11-01), registration cancelled 2005-11-01, S/N 18267548, built 1980 (OpenAirDocs) - Reported make and model: Cessna 182Q - Registry model: [Cessna 182Q](https://openairdocs.org/model/cessna-182q) (registry code 2072732) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18267548 - Airframe hours: 2393 - Engines: Teledyne Continental O-470-U 230 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 1, 2004, 198 hours before - Departed: PWM, Portland, ME - Destination: GON, Groton, CT - Flight plan: IFR - Airport: GON, Groton - New London Airport, runway 5, 5,000 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 58; injuries: fatal; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review October 1, 2004; seat: left; toxicology performed; flight hours: 1,407 total, 67 in the last 90 days, 25 in the last 30 days - Co-pilot; age 50; injuries: fatal; private; airplane ratings: single-engine land; medical: class 3; last flight review October 1, 2004; seat: right; toxicology performed; flight hours: 544 total, 25 in the last 90 days, 13 in the last 30 days ## Weather - Conditions: Instrument (IMC), Day - Wind: calm - Visibility: 5 statute miles - Lowest ceiling: 200 ft overcast - Temperature: 73 °F, dew point 70 °F - Altimeter: 30.25 inHg - Observed at: GON, 1 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20050627014649A](https://openairdocs.org/incident/20050627014649A), Jun 27, 2005: Cessna 182Q, Groton - New L, CT, Destroyed, 4 fatal. (-23) On June 27, 2005 a Cessna 182-Q, reg #N5155N, sn 18267548, enroute from portland me to Groton, CT crashed. Aircraft was on an ILS approach to runway 05.… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.