FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09FA267 · Cirrus Design Corp SR22

28 Apr 2009 · Mayfield Village, OH, United States

Cirrus Design Corp SR22 · Accident: loss of control in flight during initial climb

From Cuyahoga County Airport (CGF) to Buffalo Niagara International Airport (BUF)

Report a problem

Event

NTSB case
CEN09FA267
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
2 · 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 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
N504MD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cuyahoga County Airport (CGF), Cleveland, OHTo Buffalo Niagara International Airport (BUF), Buffalo, NY
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
Initial climb
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The instrument certified airplane climbed into instrument meteorological conditions about 30 seconds after takeoff. Radar track data showed that the airplane entered a right turn shortly after takeoff and entered the cloud base. The airplane remained in that right turn until it completed nearly 1-1/2 complete turns. The airplane rolled out and subsequently climbed 1,500 feet over next 17 seconds. The airspeed decreased to 50 knots and the airplane’s heading abruptly transitioned from the south to the north-northwest which could have represented an aerodynamic stall. The airplane then descended before beginning another climb. The airplane completed two additional descent and climb oscillations with minimum airspeeds of 60 knots and 50 knots, respectively. Maximum pitch angles of 50 degrees nose up and nose down, and bank angles of 75 degrees were recorded during the flight. The duration of the accident flight was approximately 4 minutes and 30 seconds.

The airplane impacted a wooded area located about 3 miles from the departure airport and was destroyed by impact forces and a postimpact fire. An examination of the airframe and engine did not revealed preimpact anomalies. No flight display and/or autopilot system faults were recorded during the accident flight. Further review of the flight data did not reveal inconsistencies within the data itself. The data indicated that the pilot initially engaged the autopilot about 5 seconds after lifting off when the airplane was approximately 61 feet above ground level. The autopilot bugs were set to the assigned heading and initial altitude prior to takeoff. However, after takeoff the pilot failed to properly engage the autopilot altitude preselect mode; the altitude hold mode was entered instead. As a result, the altitude and vertical speed bug settings were reset automatically to maintain the airplane’s altitude. At that point, the airplane’s altitude was above that specified by the autopilot bug. Subsequent attempts to engage the vertical speed/altitude pre-select mode caused the system to begin a descent to intercept the inadvertent altitude set in the autopilot.

About 1 minute into the flight, the pilot reset the altitude bug above the airplane’s current altitude at that time. The data suggests that the pilot never adequately regained control of the airplane. The pilot purchased the accident airplane about 7 months prior to the accident. He completed visual flight rules transition training at the time he took delivery of the airplane. The training did not include an instrument proficiency check. Prior to the transition training, the pilot reported a total flight time of 1,344 hours, which included 20 hours flight time and 4 hours instrument flight time within the one-year period preceding the training.

Probable cause

The pilot’s failure to maintain control of the airplane while operating in instrument meteorological conditions due to spatial disorientation. Contributing to the accident was the pilot’s inattention to basic aircraft control while attempting to program the autopilot system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09FA267
Event ID
20090428X81708
Case number
CEN09FA267
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: 6552cfe9767e677ab8916b2072ad415ae92cac994dc5171f1fce6e5bbc998d7b; retrieved 2026-09-13T20:06:06.884Z.