FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI06FA043 · Cirrus Design Corp. SR22

11 Dec 2005 · Arco, MN, United States

Cirrus Design Corp. SR22 · Accident: in flight encounter with weather en route

From Wayne Municipal Airport / Stan Morris Field (LCG) to Flying Cloud Airport (FCM)

Report a problem

Event

NTSB case
CHI06FA043
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
3 · 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. 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
N621PH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wayne Municipal Airport / Stan Morris Field (LCG), Wayne, NETo Flying Cloud Airport (FCM), Minneapolis, MN
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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › VFR flight into imc, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was destroyed when it impacted terrain following an in-flight loss of control. The night cross-country flight was conducted under visual flight rules (VFR) by a non-instrument rated private pilot. Air traffic control radar track data and associated surface weather observations indicated that the flight encountered deteriorating cloud ceilings along the route. The pilot obtained a pre-flight weather briefing, during which the briefer informed him of forecast and reported instrument flight rules (IFR) conditions along the proposed route of flight. Track data indicated that the flight proceeded approximately 65 nautical miles (nm) north of the course proposed in the pre-flight briefing. During the flight, the pilot contacted Minneapolis Air Route Traffic Control Center and requested flight following. The controller informed the pilot that radar contact could not be maintained in the area and at the altitude the airplane was operating. The controller suggested that the pilot climb to a higher altitude in order to permit radar service. The pilot replied, "I've got clouds above me" and stated that he would continue under VFR. The radar altitude returns decreased from 3,400 feet mean sea level (msl) to 2,100 feet msl during the final 65 nautical miles (nm) of the flight. The reported cloud ceiling 65 nm south of the accident site and along the flight path was 3,600 above ground level (agl) (5,000 feet msl). The reported ceiling 25 nm south of the site and along the flight path was 1,400 feet agl (3,100 msl). The reported ceiling 15 nm east of the site was 800 feet agl (2,000 feet msl). Radar track data indicated that the airplane entered a right turn from a northbound course at 2,100 feet msl. Final radar contact was approximately 60 seconds later and depicted the airplane on a westbound course at 2,800 feet msl. Elevation at the accident site was about 1,581 feet. The wreckage was contained within the immediate vicinity of the impact point and was oriented on a southerly heading. First responders noted that the snow cover was undisturbed except in the immediate vicinity of the airplane. A post accident inspection did not reveal any anomalies consistent with a pre-impact failure. The airplane's ground speed and calibrated airspeed were calculated from radar track and winds aloft data. During the climbing turn, within the final 60 seconds of available radar data, the airplane's calibrated airspeed decreased to 41 knots. The published stall speed for the airplane in level flight, with a flaps-up configuration, was 69 knots. The stall speed increased to 74 knots and 82 knots at bank angles of 30 degrees and 45 degrees, respectively.

Probable cause

The pilot's inadvertent cruise flight into instrument meteorological conditions, and his failure to maintain control of the aircraft after experiencing spatial disorientation. Factors associated with the accident are the pilot's improper planning/decision making, low ceilings, a dark night, and spatial disorientation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI06FA043
Event ID
20051216X01982
Case number
CHI06FA043
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, coordinates. 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: c43b1e6f54fe53ea5fa877a4280cdc8d0f5b171b020568203becd7f6477079ca; retrieved 2026-09-20T17:43:13.895Z.