FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03FA057 · Cirrus Design Corp. SR-22

18 Jan 2003 · Hill City, MN, United States

Cirrus Design Corp. SR-22 · Accident: in flight collision with object while maneuvering

From Grand Rapids Itasca Co-Gordon Newstrom field (GPZ) to Saint Cloud Regional Airport (STC)

Report a problem

Event

NTSB case
CHI03FA057
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
2 · 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
Visual Meteorological Cond

Cirrus Design Corp. SR-22

Aircraft type
Cirrus SR-22
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
N9523P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Grand Rapids Itasca Co-Gordon Newstrom field (GPZ), Grand Rapids, MNTo Saint Cloud Regional Airport (STC), St Cloud, 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
Maneuvering · turn to reverse direction
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 collision with object
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); Tree(s)
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 › Altitude, not maintained
  • Pilot in command › Spatial disorientation

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

NTSB narrative

The Cirrus SR-22 aircraft was destroyed upon impact with trees and terrain following a loss of altitude during a turn. The accident site was located in relatively level, wooded terrain. The surrounding area was sparsely populated and heavily wooded. The accident occurred prior to civil twilight and marginal VFR weather conditions were reported at the departure airport. FAA radar data depicted an aircraft proceeding from the departure airport to the south, roughly paralleling a two-lane roadway. The aircraft initially leveled at 2,500 feet pressure altitude. The altitude gradually increased to 3,200 feet. Shortly afterward, the aircraft entered a descending left turn to reach a minimum altitude of 2,400 feet. This resulted in an average descent rate of 2,000 fpm. The aircraft immediately began a climb, as the radius of the left turn decreased noticably. Final radar contact was at 2,900 feet pressure altitude, 0.21 nautical miles, on a course of 278 degrees magnetic to the accident site. The rate of climb averaged 2,500 fpm between the final two radar data points. Several witnesses reported seeing an aircraft flying southbound shortly before the time of the accident. They reported the aircraft was relatively low and was traveling at a high rate of speed. None of the witnesses reported noticing any problems with the aircraft or engine. Witness reports of the weather conditions varied from mostly cloudy to clear, depending on their location. Impact angle was approximately 15 degrees nose down, based on observed tree strikes. The debris path was approximately 500 feet long and the aircraft was highly fragmented. A post accident examination of the aircraft and engine did not reveal any anomalies. The aircraft had logged 35.7 hours since new. The pilot held a private pilot certificate, with a single-engine land rating. He had logged 248.0 hours total time, including 57.0 hours of instrument time and 18.9 hours of night flight time. The pilot was the owner of the aircraft and had taken delivery nearly six weeks prior to the accident. He had completed a flight training program specific to the SR-22 aircraft. This resulted in a VFR-only completion certificate and a high-performance aircraft endorsement. The pilot had logged a total of 19.0 hours in the SR-22. This included 0.3 hour of actual instrument time and 2.3 hours of night flight time. The remaining flight time logged, with the exception of 1.0 hour, was in a Cessna 172 aircraft.

Probable cause

Spatial disorientation experienced by the pilot, due to a lack of visual references, and a failure to maintain altitude. Contributing factors were the pilot's improper decision to attempt flight into marginal VFR conditions, his inadvertent flight into instrument meteorological conditions, the low lighting condition (night) and the trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03FA057
Event ID
20030122X00087
Case number
CHI03FA057
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: d305600a487286bcec1063adf8dbcb7b667afc6415930c9be99b860215e5491b; retrieved 2026-09-20T19:31:28.402Z.