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

Cirrus Design Corp. SR22 accident near Statesville, North Carolina, October 27, 2006

On October 27, 2006 at about 4:16 pm local time, a Cirrus Design Corp. SR22, registered N969ES, was substantially damaged in an accident near Statesville, North Carolina (Statesville Regional Airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed and 2 people were seriously injured. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain airspeed while maneuvering with a low ceiling in instrument flight conditions, resulting in an inadvertent stall, and collision with trees and the ground. Factors in the accident were the pilot's failure to follow the published missed approach procedures, and the airplane's checklist procedures for a balked landing.

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

What the record shows

Date
October 27, 2006 · about 4:16 pm local time
Place
Statesville, North Carolina · Statesville Regional Airport · map
Type
Accident
Injuries
2 people were killed and 2 people were seriously injured.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cirrus Design Corp. SR22
Registration
N969ES · no longer on the register · serial IO-550-N (7)
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot filed an instrument flight rules (IFR) flight plan and obtained an abbreviated weather briefing for a flight from North Palm Beach, Florida, to a visual flight rules (VFR) airport at Mooresville, North Carolina, with a 1200 arrival. The forecast for the destination airport was: overcast ceiling at 1,000 feet, visibility 5 miles, with light rain and mist. The closest terminal aerodrome forecast to the pilot's destination airport was Charlotte/Douglas International Airport, approximately 30 miles south of the accident site. The forecast at 1026 was: overcast ceiling at 400 feet, visibility 2 miles, in moderate rain and mist. The forecast at 1131 was: overcast ceiling at 400 feet, visibility 1 1/2 miles, in light rain and mist. Between 1200 to 1600 the ceiling was forecast for 700 feet and 2 miles visibility. The pilot did not obtain any weather updates while en-route. Upon arrival in the Charlotte area, the controller cleared the pilot to start his descent. The pilot asked the controller for the weather at his destination airport. The controller informed the pilot the weather was IFR. The pilot requested and received clearance to divert to Statesville Regional Airport. The pilot was vectored and subsequently cleared for the ILS Runway 28 approach at Statesville. The pilot stated he flew the approach with the autopilot on, and completed the before landing check, lowered the flaps to 50 percent and ultimately 100 percent. He stated he did not remember descending below the clouds, or any events associated with the accident. Witnesses observed the airplane come out of the clouds over the runway. An increase in engine power was heard, the airplane was observed to start a right turn and entered the clouds. The pilot initiated a circling approach without ATC clearance and without the required weather minima for a circling approach. Witnesses heard the airplane north of the airport in the clouds, and observed the airplane a short time later below the clouds on the south side of runway 28, traveling from southeast to northwest. The airplane crossed the runway, entered the clouds, came out of the clouds, and was observed making a steep turn to the right and back to the left. The nose of the airplane then pitched down, and the airplane collided with trees and the ground. The checklist for a balked landing requires the pilot to set the flaps at 50 percent, airspeed between 75 to 85 KIAS until clear of obstacles, and then raise the flaps to 0 percent. The flaps at the crash site were extended 100 percent.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 717 hours in all; 501 in this make and model; 28 in the last 90 days; 14 in the last 30 days; 520 as pilot in command
  • Last flight review: June 1, 2005
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 598.3 hours
  • Last inspection: annual inspection, July 1, 2006; 20.9 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-550-N (7) (piston); 0 hours total

The flight

  • Departed from: F45 West Palm Beach FL at 1:00 pm
  • Destination: 14A Mooresville NC
  • Flight plan: IFR
  • Runway 28, 7,005 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 040° at 3 knots
  • Visibility: 1.5 statute miles
  • Sky: overcast at 300 ft
  • Temperature: 46°F (8°C), dew point 46°F (8°C)
  • Altimeter: 29.98 inHg
  • Observation at 4:21 pm from KSVH

Injuries

FatalSeriousMinorNone
Crew1
Passengers21

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.