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

Cirrus SR22 accident near Cloquet, Minnesota, July 30, 2019

On July 30, 2019 at about 2:55 pm local time, a 2003 Cirrus SR22, registered N353KT, was substantially damaged in an accident during landing near Cloquet, Minnesota (Cloquet Carlton County airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's improper landing flare, which resulted in a bounced landing.

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

What the record shows

Date
July 30, 2019 · about 2:55 pm local time
Place
Cloquet, Minnesota · Cloquet Carlton County · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cirrus SR22 Undesignat, built 2003 · all SR22s on the register
Registration
N353KT · no longer on the register · serial 0486
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, while landing, the airplane bounced twice on touchdown. During the second bounce, the nose landing gear collapsed, and the airplane then impacted the runway. The airplane sustained substantial damage to the engine mount and firewall. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

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. Abnormal runway contact during landing defining event
  2. Landing gear collapse during landing

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 421 hours in all; 13 in this make and model; 13 in the last 90 days; 3.5 in the last 30 days; 421 as pilot in command
  • Last flight review: July 12, 2019
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,804.9 hours
  • Last inspection: 100-hour inspection, July 8, 2019
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-550-N7 (piston); 1,805 hours total
  • Operator: Duluth Flying Club

The flight

  • Departed from: DLH Duluth MN at 2:15 pm
  • Destination: DLH Duluth MN
  • Flight plan: none
  • Runway 35, 4,002 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 310° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 46°F (8°C)
  • Altimeter: 30.14 inHg
  • Observation at 2:55 pm from KCOQ

Injuries

FatalSeriousMinorNone
Flight crew1

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

3 documents, released by the NTSB on October 3, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

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.