FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC05FA109 · Cessna 182Q

27 Jun 2005 · Groton, CT, United States

Cessna 182Q · Accident: loss of control in flight on approach

From Portland International Jetport (PWM) to Groton New London Airport (GON)

Report a problem

Event

NTSB case
NYC05FA109
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
4 · 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
Instrument Meteorological Cond

Cessna 182Q

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
N5155N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Portland International Jetport (PWM), Portland, METo Groton New London Airport (GON), Groton, CT
Aircraft age
Not recorded
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
Approach · IFR final approach
First occurrenceThe 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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC05FA109
Event ID
20050706X00942
Case number
NYC05FA109
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: be9fe53de5aba10276574f198d883af678f2834f14acffb34d214dd806db0825; retrieved 2026-09-20T18:00:01.157Z.