SEA05FA023 · Cirrus Design Corp. SR22
Cirrus Design Corp. SR22 · Accident: in flight collision with object while maneuvering
From Bozeman Yellowstone International Airport (BZN) to an unrecorded destination
Event
- NTSB case
- SEA05FA023
- 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
- Visual 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
- N1159C
- Operator
- Brandon J. Speth · private individual
- Onboard fatalities
- Unknown
- Route
- From Bozeman Yellowstone International Airport (BZN), Belgrade, MTTo not recorded
- 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
- 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
- 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/clearance, not maintained
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, flown by a commercial pilot and carrying three passengers, departed in day visual meteorological conditions for a local flight over rugged mountainous terrain. The purpose of the flight was to meet up with a motor glider and make some "flybys" of the glider. The glider pilot was giving a ride to the airplane pilot's friend. The glider pilot reported that the airplane made two passes by the glider. When the airplane passed by the glider for the second time, it was "in coordinated flight," with the flaps up, and it was either flying level or descending slightly. At the time, the glider was at an altitude of about 8,900 feet and had a ground speed of about 57 knots. The glider pilot lost sight of the airplane as it proceeded north into a cirque or bowl formed by a mountain range (peak elevation about 9,600 feet) running north to south and a transverse range (peak elevation 8,916 feet) running west and then hooking south. The glider pilot and passenger did not witness the accident. However, the glider did enter the bowl about 90 seconds after the airplane had passed the glider. The glider pilot executed a left 180 degree turn in the bowl. During the turn, the glider was at altitudes of 9,100 to 9,200 feet and encountered an air mass that was sinking about 100 to 200 feet per minute. The surviving passenger, who was seated in the left rear seat, reported that as the airplane made the second pass on the glider, the stall warning indicator sounded. The pilot dropped the nose to level out, and the stall warning indicator stopped sounding. The passenger heard a high-pitched whine that sounded like a noise he had heard during the preflight check. He thought it was the sound of the flap motor, but when he looked out, he saw that the flaps were not moving. He could not see the pilot moving the flap control, and neither the pilot, nor the other passengers made any comments about the flaps. The pilot then initiated a descending left turn. During this turn, the pilot looked over his shoulder and, in a normal tone of voice, said, "hang on, we might get a couple of trees on this one." It was about 10 to 15 seconds from the time the stall warning horn stopped sounding until they hit the trees. Distribution of the wreckage at the accident site indicated the airplane impacted trees on the transverse ridge at an elevation of 8,553 feet on a southwesterly heading and traveled about 360 feet before coming to rest. Examination of the airframe and engine revealed no evidence of any discrepancies that would have prevented normal operation of the airplane. The flaps were found in the retracted position. Functional testing of the flaps was precluded by impact and fire damage. The pilot who flew the airplane just prior to the accident flight stated that she experienced no problems with the airplane and that the flaps worked normally during her flight. When interviewed 11 days after the accident, the surviving passenger reported that there were no problems with the airplane during the runup or takeoff. About 8 weeks after the accident, he told his attorney that he recalled that the pilot mentioned before takeoff that the flaps were not working.
Probable cause
The pilot's failure to maintain altitude/clearance while maneuvering in mountainous terrain, which resulted in an inflight collision with trees and terrain. Contributing factors were the mountainous terrain and the downdraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05FA023
- Event ID
- 20041209X01964
- Case number
- SEA05FA023
- 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: 810a7aededdc9100bbdd67afa7c9ad838fc36773b557bba6d5daa3df429cda5a; retrieved 2026-09-20T18:11:15.063Z.