GAA18CA085 · Cessna 172 S
University of North Dakota Cessna 172 S · Accident: abnormal runway contact during landing
From Grand Forks International Airport (GFK) to Park Rapids Municipal Airport Konshok Field (PKD)
Event
- NTSB case
- GAA18CA085
- 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 172 S
- 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
- N524ND
- Operator
- University of North Dakota
- Onboard fatalities
- Unknown
- Route
- From Grand Forks International Airport (GFK), Grand Forks, NDTo Park Rapids Municipal Airport Konshok Field (PKD), Park Rapids, MN
- Aircraft age
- About 8 years (built 2009)
- 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
The director of aviation safety for the flight school reported that the student pilot was on her first solo cross-country flight and that, during the approach to land, the airplane was fast and high. Subsequently, the airplane landed nose low, and the propeller struck the ground. The student did not know the propeller or fuselage had been damaged during the landing and continued the rest of her intended flight without further incident.
The next assigned flight crew discovered the damage, and an examination by the maintenance department revealed that the airplane had sustained substantial damage to the fuselage.
The director of aviation safety reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The student pilot’s improper landing flare, which resulted in the propeller striking the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA085
- Event ID
- 20171214X23802
- Case number
- GAA18CA085
- 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: 2c6288d8e6a85f8ba3075824e47bbbdd9bde66b2d5490196140b3cdbc6915dc3; retrieved 2026-09-16T06:08:46.802Z.