FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06CA074 · Avid Aircraft Mark IV

30 Dec 2005 · California City, CA, United States

Avid Aircraft Mark IV · Accident: loss of control on ground/water during takeoff

From California City Municipal Airport (L71) to Rosamond Skypark Airport (L00)

Report a problem

Event

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

Avid Aircraft Mark IV

Aircraft type
Avid MARK
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
N99BK
Operator
Unknown
Onboard fatalities
Unknown
Route
From California City Municipal Airport (L71), California City, CATo Rosamond Skypark Airport (L00), Rosamond, 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
Takeoff · roll/run
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 on ground/water
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

  • Pilot in command › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained

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 nosed over after veering off the runway on takeoff. The pilot had a crosswind of 18 knots, gusting to 20 knots, from 30 degrees to his right. On the takeoff roll, the right wing and tail came up, pushing the airplane off the left side of the runway. The airplane nosed over when it entered the dirt. The pilot reported that there were no mechanical malfunctions or failures.

Probable cause

the pilot's inadequate compensation for the crosswind and failure to maintain directional control of the airplane on takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06CA074
Event ID
20060201X00145
Case number
LAX06CA074
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: investigation status, coordinates. 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: 9378c761e4dcb905833142a5438a2920f4d27fe53f6e3ab742e22ee685039e0e; retrieved 2026-09-22T05:10:37.297Z.