FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12FA040 · Cessna T337 G

18 Nov 2011 · Casper, WY, United States

Cessna T337 G · Accident: loss of control in flight on approach

From Rawlins Municipal Airport/Harvey Field (RWL) to Casper-Natrona County International Airport (CPR)

Report a problem

Event

NTSB case
WPR12FA040
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
1 · 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

Cessna T337 G

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
N357
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rawlins Municipal Airport/Harvey Field (RWL), Rawlins Airport, WYTo Casper-Natrona County International Airport (CPR), Casper, WY
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
Approach · IFR missed approach
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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot received two predeparture weather briefings, both of which reported that snow showers were expected over most of the state. During the second briefing, the pilot was advised that adverse weather conditions, including mountain obscuration, moderate icing, moderate turbulence, and low-level wind shear, existed throughout the planned route of flight. The pilot still decided to depart. As the airplane neared its destination, the approach controller issued the pilot vectors to the final instrument landing system approach course. The approach controller subsequently saw that the airplane was at 6,900 feet mean sea level (msl), which was 300 feet below the minimum vectoring altitude for the approach (7,200 feet msl). The approach controller issued the pilot a low altitude alert, and the pilot climbed the airplane back to the minimum vectoring altitude of 7,200 feet msl. About 1 minute after the approach controller transferred control of the flight over to the tower air traffic controller, the controller saw that the airplane was about 1/4 mile right of the inbound approach course. The controller then issued the pilot missed approach instructions, advising him to fly the runway heading and to climb and maintain 8,000 feet msl. The tower controller then transferred the pilot back to the approach controller, who advised the pilot that the runway visual range had decreased below that required for the approach. The pilot then elected to be vectored back to the final approach course to hold on the localizer until the weather improved.

While he was issuing the pilot vectors to the localizer, the approach controller observed the airplane flying an inappropriate heading. After he advised the pilot of the irregularity, the approach controller issued a revised heading toward the localizer. The approach controller observed the airplane begin the right turn toward the assigned heading, and shortly thereafter, observed that the airplane was 1,200 feet below its assigned altitude. The approach controller issued the pilot another low altitude alert. There were no further radio communications with the pilot. The airplane impacted terrain about 8 nautical miles northeast of the airport, slightly left of the missed approach course, in a left-wing-low, steep nose-down attitude.

About 2 minutes before the accident, the destination airport reported 1/2-mile visibility in moderate snow and freezing fog, with scattered clouds at 800 feet above ground level (agl) and an overcast cloud layer at 1,300 feet agl. Postaccident review of the weather conditions in the area at the time of the accident indicated that the pilot was operating in instrument meteorological conditions and that conditions were favorable for structural icing at a moderate to severe level. Postaccident examination revealed no evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation. Based on the weather conditions that the pilot encountered while maneuvering near the destination airport, it is likely that the pilot failed to maintain adequate airspeed due to structural icing, which resulted in a loss of airplane control and subsequent impact with terrain.

Probable cause

The pilot's failure to maintain airspeed and airplane control while maneuvering in low visibility and icing conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12FA040
Event ID
20111118X00713
Case number
WPR12FA040
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. 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: d121ee017e5857dce6dbb4d1878a4c389053ec15259c078532399e5a0217c80b; retrieved 2026-09-13T21:59:37.339Z.