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

Cirrus Design Corp. SR22 accident near Arco, Minnesota, December 11, 2005

On December 11, 2005 at about 11:16 pm local time, a Cirrus Design Corp. SR22, registered N621PH, was destroyed in an accident near Arco, Minnesota (Marshall Muni-Ryan Field). It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

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

What the record shows

Date
December 11, 2005 · about 11:16 pm local time
Place
Arco, Minnesota · Marshall Muni-Ryan Field · map
Type
Accident
Injuries
3 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cirrus Design Corp. SR22
Registration
N621PH · no longer on the register · serial 1481
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

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.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 272 hours in all; 42 in this make and model; 37 in the last 90 days; 37 in the last 30 days; 180 as pilot in command; 0 on instruments
  • Last flight review: November 1, 2005
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 317 hours
  • Last inspection: annual inspection, June 1, 2005; 313.5 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-550-N (piston); 0 hours total

The flight

  • Departed from: LCG Wayne NE at 10:08 pm
  • Destination: FCM Minneapolis MN
  • Flight plan: none

Weather at the time

  • Light: night
  • Wind: from 100° at 7 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 800 ft; a few clouds at 400 ft
  • Temperature: 25°F (-4°C), dew point 21°F (-6°C)
  • Altimeter: 29.73 inHg
  • Observation at 11:15 pm from MML, 15 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers2

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.

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.