FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20LA367 · Cirrus SR22

29 Aug 2020 · Lawrenceville, IL, United States

Cirrus SR22 · Accident: controlled flight into terrain/object (CFIT) on approach

From Sullivan County Airport (SIV) to Lawrenceville Vincennes International Airport (LWV)

Report a problem

Event

NTSB case
CEN20LA367
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cirrus SR22

Aircraft type
Cirrus SR22
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N607SR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sullivan County Airport (SIV), Sullivan, INTo Lawrenceville Vincennes International Airport (LWV), Lawrenceville, IL
Aircraft age
About 13 years (built 2007)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · IFR final approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The instrument-rated pilot was conducting a night instrument approach to an airport 22 nautical miles south from his departure airport in instrument meteorological conditions. Shortly after departure, the pilot established communications with air traffic control and was instructed to maintain 2,600 ft and fly direct to the initial approach fix for the GPS approach. Air traffic data revealed the airplane flew past the initial approach fix before turning south then remained west of the final approach course while inbound on the approach. For the last 2 minutes of the flight, the airplane descended from 2,200 ft to 600 ft at an average rate of 800 ft per minute and an average groundspeed of 116 knots. The airplane impacted trees and terrain about 1.5 miles north of the runway threshold at the destination airport and was destroyed by impact and postimpact fire.

Examination of the accident site revealed multiple tree impacts north of where the main wreckage came to rest. The impact signatures observed on the trees and the wreckage fragmentation pattern were consistent with the airplane having a slight nose-down, near-level attitude with high forward velocity at impact. Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.

Toxicological testing detected carboxyhemoglobin in the pilot’s blood at 11%; however, soot was detected in the pilot’s throat during autopsy, indicating the source of the carboxyhemoglobin was likely from the postimpact fire.

The pilot had purchased the airplane about 2 months before the accident and had completed the Cirrus Embark training program, which included ground and flight instruction. The pilot had logged about 46 flight hours, including 9.1 night hours, 1.8 hours in actual instrument conditions, and 7 instrument approaches prior to the day of the accident. The day before the accident, the airplane’s GPS/NAV/COM system was changed from a Garmin system to a new Avidyne system. Based on available information, the accident approach was the pilot’s second instrument approach flown with the new system.

Based on the wreckage distribution and the low visibility present at the time of the accident, it is likely that the airplane impacted trees and terrain as a result of the pilot’s controlled flight into terrain due to the improper execution of the instrument approach. The pilot’s lack of familiarity with a new avionics system likely contributed to his inability to maintain approach parameters in night instrument meteorological conditions.

Probable cause

The pilot’s controlled flight into terrain as a result of his failure to properly execute an instrument approach and maintain clearance from trees in night instrument meteorological conditions. Contributing to the accident was the pilot’s unfamiliarity with a newly installed avionics system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20LA367
Event ID
20200829X95443
Case number
CEN20LA367
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a87d7402ad296f6a019710aa37b4cfc48d6b4721a5c7620f2a8310b4d514ab1d; retrieved 2026-09-15T07:18:54.377Z.