CEN13FA130 · Raytheon Aircraft Company 58
Bottorff Construction Raytheon Aircraft Company 58 · Accident: loss of control in flight en route
From North Platte Regional Airport Lee Bird Field (LBF) to York Municipal Airport (JYR)
Event
- NTSB case
- CEN13FA130
- 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
- Instrument Meteorological Cond
Raytheon Aircraft Company 58
- Aircraft type
- Beechcraft 58
- 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
- N36VE
- Operator
- Bottorff Construction
- Onboard fatalities
- Unknown
- Route
- From North Platte Regional Airport Lee Bird Field (LBF), North Platte, NETo York Municipal Airport (JYR), York, NE
- Aircraft age
- About 13 years (built 2000)
- 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 structures
- Environmental issues › Conditions/weather/phenomena
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 filed an instrument flight rules flight plan and, about an hour before departure, he obtained a weather briefing, which included an airmen's meteorological information (AIRMET) for the potential for moderate icing conditions and turbulence below 8,000 ft over the route of flight. About the time the airplane departed, weather conditions worsened with freezing fog, heavy snow fall, and reduced visibility. However, at that time, neither a significant meteorological information (SIGMET) nor a center weather advisory warning of severe icing conditions had been issued. After departure, an air traffic controller cleared the airplane to climb to 9,000 ft mean sea level (msl). When the airplane was about 7,000 ft msl and still climbing, the pilot asked the controller if there were any reports regarding the cloud tops, and the controller responded that there were not. Less than a minute later, radar data showed the airplane descending, and the pilot issued a "mayday" call. Radio and radar contact were then lost. The wreckage was found about 11 miles northeast of the airport. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.
Flight crewmembers of two flights inbound to the airport around the time of the accident reported that they encountered freezing rain and severe mixed icing; these conditions were beyond the airplane's icing certification standards and could have caused increased weight, degraded performance, and unpredictable aerodynamic characteristics. Federal Aviation Administration guidance warns that, when severe icing conditions are encountered, the pilot shall immediately request priority handling to facilitate a route or an altitude change to exit the icing conditions.
Based on the weather information, it is likely that the airplane encountered severe icing conditions about the time of the accident, which resulted in structural icing that exceeded the airplane's capabilities and resulted in a loss of control. Based on the wreckage distribution, which was consistent with a high-speed impact, and the low visibility present at the time of the accident, it is likely that, after the loss of airplane control, the pilot experienced spatial disorientation; however, there was insufficient evidence to determine the role that spatial disorientation might have played in the accident.
Probable cause
The pilot’s inadvertent encounter with severe icing conditions, which resulted in structural icing and the subsequent loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13FA130
- Event ID
- 20130111X25405
- Case number
- CEN13FA130
- 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. 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: 56bcb78efa85f3ece344c06181c068c467e3c2c0ae546b46ec23dacd3ff978b3; retrieved 2026-09-14T15:51:51.998Z.