FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC93LA011 · Anderson Aircraft Corp. PITTS S-1

8 Oct 1992 · Minersville, PA, United States

Bardic Aviation Anderson Aircraft Corp. PITTS S-1 · Accident: loss of control in flight while maneuvering

From Schuylkill County Joe Zerbey Airport (ZER) to Ziro Airport (ZER)

Report a problem

Event

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

Anderson Aircraft Corp. PITTS S-1

Aircraft type
Anderson PITTS S-1
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
N31SP
Onboard fatalities
Unknown
Route
From Schuylkill County Joe Zerbey Airport (ZER), Pottsville, PATo Ziro Airport (ZER)
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
Maneuvering
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 in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Flt control syst, elevator control › Foreign object
  • Flt control syst, elevator control › Jammed
  • Pilot in command › Aircraft control, not possible

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

NTSB narrative

THE PILOT WAS PERFORMING AEROBATIC MANEUVERS TO PROVIDE AN OPINION OF THE AIRPLANE TO THE OWNER. FAA RECORDS INDICATE THAT THE PILOT WAS CERTIFIED FOR AEROBATIC MANEUVERS TO THE SURFACE. THE PILOT HAD OVER 300 HOURS OF FLIGHT EXPERIENCE IN THE PITTS. AFTER SEVERAL AEROBATIC MANEUVERS, THE PILOT WAS UNABLE TO COUNTER A NOSE-UP ATTITUDE AND THE AIRPLANE STALLED AND ENTERED A SPIN. HE WAS ABLE TO STOP THE SPIN ROTATION, BUT WAS UNABLE TO CONTROL THE AIRPLANE PITCH PRIOR TO IMPACTING THE GROUND. A C-CLAMP WAS FOUND IN THE AFT FUSELAGE, NEAR THE ELEVATOR CONTROLS. THE CLAMP WAS BENT, GOUGED, AND HAD MARKS WHERE THE PAINT HAD BEEN REMOVED. AN ELEVATOR CONTROL ROD WAS FRACTURED.

Probable cause

A LOSS OF CONTROL DUE TO A FOREIGN OBJECT JAMMING THE ELEVATOR FLIGHT CONTROLS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC93LA011
Event ID
20001211X15941
Case number
NYC93LA011
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: 9be63b1497d255e0e00ee2746a302a6381382f950e6d92853ae4e5baa3c6d08b; retrieved 2026-09-21T14:41:12.021Z.