CEN13FA274 · Boeing-Stearman IB75A
Boeing-Stearman IB75A · Accident: controlled flight into terrain/object (CFIT) while maneuvering
From James M. Cox Dayton International Airport (KDAY) to James M. Cox Dayton International Airport (KDAY)
Event
- NTSB case
- CEN13FA274
- 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
- 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
Boeing-Stearman IB75A
- Aircraft type
- Boeing Stearman IB75
- 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
- N450JW
- Operator
- Jane Wicker Airshow
- Onboard fatalities
- Unknown
- Route
- From James M. Cox Dayton International Airport (KDAY), Dayton, OHTo James M. Cox Dayton International Airport (KDAY), Dayton, OH
- Aircraft age
- About 72 years (built 1941)
- 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
- 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
- Controlled flight into terrain/object (CFIT)
- 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 › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
A video study using five videos taken of the accident sequence by airshow spectators revealed that, during the wing-walking performance, the airplane began a shallow climb to reposition for the next performance maneuver. After the airplane was aligned along the show line, the airplane began a left roll to the inverted position and continued rolling until it was nearly inverted, but it stopped at an orientation of 156 degrees of rotation (24 degrees short of fully inverted flight). During the last seconds of the flight, the airplane's flightpath shifted from the east to the east-northeast, which directed it outside of the performance area and toward a Boeing 757 parked near aircraft hangars about 0.3 mile east-southeast of the accident site. About 1.3 seconds before the accident, the airplane began rolling right and then abruptly pitched toward the ground just before impact. During the final 2 seconds, the airplane's groundspeed reduced from about 106 to 84 knots. An examination of the airplane's wreckage did not reveal any preimpact anomalies that would have precluded normal operation.
An airshow crewmember reported hearing the wing walker telling the pilot before the airshow performance that he had previously flown too fast when she was walking along the wing to position herself. It is unknown if they further discussed the exact needs of the wing walker during the performance. However, it is likely that the pilot flew a more gradual maneuver to reduce the forces against the wing walker while she repositioned herself on the wing, which resulted in the entry into the maneuver not being set up as expected and created a tighter turn radius. On the videos, the airplane appeared to be flying slower than normal and did not pitch to the target nose-high parameter before beginning the left roll. The airplane developed a negative, or descending, vector as the airplane rolled toward the inverted position. The roll to the inverted position was stopped short of expected; because of the bank, the airplane was heading toward the crowd line. The airplane flew for a few seconds while partially inverted and well below the maneuver's 110-mph target airspeed. The airplane then began a right roll, although the planned maneuver typically used a left roll. It could not be determined if the pilot chose to discontinue the maneuver and exit with a reversed right turn to avoid a perceived collision hazard with the parked Boeing 757, to remain within the performance area, to not overfly the crowd, or a combination of these factors.
Probable cause
The pilot's controlled flight into terrain. Contributing to the accident was the pilot's modified airshow maneuver, which placed the airplane at low altitude and airspeed and out of position within the performance area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13FA274
- Event ID
- 20130513X32942
- Case number
- CEN13FA274
- 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, coordinates. 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: 6daaba7f3acf621044c0f95bcb0269e6b9a66c0be3e9a33041058d04c511af6c; retrieved 2026-09-14T15:56:44.565Z.