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

Cessna 172 accident near Groton, Connecticut, November 11, 2008

On November 11, 2008 at about 4:32 pm local time, a Cessna 172, registered N91HF, was substantially damaged in an accident during landing (landing roll) near Groton, Connecticut (Groton-New London Airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The student pilot's failure to maintain directional control during landing.

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

What the record shows

Date
November 11, 2008 · about 4:32 pm local time · cases in 2008
Place
Groton, Connecticut · Groton-New London Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 R · all 172s on the register
Registration
N91HF · not in the FAA's current or past register files · serial 17280067
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

During landing of the Cessna 172R, the student pilot reduced the power to begin the flare. The airplane ballooned and the pilot added “a little power” to prevent a hard landing. Once on the runway, the pilot applied the brakes to slow the airplane. The airplane turned left, approximately 45 degrees from center line. The pilot reported he applied full brakes and attempted to return the airplane back toward the runway's centerline, but the airplane did not respond and continued to veer towards the edge of the runway. The airplane departed the left side of the runway, impacting some runway signs and markers. The right wheel strut failed, dropping the airplane's right side and pivoting the airplane's tail. The airplane came to rest on the runway, facing back toward the direction of travel. In the National Transportation Safety Board Form 6120.1 submitted by the pilot, "No" was checked for "Was there a Mechanical Malfunction/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

What happened, in order

  1. Loss of control on ground during landing (landing roll) defining event
  2. Runway excursion during landing (landing roll)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained

Pilot

  • Flight time: 54 hours in all; 54 in this make and model; 21 in the last 90 days; 7 in the last 30 days; 6 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 6,648 hours
  • Last inspection: annual inspection, October 30, 2008
  • Maximum gross weight: 2,450 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO360 (piston); 0 hours total
  • Operator: Heritage Flight Academy, LLC

The flight

  • Departed from: ISP Islip NY at 10:30 am
  • Destination: GON Groton CT
  • Flight plan: none
  • Runway 33, 4,000 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 290° at 11 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 46°F (8°C), dew point 28°F (-2°C)
  • Altimeter: 30.23 inHg
  • Observation at 2:56 pm from GON

Injuries

FatalSeriousMinorNone
Flight crew1

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA09CA048.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.