CHI01LA318 · Cirrus Design Corp. SR-20
Cirrus Design Corp. SR-20 · Accident: loss of engine power en route
From Crystal Airport (MIC) to Rapid City Regional Airport (RAP)
Event
- NTSB case
- CHI01LA318
- 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
- 0 · 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 Design Corp. SR-20
- Aircraft type
- Cirrus SR-20
- 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
- N747TW
- Operator
- Kenneth Klein
- Onboard fatalities
- Unknown
- Route
- From Crystal Airport (MIC), Minneapolis, MNTo Rapid City Regional Airport (RAP), Rapid City, SD
- Aircraft age
- Not recorded
- 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
- En route · cruise
- First occurrenceThe 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
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Other maintenance personnel › Maintenance, inspection, inadequate
- Other maintenance personnel › Maintenance, service of aircraft/equipment, improper
- Unsuitable terrain or takeoff/landing/taxi area › Encountered
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that 3-5 minutes after leveling off at 3,000 feet, a red oil light appeared on the instrument panel. The pilot said he looked over at the oil pressure gauge. It read zero pressure. The pilot said that the engine started missing. He contacted departure control and informed them he had an emergency with no oil pressure. The pilot said, "Departure asked if I wanted [the] ILS for Flying Cloud [Airport], which was 12-13 mile[s] away." The pilot said it was too far and decided to go for Waconia. The pilot said he set up for best glide airspeed and informed departure that he was still in the weather. The pilot said that at 2,000 feet, he noticed smoke begin to appear from the cowling. The pilot said he broke out of the clouds approximately 800 feet agl. The pilot said he set the airplane down in a cornfield, slid approximately 70 feet, and came to a stop. An examination of the airplane's engine revealed 3 punctures in the top of the crankcase at cylinder numbers 1, 2, and 4. A 2-inch diameter piece of the crankcase rested on top of the engine. The oil drain plug was absent. The threads at the oil drain port showed no damage or evidence of safety wiring. The oil dip stick and oil filter showed heat damage. A film of oil was observed on the firewall. There was no evidence of oil in the engine. No other anomalies were found. A mechanic for the airplane's owner said that he started an oil change on the airplane a week before the accident. The mechanic said that while performing the oil change he noticed damage to the airplane's nose gear. The mechanic said he abandoned the oil change. He said at that time he didn't have safety wire or a new crush washer for the drain plug. He left the airplane in that condition. He said it was the last time he saw the airplane. A second mechanic said that the day before the accident he and his partner repaired the nose gear and completed the work on the airplane. The mechanic said, "I vividly remember checking the safety on the oil filter. I cannot remember the condition of the oil drain plug. We cowled the powerplant and conducted a leak check." The mechanic said that the pilot ran the engine for approximately 1 minute. It was then inspected for leaks. No leaks were found. The POH narrative for Forced Landings states, "For forced landings on unprepared surfaces, use full flaps if possible." No reference to flap position is cited in the checklist steps. The flaps were up at the accident site.
Probable cause
Improper servicing of the airplane by other maintenance personnel, inadequate inspection of the airplane by the other maintenance personnel prior to the airplane's flight, and the unsuitable terrain encountered during the forced landing. Factors relating to the accident were the oil exhaustion, the low ceiling providing the pilot little time to select a field once the airplane was beneath the clouds, the pilot not following proper emergency procedures requiring use of full flaps for the forced landing, and the corn crop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA318
- Event ID
- 20010921X01977
- Case number
- CHI01LA318
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 1125365d98c1dc0bcd3454529a75820f4c791f8316c651e5ed678450b0e243fd; retrieved 2026-09-21T09:49:16.831Z.