FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA338 · Stevens STARDUSTER II AS300 STARDUSTER

16 Sept 2000 · N. LAS VEGAS, NV, United States

Stevens STARDUSTER II AS300 STARDUSTER · Accident: loss of control on ground/water during landing

From North Las Vegas Airport (VGT) to an unrecorded destination

Report a problem

Event

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

Stevens STARDUSTER II AS300 STARDUSTER

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
N27CG
Operator
Unknown
Onboard fatalities
Unknown
Route
From North Las Vegas Airport (VGT)To not recorded
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
Landing · landing roll
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

  • Landing gear, tailwheel assembly › Failure, total

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

NTSB narrative

On the landing rollout the airplane ground looped. The airplane sustained substantial damage after the right wing struck a downward sloping berm. The owner was receiving instruction in conventional geared airplanes. They had flown for an about an hour, practicing touch-and-go takeoffs and landings, on the morning of the accident. No discrepancies were noted with the airplane or landing gear. On the landing rollout the tail wheel began to wobble, and the airplane veered to the left. The landing gear system was inspected. Clips attach to springs that connect the tail wheel assembly to the rudder control. The right clip was broken, which allowed the tail wheel to caster freely. The pilot noted no discrepancies with the landing gear during the preflight inspection.

Probable cause

Failure of the right clip that attaches a spring to the tail wheel/rudder control assembly, which resulted in a loss of directional control and collision with a berm.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA338
Event ID
20001212X22014
Case number
LAX00LA338
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: d53b5086d9f5e36e7688002a661689284de85c62037779f14d22121efe510c42; retrieved 2026-09-22T12:26:40.001Z.