FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10CA222 · Cubcrafters Inc CC11-160

2 May 2010 · Los Alamos, CA, United States

Cubcrafters Inc CC11-160 · Accident: collision with terrain/object (non-CFIT) during landing

From 1ZA · Santa Ynez, CA to Los Alamos, CA (private airstrip)

Report a problem

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

Event

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

Cubcrafters Inc CC11-160

Aircraft type
Cubcrafters CC11
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
N72RZ
Onboard fatalities
Unknown
Route Narrative disagrees
From 1ZA · Santa Ynez, CATo Los Alamos, CA (private airstrip)
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 · landing roll
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
Collision with terrain/object (non-CFIT)
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

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

NTSB narrative

The private pilot reported that he was landing the tail wheel-equipped airplane at a privately-owned grass airstrip with a "slight" crosswind. He reported that after touchdown, during the landing roll, he lost directional control of the airplane and it collided with an unoccupied parked vehicle adjacent to the runway. The collision resulted in substantial damage to the right wing. No mechanical deficiencies or anomalies with the airplane were reported.

Probable cause

The pilot's inadequate compensation for the crosswind conditions resulting in the loss of directional control while landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10CA222
Event ID
20100502X83853
Case number
WPR10CA222
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: 4c7053e1b1a0bc6f246e09c84947cb770ecf3f926fbf734c88a395a577770546; retrieved 2026-09-15T13:57:58.430Z.