ASN Wikibase Occurrence # 44450
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 27 June 2005 |
| Time: | 13:20 |
| Type: |  Cessna 182Q Skylane |
| Owner/operator: | Private |
| Registration: | N5155N |
| MSN: | 18267548 |
| Year of manufacture: | 1980 |
| Total airframe hrs: | 2393 hours |
| Engine model: | Teledyne Continental O-470-U |
| Fatalities: | Fatalities: 4 / Occupants: 4 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Groton, CT -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Portland, ME (PWM) |
| Groton, CT (GON) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Probable Cause: The pilot's failure to maintain aircraft control while executing an ILS (Instrument Landing System) approach to minimums.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20050706X00942&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 06-Dec-2017 10:14 | ASN Update Bot | Updated [Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation