FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10LA250 · Wildman RV6-A

20 May 2010 · Columbia, CA, United States

Wildman RV6-A · Accident: hard landing

From Gustine Airport (3O1) to Columbia Airport (O22)

Report a problem

Event

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

Wildman RV6-A

Aircraft type
Wildman RV6
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
N578RJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gustine Airport (3O1), Gustine, CATo Columbia Airport (O22), Columbia, 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
Hard landing
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The pilot-rated passenger seated in the right seat reported that, just prior to landing, the pilot listened to the airport's automated weather observing system, which reported a 90-degree crosswind of 7 knots gusting to 14 knots. During the landing sequence, and just before touchdown, the airplane suddenly lost altitude and landed hard, striking the left wing and landing gear on the runway. Subsequently, the airplane bounced and veered to the left. The airplane bounced a second time before impacting and coming to rest against three unoccupied, parked airplanes. Postaccident examination verified flight control continuity throughout the rudder, elevator, right aileron, and left flap. The damage to the left aileron outboard hinge and right flap control arm were both consistent with impact damage.

Probable cause

The pilot’s inadequate compensation for the gusting crosswind and improper landing flare.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10LA250
Event ID
20100522X10816
Case number
WPR10LA250
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: 2450f918634f2ef7d73e939d687b997aafe80b82da22006e9f24864f27185b0d; retrieved 2026-09-15T14:10:17.269Z.