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

Cessna 172S accident near Grand Forks, North Dakota, July 2, 2009

On July 2, 2009 at about 1:30 pm local time, a Cessna 172S, registered N538ND, was substantially damaged in an accident during landing (flare/touchdown) near Grand Forks, North Dakota (Grand Forks International 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 improper landing flare that resulted in a hard landing.

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

What the record shows

Date
July 2, 2009 · about 1:30 pm local time
Place
Grand Forks, North Dakota · Grand Forks International · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172S · all 172Ss on the register
Registration
N538ND · registry record · serial 172S10832
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The accident occurred during the student pilot's third landing on his first solo flight. He reported that his first two landings were uneventful, but the airplane landed hard on the third landing for unknown reasons. An after-flight inspection revealed that one of the propeller blade tips was curled from contact with the runway and that the engine firewall was substantially deformed.

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. Hard landing during landing (flare/touchdown) defining event
  2. Abnormal runway contact during landing (flare/touchdown)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot

Dual student

  • Certificate: student
  • Flight time: 23 hours in all; 23 in this make and model; 23 in the last 90 days; 23 in the last 30 days; 0 as pilot in command
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 558 hours
  • Last inspection: approved inspection programme, June 29, 2009
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total
  • Operator: Und Aerospace Foundation

The flight

  • Departed from: KGFK Grand Forks ND at 1:20 pm
  • Destination: KGFK Grand Forks ND
  • Flight plan: none
  • Runway 35L, 7,349 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 010° at 5 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 25,000 ft
  • Temperature: 66°F (19°C), dew point 59°F (15°C)
  • Altimeter: 30.06 inHg
  • Observation at 1:53 pm from KGFK

Injuries

FatalSeriousMinorNone
Flight crew1

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.