GAA17CA537 · Bellanca 8GCBC
Bellanca 8GCBC · Accident before flight
From Resort Airport (0AL1) to Resort Airport (0AL1)
Event
- NTSB case
- GAA17CA537
- 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
Bellanca 8GCBC
- Aircraft type
- Bellanca 8
- 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
- N181TM
- Operator
- Adroaldo Begrow
- Onboard fatalities
- Unknown
- Route
- From Resort Airport (0AL1), Foley, ALTo Resort Airport (0AL1), Foley, AL
- Aircraft age
- About 43 years (built 1974)
- 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
- Prior to flight
- 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
- Miscellaneous/other
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during banner towing operations, he was on approach to drop the banner and pulled the tow release, but the banner did not release. The banner hit the ground and broke away from the airplane, and the airplane nosed over.
The release mechanism has three hooks, but they typically only use the No. 1 hook. Postaccident examination of the hook release mechanism did not reveal any anomalies that would have prevented the banner from being released. The pilot believed that the ground crew mistakenly set up the No. 3 hook to pick up and tow the banner instead of the No. 1 hook. Therefore, when he went to release the banner from the No.1 hook, there was nothing to release.
Postaccident examination of the airplane revealed substantial damage to the empennage.
The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The ground crew’s incorrect hook up of the banner, which resulted in a nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA537
- Event ID
- 20170823X31730
- Case number
- GAA17CA537
- 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. 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: cb097b56caad17953d688c2b826a95e9b8150f34306ad4d36828a101336950ce; retrieved 2026-09-16T05:44:44.484Z.