Cirrus Design CORP SR22 accident near Melbourne, Florida, February 29, 2012
On February 29, 2012 at about 10:01 pm local time, a Cirrus Design CORP SR22, registered N544SR, was substantially damaged in an accident during approach (VFR pattern base) near Melbourne, Florida (Melbourne International airport). It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's abrupt maneuver in response to a perceived traffic conflict, which resulted in an accelerated stall and a loss of airplane control at low altitude. Contributing to the accident was the air traffic controller's incomplete instructions, which resulted in improper sequencing of traffic landing on the same runway.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 29, 2012 · about 10:01 pm local time · cases in 2012
- Place
- Melbourne, Florida · Melbourne International · cases near this airport · map
- Type
- Accident
- Injuries
- 3 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR22
- Registration
- N544SR · no longer on the register · serial 2559
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Several airplanes and a helicopter were in the traffic pattern at the tower-controlled airport performing simultaneous operations to parallel runways (9L and 9R) around the time of the accident. The accident pilot contacted the tower air traffic controller while south of the airport requesting a full-stop landing; the controller advised the pilot to report when the airplane entered the downwind leg of the traffic pattern. The controller subsequently cleared the accident airplane to land and expected the pilot complete a "normal" downwind traffic pattern and land behind the airplane already established on final approach for runway 9R; however, the controller did not provide sequencing instructions. The accident airplane proceeded directly to a tight right-base entry into the traffic pattern for landing on runway 9R, contrary to the controller's original expectation but permissible based on the clearance to land. The controller radioed the accident pilot to confirm that he had visual contact with the airplane on a 1-mile final approach for runway 9R (the traffic was 300 feet below and 1 mile west). This was the first indication by the controller to the accident pilot that there was additional landing traffic sequenced to the same runway he had been cleared to land on. The accident pilot replied that he was on a "real short base" for runway 9R, and the controller responded, "no sir, I needed you to extend to follow the [airplane] out there on a mile final, cut it in tight now, cut it in tight for nine right." The two airplanes had closed within 1/2 mile of each other, but were still separated by 300 feet altitude. The pilot of the airplane on short final for 9R maintained situational awareness throughout, perceived the conflict before the controller or the accident pilot, and responded calmly and benignly to the conflict. The accident pilot needed only to arrest his descent, at a minimum, to avoid any collision. A flight instructor and an airline pilot both described seeing the accident airplane pitch up, bank left, then roll inverted. The flight instructor stated that this action occurred as the controller was "yelling at" the pilot. Both witnesses described what they saw as "an accelerated stall." Data extracted from the multifunction and primary flight displays revealed that the airplane pitched up and rolled inverted to the left at the same time that engine power was increased rapidly. When engine power is increased, a pilot must apply sufficient right rudder to counteract the left-rolling tendency, particularly if the airspeed is slow and the angle of attack is high, as it would be during landing. When instructed by the controller to "cut it in tight," the accident pilot over-controlled the airplane, lost control, and impacted terrain. Contributing to the traffic conflict was the controller's lack of upfront sequencing instructions or subsequent sequencing instructions when the accident aircraft was cleared to land. Examination of the data and a postaccident examination of the wreckage revealed no preimpact mechanical anomalies that would have precluded normal operation.
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
- Aerodynamic stall/spin during approach (VFR pattern base) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- factor Environmental issues › Operating environment › Air traffic/operating proc › ATC clearance procedure › Compliance w/ procedure
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 515 hours in all; 350 in this make and model; 28 in the last 90 days
- Last flight review: April 30, 2009
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 1,250 hours
- Last inspection: annual inspection, August 30, 2011
- Maximum gross weight: 3,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor IO-550-N (piston); 0 hours total
The flight
- Departed from: X59 Valkaria FL at 9:55 pm
- Destination: MLB Melbourne FL
- Flight plan: none
- Runway 09R, 10,181 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 130° at 13 knots, gusting 18
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 68°F (20°C)
- Altimeter: 30.11 inHg
- Observation at 9:53 pm from MLB, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
17 documents, released by the NTSB on November 27, 2012. 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.
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
- N544SR: not on the register today · the record of its deregistration
- Engine: Cont Motor IO-550-N 2,794 aircraft carry this series today · as the NTSB recorded it
- Melbourne Orlando International · nearest airport
- Valkaria Airport · departed from
- Accidents and incidents in Florida 6,111 since 1982 · 982 in the last ten years
- Florida 21,718 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA12FA196.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.
