Aviation Crash Map

Cessna 550 N262Y

1 October 2010 · Manteo, North Carolina, United States · Minor injuries

Summary

On 1 October 2010 at about 12:30 local time, a Cessna 550 registered N262Y, operated by Colnan Inc., was involved in an accident near Manteo, North Carolina, United States. 7 people were on board and 7 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 12:30
Classification
Accident
Location
Manteo, North Carolina, United States
Nearest airport
Dare County Regional (MQI)
Coordinates
35.9189, -75.6953
Aircraft
Cessna 550
Registration
N262Y
Category
Airplane
Engines
2
Operator
Colnan Inc.
Operating rule
Part 91: General Aviation
Purpose of flight
Executive/Corporate
Phase of flight
Not recorded
Route
Tampa → Manteo
Aircraft damage
Substantial
Weather
IMC
Light
Day
NTSB number
ERA11FA001

People

7 people had minor injuries.

On board Died Serious Minor Uninjured
7 0 0 7 0

Probable cause

The pilot-in-command's failure to maintain proper airspeed and his failure to initiate a go-around, which resulted in the airplane touching down too fast on a short, wet runway and a subsequent runway overrun. Contributing to the accident was the copilot's failure to adequately monitor the approach and call for a go around and the flight crew's lack of proper crew resource management.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

According to postaccident written statements from both pilots, the pilot-in-command (PIC) was the pilot flying and the copilot was the pilot monitoring. As the airplane approached Dare County Regional Airport (MQI), Manteo, North Carolina, the copilot obtained the current weather information. The automated weather system reported wind as 350 degrees at 4 knots, visibility at 1.5 miles in heavy rain, and a broken ceiling at 400 feet. The copilot stated that the weather had deteriorated from the previous reports at MQI. The PIC stated that they would fly one approach to take a look and that, if the airport conditions did not look good, they would divert to another airport. Both pilots indicated in phone interviews that, although they asked the Washington air route traffic control center controller for the global positioning system (GPS) runway 5 approach, they did not expect it due to airspace restrictions. They expected and received a GPS approach to runway 23 to circle-to-land on runway 5. According to the pilots' statements, the airplane was initially fast on approach to runway 23. As a result, the copilot could not deploy approach flaps when the PIC requested because the airspeed was above the flap operating range. The PIC subsequently slowed the airplane, and the copilot extended flaps to the approach setting. The PIC also overshot an intersection but quickly corrected and was on course about 1 mile prior to the initial approach fix. The airplane crossed the final approach fix on speed (Vref was 104) at the appropriate altitude, with the flaps and landing gear extended. The copilot completed the approach and landing checklist items but did not call out items because the PIC preferred that copilots complete checklists quietly. The PIC then stated that they would not circle-to-land due to the low ceiling. He added that a landing on runway 23 would be suitable because the wind was at a 90-degree angle to the runway, and there was no tailwind factor. Based on the reported weather, a tailwind component of approximately 2 knots existed at the time of the accident, and, in a subsequent statement to the Federal Aviation Administration, the pilot acknowledged there was a tailwind about 20 degrees behind the right wing. The copilot had the runway in sight about 200 feet above the minimum descent altitude, which was 440 feet above the runway. The copilot reported that he mentally prepared for a go around when the PIC stated that the airplane was high about 300 feet above the runway, but neither pilot called for one. The flight crew stated that the airplane touched down at 100 knots between the 1,000-foot marker and the runway intersection-about 1,200 feet beyond the approach end of the 4,305-foot-long runway. The speed brakes, thrust reversers, and brakes were applied immediately after the nose gear touched down and worked properly, but the airplane departed the end of the runway at about 40 knots. According to data extracted from the enhanced ground proximity warning system, the airplane touched down about 1,205 feet beyond the approach end of the 4,305-foot-long wet runway, at a groundspeed of 127 knots. Data from the airplane manufacturer indicated that, for the estimated landing weight, the airplane required a landing distance of approximately 2,290 feet on a dry runway, 3,550 feet on a wet runway, or 5,625 feet for a runway with 0.125 inch of standing water. The chart also contained a note that the published limiting maximum tailwind component for the airplane is 10 knots but that landings on precipitation-covered runways with any tailwind component are not recommended. The note also indicates that if a tailwind landing cannot be avoided, the above landing distance data should be multiplied by a factor that increases the wet runway landing distance to 3,798 feet, and the landing distance for .125 inch of standing water to 6,356 feet. All distances in the performance chart are based on flying a normal approach at Vref, assume a touchdown point 840 feet from the runway threshold in no wind conditions, and include distance from the threshold to touchdown. The PIC's statement about the airplane being high at 300 feet above the runway reportedly prompted the copilot to mentally prepare for a go around, but neither pilot called for one. However, the PIC asked the copilot what he thought, and his reply was " it's up to you." The pilots touched down at an excessive airspeed (23 knots above Vref), more than 1,200 feet down a wet 4,305-foot-long runway, leaving about 3,100 feet for the airplane to stop. According to manufacturer calculations, about 2,710 feet of ground roll would be required after the airplane touched down, assuming a touchdown speed at Vref; a longer ground roll would be required at higher touchdown speeds. Although a 2 knot crosswind component existed at the time of the accident, the airplane's excessive airspeed at touchdown (23 knots above Vref) had a much larger effect on the outcome of the landing.

Quoted verbatim from the NTSB record.

Other Cessna 550 accidents

Date Aircraft Location Operator Outcome Died
31 Aug 2010 Cessna 550
PA-TAA
Bugoiya, Papua New Guinea Trans Air PNG Fatal 4
14 Feb 2010 Cessna 550B
OK-ACH
Reinhardtsdorf-Schöna, Germany
no coordinates
Time Air Flight Fatal 2
4 Jan 2009 Cessna 550
N815MA
Wilmington, North Carolina, United States Caribair SA No injuries -
29 Mar 2009 Cessna 550
N44FR
Salt Lake City, Utah, United States Fritzi Jet LLC No injuries -
3 Nov 2011 Cessna 550
N938D
Key West, Florida, United States South Aviation No injuries -
5 Jun 2009 Cessna 550
N73HH
Sellersburg, Indiana, United States M & L Airways Inc No injuries -

All 63 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
13 Jun 2010 Dwight Lohr BABY ACE
N39D
Carolina Beach, North Carolina, United States - Serious injuries -
7 Mar 2010 Aeronca 7AC
N84694
Roanoke Rapids, North Carolina, United States - No injuries -
24 Jul 2010 Mulloy Charles ZODIAC 601XL
N601CX
Enochville, North Carolina, United States - Serious injuries -
17 Oct 2010 Bobo Christopher J LOEHLE 5151
N838B
Southern Pines, North Carolina, United States COX Keith A Serious injuries -
15 Mar 2010 Cessna T337G
N74E
Shelby, North Carolina, United States Delta Whiskey Bravo Inc No injuries -
31 Dec 2010 Cessna 172
N4383Q
Dublin, North Carolina, United States Bladen Aviation Inc No injuries -

All 170,864 records in United States