FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI01LA116 · Piper PA-28-161

13 Apr 2001 · Culver, IN, United States

Piper PA-28-161 · Accident: on ground/water collision with object during takeoff

From Clarion North Medical Center Heliport (IN73) to an unrecorded destination

Report a problem

Event

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

Piper PA-28-161

Aircraft type
Piper PA-28
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
N3573S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Clarion North Medical Center Heliport (IN73), Culver, INTo 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
Takeoff · rejected takeoff
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
On ground/water collision with object
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(cfi) › Remedial action, delayed

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

NTSB narrative

The airplane impacted trees when it veered off runway 16 after an aborted takeoff during an instructional flight. During takeoff, the airplane climbed to an altitude of 5 feet above the runway before settling back onto the runway. The certified flight instructor took control of the airplane and applied maximum braking but was unable to stop. He then veered the airplane off the runway in an attempt to avoid running off a steep slope and a swamp located beyond the end of the runway. Winds reported at a weather station located 34 miles northeast of the airport were 260 at 7 kts. There are several FAA publications which address settling onto the runway after liftoff in regards to high rotational rates, rotation speed, ground effect, and downwind takeoffs.

Probable cause

the CFI delayed remedial action during the takeoff. Additional factors were the wrong runway was selected, the tailwind, and the trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI01LA116
Event ID
20010416X00761
Case number
CHI01LA116
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: 5dfebff6dc2d0ccebd5b6e8c64e86f645ee88c0478a9dbdd44f31e35942ca658; retrieved 2026-09-22T12:02:28.981Z.