Skip to content

Atlas / NTSB / GAA19CA436

NTSB CAROL · Event

Event GAA19CA436

2019-06-28 Lincoln, California, United States Airport · LHM None 1 aircraft Status: Completed

Registry · N2RG

FAA Aircraft Registry record.

Make / Model

GROSCH STARDUSTER TOO SA-30

Year of manufacture

2015 · 4 years old at event

Engine

LYCOMING O-320 SERIES (150 hp)

Seats / Engines

2 seats · 1 engine

Last airworthiness date

20150819

ADS-B equipped

Yes — Mode-S A18ECF

Registrant of record

GROSCH RICHARD C

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's improper landing flare, which resulted in a hard landing, subsequent loss of directional control, runway excursion, and ground-loop.

Factual narrative

The pilot reported that, during the third landing, the biplane landed hard and veered off the left side of the runway. The airplane ground looped and the left main landing gear collapsed. He added that he thought the tailwheel was swiveling, but not turning with the rudder. While working on repairs, he observed that the shear pins on the "Mollie heavy duty tailwheel" sheared off, which resulted in the tailwheel not working properly. The airplane sustained substantial damage to the lower right wing. The airport's automated weather observation station reported that, about 8 minutes before the accident, the wind was from 200° at 3 knots. The pilot landed the airplane on runway 15. The airplane was not made available to the Federal Aviation Administration or the National Transportation Safety Board for examination. The pilot reported that, during the third landing that day, the biplane landed hard and veered off the left side of the runway. The airplane ground looped, and the left main landing gear collapsed. The pilot added that he thought the tailwheel was swiveling but not turning with the rudder. While working on repairs, he observed that the shear pins on the tailwheel had sheared off. The airplane sustained substantial damage to the lower right wing. The airplane was not made available to the National Transportation Safety Board for examination, so the reason for the anomaly reported by the pilot could not be determined. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C

Verbatim from NTSB's published report. Source file NTSB_2019_GAA19CA436.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗