FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA007 · Aviat Pitts S-2B

10 Oct 2003 · Cromwell, MN, United States

Aviat Pitts S-2B · Accident: in flight collision with terrain/water while maneuvering

From Duluth International Airport (DLH) to Duluth International Airport (DLH)

Report a problem

Event

NTSB case
CHI04LA007
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
1 · 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

Aviat Pitts S-2B

Aircraft type
Aviat PITTS S-2B
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
N68PS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Duluth International Airport (DLH), Duluth, MNTo Duluth International Airport (DLH), MN
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 terrain/water
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

  • Pilot in command › Altitude/clearance, not maintained

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

NTSB narrative

The airplane impacted a lake while performing aerobatics at an altitude of about 1,500 feet above ground level. A witness, who stated that he was familiar with the pilot's aerobatic routine stated that the pilot began an intentional spin about 1,500 feet above ground level (AGL), initiated a recovery at 150-200 feet AGL, and impacted the lake. Examination of the wreckage confirmed flight control continuity. The pilot was found in the rear seat secured by the airplane restraint harness. He was wearing a parachute.

Probable cause

The altitude/clearance not maintained by the pilot while performing aerobatic maneuvers. Contributing factors were the planning/decision to perform an aerobatic maneuver at a low altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA007
Event ID
20031015X01734
Case number
CHI04LA007
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: 4133583b57a5f732463415af7f495a958d2b477c94d73f6285b1c76fd1ad045c; retrieved 2026-09-20T18:54:22.212Z.