ERA09IA009 · Cirrus Design Corp SR22
Tiger Jones Aircraft Cirrus Design Corp SR22 · Incident: flight control system malfunction/failure on approach
From Daytona Beach International Airport (DAB) to Lakeland Linder International Airport (LAL)
Event
- NTSB case
- ERA09IA009
- 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
- Incident
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N101CD
- Operator
- Tiger Jones Aircraft
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo Lakeland Linder International Airport (LAL), Lakeland, FL
- 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 downwind
- 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
- Flight control system malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While approaching the destination airport, the pilot attempted to extend the flaps to the 50-precent position. After moving the selector, the pilot heard a "bang" and the airplane rolled right. The pilot maintained control of the airplane, and after landing noted that the flaps were extended asymmetrically. Post-incident examination of the flap system revealed that flap actuator rod end was bent 90 degrees, and broken. No other anomalies of the flap system were found. The condition of the flap actuator rod end suggested that the rod end was bent initially while retracting the flaps, an action associated with extension of the flap actuator. This resulted in cracks forming at the thread roots along the outer bend. Subsequent attempts to extend the flaps placed the rod end under a reverse bending moment that acted to straighten the rod end. The manufacturer's assessment of the situation in a service bulletin concluded that the flaps could have been retracted beyond the full up position, possibly due to a sensor failure, initially bending the rod end. During a subsequent deployment, during the incident flight, the flaps over-deployed and allowed the flap actuator linkages to over-center. The rod end subsequently failed, and allowed the asymmetric flap condition.
Probable cause
A failure of the flap actuator rod end due to low stress, high cycle fatigue, and subsequent overstress failure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09IA009
- Event ID
- 20081008X50538
- Case number
- ERA09IA009
- 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: 1d0d3a9c624841d4aeacc3cf96ab2a0bee6429f55dd6d17ee7eb318ee0ca3cb8; retrieved 2026-09-15T10:26:20.403Z.