FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA247 · Piper PA-28-180

27 Apr 2013 · Owatonna, MN, United States

Piper PA-28-180 · Accident: loss of control on ground during landing

From Airlake Airport (LVN) to Owatonna Degner Regional Airport (OWA)

Report a problem

Event

NTSB case
CEN13CA247
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-28-180

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
N7780N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Airlake Airport (LVN), Minneapolis, MNTo Owatonna Degner Regional Airport (OWA), Owatonna, MN
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 · aborted after 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
Loss of control on ground
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that the he was conducting practice instrument approaches under visual flight rules with a safety pilot at the time of the accident. After the fourth approach, they elected to land the airplane. The safety pilot assumed control of the airplane so that the pilot could prepare for landing. The airplane ended up on a “very close-in base leg” that resulted in the airplane being high on final approach. The pilot took control of the airplane from the safety pilot and elected to continue the landing. The pilot reported that the conditions, including a right crosswind, resulted in the airplane touching down on the left side of the runway. The pilot elected to execute a go-around and applied full engine power. The airplane subsequently made an unintended left turn and impacted the grassy area adjacent to the runway, substantially damaging the left wing. The pilot reported that there were no mechanical failures or malfunctions associated with the airplane before the accident. In addition, postaccident examination did not reveal any anomalies consistent with a preimpact failure or malfunction.

Probable cause

The pilot’s loss of directional control during an aborted landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA247
Event ID
20130430X25846
Case number
CEN13CA247
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, coordinates. 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: 63536fcb7eb56433acef994bc25ebd0a7716fcf7477a91abe260f53806f0f050; retrieved 2026-09-15T21:23:08.144Z.