FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12CA468 · Piper PA-11

20 Jul 2012 · Neilsville, WI, United States Narrative disagrees

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

From Marshfield Municipal Airport (MFI) to Neillsville Municipal Airport (VIQ)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN12CA468
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-11

Aircraft type
Piper PA-11
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
N4844M
Onboard fatalities
Unknown
Route
From Marshfield Municipal Airport (MFI), Marshfield, WITo Neillsville Municipal Airport (VIQ), Neilsville, WI
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

  • Personnel issues › Task performance

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

NTSB narrative

After touching down, the pilot noticed that the airplane was not aligned with the runway and decided to abort the landing. The airplane turned left of the runway toward a cornfield, and the pilot applied power and pulled up. The airplane stalled and collided with the cornfield. The airplane sustained substantial damage to the fuselage, an engine mount, the wing struts, and the left wing spar. The pilot reported there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot did not maintain control of the airplane during an attempted aborted landing, which resulted in an inadvertent stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12CA468
Event ID
20120723X12236
Case number
CEN12CA468
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: 863a90946ab965b89768f5f801eab352c9ba5cbdc411de6cf9cc6079af87c4f7; retrieved 2026-09-15T19:02:25.843Z.