CHI06LA146 · Piper PA-23-250
Piper PA-23-250 · Accident: loss of control on ground/water during landing
From Marshfield Municipal Airport (MFI) to Faribault Municipal Airport-Liz Wall Strohfus Field (FBL)
Event
- NTSB case
- CHI06LA146
- 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-23-250
- Aircraft type
- Piper PA-23
- 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
- N63790
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marshfield Municipal Airport (MFI), Marshfield, WITo Faribault Municipal Airport-Liz Wall Strohfus Field (FBL), Faribault, 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
- First occurrenceThe 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/water
- 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
- Pilot in command › Directional control, not obtained/maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane veered off the runway during landing and impacted a ditch. The pilot stated that he attempted to correct to the left when the airplane veered hard to the right upon touchdown. Examination of the accident site revealed two sets of skid marks on the runway and two sets of tire marks through the adjacent grass area that preceded the airplane. Both tire skids/marks were similar. None of the tires had flat spotting and all of the tires were in good condition. The airplane came to rest about 57 feet from the left side of the runway, facing about 180 degrees opposite to runway 30. Operation of the brake system showed no anomalies. The steering system linkage was found to be operative to the nose gear trunnion. The nose landing gear and right main landing gear were collapsed. All components of the landing gear system were present and associated breakage was consistent with impact damage. .
Probable cause
Directional control not obtained/maintained by the pilot during landing. A contributing factor was the ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06LA146
- Event ID
- 20060614X00733
- Case number
- CHI06LA146
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-06-03.
- API snapshot SHA-256: 69368976bd484f2d12aad720135d2279efe5e8bfef58e2dd99dd7727b7ff2577; retrieved 2026-09-22T04:49:19.584Z.