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

Diamond Aircraft Ind INC DA 20-C1 accident near Bloomington, Illinois, June 30, 2010

On June 30, 2010 at about 8:43 pm local time, a Diamond Aircraft Ind INC DA 20-C1, registered N802CT, was substantially damaged in an accident during landing (flare/touchdown) near Bloomington, Illinois (Central Illinois Regional Arpt airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain adequate airspeed during landing, which resulted in a stall.

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

What the record shows

Date
June 30, 2010 · about 8:43 pm local time
Place
Bloomington, Illinois · Central Illinois Regional Arpt · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Diamond Aircraft Ind INC DA 20-C1
Registration
N802CT · no longer on the register · serial C0102
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that he was landing after a local flight. He stated that during the landing flare he “stalled the plane about 10 feet AGL [above ground level].” The airplane sustained substantial damage when the right wing tip contacted the ground. The pilot performed a go-around and the airplane's left wing contacted the runway during the go-around. The pilot’s accident report listed no pre-impact mechanical malfunctions with the airplane.

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. Aerodynamic stall/spin during landing (flare/touchdown) defining event
  2. Abnormal runway contact during landing (flare/touchdown)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 132 hours in all; 79 in this make and model; 4 in the last 90 days; 2 in the last 30 days; 94 as pilot in command
  • Last flight review: January 9, 2009
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection
  • Seats: 2
  • Landing gear: fixed
  • Engine: Cont Motor IO-240 SER (piston); 0 hours total

The flight

  • Departed from: BMI Bloomington IL at 7:50 pm
  • Destination: BMI Bloomington IL
  • Flight plan: VFR
  • Runway 11, 6,526 ft by 150 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 77°F (25°C), dew point 52°F (11°C)
  • Altimeter: 30.25 inHg
  • Observation at 8:56 pm from BMI

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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.

Other NTSB records under N802CT the same tail number, which may have belonged to a different aircraft at the time

2020-09-11WPR20CA305 · accident near Fillmore, UT · substantial damage · no injuries

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.