FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA309 · Nanchang China CJ-6A

30 Jun 2013 · Ocean City, MD, United States

Nanchang China CJ-6A · Accident: aerodynamic stall/spin while maneuvering

From Ocean City Municipal Airport (OXB) to Ocean City Municipal Airport (OXB)

Report a problem

Event

NTSB case
ERA13FA309
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
2 · 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

Nanchang China CJ-6A

Aircraft type
Nanchang China CJ-6
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
N116RL
Operator
Thomas J. Geoghegan · private individual
Onboard fatalities
Unknown
Route
From Ocean City Municipal Airport (OXB), Ocean City, MDTo Ocean City Municipal Airport (OXB), Ocean City, MD
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 · aerobatics
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
Aerodynamic 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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

Witness accounts and on-board video recordings of the accident flight revealed that the pilot initiated and performed a series of aerobatic maneuvers with the airplane before initiating a stall, rolling the airplane inverted, and entering a steady-state spin to water contact. The airplane completed 22 revolutions in the spin, with the engine running smoothly, and the stick held fully aft. Examination of the wreckage revealed no evidence of any preimpact mechanical anomaly. Review of the pilot's flight records revealed no evidence of formal aerobatic training. However, the records indicated that he had conducted aerobatic maneuvers, including, on at least one occasion, a flat spin.

The on-board video recordings showed no signs of pilot distress or incapacitation and indicated that the pilot was actively engaged in controlling the airplane and was providing control inputs to maintain the spin to impact. There was no indication of any distracting event or of the pilot attempting to diagnose, troubleshoot, or respond to a perceived in-flight control, system, or engine anomaly. There were multiple cues available to the pilot that the maneuver should be terminated, including an increasing ground presence/perspective from the out-the-window view and the rapidly decreasing altitude indicated on the altimeter in the panel. However, the pilot failed to terminate the maneuver at an altitude adequate to prevent impacting the water. Therefore, it is most likely that the pilot lost situational awareness during the aerobatic maneuver/prolonged spin and did not recover from the spin before impact.

Given the fact that this was a sustained aerobatic maneuver, it is possible that the pilot lost situational awareness due to target fixation, a phenomenon that can occur at varying levels ranging from a breakdown in an instrument scan to failing to pull out of an aerial application run. In these cases, the pilot has cues that a response is required and has the knowledge and skills necessary to successfully perform the response. However, because of the narrowing of attention resulting from the goal-directed activity associated with this phenomenon, a loss of overall situational awareness occurs and the appropriate response is not commanded/input. The circumstances of this accident are consistent with the loss of situational awareness due to target fixation. The pilot appears to have focused on the performance/sustainment of the spin maneuver and therefore misjudged or lost awareness of his exit altitude.

Probable cause

The pilot's failure to terminate the intentional aerobatic spin at an altitude adequate to prevent impacting the water. Contributing to the accident was the pilot's loss of situational awareness due to target fixation during the prolonged aerobatic maneuver.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA309
Event ID
20130630X12443
Case number
ERA13FA309
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: 349ffd904fb27e8d1867ff40b0aae16ebfc34d64022d8314b75c9fd0beec0326; retrieved 2026-09-14T16:00:01.690Z.