FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11LA390 · Piper PA-28R-201

14 May 2011 · Grand Forks, ND, United States

University of North Dakota Piper PA-28R-201 · Accident: hard landing

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

Report a problem

Event

NTSB case
CEN11LA390
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

Piper PA-28R-201

Aircraft type
Piper PA-28
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
N204ND
Onboard fatalities
Unknown
Route
From Grand Forks International Airport (KGFK), Grand Forks, NDTo Grand Forks International Airport (KGFK), 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 · flare/touchdown
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
Hard landing
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 › Action/decision

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

NTSB narrative

The flight instructor reported that his student was practicing a simulated forced landing to a runway when the accident occurred. He stated that, after a firm touchdown, the airplane began to veer to the right. He noted that the right wing was lower than the left wing and his initial thought was that the right tire was flat. After coming to a stop, the airplane would not move forward without an excessive application of engine power. A postaccident examination of the airplane revealed that the right main landing gear had collapsed rearward, with substantial damage to both wings and the fuselage. Examination of the right main landing gear did not reveal any preimpact anomalies or failures that would have prevented normal operation. Interviews of recent flight crews did not reveal any hard landings that could have damaged the right main landing gear before the accident flight.

Probable cause

The flight instructor’s inadequate supervision of the landing, which resulted in an inadequate flare and subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11LA390
Event ID
20110614X10547
Case number
CEN11LA390
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: df35b01b5a1f5f8273f95e54f8a4fc9761aeafd8e9e9c9c8b9db2ef2870bf507; retrieved 2026-09-15T16:16:52.521Z.