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

Cessna 550 accident near Manteo, North Carolina, October 1, 2010

On October 1, 2010 at about 12:30 pm local time, a Cessna 550, registered N262Y, was substantially damaged in an accident during landing near Manteo, North Carolina (Dare County Regional airport). It was an executive or corporate flight under general aviation rules (Part 91). 7 people had minor injuries. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

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

What the record shows

Date
October 1, 2010 · about 12:30 pm local time
Place
Manteo, North Carolina · Dare County Regional · map
Type
Accident
Injuries
7 people had minor injuries.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cessna 550 CITATION I · all 550s on the register
Registration
N262Y · no longer on the register · serial 550-0291
Damage
Substantial damage
Flight
Executive or corporate flight · general aviation rules (Part 91)

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

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.

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. Landing area overshoot during landing defining event
  2. Runway excursion during landing
  3. Collision during takeoff/land during landing

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 Personnel issues › Action/decision › Action › Lack of action › Copilot
  • Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Wet › Decision related to condition
  • factor Personnel issues › Task performance › Communication (personnel) › CRM/MRM techniques › Flight crew

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
  • Flight time: 9,527 hours in all; 2,025 in this make and model; 30 in the last 90 days; 18 in the last 30 days; 9,400 as pilot in command; 50 on instruments
  • Last flight review: August 7, 2010
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: flight instructor, commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 3,193 hours in all; 150 in this make and model; 57 in the last 90 days; 25 in the last 30 days; 2,673 as pilot in command; 1,552 on instruments
  • Last flight review: September 4, 2010
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 9,643 hours
  • Last inspection: condition inspection, August 16, 2010; 279 hours since
  • Maximum gross weight: 14,700 lb
  • Seats: 8
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney JT15D-4 (turbojet); 0 hours total
  • Engine 2: Pratt & Whitney JT15D-4 (turbojet); 0 hours total
  • Operator: Colnan Inc.

The flight

  • Departed from: TPA Tampa FL at 10:29 am
  • Destination: MQI Manteo NC
  • Flight plan: IFR
  • Runway 23, 4,305 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 350° at 4 knots
  • Visibility: 2 statute miles
  • Sky: broken clouds at 400 ft
  • Temperature: 72°F (22°C), dew point 70°F (21°C)
  • Altimeter: 29.62 inHg
  • Observation at 12:43 pm from MQI

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers5

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.