FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA500 · Aerotek PITTS SPECIAL S-1S

17 Sept 2016 · Reno, NV, United States

Aerotek PITTS SPECIAL S-1S · Accident: loss of control on ground during landing

From Reno-Stead Airport (RTS) to Reno-Stead Airport (RTS)

Report a problem

Event

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

Aerotek PITTS SPECIAL S-1S

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
N91JW
Operator
Unknown
Onboard fatalities
Unknown
Route
From Reno-Stead Airport (RTS), Reno, NVTo Reno-Stead Airport (RTS), Reno, NV
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
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

According to the pilot of the tailwheel-equipped biplane, during the landing roll, the tailwheel became "stuck" in an expansion joint that runs down the centerline of the runway. She reported that when the tailwheel became unstuck, the biplane "swung wildly to the left," the bottom right wing struck the ground, and the airplane came to a stop on the runway after turning 180° to the left.

A video of the accident, taken by a camera mounted on the accident biplane and posted on social media, revealed that the biplane touched down on the runway to the left of the centerline. During the landing roll and after crossing the taxiway A2 intersection, the biplane began drifting right. The tailwheel is seen crossing the centerline expansion joint about 30° to the joint and then rolling over the joint without hesitation. The tail is then seen swinging to the right at an increasing rate. The biplane ground looped to the left, and the bottom right wing sustained substantial damage.

The pilot reported that there were no preaccident mechanical failures or anomalies with the airplane that would have prevented normal operation.

Probable cause

The pilot’s failure to maintain directional control during the landing roll, which resulted in a ground loop.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA500
Event ID
20160922X33620
Case number
GAA16CA500
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 81c90adf0dbc3c263959be5ed361110232bfa9d0219603bcf8deadb70a7089a2; retrieved 2026-09-16T04:17:58.040Z.