The U.S. aircraft register, updated daily
Accidents · NTSB CEN09FA267 · Final report

Cirrus Design CORP SR22 accident near Mayfield Village, Ohio, April 28, 2009

On April 28, 2009 at about 8:15 pm local time, a Cirrus Design CORP SR22, registered N504MD, was destroyed in an accident during initial climb near Mayfield Village, Ohio (Cuyahoga County airport). It was a business flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 28, 2009 · about 8:15 pm local time · cases in 2009
Place
Mayfield Village, Ohio · Cuyahoga County · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cirrus Design CORP SR22
Registration
N504MD · registry record · serial 2695
Damage
Destroyed
Flight
Business flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during initial climb defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Psychological › Perception/orientation/illusio › Spatial disorientation › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Task performance › Use of equip/info › Use of automation › Pilot

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,344 hours in all; 1,280 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 224.1 hours
  • Last inspection: annual inspection, October 7, 2008
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO-550-N (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: CGF Cleveland OH at 8:12 pm
  • Destination: BUF Buffalo NY
  • Flight plan: IFR
  • Runway 06, 5,102 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 010° at 8 knots
  • Visibility: 4 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 45°F (7°C), dew point 43°F (6°C)
  • Altimeter: 30.37 inHg
  • Observation at 8:16 pm from CGF, 2 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

23 documents, released by the NTSB on October 1, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Witness Statements PDF, 2 pages View Download
2 Report Photos with 15 Imbedded Images) PDF, 8 pages View Download
3 Transcript of Communications -- Flight Service PDF, 3 pages View Download
4 Transcript of Radio Communications -- Control Tower PDF, 7 pages View Download
5 Transcript of Radio Communications -- Departure Control PDF, 3 pages View Download
6 Cockpit Display(s) - Recorded Flight Data - Specialist's Factual Report PDF, 34 pages View Download
7 Cockpit Display(s) - Recorded Flight Data - Attachment 1 Tabular Data Accident Flight - (Csv Format) data file Download
8 Cockpit Display(s) - Recorded Flight Data - Attachment 2 Tabular Data Previous Flight- (Csv Format) data file Download
9 Meteorology 5 - Factual Report of Weather Specialist PDF, 13 pages View Download
10 Weather Observation Log - Cuyahoga County (Cgf) PDF, 1 page View Download
11 Summary of Accident Site and Airplane Examination PDF, 4 pages View Download
12 Statement - Flight Instructor PDF, 1 page View Download
13 Cirrus Pilot Training Record PDF, 5 pages View Download
14 Airport Diagram-terminal Procedures - Cgf PDF, 4 pages View Download
15 Maintenance Records - Airframe Log PDF, 16 pages View Download
16 Maintenance Records - Engine Log PDF, 6 pages View Download
17 Maintenance Records - Propeller Log PDF, 4 pages View Download
18 Maintenance Records - Ad Compliance PDF, 9 pages View Download
19 Aircraft Fueling Record PDF, 3 pages View Download
20 Pilot's Operating Handbook and Maintenance Manual Excerpts PDF, 15 pages View Download
21 Toxicological Report - Pilot PDF, 1 page View Download
22 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
23 Statement of Party Representatives to NTSB Investigation PDF, 3 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN09FA267.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.