ERA12FA303 · Cirrus Design Corp SR22
Bill Air Cirrus Design Corp SR22 · Accident: aerodynamic stall/spin during takeoff
From Anderson Regional Airport (KAND) to Anderson Regional Airport (KAND)
Event
- NTSB case
- ERA12FA303
- 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
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
- N154CK
- Operator
- Bill Air
- Onboard fatalities
- Unknown
- Route
- From Anderson Regional Airport (KAND), Anderson, SCTo Anderson Regional Airport (KAND), Anderson, 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
- 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
- Aerodynamic stall/spin
- 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 pilot receiving instruction performed several takeoffs and landings with a flight instructor aboard. The flight instructor then disembarked and told the pilot to perform three additional solo takeoffs and landings (to a full stop), which the instructor observed from the ground. According to the flight instructor, the pilot's first flight around the airport traffic pattern appeared normal and terminated in a full stop landing and taxi back to the runway for the next takeoff. The instructor stated that the airplane appeared to touch down normally during the second landing; however, shortly thereafter the engine power increased and the airplane began to ascend. The airplane then climbed at a steep angle, entered an aerodynamic stall, and impacted terrain to the left of the runway.
Review of data recorded by an onboard recoverable data module showed that as the airplane approached the runway during the landing, the stall warning activated and 1 second later the pilot increased engine power. As the engine power increased, the airplane began an unarrested turn to the left and the pilot retracted the airplane's flaps from the fully extended to the fully retracted position, which was contrary to the airframe manufacturer's published procedure for a balked landing. The data showed that after it reached an altitude of about 75 feet above ground level, the airplane entered an aerodynamic stall, and then rolled left while pitching down. The data recording ended before the airplane impacted terrain.
Examination of the wreckage revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. The installed whole airframe parachute system likely deployed during the postimpact fire; however, given the low altitude at which the aerodynamic stall occurred, it is unlikely that preimpact deployment of the system would have positively affected the outcome of the accident.
Review of the pilot's flight logs showed that he had accumulated more than 330 total hours of flight experience, including more than 220 hours in the accident airplane; however, he had not previously flown the accident airplane solo before the accident flight. Review of autopsy and toxicology test results showed no evidence of any preexisting condition that would have been expected to result in the pilot's incapacitation.
Probable cause
The pilot's failure to maintain control of the airplane during the aborted landing, which resulted in an aerodynamic stall and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA303
- Event ID
- 20120427X35846
- Case number
- ERA12FA303
- 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: dfc536cd9876b22733fcd6901de9af0c38c9cbafc802f13162e80d6063869b2d; retrieved 2026-09-13T22:20:13.253Z.