WPR13LA096 · Quicksilver SPORT IIS
Quicksilver SPORT IIS · Accident: aircraft/propeller/rotor contact with person while standing
From Camarillo International Airport (CMA) to Camarillo International Airport (CMA)
Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR13LA096
- 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
Quicksilver SPORT IIS
- Aircraft type
- Quicksilver SPORT IIS
- 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
- N1712
- Operator
- Chicco Miguel e
- Onboard fatalities
- Unknown
- Route
- From Camarillo International Airport (CMA), Camarillo, CATo Camarillo International Airport (CMA), Camarillo, CA
- Aircraft age
- About 8 years (built 2005)
- 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
- Standing · engine(s) operating
- 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
- Aircraft/propeller/rotor contact with person
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was preparing his airplane for departure in a designated "run-up" area. The passenger's girlfriend wanted to document the flight with photographs and video. As she approached the airplane from the rear to check an airframe-mounted camera before the airplane departed, she was struck in the head by the propeller of the rear mounted engine. The pilot heard the noise and immediately shut the engine down. Several other people, who were standing nearby, had warned her to stay clear of the engine/propeller area.
Probable cause
The person on the ground’s failure to stay clear of a spinning propeller.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13LA096
- Event ID
- 20130120X21032
- Case number
- WPR13LA096
- 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, damage. 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: bd546e5258e854e67607ff855c1c2956f608d36cc8e17836c0f0e1615dcc07cf; retrieved 2026-09-15T20:46:31.350Z.