FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA145 · Owens/Richburg VANS RV6-A

2 Apr 2000 · Sacramento, CA, United States

Owens/Richburg VANS RV6-A · Accident: dragged wing, rotor, pod, float or tail/skid on approach

From Rio Vista Municipal Airport (O88) to Sacramento Executive Airport (SAC)

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
LAX00LA145
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
0
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

Owens/Richburg VANS RV6-A

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
N4419Q
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Rio Vista Municipal Airport (O88), Rio Vista, CATo Sacramento Executive Airport (SAC)
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
Approach · VFR pattern base
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
Dragged wing, rotor, pod, float or tail/skid
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 › Altitude/clearance, not maintained
  • Wing, wingtip › Bumped

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

NTSB narrative

The accident airplane was cleared to land in front of another airplane. During the base to final turn the left wing tip struck the runway. The nose landing gear was sheared off and the main landing gear collapsed aft, but remained attached. No mechanical malfunctions were noted with the local flight.

Probable cause

Failure to maintain sufficient altitude while on the base to final turn for landing subsequently striking the wing tip on the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA145
Event ID
20001212X20846
Case number
LAX00LA145
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. 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: 8e62b1af965e5f9000a2f6ced6eb8555a89c3541dc7bd092c4bb618d52889351; retrieved 2026-09-22T13:00:39.647Z.