LAX04CA013 · Cleveland Orson Starduster II SA-300
Cleveland Orson Starduster II SA-300 · Accident: on ground/water collision with object while taxiing
From Sacramento Executive Airport (SAC) to Stockton Metropolitan Airport (SCK)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX04CA013
- 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
Cleveland Orson Starduster II SA-300 Possible conflict
- Aircraft type
- Cleveland Orson STARDUSTER II SA-300
- 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
- N379C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sacramento Executive Airport (SAC), Sacramento Exec, CATo Stockton Metropolitan Airport (SCK), Stockton, 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
- Taxi
- 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
- On ground/water collision with object
- 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 › Clearance, not maintained
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The Starduster collided with a parked and unoccupied Piper, while taxiing into a parking spot. While attempting to line the Starduster up with the parking line, the pilot was looking off the left wing. The right interplane-strut of the Starduster collided with the Piper's nose spinner. The propeller of the Starduster then made contact with the other airplane's right wing. The pilot noted no mechanical problems with his airplane.
Probable cause
the pilot's inadequate visual lookout resulted in his failure to maintain clearance from the parked airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04CA013
- Event ID
- 20031222X02079
- Case number
- LAX04CA013
- 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 2003-10-14.
- API snapshot SHA-256: 488a110f778acdfdcc99ba86855094c74531b1d0f61383cd5407126b190326da; retrieved 2026-09-22T08:20:31.560Z.