GAA15CA008 · Cessna 170A
Cessna 170A · Accident: ground collision before flight
From Sarasota Bradenton International Airport (SRQ) to Sarasota Bradenton International Airport (SRQ)
Event
- NTSB case
- GAA15CA008
- 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
- 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
- Visual Meteorological Cond
Cessna 170A
- Aircraft type
- Cessna 170
- 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
- N170TW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sarasota Bradenton International Airport (SRQ), SARASOTA/BRADENTON, FLTo Sarasota Bradenton International Airport (SRQ), SARASOTA/BRADENTON, FL
- Aircraft age
- About 64 years (built 1951)
- 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
- Ground collision
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and passenger were on a cross-country flight when the pilot noticed that the battery was no longer charging. After landing, the pilot decided to save battery power for the return flight by hand propping the airplane. He briefed the passenger for the hand start procedure, but did not realize the throttle was in the full throttle position. Upon starting, the engine went to full power. The pilot was unable to reenter the airplane before it made two tight left circles on the ramp and collided with an open hangar and the airplane inside.
Federal Aviation Administration Pilot's Handbook of Aeronautical Knowledge FAA-8037-3a contains a section titled, "Hand Propping", which indicates to never allow a person unfamiliar with the controls to occupy the pilot's seat when hand propping. The section also indicates that an additional precaution includes placement of chalks in front of the main tires or if not feasible, the airplane's tail may be securely tied.
Probable cause
The pilot's failure to use the proper hand propping procedures, resulting in a runaway airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA008
- Event ID
- 20150316X61908
- Case number
- GAA15CA008
- 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: 8575eb0e2345f460a2f7eaf56e13e35490b84c48ab21f0633ef60287f1e37258; retrieved 2026-09-16T02:09:26.348Z.