Accident Cirrus SR22 GTS G3 N544SR,
ASN logo
ASN Wikibase Occurrence # 144125
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Wednesday 29 February 2012
Type:Silhouette image of generic SR22 model; specific model in this crash may look slightly different    
Cirrus SR22 GTS G3
Registration: N544SR
MSN: 2559
Year of manufacture:2007
Total airframe hrs:1250 hours
Engine model:Continental IO-550-N
Fatalities:Fatalities: 3 / Occupants: 3
Aircraft damage: Substantial
Location:Melbourne International Airport - KMLB, Melbourne, FL -   United States of America
Phase: Approach
Departure airport:Valkaria, FL (X59)
Destination airport:Melbourne, FL (MLB)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.
Probable Cause: 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.

Accident investigation:
Investigating agency: NTSB
Report number: ERA12FA196
Status: Investigation completed
Duration: 9 months
Download report: Final report





Revision history:

29-Feb-2012 20:24 Geno Added
29-Feb-2012 20:32 Geno Updated [Narrative]
01-Mar-2012 01:37 RobertMB Updated [Time, Registration, Operator, Nature, Source, Damage, Narrative]
01-Mar-2012 08:16 Geno Updated [Registration, Cn, Source]
01-Mar-2012 11:36 Geno Updated [Source]
01-Mar-2012 14:25 RobertMB Updated [Aircraft type, Source]
06-Mar-2012 21:41 Geno Updated [Time, Source, Narrative]
19-Mar-2012 08:45 Anon. Updated [Departure airport]
20-Dec-2013 20:14 MarkStep Updated [Source, Narrative]
21-Dec-2016 19:26 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
14-Sep-2017 17:27 harro Updated [Source, Embed code, Narrative]
27-Nov-2017 20:18 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314