LAX05LA222 · Quiksilver MX LII Sport
Quiksilver MX LII Sport · Accident: loss of control in flight during initial climb
From Brian Ranch Airport (CL13) to Brian Ranch Airport (CL13)
Event
- NTSB case
- LAX05LA222
- 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
- 1 · 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
Quiksilver MX LII Sport
- Aircraft type
- Quiksilver MX LII SPORT
- 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
- UNREG
- Operator
- David Bosworth
- Onboard fatalities
- Unknown
- Route
- From Brian Ranch Airport (CL13), Brian Ranch, CATo Brian Ranch Airport (CL13), Brian Ranch, 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
- Initial climb
- First occurrenceThe 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
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted terrain just after takeoff. A relative of the pilot reported that just prior to the accident, the relative and the pilot attempted to takeoff. The airplane would not gain altitude due to a control problem so the pilot dropped the relative off and departed alone. Immediately following the takeoff, when the airplane was about 75 feet above ground level, the airplane banked to the left, then the right, and descended into the terrain. The Federal Aviation Administration (FAA) accident coordinator inspected the airplane and found no evidence of power or control malfunctions. Review of the aircraft specifications disclosed that it exceed the limitations of 14 CFR Part 103.1 for classification as an ultralight. The pilot did not hold any FAA pilot certificates. According to records of the United States Ultralight Association, Inc. (USUA) and the FAA, the pilot did not hold a training exemption for this ultralight, nor had a waiver been issued for 14 CFR 103.7. Records reviewed by USUA personnel indicated that the pilot was a registered ultralight pilot since 1986.
Probable cause
an in-flight loss of control for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA222
- Event ID
- 20050706X00936
- Case number
- LAX05LA222
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-07-02.
- API snapshot SHA-256: ecb7651ff492a1ea0368a3ce8395e367063d441d774daae3838abf6b106c028f; retrieved 2026-09-20T17:59:35.888Z.