FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA279 · Ernst Pitts S2E

25 Sept 2004 · Hanover, IN, United States

Ernst Pitts S2E · Accident: in flight collision with object while maneuvering

From Lee Bottom Airport (64I) to Moraine Air Park (I73)

Report a problem

Event

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

Ernst Pitts S2E

Aircraft type
Ernst PITTS S2E
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
N8005X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lee Bottom Airport (64I), Hanover, INTo Moraine Air Park (I73), Dayton, OH
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
In flight collision with object
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
Tree(s)
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

  • Pilot in command › Clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The experimental amateur-built aerobatic airplane was substantially damaged when it impacted trees and terrain during an aerobatic maneuver. The pilot reported that they entered a hammerhead [stall maneuver] at 140 - 145 [miles per hour]. The pilot-rated passenger reported that the pilot executed a "sporty" takeoff, followed by a vertical climb. He stated the pilot performed a hammerhead stall and a low-level pass down the runway. The pilot-rated passenger stated that near the end of the runway the pilot once again pulled into a vertical climb, followed by another hammerhead stall. He reported that as the pilot applied power entering the climb the engine hesitated momentarily similar to when the throttle is advanced too quickly. The passenger stated that the aircraft did not have enough altitude to regain airspeed after the stall. Witnesses stated that the accident airplane took off and pulled into a vertical climb. The pilot executed several aerobatic maneuvers including low-level passes over the runway. The witnesses thought the airplane had departed the area when they saw it descend into trees south of the airport. The airport manager, one of the witnesses, stated that the airplane impacted at a 60-degree or more angle and recalled that it was not spinning or turning. The witnesses did not perceive any engine problems. The aircraft impacted a one-lane airport perimeter road south-southeast of the runway. Trees, approximately 25 feet in height, lined both sides of the road. Numerous tree strikes were observed on the tree line south of the road. The aircraft came to rest on the north side of the road, oriented in a southerly direction. A post-accident examination did not reveal any anomalies associated with a pre-impact failure. The operation manual for the accident aircraft stated that the recommended entry speed for a hammerhead stall maneuver was between 130 and 180 miles per hour.

Probable cause

The pilot's failure to maintain clearance to the trees and terrain during the aerobatic maneuver. Contributing factors were the pilot's decision to perform a low-level, ostentatious aerobatic display and the trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA279
Event ID
20041008X01603
Case number
CHI04LA279
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, 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: f25ca5e31708f86a1c50c5c88dc358c586a4575f225b42bb103628b5ee0ee7ab; retrieved 2026-09-21T09:12:40.690Z.