WPR22FA256 · Cessna T337G
Bluebird Aviation Cessna T337G · Accident: loss of control in flight en route
From Rocky Mountain Metropolitan Airport (BJC) to an unrecorded destination
Event
- NTSB case
- WPR22FA256
- 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
- 4 · 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
Cessna T337G
- Aircraft type
- Cessna 337
- 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
- N337KN
- Operator
- Bluebird Aviation
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), Broomfield, COTo not recorded
- Aircraft age
- About 50 years (built 1972)
- 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 · climb to cruise
- Defining eventThe 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 control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot and passengers departed on a local sightseeing flight in the twin-engine, centerline-thrust airplane. ADS-B data showed the airplane depart toward mountainous terrain in the general direction of the planned tour route. The airplane’s climb rate appeared appropriate and consistent with normal operation until the airplane leveled off about 11 minutes later, at an altitude about 9,500 ft mean sea level (msl) about 3,000 ft below a typical cruise altitude for that flight. A short time later, the airplane slowed and entered a left descending turn, reaching a descent rate of almost 6,000 ft per minute (fpm). Witnesses near the accident site reported observing the airplane flying low overhead. The right wing rose abruptly, dropped, and the left wing rose as the airplane entered a nose-down attitude and began to “corkscrew.” One witness stated that the engine noise stopped as the airplane entered the descent. The witness also stated that, up until that point, the engine(s) sounded like they were “struggling.” The airplane impacted wooded terrain about 7,800 ft msl and came to rest upright. The ground scars, impact signatures observed on the trees, and wreckage signatures indicated that the airplane impacted terrain in a nose-low attitude, consistent with a spin. A post-impact fire consumed most of the airframe. Both the front and rear engines sustained extensive thermal and impact damage, and the propeller for the rear engine was found in the feathered position. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation; however, the scope of the examination was limited due to the extensive thermal and impact damage, and a mechanical issue could not be ruled out. The feathered position of the rear engine’s propeller suggests that it is likely that the engine had lost power or been shut down; however, the reason could not be determined based on the available information. It is possible that the pilot was attempting to return to the airport when the accident occurred. Given the high density altitude conditions present at the time of the accident, the airplane’s single-engine climb performance would have been marginal. Additionally, although the pilot’s logbook was not available for review, he was recently hired by the accident operator and had accumulated about 3.5 total hours in the accident airplane since he was hired. According to the operator, the pilot’s training in the accident airplane did not include an engine shutdown; instead, a loss of engine power was simulated by reducing the throttle. The circumstances of the accident are consistent with the pilot’s exceedance of the airplane’s critical angle of attack while maneuvering with one engine inoperative, which resulted in an aerodynamic stall/spin and loss of control. Due to the extensive thermal and impact damage, the investigation was not able to determine why the rear engine was not operating.
Probable cause
The pilot’s exceedance of the airplane’s critical angle of attack while maneuvering with one engine inoperative, which resulted in an aerodynamic stall/spin and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22FA256
- Event ID
- 20220717105490
- Case number
- WPR22FA256
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: f463b827845fddf4b480015f1e86754f0ee1ffe34f98a2f59ee901e1649d4682; retrieved 2026-09-15T07:47:30.555Z.