NYC02LA071 · Cirrus Design Corp. SR-20
Cirrus Design Corp. SR-20 · Accident: airframe, component or system failure on approach
From Blue Grass Airport (LEX) to Blue Grass Airport (LEX)
Event
- NTSB case
- NYC02LA071
- 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
- Instrument Meteorological Cond
Cirrus Design Corp. SR-20
- Aircraft type
- Cirrus SR-20
- 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
- N244CD
- Operator
- Paul A. Heflin · private individual
- Onboard fatalities
- Unknown
- Route
- From Blue Grass Airport (LEX), Lexington, KYTo Blue Grass Airport (LEX), KY
- 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
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The instrument rated pilot and passenger departed into instrument meteorological conditions (IMC) and intended to practice some instrument approaches. Shortly after takeoff, the pilot reported a turn coordinator failure. The turn coordinator indicated a left bank regardless of control inputs and the pilot became disoriented. The airplane was equipped with a Cirrus Airplane Parachute System (CAPS). The pilot stated he pulled the CAPS activation handle repeatedly; however, the cable did not extend and "nothing seemed to happen." The airplane broke out of the cloud layer, and the pilot performed an emergency landing to a field. Witnesses near the accident site reported that the CAPS parachute deployed after ground contact. Post accident testing of the wreckage did not reveal any pre-impact instrumentation, or autopilot failures. The CAPS system also functioned normally; however, it was noted that the pull forces to activate the CAPS parachute varied significantly.
Probable cause
The pilot's failure to maintain aircraft control. Factors in this accident were the undetermined failure of the turn coordinator, as reported by the pilot, and the instrument meteorological conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA071
- Event ID
- 20020326X00393
- Case number
- NYC02LA071
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 2ca89ad439cf390259bba6090884eef03b9f228f977aa8c42389cbb97457d476; retrieved 2026-09-21T19:45:42.873Z.