ERA12CA027 · ICA Brasov IS-29D2
ICA Brasov IS-29D2 · Accident: controlled flight into terrain/object (CFIT) on approach
From Chilhowee Gliderport (92A) to Chilhowee Gliderport (92A)
Event
- NTSB case
- ERA12CA027
- 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
ICA Brasov IS-29D2
- Aircraft type
- Ica Brasov IS-29
- Category
- Glider
- 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
- N1339X
- Operator
- Tampa Bay Soaring Society
- Onboard fatalities
- Unknown
- Route
- From Chilhowee Gliderport (92A), Benton, TNTo Chilhowee Gliderport (92A), Benton, TN
- 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
- Approach · VFR pattern final
- 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
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the glider stated that he was returning to the airport at the conclusion of a 1.5-hour flight. The pilot approached the airport at a slow airspeed and a lower-than-normal altitude due to a misinterpretation of the altimeter reading. The pilot continued the approach for landing, and the glider struck telephone wires on the final leg of the traffic pattern. The glider sustained substantial damage to the wing spar and tailboom. The pilot reported there were no preaccident mechanical malfunctions or anomalies with the glider.
Probable cause
The pilot's improper in-flight planning, which resulted in a low-altitude traffic pattern entry and subsequent collision with telephone wires.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12CA027
- Event ID
- 20111015X32756
- Case number
- ERA12CA027
- 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, coordinates. 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: ba938d040ae67884aaafd7e7f7326d8524ca68b00ce053683078ba46124ff057; retrieved 2026-09-15T16:50:53.252Z.