WPR13CA260 · Wampach Murphy Moose Aeromooses
Wampach Murphy Moose Aeromooses · Accident: abnormal runway contact during landing
From Placerville Airport (PVF) to Mustang Airport (2CL9)
Event
- NTSB case
- WPR13CA260
- 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
Wampach Murphy Moose Aeromooses
- Aircraft type
- Wampach MURPHY MOOSE
- 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
- N331RW
- Operator
- Richard Wampach
- Onboard fatalities
- Unknown
- Route
- From Placerville Airport (PVF), Placerville, CATo Mustang Airport (2CL9), Galt, CA
- 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
- 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 pilot reported that he had flown into the airport previously, but never in the accident airplane. While on final approach, he noticed power lines between his position and the runway, and he "pulled back" on the pitch control to overfly the power lines. The pilot continued the approach and landing, but in the flare, the airplane "dropped and bounced." When the airplane was airborne after the bounce, he added power to initiate a go-around. However, the airplane did not climb as expected, and he was experiencing directional control problems. The pilot reduced power, and landed the airplane in a field adjacent to the runway. During the rollout in the field, the pilot noticed a ditch ahead of him, perpendicular to his direction of travel, and about 5 to 10 feet wide. He added power to attempt to fly over the ditch, but the main gear struck the far side of the ditch, which damaged the landing gear and fuselage structure. The airplane came to rest about two to three airplane lengths beyond the ditch. The airplane sustained substantial damage to the lower fuselage, right wing, and empennage, including the rudder control system. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's improper landing flare, which resulted in an abnormal runway contact.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA260
- Event ID
- 20130604X82326
- Case number
- WPR13CA260
- 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: 5ebbdba29e4ccb324e464445fd4d1ea33b98738c0345e5a89c5f3c8bbecb6423; retrieved 2026-09-15T21:47:05.187Z.