FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD00FA082 · Grumman AA-5B

10 Sept 2000 · Carrollton, OH, United States

Grumman AA-5B · Accident: in flight collision with terrain/water during landing

From Put In Bay Airport (3W2) to Carroll County-Tolson Airport (TSO)

Report a problem

Event

NTSB case
IAD00FA082
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
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
Instrument Meteorological Cond

Grumman AA-5B

Aircraft type
Grumman AA-5
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
N28817
Operator
Unknown
Onboard fatalities
Unknown
Route
From Put In Bay Airport (3W2), PUT-IN-BAY, OHTo Carroll County-Tolson Airport (TSO), 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
Landing · aborted
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
Substantial

Cause areas

  • Pilot in command › Aborted landing, delayed

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

NTSB narrative

The pilot attempted his first landing to the wet 4,300-foot long asphalt runway, but touched down beyond the halfway point and aborted the landing. On his second attempt to land on Runway 7, the pilot approached at 80 knots, and landed about 300 feet beyond the landing threshold. The pilot then raised the flaps and applied the brakes, but the brakes locked and the aircraft skidded. About 2/3 down the runway, the pilot aborted the landing. He applied full power, added 10 degrees of flaps, and started a climb. The pilot heard the stall horn and realized that he could not out climb the tree covered hills located off the end the runway, and elected to 'crash straight ahead.' The pilot reported that the cause of the accident was, 'I came in a little too hot.' The pilot also acknowledged that he did not get a good look at the windsock, but thought he landed with a tailwind. The surface winds were from 250 degrees at 6 knots, and at 2,600 feet msl they were from 250 degrees at 31 knots. The pilot reported no mechanical deficiencies.

Probable cause

Pilot's improper decision to delay the aborted landing, which resulted in an insufficient airspeed during climb and subsequent collision with terrain. A factor was the wet runway and tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD00FA082
Event ID
20001212X21991
Case number
IAD00FA082
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: 2f591d8a61664e290291091b82c889ada033c16e947f2af7d9c127f5141664f4; retrieved 2026-09-20T20:52:23.429Z.