FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09LA586 · Cessna 172S

7 Sept 2009 · Duluth, MN, United States

University of North Dakota Cessna 172S · Accident: abnormal runway contact during landing

From Grand Forks International Airport (GFK) to Grand Forks International Airport (GFK)

Report a problem

Event

NTSB case
CEN09LA586
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
0 · 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
Visual Meteorological Cond

Cessna 172S

Aircraft type
Cessna 172
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
N568ND
Onboard fatalities
Unknown
Route
From Grand Forks International Airport (GFK), Grand Forks, NDTo Grand Forks International Airport (GFK), Grand Forks, ND
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
Landing
Defining eventThe 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
Abnormal runway contact
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During a solo cross-country flight, the private pilot landed and shut down the airplane at two airports before returning to the initial airport of departure. During refueling after the end of the entire cross-country flight, a lineman noticed that the propeller tip was bent aft. He notified dispatch immediately, and dispatch reported that the damage had not been reported by anyone. During the maintenance turnaround of the airplane, the engine firewall was also found to be damaged. The private pilot was contacted later and indicated that all three landings of the cross-country flight were normal, and he did not know when the damage occurred. However, he reported that he ballooned during the first landing. He also reported that prior to departing from the second airport, he taxied over a rough area and heard a "bing." He reported feeling a vibration in the airplane during the final leg of the cross-country flight. An instructor pilot who had flown in the airplane prior to the solo cross-country flight stated that he was confident that no hard landing damage had occurred on that previous instruction flight. The damage to the firewall and the propeller is consistent with a hard landing during one of the legs of the solo cross-country flight.

Probable cause

The pilot's failure to maintain aircraft control during landing, resulting in a hard landing and a propeller strike with the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09LA586
Event ID
20090915X53650
Case number
CEN09LA586
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 501af237edefa0da0df73fc61bf9a9c939712014349e78a01d971e580cea7e45; retrieved 2026-09-15T13:18:37.993Z.