FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA217 · Goodacre CA4-HP

26 Apr 2009 · Mansfield, WA, United States

Goodacre CA4-HP · Accident: loss of control in flight during landing

From Sandpoint Airport (SZT) to Mansfield Airport (8W3)

Report a problem

Event

NTSB case
WPR09LA217
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

Goodacre CA4-HP

Aircraft type
Goodacre CA4
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
N33254
Operator
James D. Dunn · private individual
Onboard fatalities
Unknown
Route
From Sandpoint Airport (SZT), Sandpoint, IDTo Mansfield Airport (8W3), Mansfield, WA
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
Loss of control in flight
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 stated that prior to entering the pattern at the destination airport, he observed the airport's wind indicator, which showed a landing on runway 03, and to "expect a left crosswind component." The pilot reported that the approach for landing was normal; however, the airplane was bounced around from the "winds and/or turbulence," and that he had decided to go-around. Power was applied and then he raised the flaps. The airplane continued to descend and touched down on the runway, with full power. The airplane bounced back into the air with the right wing low. The airplane subsequently departed the runway environment as the pilot attempted to apply left aileron to raise the right wing. The airplane came to rest off the runway in a plowed wheat field. Examination of the airplane found no mechanical anomalies.

Probable cause

The pilot's failure to maintain aircraft control while landing with a known crosswind condition.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA217
Event ID
20090427X31901
Case number
WPR09LA217
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: c17d50191d812429d899f12c77eacb2471469c7b72b15842d5f48441193d5b7e; retrieved 2026-09-15T10:59:16.012Z.