FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL84LA131 · Pitts SPECIAL S2A SPECIAL S2

10 Mar 1984 · Apex, NC, United States

Pitts SPECIAL S2A SPECIAL S2 · Accident: hard landing

Report a problem

Event

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

Pitts SPECIAL S2A SPECIAL S2

Aircraft type
Pitts SPECIAL S2A
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
N83798
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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 · flare/touchdown
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
Hard landing
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

  • Dual student › Directional control, not possible
  • Dual student › Flare, improper
  • Landing gear, normal brake system › Lack of
  • Landing gear, normal brake system › Previous damage
  • Pilot in command(cfi) › Ground loop/swerve, uncontrolled
  • Pilot in command(cfi) › Remedial action, inadequate

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

NTSB narrative

THE ACFT MADE A HARD LANDING AND DAMAGED A BRAKE. DURING THE SECOND LANDING THE BRAKES WERE FOUND TO BE MALFUNCTIONING AND AS THE RUDDER BECAME INEFFECTUAL THE ACFT LEFT THE RWY AND COLLIDED WITH A HANGER. THE OWNER OF THE ACFT WAS IMPROPERLY ACTING AS AN INSTRUCTOR TO A PRIVATE PLT. THE OWNER WAS NOT A CFI.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL84LA131
Event ID
20001214X38966
Case number
ATL84LA131
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: 60254b951f9c10a2fb4501f606fc767ba5937b36a998d22b54db0511df5c2810; retrieved 2026-09-23T20:46:05.896Z.