CEN17FA152 · Temco GC 1B
Temco GC 1B · Accident: loss of control in flight during takeoff
From Williams Flying Field (24IN) to Shelbyville Municipal Airport (GEZ)
Event
- NTSB case
- CEN17FA152
- 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
Temco GC 1B
- Aircraft type
- Temco GC-1
- 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
- N2377B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Williams Flying Field (24IN), Hartsville, INTo Shelbyville Municipal Airport (GEZ), Shelbyville, IN
- Aircraft age
- About 69 years (built 1948)
- 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
- 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
- Loss of control in flight
- 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 › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident pilot and a friend flew in the friend's airplane to pick up the accident airplane after recent repairs were completed due to a previous ground loop event in 2016. The accident pilot's friend and the mechanic observed the airplane during the takeoff. The airplane accelerated straight and normal and flew "cleanly" off the turf runway. Shortly after rotation, the airplane rolled left until the airplane impacted trees in a near inverted attitude adjacent to the runway. The mechanic stated that he thought the airplane experienced a departure stall during the takeoff. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The witness observations are consistent with the pilot's loss of control after exceeding the airplane's critical angle of attack during takeoff, which resulted in a power-on, aerodynamic departure stall.
Probable cause
The pilot's loss of control after exceeding the airplane's critical angle of attack during takeoff, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17FA152
- Event ID
- 20170412X64143
- Case number
- CEN17FA152
- 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: 462161ecd45628d9e055cbf970844807c7f220c11f461606a2fb465bc72fe941; retrieved 2026-09-15T06:01:04.583Z.