ERA09IA315 · Cirrus Design Corp SR22
Satsair Cirrus Design Corp SR22 · Incident: flight control system malfunction/failure on approach
From Greenville Downtown Airport (GMU) to Greenville Downtown Airport (GMU)
Event
- NTSB case
- ERA09IA315
- 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
- N695CD
- Operator
- Satsair
- Onboard fatalities
- Unknown
- Route
- From Greenville Downtown Airport (GMU), Greenville, SCTo Greenville Downtown Airport (GMU), Greenville, SC
- 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
- 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
- None
Cause areas
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot was "returning the airplane to service," following a maintenance inspection. No anomalies were noted during the preflight inspection, engine start, taxi, run-up, and takeoff roll. As the airplane became airborne, the pilot noticed that the elevator control felt "loose," with about 1/2 inch of "play." The pilot proceeded to an area west of the airport, where the he performed in-fight checks uneventfully. As the airplane was returning to the airport, on short final approach, the pilot reduced the throttle to idle power for landing. Subsequently, about 25 feet above the ground, the nose pitched down. The pilot tried to pull back on the control yoke to flare, but the elevator control was stuck in the mid-range position. The airplane touched down on the nose gear and bounced back up into the air. The sudden jolt of the touchdown seemed to free the elevator control and the pilot was able to complete a normal landing. As the pilot taxied from the runway, he was able to duplicate the control jam. The operator noted that the pitch trim cartridge control rod felt "gritty" when actuated by hand. The operator subsequently reported that the anomaly did not reoccur after the pitch trim cartridge was removed and replaced. In addition, the operator did not report any work performed on the pitch trim cartridge during the recent maintenance inspection. Further examination of the airplane's pitch trim cartridge revealed some corrosion and black grease residue present; however, there was no conclusive evidence found to support a flight control jam.
Probable cause
A pitch control malfunction for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09IA315
- Event ID
- 20090602X31751
- Case number
- ERA09IA315
- 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, damage. 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: 3bade3a5ac8940df6cc8f7b9019f8a8e05a0f451eeb4baea8c4a8f8174801fa4; retrieved 2026-09-15T11:16:19.527Z.